Weekly 1:1 Operating Cadence How-to
Status dumps are not 1:1s. Treat the shared 1:1 doc as an operating system, not meeting notes. Standing sections with last-week commitments at the top force accountability. Status belongs in async; live time buys judgment, coaching, and unblocking.
This play installs a repeatable weekly (or biweekly) cadence. Pair the deep guide How to run a 1:1 meeting with the New Manager hub calendar modules. Move project noise into async updates instead of meetings.
Play card
| Field | Detail |
|---|---|
| Time box | 25–50 minutes recurring (plus ≤10 min prep each side) |
| Players | Manager + one direct report (IC co-owns the agenda) |
| Goal | A living shared doc: prior commitments reviewed, decisions made, next commitments named |
| Done looks like | Both leave with written owners, dates, and one feedback or career touch at least monthly |
When to use
- You manage people and want a rhythm that survives busy weeks.
- 1:1s keep collapsing into ticket walkthroughs.
- A new report needs structure after a first 1:1 (see first 90 days as a new manager).
- An IC wants to co-own the agenda instead of waiting to be interviewed.
Weekly vs biweekly: Default weekly for new reports, shaky contexts, or high change. Move to biweekly once priorities are stable and trust is solid. Confirm the choice with your manager so span and norms stay coherent.
When not to use
- Do not cancel 1:1s as the default stress response. Shorten them, move async status out, or protect a 25-minute floor. Canceling teaches that people time is optional.
- Do not use weekly 1:1s as the only place hard feedback ever appears. When stakes rise, run Difficult conversation prep before the meeting.
- Do not turn a 1:1 into an HR investigation. For harassment, discrimination, safety, or legal risk, pause and use company channels. Education path: When to talk to HR vs manager and HR for humans.
- Do not treat mental health disclosures as something you “fix” in a template. Listen, support access to resources, and follow policy. This play is not clinical advice.
Prep (≤10 minutes each)
Report
1. Update the shared doc: wins, priorities, blockers, decisions needed.
2. Mark last-week commitments done / not done with one line why.
3. Add one topic under feedback or career (even a stub).
Manager
1. Skim the doc before the call. Do not discover the agenda live.
2. Note one piece of specific feedback (positive or corrective) you can deliver in two minutes.
3. Flag any decision only you can make so it does not die in small talk.
If status still floods the doc, move the narrative to an async update and keep the 1:1 for judgment.
Timed agenda template (30-minute default)
Adjust up to 50 minutes for career-heavy weeks or complex decisions.
| Minutes | Section | Purpose |
|---|---|---|
| 0–3 | Open + last commitments | Accountability before new topics |
| 3–12 | Priorities vs plan | What slipped, what to cut, what still matters |
| 12–18 | Blockers and decisions | Help needed, not a full status tour |
| 18–24 | Feedback both ways | One concrete ask each direction when possible |
| 24–28 | Career / growth (rotate) | At least once a month; stub weekly if short |
| 28–30 | Close commitments | Who / what / when written in the doc |
25-minute cut: Drop career to a monthly deep session; keep commitments, priorities, blockers, and one feedback beat.
50-minute expand: Add rehearsal for a stakeholder talk, a delegation handoff, or a longer career conversation (career conversations with manager).
Run-of-show steps
- Open on the doc, not vibes. “Let’s start with last week’s commitments.”
- Report leads priorities. Manager challenges scope and tradeoffs; does not monologue the team roadmap.
- Convert status into asks. If a story has no decision or help request, park it for async.
- Protect feedback. Use how to ask for feedback at work language so it is not a once-a-year ambush.
- Write commitments before you hang up. Verbal agreements without owners evaporate.
- End on time. Overruns reward poor prep. Park overflow with a dated follow-up.
Script bank
Redirect a status dump
“I’m hearing the update. What decision do you need from me, or what blocker should we remove in the next two days?”
Invite career without forcing it
“We have eight minutes. Want to use them on growth this week, or park a topic for next 1:1 so we do it properly?”
Close with commitments
“I’ll write: you own X by Thursday; I own the intro to Y by tomorrow. Anything wrong in that capture?”
When you need a harder talk later
“This needs a fuller conversation than today. I’ll prep and we’ll schedule a focused slot.” Then use Difficult conversation prep.
Output artifact: shared running doc
Keep one doc per pair. Suggested skeleton:
# 1:1: [Name] / [Manager]
Standing: working agreements, career goals (living)
## Open decisions
- ...
## Commitments (rolling)
| Date set | Owner | Commitment | Due | Status |
| --- | --- | --- | --- | --- |
## Week of YYYY-MM-DD
### Prep (async)
Report: ...
Manager: ...
### Live notes
Priorities:
Blockers / decisions:
Feedback:
Career:
Commitments this week:
Sample (fictional): Maya (IC) and Jordan (manager). Maya marks “ship FAQ draft” done; flags “design review blocked on vendor access.” Jordan decides to escalate access same day. Feedback: Jordan notes the FAQ was crisp for support; Maya asks how to show leadership without taking every fire drill. Commitments: Maya owns vendor chase with Jordan CC’d; Jordan owns a 15-minute stakeholder intro Friday.
What a healthy month looks like (qualitative)
Across four meetings you should see: commitments revisited (not forgotten), at least one two-way feedback exchange, one career or growth touch, fewer pure status monologues, and decisions captured in writing. You will not get a universal “best” length for every company. Fit the box to the work.
Watch-outs
- Manager monologue: If you talk more than half the time, you ran a briefing, not a 1:1.
- Only talking up: Reports who only praise and never raise risk need an explicit invite for bad news.
- Never talking career: Reviews become surprises. Rotate growth onto the agenda monthly.
- Therapy without boundaries: Empathy matters. You are not their clinician. Support resources and stay inside your role.
- Hard feedback only in crisis: Cadence should make tough topics less rare; prep play when the topic is heavy.