A 1:1 meeting template that actually gets used

Most 1:1 templates die in week three. They start as a tidy shared doc with neat headings, and within a month they’re either abandoned or they’ve curdled into a status meeting — you reading off Jira, them nodding, nobody learning anything. The problem isn’t the template. It’s that the template was built for you to feel organised, not for the conversation to be good.

A 1:1 template that survives contact with reality does three things: it puts the report’s agenda before yours, it leaves room for the human part, and it ends with something written down. Here’s one that holds up, plus the variations you’ll need.

Why most templates fail

• They’re manager-first. If the first section is “updates from me,” you’ve told your report this meeting is about your needs. They stop bringing their own.
• They’re all status. Anything you can read in a tracker doesn’t belong in a 1:1. Status crowds out the conversations only a 1:1 can have — growth, friction, how someone’s actually doing.
• Nothing carries over. If last week’s commitments evaporate, the meeting has no memory, and people learn it’s low-stakes theatre.

The template

Built for a 30-minute weekly or biweekly 1:1. The time splits are a guide, not a stopwatch — the point is the order and the proportions, not the minutes.

1. Check in — 5 minutes

Start human. A genuine “how are you, really?” before any work talk. You’re reading the temperature and signalling that this is their time. If something’s clearly off, this is the whole meeting — drop the rest.

2. Their agenda — 10 minutes

Their topics come first, and they get the biggest slice. Whatever’s on their mind: a blocker, a decision they want input on, frustration, an idea, a career thought. If they routinely come with nothing, that’s a signal in itself — seed it with a question and ask them to bring one item next time.

3. Your agenda — 7 minutes

Now your topics — but not status. Use this for context they’re missing, priorities that shifted, a heads-up, or one piece of specific feedback. Feedback lands best here: timely, private and two-way.

4. Growth and feedback both ways — 5 minutes

Not every week, but on a rhythm you protect. Where do they want to grow? What stretch is next? And turn it around: “what could I do differently to support you?” The reciprocal question is what makes the whole thing feel like a relationship instead of a review.

5. Action items — 3 minutes

Close by writing down what each of you committed to, with an owner. Out loud: “so I’ll chase the staffing question, and you’ll spike the migration by Thursday — right?” This is the single most skipped and most important step. Without it, the meeting has no follow-through, and follow-through is what builds trust.

Variations you’ll need

One template doesn’t fit every relationship. Three common adjustments:

• A new report. For the first month, weight it toward context and expectations: how they like to work, how they want feedback, what good looks like, what’s confusing so far. Less growth talk, more onboarding.
• A remote or async report. Protect the check-in — it’s the connection you’re not getting in the hallway. Consider a shared doc they add to during the week so the agenda builds itself before you meet.
• A skip-level. Drop your agenda almost entirely. You’re there to listen: how’s their manager doing, what would they change about the team, what’s not reaching you through the normal channels.

What it looks like filled in

The template is easier to trust when you can see it move. Here’s a real-feeling 30-minute 1:1 with an engineer called Sam, mid-project:

• Check in (0–5). “How are you, actually?” Sam mentions the on-call week wiped them out. You note it — that’s a thread, not a throwaway.
• Their agenda (5–15). Sam wants to talk through a design decision they’re stuck on, and — once there’s space — admits the Ledger project feels like it’s drifting. You mostly ask questions.
• Your agenda (15–22). You share context on a shifting priority, then give one specific piece of feedback: their review comments last week were sharp and clearly helped a teammate.
• Growth and feedback (22–27). You ask what would make next quarter feel like progress; Sam wants more architecture work. You ask what you could do better, and they’d like earlier warning on priority changes — fair, and yours to fix.
• Action items (27–30). “I’ll get you into the platform design review and flag priority shifts sooner. You’ll write up the Ledger drift so we can look at it Thursday.” Written down, owners clear.

Notice how little of that was status. The delivery update took thirty seconds; the rest was the stuff only a 1:1 produces — a tired engineer, a drifting project, a growth signal and a piece of feedback about your own blind spot. That’s a meeting worth protecting.

Keeping it alive past week three

The template is the easy part. Keeping it from rotting into a status meeting takes two habits:

• Always carry the thread. Open by revisiting last time’s action items and open topics. A meeting with memory feels meaningfully different from one that resets every week.
• Capture as you go, not after. Notes you mean to write up “later” don’t get written. The agenda for next time should assemble itself from this time’s loose ends.

That’s the part a static doc can’t do for you, and it’s where CoManager’s 1:1 hub earns its place: every meeting arrives pre-loaded with open threads, last time’s follow-ups and the things worth watching, so the agenda is built before you sit down. Anything you commit to becomes a tracked action item with an owner and a due date — no retyping, nothing lost between meetings. And the offhand things you notice between 1:1s can be captured in two taps and resurface on the agenda at exactly the right moment.

Copy the template, adapt the proportions to your team, and protect the two habits. Do that and your 1:1s will still be worth having in week thirty — not just week three.