1:1 Action Items: Follow-Ups That Actually Get Done
7 min read · Teammons Learn
Think back over your last five 1:1s and try to list the commitments that came out of them. Most managers can name one, maybe two, and can't say for sure whether anyone followed through. That's not a character flaw — it's what happens when action items are made verbally, owned by nobody, and stored nowhere. They evaporate within 48 hours, and everyone quietly agrees not to mention it.
The fix is not better memory or more discipline. It's a small, boring system: every commitment gets an owner and a due date, the list lives in exactly one place, and the next meeting opens by walking through it. Here's how to run that system end to end — and why your own follow-through matters more to your team's trust than almost anything else you do in a 1:1.
Why 1:1 promises evaporate
Watch a typical 1:1 end. Two people had a genuinely useful conversation, agreed on a few things, and walked out feeling good. Ten minutes later, both are in other meetings. Nothing about a conversation creates a task — talking feels complete the moment it ends, which is exactly the problem. The failure doesn't happen during the discussion. It happens in the last three minutes of the meeting and the ten minutes after it.
- The ownerless item. "The budget question should get sorted out." Sorted out by whom? Passive voice is where commitments go to die.
- The someday item. It has an owner but no date, so it loses every prioritization battle to anything with a deadline — forever.
- The mental note. Agreed verbally, never written. Two weeks later you each remember a different version, or neither of you remembers at all.
- The scattered item. One commitment lives in a Slack thread, another in your notebook, a third in their head. Three lists is the same as no list.
Every dropped item also carries a hidden cost: the next commitment made in that 1:1 gets taken a little less seriously. Evaporation compounds.
The anatomy of an action item that survives
A survivable action item has four parts: a named owner, an active verb, a concrete deliverable, and a date. "Sarah drafts the Q3 headcount proposal by Thursday" will probably happen. "Discuss headcount" never will. Compare:
- Evaporates: "Look into the conference budget." Survives: "Marcus emails finance for the L&D budget number by Wednesday."
- Evaporates: "Work on delegation." Survives: "Priya hands the weekly metrics report to Dev before our next 1:1 and tells me how the handoff went."
- Evaporates: "I'll talk to marketing." Survives: "I ask Jen whether the launch date moved and Slack you her answer by Friday."
Capture the item during the meeting, out loud, in your shared 1:1 notes: "Let me write that down — you're sending the draft to legal by Tuesday, right?" Saying it aloud doubles as a confirmation step. Surprisingly often, the other person will correct you on the spot — which means you just caught a misunderstanding two weeks early, for free.
End with a 60-second recap — and cap the list
Reserve the last two minutes of every 1:1 for a recap. The script is short: "Before we wrap — I count three items. You're sending the legal draft by Tuesday, I'm getting you an answer on the conference budget by Friday, and we're parking the reorg question until Kim is back. Did I miss anything?" Sixty seconds, and every item gets a final sanity check while you're both still in the room.
Then enforce a cap: two or three action items per meeting, total, across both of you. A 1:1 that produces seven action items has really produced zero — nobody is doing seven extra things on top of their actual job by next week. If the conversation generated more than three, pick the ones that matter and put the rest on the agenda as topics, not tasks.
Open the next 1:1 with last week's list
This is the single highest-leverage habit in this article. Spend the first three to five minutes of every 1:1 walking through the open items from last time — before new topics, before anything else. People do what gets reviewed. A commitment that will definitely come up next Tuesday behaves completely differently in someone's head than one that vanished into a doc nobody reopens.
Tone matters here. This is a rhythm, not an interrogation — "where did we land on the legal draft?" not "why isn't this done?" Every item gets one of four statuses, and each status has a move:
- Done — acknowledge it. Five seconds of "nice, that unblocks the vendor call" costs nothing and makes the whole system feel worth participating in.
- In progress — set a new date out loud and move on. No guilt required; dates move.
- Blocked — promote it to the top of today's agenda. Clearing blockers is one of the most valuable things you can do with this meeting.
- Dead — kill it explicitly and say why. Items that silently roll forward week after week teach everyone that the list is decorative.
Your follow-through is trust currency
There's a brutal asymmetry in every 1:1. You have several reports and dozens of open threads; each report has exactly one manager. You will forget some things you said in their 1:1. They will remember every single one. When you say "I'll find out where your promotion case stands" and then go silent for three weeks, they don't think "busy week." They conclude the topic doesn't actually matter to you — or that they don't.
The items that cost the most when dropped are career promises: the intro you offered to make, the stretch project you floated, the comp question you said you'd escalate. Those commitments usually come out of career development conversations, and dropping one does more damage than dropping five routine tasks, because it reads as a verdict on the person.
The standard to hold yourself to is visibility, not speed. "No update yet — the comp review got pushed to next month, I haven't forgotten" preserves essentially all of the trust. Silence spends it.
When items keep slipping, diagnose — don't nag
If the same report rolls the same item for the third straight week, resist the urge to simply push harder. Chronic slippage is usually a design problem with the item itself, not a character problem with the person. Run three checks:
- Is it too big? "Build the onboarding dashboard" isn't a week's action item, it's a project. Shrink it to the first physical action: "email Raj for the events data."
- Is it losing to real work? Action items sit on top of a full job. Decide together what this item beats this week — or move the date honestly instead of pretending.
- Was it ever really agreed to? People sometimes accept items just to end a discussion. Ask straight: "Do you actually think this is worth doing?" A candid no today beats three weeks of polite slippage.
And if it's not the items — if well-shaped, genuinely agreed commitments still slip across the board — then you're looking at a performance pattern. That deserves a direct, plainly delivered feedback conversation, not a fourth week of raised eyebrows over the list.
Keep the list where the conversation lives
None of this works if the action items live in four places. The system needs exactly one home per person: the same running agenda where you queue topics and keep notes. Items captured in your private notebook are invisible to your report. Items they keep in their own task app are invisible to you. Items in Slack threads are invisible to everyone within a week.
The mechanics matter less than the singularity. A shared doc per person works fine if you're disciplined about it; a tool like Teammons carries every unfinished action item forward onto the next meeting's agenda automatically, so the opening review is sitting there waiting for you. Either way, the test is the same: at any moment, both of you should be able to answer "what do we owe each other?" by looking at one screen.
Frequently asked questions
What's the best way to follow up on action items between 1:1s?
Mostly, don't — let the opening review of the next 1:1 be the follow-up, so accountability feels like rhythm instead of surveillance. Ping mid-week only when something is time-critical or blocking others, and make the ping about the work ("anything you need from me on the legal draft?") rather than the deadline.
Who should track action items from a 1:1 — the manager or the employee?
Capture them together in a shared doc during the meeting, but the manager owns the ritual of reviewing them every week. If tracking lives only in your report's head, you'll never know whether silence means "done" or "forgotten."
How many action items should come out of a single 1:1?
Two or three total, across both of you, is plenty. More than that means you're either running a status meeting or setting items up to fail — carry the extras forward as agenda topics instead.
What should I do if a direct report never completes their action items?
First check the items themselves — vague, oversized, or low-priority tasks slip for everyone. If well-shaped items still slip repeatedly, name the pattern directly in the 1:1 as a feedback conversation, not an escalating series of nudges.
Stop keeping the follow-up list in your head — a 1:1 tool that carries every open action item into the next agenda closes the loop for you.