Running Effective 1:1s
Scope
Covers
- Designing a lightweight 1:1 operating system (purpose, cadence, meeting types, shared docs)
- Running 1:1s as coaching conversations (not just status updates)
- Holding career development conversations (life story → future dreams → action plan)
- Doing basic wellbeing/recovery check-ins (joy/energy) without crossing into therapy/medical advice
- Running skip-levels and special sessions (e.g., post-crisis “make them feel heard” 1:1s)
When to use
- “My 1:1s are turning into status updates—help me redesign them.”
- “Create a 1:1 agenda + shared doc template for me and my direct reports.”
- “I’m a new manager—set up my 1:1 cadence and question bank.”
- “Help me run better career conversations in 1:1s.”
- “Plan a skip-level program and templates.”
When NOT to use
- You need HR/legal guidance, an investigation, or a performance improvement plan (involve HR/legal; use your company process)
- You need a project status meeting cadence (use team/ops rituals; 1:1s should not be the primary status channel)
- The situation involves immediate safety/mental health crisis (seek professional help and follow company policy)
Inputs
Minimum required
- Your role and context (manager level, org type, function, time zones)
- Who the 1:1s are for (directs, skip-levels) and relationship stage (new, stable, strained)
- Current 1:1 cadence and what’s not working (2–5 concrete examples)
- What you want to change (coaching, feedback, career growth, wellbeing, alignment, retention)
- Constraints: meeting load, confidentiality/PII rules, any HR policies, time box/deadline
Missing-info strategy
- Ask up to 5 questions from references/INTAKE.md (3–5 at a time).
- If key details are missing, proceed with a default 1:1 operating system and clearly label assumptions.
- Do not request secrets or sensitive personal data; use anonymized summaries.
Outputs (deliverables)
Produce a 1:1 Operating System Pack in Markdown (in-chat; or as files if requested):
- Context + goals (what 1:1s are for in this team; what they are not for)
- Cadence + meeting types plan (weekly/biweekly + barbell approach + skip-level cadence)
- Shared 1:1 doc templates (agenda, notes, action items, topics backlog)
- Coaching toolkit (conversation rules + question bank + “coach vs advisor” prompts)
- Career development conversation plan (life story → dreams → action plan, with templates)
- Wellbeing/recovery check-in pattern (joy/energy prompts + boundaries + escalation guidance)
- Special-situation playbooks (post-crisis listening session; urgent topical meeting; skip-level template)
- Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
Expanded guidance: references/WORKFLOW.md
Workflow (8 steps)
1) Intake + boundaries + safety
- Inputs: user context; references/INTAKE.md.
- Actions: Confirm goals for 1:1s, current failure modes, constraints, and any HR/safety boundaries. Decide which deliverables are needed (full pack vs just templates).
- Outputs: Context snapshot + assumptions/unknowns list.
- Checks: The purpose of 1:1s is explicit and does not conflict with HR/legal policy.
2) Define the 1:1 purpose and “what goes where”
- Inputs: goals + failure modes.
- Actions: Separate topics into channels: team status rituals vs 1:1 coaching, career, feedback, and blockers. Define what the 1:1 should consistently cover (and what it should not).
- Outputs: “What goes where” map + 1:1 purpose statement.
- Checks: Status updates have a non-1:1 home (async or team ritual).
3) Choose cadence + meeting types (barbell design)
- Inputs: roster, seniority, relationship needs, time budget.
- Actions: Propose a cadence plan: standing 1:1s where they add value, plus a barbell approach (high-quality relationship catch-ups + urgent topical meetings). Add a skip-level cadence if needed.
- Outputs: Cadence + meeting types plan.
- Checks: The plan reduces meeting bloat while improving timeliness and relationship quality.
4) Create the shared 1:1 documentation system
- Inputs: tools available (doc, notes, tracker), privacy constraints.
- Actions: Define a shared doc per report (or per relationship) with: agenda, running topics backlog, notes, decisions, and action items. Include a pre-work expectation for both sides.
- Outputs: Shared 1:1 doc template + action item tracker conventions.
- Checks: Every meeting ends with written next steps and owners; sensitive content is handled appropriately.
5) Shift from “advisor” to “coach” (conversation rules)
- Inputs: common problem types brought to 1:1s.
- Actions: Write a coaching toolkit: default questions, how to avoid jumping to answers, and how to help the report reason through tradeoffs. Include a “when to be directive” exception list (risk, safety, time-critical).
- Outputs: Coaching rules + question bank.
- Checks: The toolkit trains independent problem solving rather than escalating everything to the manager.
6) Build a career development sequence (3 conversations)
- Inputs: role expectations, growth paths, aspirations (if known).
- Actions: Create a career plan that schedules three deeper conversations: Life Story, Future Dreams, Career Action Plan. Define how tactical 1:1s connect to growth over time.
- Outputs: Career conversation plan + templates.
- Checks: The plan results in 1–3 concrete growth bets and follow-up checkpoints.
7) Add wellbeing/recovery + special situations
- Inputs: team stress level, recent change events, relationship health.
- Actions: Add a lightweight joy/energy check-in pattern and a “behavioral activations” list. Add special playbooks: post-crisis listening session (feel heard), urgent topical meeting, and skip-level structure.
- Outputs: Wellbeing pattern + special-situation playbooks + templates.
- Checks: Boundaries are clear (not therapy); escalation paths are documented.
8) Quality gate + rollout plan
- Inputs: full draft pack.
- Actions: Run references/CHECKLISTS.md and score with references/RUBRIC.md. Add Risks / Open questions / Next steps. Propose a 2–4 week pilot with review prompts.
- Outputs: Final 1:1 Operating System Pack.
- Checks: Pack is immediately usable; responsibilities and follow-ups are explicit.
Quality gate (required)
- Use references/CHECKLISTS.md and references/RUBRIC.md.
- Always include: Risks, Open questions, Next steps.
Examples
Example 1 (new manager): “I’m a new product lead with 6 direct reports across time zones. Design my 1:1 cadence, a shared 1:1 doc template, and a coaching question bank. Include a career conversation plan and a 4-week pilot.”
Expected: cadence plan + templates + coaching toolkit + career sequence + quality gates.
Example 2 (meeting bloat): “My calendar is overloaded with weekly 1:1s. I still want strong relationships and fast escalation on urgent topics. Propose a barbell approach, updated agendas, and a skip-level cadence.”
Expected: reduced standing roster with explicit alternatives; relationship catch-ups + urgent topical meetings; skip-level template.
Boundary example: “I need to document poor performance and start a PIP.”
Response: recommend HR/performance management process; offer to help create a feedback conversation plan and expectations doc, but not to run an HR process via 1:1 templates.
1---2name: running-effective-1-1s3description: Run effective 1:1s and skip-levels as a manager/leader and produce a 1:1 Operating System Pack (cadence plan, agendas, shared doc templates, coaching prompts, career conversation plan, and quality gates). Use for 1:1, one-on-one, 1-on-1, manager check-ins, coaching, career conversations, and skip levels. Category: Leadership.4---5
6# Running Effective 1:1s
7
8## Scope
9
10**Covers**
11- Designing a lightweight **1:1 operating system** (purpose, cadence, meeting types, shared docs)
12- Running 1:1s as **coaching conversations** (not just status updates)
13- Holding **career development** conversations (life story → future dreams → action plan)
14- Doing basic **wellbeing/recovery** check-ins (joy/energy) without crossing into therapy/medical advice
15- Running **skip-levels** and special sessions (e.g., post-crisis “make them feel heard” 1:1s)
16
17**When to use**
18- “My 1:1s are turning into status updates—help me redesign them.”
19- “Create a 1:1 agenda + shared doc template for me and my direct reports.”
20- “I’m a new manager—set up my 1:1 cadence and question bank.”
21- “Help me run better career conversations in 1:1s.”
22- “Plan a skip-level program and templates.”
23
24**When NOT to use**
25- You need HR/legal guidance, an investigation, or a performance improvement plan (involve HR/legal; use your company process)
26- You need a project status meeting cadence (use team/ops rituals; 1:1s should not be the primary status channel)
27- The situation involves immediate safety/mental health crisis (seek professional help and follow company policy)
28
29## Inputs
30
31**Minimum required**
32- Your role and context (manager level, org type, function, time zones)
33- Who the 1:1s are for (directs, skip-levels) and relationship stage (new, stable, strained)
34- Current 1:1 cadence and what’s not working (2–5 concrete examples)
35- What you want to change (coaching, feedback, career growth, wellbeing, alignment, retention)
36- Constraints: meeting load, confidentiality/PII rules, any HR policies, time box/deadline
37
38**Missing-info strategy**
39- Ask up to 5 questions from [references/INTAKE.md](references/INTAKE.md) (3–5 at a time).
40- If key details are missing, proceed with a **default 1:1 operating system** and clearly label assumptions.
41- Do not request secrets or sensitive personal data; use anonymized summaries.
42
43## Outputs (deliverables)
44
45Produce a **1:1 Operating System Pack** in Markdown (in-chat; or as files if requested):
46
471) **Context + goals** (what 1:1s are for in this team; what they are not for)
482) **Cadence + meeting types plan** (weekly/biweekly + barbell approach + skip-level cadence)
493) **Shared 1:1 doc templates** (agenda, notes, action items, topics backlog)
504) **Coaching toolkit** (conversation rules + question bank + “coach vs advisor” prompts)
515) **Career development conversation plan** (life story → dreams → action plan, with templates)
526) **Wellbeing/recovery check-in pattern** (joy/energy prompts + boundaries + escalation guidance)
537) **Special-situation playbooks** (post-crisis listening session; urgent topical meeting; skip-level template)
548) **Risks / Open questions / Next steps** (always included)
55
56Templates: [references/TEMPLATES.md](references/TEMPLATES.md)
57Expanded guidance: [references/WORKFLOW.md](references/WORKFLOW.md)
58
59## Workflow (8 steps)
60
61### 1) Intake + boundaries + safety
62- **Inputs:** user context; [references/INTAKE.md](references/INTAKE.md).
63- **Actions:** Confirm goals for 1:1s, current failure modes, constraints, and any HR/safety boundaries. Decide which deliverables are needed (full pack vs just templates).
64- **Outputs:** Context snapshot + assumptions/unknowns list.
65- **Checks:** The purpose of 1:1s is explicit and does not conflict with HR/legal policy.
66
67### 2) Define the 1:1 purpose and “what goes where”
68- **Inputs:** goals + failure modes.
69- **Actions:** Separate topics into channels: team status rituals vs 1:1 coaching, career, feedback, and blockers. Define what the 1:1 should consistently cover (and what it should not).
70- **Outputs:** “What goes where” map + 1:1 purpose statement.
71- **Checks:** Status updates have a non-1:1 home (async or team ritual).
72
73### 3) Choose cadence + meeting types (barbell design)
74- **Inputs:** roster, seniority, relationship needs, time budget.
75- **Actions:** Propose a cadence plan: standing 1:1s where they add value, plus a **barbell approach** (high-quality relationship catch-ups + urgent topical meetings). Add a skip-level cadence if needed.
76- **Outputs:** Cadence + meeting types plan.
77- **Checks:** The plan reduces meeting bloat while improving timeliness and relationship quality.
78
79### 4) Create the shared 1:1 documentation system
80- **Inputs:** tools available (doc, notes, tracker), privacy constraints.
81- **Actions:** Define a shared doc per report (or per relationship) with: agenda, running topics backlog, notes, decisions, and action items. Include a pre-work expectation for both sides.
82- **Outputs:** Shared 1:1 doc template + action item tracker conventions.
83- **Checks:** Every meeting ends with written next steps and owners; sensitive content is handled appropriately.
84
85### 5) Shift from “advisor” to “coach” (conversation rules)
86- **Inputs:** common problem types brought to 1:1s.
87- **Actions:** Write a coaching toolkit: default questions, how to avoid jumping to answers, and how to help the report reason through tradeoffs. Include a “when to be directive” exception list (risk, safety, time-critical).
88- **Outputs:** Coaching rules + question bank.
89- **Checks:** The toolkit trains independent problem solving rather than escalating everything to the manager.
90
91### 6) Build a career development sequence (3 conversations)
92- **Inputs:** role expectations, growth paths, aspirations (if known).
93- **Actions:** Create a career plan that schedules three deeper conversations: **Life Story**, **Future Dreams**, **Career Action Plan**. Define how tactical 1:1s connect to growth over time.
94- **Outputs:** Career conversation plan + templates.
95- **Checks:** The plan results in 1–3 concrete growth bets and follow-up checkpoints.
96
97### 7) Add wellbeing/recovery + special situations
98- **Inputs:** team stress level, recent change events, relationship health.
99- **Actions:** Add a lightweight joy/energy check-in pattern and a “behavioral activations” list. Add special playbooks: post-crisis listening session (feel heard), urgent topical meeting, and skip-level structure.
100- **Outputs:** Wellbeing pattern + special-situation playbooks + templates.
101- **Checks:** Boundaries are clear (not therapy); escalation paths are documented.
102
103### 8) Quality gate + rollout plan
104- **Inputs:** full draft pack.
105- **Actions:** Run [references/CHECKLISTS.md](references/CHECKLISTS.md) and score with [references/RUBRIC.md](references/RUBRIC.md). Add **Risks / Open questions / Next steps**. Propose a 2–4 week pilot with review prompts.
106- **Outputs:** Final 1:1 Operating System Pack.
107- **Checks:** Pack is immediately usable; responsibilities and follow-ups are explicit.
108
109## Quality gate (required)
110- Use [references/CHECKLISTS.md](references/CHECKLISTS.md) and [references/RUBRIC.md](references/RUBRIC.md).
111- Always include: **Risks**, **Open questions**, **Next steps**.
112
113## Examples
114
115**Example 1 (new manager):** “I’m a new product lead with 6 direct reports across time zones. Design my 1:1 cadence, a shared 1:1 doc template, and a coaching question bank. Include a career conversation plan and a 4-week pilot.”
116Expected: cadence plan + templates + coaching toolkit + career sequence + quality gates.
117
118**Example 2 (meeting bloat):** “My calendar is overloaded with weekly 1:1s. I still want strong relationships and fast escalation on urgent topics. Propose a barbell approach, updated agendas, and a skip-level cadence.”
119Expected: reduced standing roster with explicit alternatives; relationship catch-ups + urgent topical meetings; skip-level template.
120
121**Boundary example:** “I need to document poor performance and start a PIP.”
122Response: recommend HR/performance management process; offer to help create a feedback conversation plan and expectations doc, but not to run an HR process via 1:1 templates.
majiayu000