How to Run Effective 1:1s: A Repeatable Structure, Agenda Template, and Cadence

The 1:1 is the highest-leverage meeting a manager runs, and the one most likely to rot into a status update. Done well, it’s where trust gets built, problems surface while they’re still cheap, and careers actually get managed. Done badly, it’s thirty minutes of “so, how’s the project going?” that both people quietly resent.

The difference is almost never charisma. It’s structure. Effective 1:1s are a repeatable system: a deliberate cadence, a shared agenda with a stable shape, questions that go beyond status, and ruthless follow-through on what was agreed. This guide gives you all four, ready to use this week.

How Often Should You Have 1:1s — and How Long?

Start from a default and adjust deliberately, not by drift.

CadenceLengthBest forWatch out for
Weekly30 minNew reports (first 90 days), new managers, high-change periods, struggling performers, most remote/hybrid teamsLetting it collapse into pure status because the gap between meetings is short
Biweekly45 minEstablished, senior reports in stable periods; managers with 7+ directsTwo cancellations = a month of silence; topics arrive stale
MonthlySkip-levels and mentoring — not direct-report 1:1sA monthly direct-report 1:1 is a review, not a relationship

Rules that matter more than the exact cadence:

  • The math is the argument for 30/weekly over 60/monthly. Same manager-time budget; radically different signal freshness. Problems compound weekly; catching them at week one instead of week four is the entire point.
  • Remote and hybrid teams should bias one notch more frequent than they think they need. The hallway used to carry half this information; it’s gone.
  • Reschedule, never cancel. A cancelled 1:1 tells your report exactly where they rank. If you must move it, move it — same week, no exceptions. Cancellation rate is the single most honest metric of whether your 1:1 program is real.
  • Protect the slot. Recurring calendar hold, same time weekly, treated with the same gravity as an exec review.

Who Owns the Agenda?

The report owns the agenda; the manager owns the system.

The meeting is primarily the report’s — their blockers, their growth, their concerns get airtime first. But the manager is accountable for the container: the cadence holds, an agenda exists before the meeting, notes get captured, and action items actually close. A useful norm: agenda items go into a shared doc or tool at least a few hours before the meeting. This kills the two failure modes at once — the meeting with no agenda (“so… what’s up?”) and the ambush agenda nobody could prepare for. If the report shows up with an empty agenda repeatedly, that’s not a green light to cancel; it’s a signal to coach them on using the meeting, or a sign they don’t yet believe it’s safe to bring real topics.

The Copy-Paste 1:1 Agenda Template

Built for 30 minutes; stretch each section proportionally for 45. The shape stays stable week to week — stability is what trains both people to prepare.

1:1 — [Report] / [Manager] — [Date]

1. CHECK-IN (3–5 min)
   How are you, actually? Energy level this week: red / yellow / green — why?

2. YOUR TOPICS (10–12 min)  ← report's list, added before the meeting
   - 
   - 
   (Blockers, decisions needed, concerns, wins, anything on your mind.)

3. GOALS & PRIORITIES PULSE (5 min)
   - Top priority this week — and is anything competing with it?
   - Any goal that's drifted off track or gone stale? What would change that?

4. FEEDBACK — BOTH DIRECTIONS (5 min)
   - Manager → report: one specific observation (reinforce or redirect).
   - Report → manager: what should I do more of / less of? What's one thing
     I could do to make your week easier?

5. GROWTH THREAD (5 min — at minimum every 2–3 sessions)
   - What did you do this month you'd want more of?
   - Progress on [current growth focus]?

6. ACTIONS & RECAP (2 min)
   - □ Owner — action — due date
   - □ Owner — action — due date
   Carry-overs from last time: reviewed? closed?

Three design notes. The check-in is not filler — the answer to “how are you, actually” is frequently the real agenda. The report’s topics come before the manager’s, permanently, or the meeting reverts to a status extraction within a month. And the recap is written down in a shared record, because an action item that lives in two memories lives nowhere.

Question Banks: Getting Past “How’s It Going?”

Rotate a few of these in whenever the conversation flattens into status. Don’t run them as a quiz — pick one or two and actually follow the thread.

Career & growth

  • What kind of work makes you lose track of time — and how much of it are you getting?
  • Where do you want to be in 18 months, and what’s one thing this quarter that moves you toward it?
  • What skill would make the biggest difference to your effectiveness right now?
  • Is there someone whose role or skills you’d like more exposure to?
  • What have you learned in the last month? What do you want to learn next?

Workload & energy

  • What’s taking more energy than it should right now?
  • If you could delete one recurring task or meeting, which one?
  • Are you closer to bored or overwhelmed this month?
  • What would you drop first if we had to cut your load 20% this week?

Blockers & the work itself

  • What’s slower than it should be? Where do you keep waiting on someone?
  • What’s the decision you need from me that you haven’t gotten?
  • What risk are we not talking about?
  • If you owned my job for a week, what would you fix first?

Feedback — report → manager

  • What’s one thing I could do differently that would help you most?
  • Where have I been too involved lately? Not involved enough?
  • Is there feedback you’ve hesitated to give me?
  • Do you feel like you know how you’re doing? What am I not telling you?

Feedback — manager → report

  • Prepare one specific, recent observation per meeting: “In [situation], you did [behavior], and the impact was [effect].”
  • Reinforcing feedback in a 1:1 is fine; save it publicly too — recognition compounds when it’s visible.
  • Redirecting feedback belongs here, in private, within days of the event — never saved up for review season.

Follow-Through: Where 1:1 Programs Live or Die

The fastest way to teach someone that 1:1s don’t matter is to let action items evaporate. Discipline here is simple and non-negotiable:

  1. Every action gets an owner and a date at the moment it’s created — “we should look into that” is not an action.
  2. Actions live in the shared 1:1 record, not in the manager’s private notebook, so both people see the same list.
  3. Every meeting opens or closes with the carry-over review. Items get closed, renegotiated, or consciously killed — never silently dropped.
  4. Manager items get done first. When your report sees your action items close reliably, theirs start closing too. Follow-through is modeled, not mandated.

If you track only one metric for yourself as a manager, track this: percentage of your own 1:1 action items closed by the agreed date.

The Skip-Level Variant

Skip-levels (you with your reports’ reports) run on a different template because the goal is different: you’re not managing the work, you’re sampling reality and building trust two layers down.

  • Cadence: monthly or quarterly per person is plenty; consistency beats frequency.
  • Frame it explicitly: “This isn’t a performance conversation, and it isn’t about grading your manager. I want to understand your experience and where I can remove friction.”
  • Ask about the system, not the individual: What’s harder than it should be? What information do you wish you had? What would you change about how the team runs? Where do you see us saying one thing and doing another?
  • Never commit to overriding the manager in the room. Take patterns, not verdicts, and close the loop with the manager transparently — skip-levels that turn into secret escalation channels destroy the middle layer.
  • Watch for themes across skip-levels, not anecdotes within one. One complaint is a data point; the same friction from three people is a finding.

Common 1:1 Mistakes (and Fixes)

MistakeWhy it happensFix
Status update in disguiseStatus is easy; the real topics are awkwardMove status to async/standups; open with the report’s topics, ban project rundowns unless there’s a decision needed
Cancelling when busy1:1 feels lower-stakes than “real work”Reschedule-never-cancel rule; track your own cancellation rate
Manager talks 80%Vacuum-filling, nerves, habitAim for the report speaking 60–70%; count silently for one meeting to calibrate
No written record”We both remember” (you don’t)Shared agenda doc/tool with a persistent action list
Feedback only flows downReport doesn’t feel safe; manager never asksPut report→manager feedback on the template so it’s routine, not an event
Growth discussed only at review timeUrgent crowds out importantGrowth thread every 2–3 sessions minimum, on the template
Same recycled “how’s everything?”No preparationQuestion banks; agenda posted before the meeting
Actions evaporateNo owner, no date, no reviewCarry-over review every session, manager items close first

Where AI Helps — and Where It Shouldn’t

A structured 1:1 practice generates real work: agendas, notes, action tracking, and the harder meta-skill of noticing your own patterns as a manager. This is the layer where AI is genuinely useful — as long as it stays in the assistant seat.

In Cadence, 1:1s run on structured shared agendas with durable meeting records, so the template above lives in the same place as your goals, recognition, and the rest of the management record instead of a lonely doc. Where enabled, AI meeting summaries turn the conversation into a clean record with the action items captured — so neither of you spends the meeting stenographing, and the carry-over review starts from an actual list. And in a private manager-lane AI coaching channel, managers can pressure-test their approach before and after the conversation: how to deliver a difficult piece of feedback, what they keep avoiding, why the last three 1:1s with one person went sideways. That coaching lane is private to the manager — a place to think, not a report to anyone. (Surfacing live goal context directly in the 1:1 sidebar is currently in Preview.)

The boundary matters more than the features. The conversation is the product; the AI is scaffolding. Summaries don’t replace listening, coaching prompts don’t replace judgment, and nothing in Cadence rates people or makes decisions about them — AI develops humans; humans own decisions. If an AI tool ever tempts you to skip the conversation because “the summary has it covered,” it’s being used wrong.

Your First Two Weeks

  1. This week: set the cadence (default: weekly, 30 minutes), send the recurring invites, and share the template above with each report — tell them section 2 is theirs.
  2. Next week: run the first structured session. Expect it to feel slightly stiff; templates loosen with repetition.
  3. Session 3 onward: enforce the carry-over review, rotate in one question-bank question per meeting, and put your own cancellation rate and action-close rate somewhere you’ll see them.

Six weeks of this, consistently, will change what your reports bring to you — because they’ll finally believe the meeting is real.

FAQ

How often should managers have 1:1s with direct reports? Default to weekly for 30 minutes — especially for new reports, new managers, and remote or hybrid teams. Biweekly 45-minute sessions work for established senior reports in stable periods. Monthly is too infrequent for direct reports; it turns the 1:1 into a mini-review instead of a working relationship.

Who should set the agenda for a 1:1 meeting? The report owns the agenda content — their topics go first — while the manager owns the system: cadence, shared template, notes, and action follow-through. Both add items to a shared agenda before the meeting so nobody is ambushed and “so, what’s up?” meetings disappear.

What should you talk about in a 1:1 besides project status? Career and growth, workload and energy, blockers and decisions needed, and feedback in both directions. Move routine status to async channels. Use rotating questions like “what’s taking more energy than it should?” and “what’s one thing I could do differently that would help you most?”

Can AI take notes in 1:1s without making them feel less personal? Yes, if it stays in the assistant seat: AI summaries capture the record and action items so both people can be present, and private AI coaching helps managers prepare for hard conversations. In Cadence these run where enabled, the manager coaching lane stays private to the manager, and AI never rates people or replaces the conversation itself.


Want the template, the record, and the follow-through in one place? See how the 1:1 engine works at cadencehr.ai/product, or check plans at cadencehr.ai/pricing.