How to Run Useful 1:1s

If your 1:1 is a live reading of Jira, you already have Slack and standups for that. The 1:1 exists for the report’s growth, energy, and blockers that do not fit a status field — and for the manager to hear truth early.

This guide is written for both sides. Managers set the container; reports own the content.

What a useful 1:1 is (and is not)

Is: a recurring private conversation with a shared doc, a light agenda, and room for career and feedback.
Is not: performance ambush, therapy without boundaries, or a meeting the manager cancels whenever “things get busy.” Cancelling 1:1s teaches people that their growth is optional.

Default cadence: weekly for new hires and anyone in a rocky season; biweekly for seniors with high trust. When in doubt, meet more often for shorter time.

A durable four-part agenda

Keep the same skeleton every week so preparation is cheap:

1. Wins and energy (5 min) — What went well? Where is energy high or drained?
2. Blockers (10 min) — What is stuck that only the manager (or escalation) can move?
3. Feedback both ways (5–10 min) — One observation each, or a deeper thread when needed.
4. Career / growth (5–10 min) — Skills, scope, visibility, next roles — even a small weekly crumb.

If the meeting is 25 minutes, cut status first, never career forever.

Shared running doc template

# 1:1 — Name ↔ Manager
## Standing notes
- Goals this quarter:
- Career themes:
 
## YYYY-MM-DD
### Wins / energy
-
 
### Blockers
-
 
### Feedback
- Manager → report:
- Report → manager:
 
### Career / growth
-
 
### Decisions / follow-ups
- [ ] owner — due

Info: Memory is a terrible project manager. If it is not in the doc, it did not happen.

Scripts that keep the meeting honest

Report opening a hard topic

“I want to use ten minutes on something that’s slowing me down: I’m waiting on Legal for the vendor clause, and it’s blocking the launch checklist. Can we escalate or re-scope?”

Manager inviting upward feedback

“What’s one thing I did last week that made your work harder — even if it was unintentional?”

Manager noticing energy drop

“You mentioned low energy two weeks in a row. Is this workload, role fit, something outside work you want to flag at a high level, or something else?”

You do not need to solve personal life in a 1:1. You do need to avoid pretending the energy signal does not exist.

Career crumb when promotion is not imminent

“Promotion aside, what’s one skill you want more reps on this month? I can help find a project that creates those reps.”

Worked example: turning status into leverage

Before: Mira spends 20 minutes listing tickets. Manager nods. Nothing changes.

After: Mira pastes a three-line blocker note before the meeting:

Blocker: Design review stuck 8 days. Risk: misses Friday release. Ask: Can you join Thursday’s review or reassign the reviewer?

They spend 1:1 time on the ask. The tickets stay in the tracker where they belong.

Common mistakes and edge cases

Mistake: manager monopolizes. If you talk 80% of the time, you are running a broadcast. Aim for the report speaking most.

Mistake: only negative feedback in 1:1s. Surprise criticism in a rare meeting destroys trust. Give timely feedback near the event; use 1:1s to pattern-spot and coach.

Mistake: no follow-ups. Decisions without owners are vibes. End with two checkboxes max if needed.

Edge case: skip-level or matrix managers. Keep a thinner cadence with the dotted-line manager; clarify who owns performance ratings so the report is not triangulating in the dark.

Edge case: remote-only teams. Cameras optional if culture allows, but do not multitask. A distracted 1:1 is worse than a reschedule with notice.

Edge case: conflict between peers. Coach the report to attempt a direct conversation first; offer to mediate only after that attempt, unless safety or harassment is involved (then follow policy immediately).

Cadence and length cheat sheet

Protect the calendar like a production dependency. If you must move it, reschedule within the same week.

Checklist for the first month of better 1:1s

• Shared doc created and linked in the invite
• Agenda skeleton agreed
• Report adds notes before at least half the meetings
• At least one upward feedback question asked
• Career theme named (even if fuzzy)
• Zero silent cancellations

How to measure progress

Pick signals you can observe over four to six weeks:

Ask quarterly: “On a scale of 1–5, how useful are our 1:1s?” If the answer is ≤3, redesign together — do not defend the old ritual.

Useful 1:1s are boring in the best way: predictable container, honest content, and a written trail that makes growth visible instead of accidental.