47 Action Items, 2 Done

How many of your last offsite's action items ever shipped? An executive team I sat with spent three days at a beautiful venue last spring and left with 47 of them, grouped under five themes. The agenda was sharp. The conversations were honest. They flew home aligned, and the CEO called it, at Monday's all-hands, one of the best offsites the team had run.

Six months later I asked the chief of staff how many were done. He opened the Notion page. Two. Twelve had been worked for a while and quietly stalled. The other thirty-three had never been touched. The offsite had produced the look of decisions and almost none of the execution. The team had been telling each other it was productive without checking whether it had produced anything.

This is one of the most reliable ways an executive offsite fails, and it's structural. The offsite creates a burst of collective energy: three days of focused talk, dinners, no calendar noise. The team reads that energy as productivity, correctly. The action items come out of real alignment in the room. The alignment doesn't survive the return to normal operations.

Each executive goes back to their own team, their own backlog, their own quarterly OKRs, none of which included the new items. What felt urgent on day three now competes with work that already has budget, headcount, and a commitment behind it. It loses. Not by anyone's choice. The new items have no operational standing against work that already had it.

The decay has a shape. Week one, the team is charged and the items get attention. The chief of staff sends the recap. Two items get real work. Week two, the operating rhythm reasserts itself. A few more get picked up by the most disciplined people. Week four, the offsite fades and the Notion page opens less often. By month two the items are losing to the fires that started after everyone got home. It's the same failure as the retro that produces the same action items every sprint.

The failure isn't the offsite. The conversations were real. The alignment was genuine. What's missing is any machine for turning agreement into work. Most offsites end with items written down and no follow-up cadence attached. The page gets made. The team flies home. The next time anyone opens it is at the next offsite, where the team agrees execution was hard and writes a fresh list headed for the same fate. It's the OKR nobody could remember on Friday, at the leadership level.

The compounding cost is the team's faith in the format. Each dead cycle lowers their confidence that the next one will land differently. By the third or fourth round, executives show up to the offsite as a calendar obligation, not an opportunity. The energy that drove the first cycle's alignment gets harder to summon, because the team has learned the alignment won't convert. The format hardens into a ritual people perform without belief.

What changes the outcome is designing the follow-up before the offsite starts. Every item written in the room gets a named owner and a date for its first check. The first follow-up, usually a thirty-minute call within a week of getting back, is on the calendar before anyone leaves the venue. Its agenda is plain: status on each item, which ones are stalling, which ones the world has overtaken. The cadence runs monthly until each item is done or formally killed.

That pre-scheduled call changes the offsite's relationship to the operating year. The offsite stops being a three-day event followed by hope. It becomes the kickoff of an execution cycle that runs a quarter or two. The items carry operational standing because a cadence exists to hold them. The people who committed know they'll be asked, on the calendar, on a date.

The accountability lives on a public scorecard. The list sits somewhere visible, with status, owner, and date. The next monthly leadership meeting opens on it. The executive who hasn't moved explains why, in front of peers. The pressure isn't cruel. It's calibrated. After a cycle or two, the team learns that committing to something at an offsite carries a real tail.

The deeper habit is treating an offsite as the start of a quarter of work, not a finished event. The offsite is the alignment session. The quarter after it is where the work happens. Alignment without the quarter is inert. A quarter without the alignment is untargeted. They're complements, not substitutes.

Most teams treat the offsite as self-contained because it's the part that feels productive. The quarter of execution that should follow is where the outcomes come from, and that's harder than the feeling of alignment. Teams that build the cadence convert the alignment. Teams that don't produce forty-seven items, two completions, and a six-month wait for the next one.

If your last offsite left you with items that aren't done, build the cadence before you schedule the next one. The format isn't broken. The bridge from agreement to execution was never built.

Before you schedule the next offsite, ask:

• What share of the last offsite's items were done on the planned timeline?
• Is there a public scorecard for them, reviewed at monthly leadership meetings?
• For the next offsite, is the first follow-up call already on the calendar for the week after?
• Do commitments made at the offsite carry the same standing as the team's quarterly OKRs?

The measure was never how aligned the room felt on day three. It's how many lines on that Notion page have a date next to them, and how many of those dates held.