How to run 1:1s where the action items actually get done

Almost every guide to one-on-one meetings is about the half hour itself: build rapport, ask open questions, listen more than you speak, do not let it become a status report. This is all true and none of it is the hard part.

The hard part is the fortnight afterwards.

Something gets agreed. It goes into a notes doc. Neither of you opens that doc again. Three weeks later the work has not happened, and nobody is quite sure whose it was — so it gets raised as though for the first time, or quietly dropped and remembered as a small resentment. Do that four times and your report stops believing that saying something in a 1:1 leads anywhere.

That is what makes 1:1s feel pointless. Not the questions.

Why action items disappear

Three reasons, in order of how often they are the culprit.

The commitment has no owner. "We should look at the onboarding flow" is not a commitment, it is a topic. Nobody wrote down who, and each of you left assuming the other might. This is the most common failure and the easiest to fix.

The commitment has no date. An action item without a deadline cannot be late, so it is never surfaced by anything. It just sits. Deadlines are not pressure; they are the mechanism by which a system can tell you something has slipped.

The commitment lives somewhere nobody works. This is the structural one. Your 1:1 notes are in a doc, a notes app, or a dedicated meeting tool. Your team's actual work is in a task tracker. The action item was written in the first place and needs to end up in the second, and that transfer depends entirely on somebody remembering to do it.

The structure

Four parts, in this order. The order matters more than the content.

1. Since last time (5 minutes)

Open with what was agreed last time and whether it happened. Not a general "how's it going" — the specific list.

This does three things. It makes clear that commitments are tracked, which changes how carefully both of you make them. It gives your report a chance to say "I didn't do it because X", which is usually more useful than the task itself. And it stops the same item being raised as new three weeks running.

If something has been open for a month, say so plainly. Not as an accusation — as information. Usually it means the thing was never actually important, and the honest move is to drop it rather than carry it for another six weeks.

2. Their agenda (10 minutes)

Whatever they wanted to raise. This goes before yours deliberately: if you go first you will fill the time, and the thing they were nervous about asking will not get asked.

The best version is a running list either of you can add to between meetings, so nobody has to remember in the moment. A point added on Wednesday when it was annoying is a much better agenda item than one recalled on Friday.

3. The work (10 minutes)

What they finished, what is blocked, and what has gone quiet. Note that "gone quiet" is a separate category from "blocked" — blocked means they are waiting on something identifiable, quiet means nobody has looked at it. Quiet items are the ones that slip, because there is no moment at which they announce themselves.

Do not narrate the whole board. If your tooling can group it into finished / blocked / no movement, you can cover a fortnight in a few minutes and spend the rest on the two items that need a decision.

4. Close the loop (5 minutes)

Before ending, say the commitments out loud, with owners and dates. Both directions — a good share of what gets agreed in a 1:1 is the manager's job. "I'll get you access to staging" is a commitment, and if only your report's items get written down, the meeting quietly becomes a place where obligations flow one way.

Then put them where the work lives, not where the notes live.

Questions worth asking

Rotate these rather than working through them all. The aim is a real answer, not coverage.

• What's the most frustrating part of your week right now?
• What are you working on that you're not sure matters?
• Is there a decision you're waiting on from me?
• What would you do differently if this were entirely your call?
• What's something you've learned recently that surprised you?
• Where do you want to be better in six months, and is your current work getting you there?

The two that consistently earn their place are the second and the third. "Work you're not sure matters" surfaces misalignment before it becomes wasted quarters. "A decision you're waiting on" surfaces the fact that you are the blocker, which is uncomfortable and usually true.

A template you can copy

1:1 — [name] — [date]

SINCE LAST TIME
- [ ] [commitment]  — owner, due
- [ ] [commitment]  — owner, due

THEIR AGENDA
- [added between meetings]

THE WORK
Finished:
Blocked:
No movement:

AGREED TODAY
- [ ] [what]  — [who]  — [when]

The bracketed owner and date in the last section are the only part that really matters. Everything above it is context; that is the output.

Cadence

Weekly for a new report or anyone in a fast-changing role. Fortnightly once things are settled. Monthly is not a 1:1, it is a check-in, and you will find yourself using it for status because there is too much ground to cover otherwise.

Never cancel. Shorten it to ten minutes if the week is chaos, but cancelling is the single clearest signal that the meeting is optional, and once it is optional it is dead. A 1:1 that gets moved is fine. A 1:1 that gets deleted teaches your report where they sit.

The part tools usually get wrong

Most 1:1 software holds the agenda and the notes, then syncs action items across to whatever task tracker you also pay for. That sync is a workaround for the underlying problem: the meeting and the work are in different systems, so the commitment has to be copied to become real.

It is worth asking what your setup does with a commitment made on a Tuesday. If the answer involves anyone remembering to move it somewhere, that is where your action items are going.

This is the specific thing TIBLR is built around: the 1:1 agenda comes from your report's actual work, a follow-up becomes a real task with an owner and a due date on the board your team already uses, and the next 1:1 opens with whether it happened. Nothing gets transferred, because nothing is in two places.

But the structure above works with a shared doc and some discipline. Start there. The tooling matters much less than opening every 1:1 with the same question: last time, we said these things would happen — did they?