1:1 Operating System Pack

Prepared for: New Product Lead, 5 direct reports (3 PMs, 1 Designer, 1 Data Analyst) Date: 2026-03-17

Step 1: Intake + Context Snapshot

Context

• Role: New product lead (recently transitioned into this leadership role)
• Team composition: 5 direct reports across two functions
  • PM-1 (Senior, PST) -- stable, low-maintenance
  • PM-2 (Senior, EST) -- stable, low-maintenance
  • PM-3 (Mid-level, EST) -- struggling with prioritization
  • Designer-1 (Mid-level, PST) -- passed over for promotion, morale risk
  • Data Analyst-1 (Junior, EST) -- new hire, week 3 of onboarding
• Working model: Remote/hybrid across PST and EST (3-hour overlap window)
• Calendar utilization: 85% -- meeting reduction is a hard constraint
• Current state: No established 1:1 system yet (new manager); risk of defaulting to status updates

Goals for the 1:1 system

1. Build trust and rapport with all five reports quickly (new manager relationship)
2. Accelerate onboarding for the new hire (Data Analyst-1)
3. Unblock PM-3's prioritization struggles through coaching, not directive management
4. Retain Designer-1 and rebuild their motivation after the promotion miss
5. Maintain strong relationships with senior PMs without over-scheduling
6. Keep total 1:1 time budget under 3.5 hours/week given 85% calendar utilization

Assumptions (labeled)

• [A1] Tools: Google Docs for shared 1:1 docs, Slack for async, existing project management tool (Jira/Linear) for status tracking
• [A2] No HR/PII policy constraints beyond standard confidentiality
• [A3] No skip-levels needed at this stage (you are not a manager of managers)
• [A4] The team has existing async status rituals (standups, written updates) or these can be established
• [A5] PST-EST overlap window is roughly 9:00 AM -- 12:00 PM PST / 12:00 PM -- 3:00 PM EST

Boundary check

• The prioritization struggles (PM-3) will be addressed through coaching questions and agenda framing, not through a performance improvement plan. If issues persist beyond 4 weeks, escalate to your manager and HR.
• The promotion miss (Designer-1) requires a career conversation and emotional acknowledgment, not HR intervention. If Designer-1 shows signs of disengagement or attrition risk beyond what career conversations can address, involve HR and your manager.

Step 2: Purpose of 1:1s + "What Goes Where" Map

Purpose statement

1:1s on this team exist for coaching, career development, feedback, relationship building, and unblocking sensitive issues. They are NOT for project status updates, cross-functional coordination, or broad announcements. Status lives in async and team rituals. 1:1s are the one meeting where the report's agenda comes first.

"What goes where" map

Anti-pattern guard

Before each 1:1, both parties should ask: "Could this be a Slack message or a team sync topic?" If yes, move it out. The shared doc's agenda section enforces this by requiring topics to be added in advance.

Step 3: Tiered Cadence + Meeting Types Plan

Design rationale

At 85% calendar utilization, a one-size-fits-all weekly cadence for 5 reports would consume 2.5-5 hours/week -- unsustainable. Instead, this plan uses a tiered cadence based on relationship stage and need, combined with a barbell approach (high-quality relationship catch-ups + fast-path urgent meetings).

Cadence plan

Weekly time budget

This is well within the 3.5-hour budget and represents a significant reduction from a blanket 5x weekly approach.

Barbell approach

Relationship catch-ups (monthly, per person)

• One 1:1 per month per report is a "no-laptop walk/coffee" session focused purely on relationship building, energy, and career themes -- not task work.
• For remote team members: a video call with no screen-sharing; cameras on; informal tone.
• Scheduling: replace the standing 1:1 slot that week (not additive).

Urgent topical meetings (on-demand)

• Any report (or you) can request a 15-30 min topical meeting within 24 hours via Slack DM with a one-line description: "Need 20 min to decide X by Friday."
• These do NOT replace standing 1:1s; they handle time-sensitive issues that cannot wait.
• SLA: respond to the request within 4 hours; schedule within 24 hours.

Time zone scheduling

All slots fall within the 9 AM - 12 PM PST overlap window. Mondays are biweekly-only, keeping them lighter.

Cadence review triggers

Re-evaluate a report's tier when:

• A new hire completes onboarding (typically week 6-8)
• A coaching goal is met (PM-3 demonstrates independent prioritization for 2 consecutive weeks)
• A career action plan is established and the report feels re-engaged (Designer-1)
• A senior report signals they want more support (promote to Tier 1 temporarily)
• A crisis, reorg, or major change event occurs (increase cadence for affected reports)

Step 4: Shared 1:1 Doc Template

Create one Google Doc per report with this structure. Both parties have edit access. Title format: 1:1: [Manager Name] <> [Report Name] -- [Quarter]

1:1 Doc: [Manager Name] <> [Report Name]

Working agreements

• Default cadence + duration: [Per cadence plan above]
• Pre-work: Both add agenda items by end of day before the meeting. If neither has items, the meeting converts to a 10-min check-in or is canceled (report decides).
• Action item tracking: Action items are logged in the table below with owner and due date. Carried forward until complete.
• Shared vs. private: Everything in this doc is shared. Manager keeps no private notes about the report. If a sensitive topic arises (personal, HR-adjacent), the report can request it stay verbal-only.
• Cancellation policy: Either party can cancel with 4+ hours notice if no agenda items. Tier 1 reports: reschedule within the same week rather than skipping entirely.

Running topics backlog

Park topics here that are important but not urgent. Pull into the weekly agenda when ready.

This week's agenda (fill before meeting)

Report's topics (these go first):

• ...

Manager's topics:

• ...

Standing check-in (pick 1-2 per meeting; rotate):

• Energy/joy: "How's your energy this week? (1-10)"
• Coaching: "What's the hardest thing right now?"
• Feedback: "What should I do more/less of?"

Notes (during meeting)

Date: YYYY-MM-DD

• ...

Decisions (if any)

Action items

Doc conventions

1. Reverse-chronological: Newest meeting notes go at the top (below the working agreements and backlog sections).
2. Tagging: Use [ACTION], [DECISION], [FOLLOW-UP] inline tags for easy scanning.
3. Quarterly rollover: At the start of each quarter, archive the previous quarter's notes into a separate doc or section, keeping the backlog and working agreements in the active doc.

Step 5: Coaching Toolkit

The default: Coach first, advise second

The rule: When a report brings a problem, your default mode is coaching -- asking questions that help them generate options, evaluate tradeoffs, and make their own decision. Switch to advisor/directive mode only when the exceptions below apply.

Why this matters: You have 5 reports. If you become the decision-maker for every problem, you become the bottleneck. Coaching builds independent problem solvers and scales your leadership.

Coaching conversation script (5-10 minutes)

Use this sequence when a report brings a problem:

1. Outcome: "What outcome do you want here?"
2. Options: "What options have you considered so far?"
3. Tradeoffs: "What are the tradeoffs? What's the riskiest assumption?"
4. Independence test: "If I wasn't available, what would you do?"
5. Smallest step: "What's the smallest next step you can take this week?"
6. Commitment: "What will you do, by when? How should we check in on it?"

Manager self-check: If you catch yourself talking for more than 2 minutes straight, stop and ask a question instead.

Coaching question bank (organized by situation type)

Situation: Prioritization struggles (PM-3)

• "Walk me through how you decided what to work on this week."
• "If you could only ship one thing this month, what would it be and why?"
• "What are you saying no to? What should you be saying no to?"
• "What would happen if you dropped the bottom two items on your list?"
• "What's the cost of delay for each of these items? Which has the highest?"
• "Who else is affected by this prioritization? Have you aligned with them?"
• "What data would help you decide between X and Y?"

Situation: New hire onboarding (Data Analyst-1)

• "What's been the most confusing thing so far?"
• "Who have you met that's been most helpful? Who should you meet next?"
• "What's one thing you wish someone had told you in your first week?"
• "Do you have everything you need to do your first project? What's missing?"
• "What questions are you afraid to ask in a group setting?"
• "How do you learn best -- pairing, docs, trial and error? How can I support that?"
• "What does success in this role look like to you at the 30/60/90 day mark?"

Situation: Passed over for promotion / morale recovery (Designer-1)

• "How are you feeling about the promotion decision? I want to hear your honest reaction."
• "What feedback did you receive? What parts resonated and what felt unfair?"
• "What would need to be true for you to feel ready for the next cycle?"
• "What kind of work would re-energize you right now?"
• "Is there a skill gap you want to close, or is this more about visibility and scope?"
• "What does your ideal next 6 months look like here?"
• "What would make you feel like your contributions are recognized, even without the title change?"

Situation: Senior / independent reports (PM-1, PM-2)

• "What's the most strategic thing on your plate right now?"
• "Where are you spending time that feels low-value? Can we change that?"
• "What decision are you wrestling with that I could be a sounding board on?"
• "What's one thing I could do to make your work easier?"
• "Is there a leadership or mentorship opportunity you'd like to take on?"
• "What's happening in the org that I should know about but might not?"

Situation: Giving feedback

• "I observed [specific behavior] in [context]. The impact was [impact]. My request is [specific change]."
• "What's your read on how [project/meeting] went?"
• "If you were coaching someone in your role, what feedback would you give them?"
• "Here's something I think you did really well -- [specific]. What made you approach it that way?"

Situation: Receiving feedback (from your report)

• "What should I do more of as your manager?"
• "What should I do less of?"
• "When have I been least helpful to you? What would you have preferred?"
• "On a scale of 1-10, how psychologically safe do you feel giving me honest feedback? What would move it up one point?"

Situation: Energy and wellbeing

• "How's your energy this week on a 1-10 scale?"
• "What gave you energy or joy this week? What drained it?"
• "Is there anything about your workload that feels unsustainable right now?"
• "What's one small thing we could change this week to help your recovery?"

When to be directive (advisor mode exceptions)

Switch from coaching to direct guidance when:

1. Safety or ethical issue: Someone's wellbeing or the company's integrity is at risk.
2. Legal/HR policy: The situation requires adherence to specific policy (e.g., data handling, compliance).
3. Time-critical incident: A production issue, customer escalation, or deadline where there is no time for discovery.
4. Repeated pattern after coaching: You have coached on this issue 3+ times and the report has not changed behavior despite clear expectations.
5. New hire lacks context: The report does not yet have enough organizational context to reason through the problem (applies to Data Analyst-1 in weeks 1-4; transition to coaching as they ramp).

Coach vs. advisor decision tree

Report brings a problem
    |
    v
Is it a safety/legal/ethical/time-critical issue?
    |-- YES --> Directive mode: Give the answer, explain why, follow up
    |-- NO  --> Continue
    |
Has this been coached 3+ times without change?
    |-- YES --> Directive mode + set explicit expectations + timeline
    |-- NO  --> Continue
    |
Does the report have enough context to reason through it?
    |-- NO  --> Provide context first, then coach
    |-- YES --> Coaching mode: Use the 6-question script above

Step 6: Career Development Conversation Plan

General approach (all reports)

Schedule three dedicated career conversations per report over 8-12 weeks. These are NOT squeezed into the last 10 minutes of a standing 1:1 -- they get their own 45-60 min time block.

Specific plan: Designer-1 (passed over for promotion)

Designer-1's career conversation plan is accelerated and front-loaded because the promotion miss creates urgency around engagement, motivation, and retention.

Phase 1: Acknowledgment and listening (Week 1 of pilot)

Dedicated session: 45 min, within the first week.

This is NOT yet the Life Story conversation. It is a listening-first session focused on the promotion decision.

Agenda:

1. Opening (5 min): "I wanted to make dedicated time to talk about the promotion decision. I care about your growth here, and I want to understand how you're feeling."
2. Listening (25 min):
   • "Walk me through your reaction to the decision."
   • "What feedback did you receive? What parts resonate and what feels unclear or unfair?"
   • "What questions do you have that haven't been answered?"
   • Reflect back what you hear. Do not defend the decision or explain organizational constraints unless asked. Your job is to listen.
3. Support and clarity (10 min):
   • "What kind of support would be most helpful from me right now?"
   • "Is there anything about your current work that you'd like to change?"
   • Share what you can about the gap (if you have information from the promotion committee). Be specific: "The feedback was about X and Y."
4. Close (5 min):
   • "I'd like to schedule a career conversation series with you over the next few weeks -- Life Story, Future Dreams, and Action Plan. My goal is to build a concrete plan for your growth here. Would that be useful?"
   • Agree on next steps.

Critical guidelines for this conversation:

• Do NOT promise a future promotion or timeline. You cannot guarantee outcomes.
• Do NOT minimize their feelings ("It's not a big deal" or "There's always next cycle").
• Do acknowledge the disappointment: "I understand this is frustrating, and your reaction is completely valid."
• Do commit to working on a growth plan together.

Phase 2: Life Story conversation (Week 2 of pilot)

45-60 min dedicated session.

Questions:

• "Take me back to your very first job or project that you loved. What drew you to it?"
• "What moments in your career have shaped the choices you've made?"
• "What do you reliably enjoy doing in your work? What drains you?"
• "What kind of recognition or impact matters most to you?"
• "What do you want more of in your work life right now?"

Output to capture:

• 3-5 career themes (e.g., "drawn to user research," "energized by ambiguity," "values craft excellence")
• Motivation drivers (e.g., autonomy, mastery, visible impact, team influence)
• Skills they want to build

Phase 3: Future Dreams conversation (Week 3 of pilot)

45-60 min dedicated session.

Questions:

• "Imagine it's 5 years from now and things have gone really well. What are you doing?"
• "List 3-4 different futures that appeal to you -- they don't have to be consistent."
• "For each one, what's appealing? What's the version of you that lives in that future?"
• "Which of these futures is most aligned with what you told me in our Life Story conversation?"

Output to capture:

• 3-4 plausible futures with what's appealing about each
• Patterns across the futures (common threads)

Phase 4: Career Action Plan (Week 4 of pilot)

45-60 min dedicated session.

Questions:

• "Based on our conversations, what 1-3 growth bets do you want to make this quarter?"
• "What specific skills or experiences would move you toward those futures?"
• "What projects or opportunities on our team (or adjacent teams) could be practice loops for these skills?"
• "What does the promotion feedback tell us about gaps to close? Which of those gaps excites you vs. feels like a box-checking exercise?"
• "How should we check in on progress -- monthly? Tied to specific milestones?"

Output to capture:

Phase 5: Ongoing integration

After the action plan is established:

• Reference growth bets in standing biweekly 1:1s (1 agenda item per meeting).
• Schedule a formal career check-in every 6-8 weeks to revisit the action plan.
• When staffing projects, explicitly consider growth bet alignment.

Career conversation schedule (other reports)

Step 7: Wellbeing / Recovery Check-in + Special Situations

Wellbeing / recovery check-in pattern

Frequency: Include a lightweight check-in in 1 out of every 2-3 standing 1:1s. It should feel natural, not clinical.

Quick check template:

• Energy (1-10): ___
• Joy this week (yes/no + what): ___
• Biggest drain: ___
• Small activation(s) to try: ___

Sample questions:

• "How's your energy this week on a scale of 1-10?"
• "What gave you energy or joy this week?"
• "What's draining you? Is it workload, ambiguity, interpersonal, or something else?"
• "What's one small thing you could do this week for recovery? (walk, hobby, boundary, etc.)"

Manager behavioral activations (things you can offer):

• Adjust scope or priorities to reduce load
• Protect their calendar from unnecessary meetings
• Shield from context-switching
• Pair them with a teammate for support on a draining task
• Offer flexibility on timing/location

Boundary and escalation rules:

• You are NOT a therapist. Do not diagnose burnout, anxiety, or depression.
• If a report consistently reports energy below 3/10 for 2+ weeks, or describes symptoms of burnout, say: "I'm concerned about your wellbeing. I want to make sure you have the right support. Our company offers [EAP/mental health benefit]. Would it be helpful to explore that?"
• If the issue is workload-driven, take action: adjust priorities, remove tasks, or escalate resourcing to your manager.
• If a report discloses a personal crisis or safety concern, follow company policy immediately. Document only what is necessary and job-relevant.

Special-situation playbook 1: Post-crisis listening session

When to use: After a layoff, reorg, major incident, leadership change, or any event that shakes the team's sense of stability.

Format: 60 min, 1:1, no laptop (or cameras on, no screen share).

1. Opening (2 min):
   • "I'd like to know your thoughts and feelings about what happened. There's no agenda today except to listen."
2. Listening (40-50 min):
   • Reflect back what you hear: "It sounds like you're feeling..."
   • Ask clarifying questions: "Can you say more about that?"
   • Do NOT defend decisions, explain rationale (unless asked), or pivot to action items.
   • Silence is OK. Let them fill it.
3. Support and clarity (8-15 min):
   • "What support do you need from me this week?"
   • "What would help you feel safe and effective in the short term?"
   • "Is there anything you need me to advocate for?"
4. Close (2 min):
   • Summarize what you heard (themes, not quotes).
   • Agree on 1-2 small next steps (support-oriented, not execution-oriented).

Special-situation playbook 2: Urgent topical meeting

When to use: A time-sensitive decision, customer escalation, or blocker that cannot wait for the next standing 1:1.

Trigger: Either party sends a Slack DM: "Need [15/20/30] min to [one-line description]. By [deadline]."

Format: 15-30 min, focused.

1. Frame (2 min): "Here's the situation. Here's the decision needed by [time]."
2. Options (5-10 min): Explore 2-3 options. Coaching mode if time allows; directive if not.
3. Decision (3 min): State the decision, rationale, and who communicates it.
4. Action items (2 min): Who does what by when. Log in the shared 1:1 doc.

Response SLA: Acknowledge the request within 4 hours. Schedule within 24 hours.

Special-situation playbook 3: Skip-level template

Note: As a product lead with 5 direct reports (no managers reporting to you), skip-levels are not currently needed. This template is included for future reference if your team grows.

Purpose (pick one per skip-level program):

• Signal gathering / org health
• Coaching and career support
• Removing blockers (without bypassing the direct manager)

Format: 30-45 min, quarterly.

Questions (pick 5-8):

• "What's working really well on your team?"
• "What's the biggest thing slowing you down?"
• "What's hard to say out loud?"
• "Where are decisions unclear?"
• "What should we stop/start/continue?"
• "What could your manager or I do differently?"

Follow-up rules:

• Share themes with the direct manager, not quotes or names.
• Do not make commitments that conflict with the direct manager's plans.
• Close the loop with the skip-level report: "Here's what I heard; here's what we're doing about it."

Step 8: Quality Gate + 4-Week Pilot Schedule

Checklist verification

A) Pack completeness

• Includes a clear purpose for 1:1s and a "what goes where" map (Section 2)
• Includes a cadence + meeting types plan with tiered approach (Section 3)
• Includes shared 1:1 doc template with agenda, notes, action items, topics backlog (Section 4)
• Includes a coaching toolkit with rules + question bank + when to be directive (Section 5)
• Includes a career conversation plan with life story, dreams, action plan (Section 6)
• Includes a wellbeing/recovery check-in pattern with boundaries/escalation (Section 7)
• Includes special-situation playbooks: post-crisis listening, urgent topical, skip-level (Section 7)
• Includes Risks / Open questions / Next steps (below)

B) 1:1 system quality

• Status updates have a non-1:1 home (async + team standup defined in "what goes where" map)
• Cadence matches relationship needs: Tier 1 (weekly) for high-touch, Tier 2 (biweekly) for senior/stable
• Each meeting ends with written next steps via the action items table in the shared doc
• The system is lightweight: average 2 hr 15 min/week, well under the 3.5-hour budget

C) Coaching quality

• Coaching prompts organized by situation type; each generates options and tradeoffs
• Default is coaching mode; manager self-check ("Am I talking too long?") is explicit
• Exceptions for directive leadership are explicit (safety, legal, time-critical, repeated pattern, new hire lacking context)

D) Career development quality

• Career conversations are scheduled as dedicated 45-60 min sessions, not squeezed into standing 1:1s
• Designer-1 has a complete 4-week accelerated plan with listening session, life story, dreams, and action plan
• Output includes growth bets with practice loops and checkpoints (table template provided)

E) Wellbeing + safety boundaries

• Joy/energy check-ins present; rotating frequency (every 2-3 meetings)
• Workload/priority adjustments listed as concrete manager actions
• Escalation guidance: EAP referral language provided; "not a therapist" boundary is explicit

F) Skip-level + special sessions quality

• Skip-level purpose, questions, and follow-up rules are clear; notes handling specified (themes, not quotes)
• Post-crisis session is listening-first with explicit "no status" rule
• Urgent topical meeting has trigger, SLA, and format defined

Rubric self-score

4-Week pilot schedule

Week 1: Launch + Designer-1 listening session

Week 2: Establish rhythm + Designer-1 Life Story

Week 3: Deepen coaching + Designer-1 Future Dreams

Week 4: Career action plan + pilot review

Pilot review questions (Week 4 Friday):

1. Cadence: Is the tiered cadence working? Does any report need more or less time? Should any Tier 1 report move to Tier 2 (or vice versa)?
2. Shared docs: Are both parties consistently adding agenda items and logging action items? If not, what's the barrier?
3. Coaching vs. status: What percentage of 1:1 time was spent on coaching/career/feedback vs. status updates? Target: at least 70% coaching/career/feedback.
4. Career conversations: Did Designer-1's career sequence produce a usable action plan? Are they re-engaged?
5. Urgent topical meetings: How many were requested? Were they timely? Did they prevent "we should have talked sooner" moments?
6. Wellbeing: Were check-ins received well? Any flags that need attention?
7. Calendar load: Is total 1:1 time staying within the 2-3 hour/week budget?
8. What to adjust: Based on the above, what changes should be made for weeks 5-8?

Post-pilot actions:

• Share a summary of what's working and what's changing with each report (transparency builds trust).
• Update the cadence plan based on review findings.
• Schedule the next round of career conversations for remaining reports (PM-1, PM-2, PM-3, Data Analyst-1 per the schedule in Section 6).

Risks

1. New manager trust deficit: As a new leader, reports may not yet trust you enough for deep career or wellbeing conversations. Mitigation: Start with lighter coaching and build trust through consistency and follow-through before pushing into vulnerable topics.
2. Designer-1 attrition risk: The promotion miss may have already shifted Designer-1 into active job search. The career conversation sequence helps, but if they disengage, have a direct retention conversation and involve your manager early.
3. Calendar pressure: At 85% utilization, adding 2+ hours of 1:1s requires cutting something else. Mitigation: Audit your existing meetings and identify 2-3 hours of meetings you can delegate, decline, or convert to async.
4. Coaching feels slow under pressure: In high-stress weeks, you may default to directive mode for efficiency. Mitigation: Keep the coach vs. advisor decision tree visible. Only go directive for the 5 listed exceptions.
5. Shared doc adoption resistance: Some reports may not add agenda items in advance. Mitigation: Model the behavior by always adding your items first. After 2 weeks, have an explicit conversation about the norm.

Open questions

1. Does your company have an EAP (Employee Assistance Program) or mental health benefit to reference in wellbeing escalation guidance?
2. What project management tool does the team use for status tracking (Jira, Linear, Asana)? This affects how firmly you can redirect status out of 1:1s.
3. Does your company have a career ladder or competency framework for the PM, Design, and Data Analyst roles? This would enrich the career conversation outputs.
4. What feedback (if any) was given to Designer-1 about the promotion decision? Knowing the specific gaps will make the Career Action Plan more targeted.
5. Are there upcoming team changes (new hires, departures, reorgs) that would affect the cadence plan in weeks 5-8?

Next steps