- name
- one-on-ones
- description
- Use when designing or improving 1:1 practices — covers cadence, agendas, manager-vs-report ownership, and common failures.
# One-on-Ones
## Why 1:1s Are the Highest-Leverage Manager Ritual
A weekly 30–60 min conversation between manager and report is the most consequential recurring interaction in a company. Done well, it surfaces problems, builds trust, drives growth, and prevents the surprises that destroy performance systems.
Done poorly, it becomes a status meeting that demoralizes both parties.
## Core Principles
1. **Standing time, not "as needed"**: cancelling 1:1s is the wrong inversion of priority
2. **Report sets the agenda by default**: their time, their priorities, their concerns
3. **Manager listens first**: avoid the "manager updates" trap
4. **Both directions**: feedback flows up as well as down
5. **Career and life**: not just the work
6. **Confidential by default**: what's said in 1:1 stays unless agreed otherwise
## Cadence
- ICs: weekly, 30–60 min
- Senior leaders / experienced reports: bi-weekly, 60 min
- New hires / new managers: weekly, longer (60+ min) for first months
Cancellations:
- Acceptable: occasional, with rescheduling that week
- Pattern: signal something's wrong (manager bandwidth, relationship, priority)
## Recommended Structure (60 min)
| Time | Topic |
|------|-------|
| 0–5 min | How are you? (actually ask) |
| 5–25 min | Report's agenda: what's on your mind? blockers? wins? |
| 25–40 min | Manager updates / context the report needs |
| 40–50 min | Feedback in both directions |
| 50–60 min | Career, growth, what's next |
Adjust to fit; don't treat as a script.
## Anti-Patterns
- **Status update**: use a doc instead
- **Manager dominates**: report doesn't get to set the agenda
- **Cancelled when busy**: signals priority
- **No documentation**: actions and decisions get lost
- **Hoarding feedback for the cycle**: 1:1 is the natural place
- **Skipping career conversations**: they deserve their own time on cadence
- **"How's life?" with no real curiosity**: performative
- **Same agenda every week**: dead conversation
## First 1:1 (New Manager-Report Pairing)
A 60-min meeting that earns months of trust:
1. Manager intro (background, philosophy, what makes them effective; their fallibility)
2. Report intro (background, motivations, what they care about)
3. Working preferences (communication style, feedback style, calendar)
4. Cadence (when, format, agenda)
5. First-month focus
6. How decisions get made on this team
7. Open questions
## Career Conversations
Not every 1:1; but on cadence (quarterly or so), explicitly career-focused:
- What do you want next? (in 6 months, 1 year, 5 years)
- What energizes you? Drains you?
- Where do you want to grow?
- What would help me support you?
- Are there opportunities you'd like to see?
The Manager's Path (Fournier) framing: career conversations require slowing down, not another tactical sync.
## Feedback in 1:1s
Feedback should flow weekly:
- Specific, recent, behavioral (SBI per `feedback-frameworks`)
- Both directions: manager invites upward feedback explicitly
- Low-stakes: small amounts often, not banked for the annual
If the manager and report have only feedback-laden 1:1s, the relationship will feel transactional. If they have only friendly 1:1s, the manager has failed.
## Documentation
Living doc shared between manager and report:
- Standing agenda items
- Recurring questions
- Action items with owners and due dates
- Feedback log
- Career conversation notes (separate section)
Documents:
- Don't replace the conversation
- Should be light enough not to feel like work
## Skip-Level 1:1s
For managers' managers:
- Quarterly with each skip-level report
- Listening mode primarily
- Provides relief valve when manager is the problem
- Surfaces patterns before they become crises
Norms:
- What's escalated to action vs. coached back to the manager
- Confidentiality respected (within ethical limits)
- Senior leader doesn't undercut the manager
## When 1:1s Fail
Common patterns:
- Status meeting only — no real conversation
- Manager not present (distracted, multitasking)
- Report doesn't trust the manager — surface conversation only
- Manager doesn't ask follow-up questions
- Issues raised but never followed up
The fix is rarely the format. The fix is usually trust, curiosity, and follow-through.
## Cross-References
- `feedback-frameworks` skill
- `coaching-skills` skill
- `manager-enablement-coach` agent
- `feedback-systems-designer` agent
## Key References
- Grove, A. (1983). *High Output Management*.
- Fournier, C. (2017). *The Manager's Path*.
- Zhuo, J. (2019). *The Making of a Manager*.
- Hogan, L. (2019). *Resilient Management*.
Ver en GitHub