The action item graveyard

I've started calling it the action item graveyard. It's the place where all the good intentions from your last meeting are buried.

Here's how items end up there. The meeting ends. Everyone files out. There's a whiteboard covered in decisions and next steps. Someone — usually the PM or whoever organized the meeting — takes a photo of the board. Maybe they send it to a Slack channel. "Notes from today's session."

That photo is the eulogy. The action items are already dead at this point — they just don't know it yet.

### The taxonomy of action item death

I've watched action items die in several specific ways:

Death by vagueness. "Figure out the pricing model" is not an action item. It's a wish. Without an owner, a deadline, and a definition of done, it's just a thing someone said in a meeting. The board photo preserves the vagueness perfectly.

Death by ownership gap. In the meeting, everyone understood who was doing what. The implicit context of the room made it clear — Sarah was talking about the API, so obviously the API item is hers. Two days later, the photo doesn't have that context. Sarah sees the photo and assumes someone else is doing the API item. So does everyone else.

Death by format friction. The action items are on a whiteboard. The work happens in Jira. Between the board and Jira is a manual transcription step. Manual transcription steps don't happen, especially when it's 5pm on a Friday after a three-hour session.

Death by notification timing. The photo lands in Slack at 4pm. Everyone is in the middle of other things. They see it, file it mentally, and move on. By the next morning, the window to act on it has closed. The item sits in Slack history and is never opened again.

Death by second-meeting limbo. In the next meeting, someone says "did we ever follow up on the pricing model thing?" Nobody can remember. The item gets rediscussed, a new decision gets made, another photo gets taken. The cycle restarts.

### The problem isn't commitment

Here's what I want to push back on: the graveyard isn't primarily a discipline problem. Teams that lose action items aren't failing because they're lazy or uncommitted.

They're failing because the hand-off between the meeting and the work is broken. The format of the whiteboard (visual, contextual, implicit) doesn't match the format of the work (typed, explicit, assigned). Every action item has to pass through a manual translation step, and that step is where mortality happens.

Fix the translation step, and you fix the graveyard.

### What fixes the translation step

BoardSnap automates the translation. Snap the whiteboard, and within ten seconds you have:

• Action items extracted as a clean, typed list — not "the photo with the items somewhere on the left side."
• Each item in a tri-state model (open / in-progress / done) that makes ownership status visible at a glance.
• A summary that includes the implicit context from the board — the decisions that frame why each item matters.
• The whole thing inside a Project, so the next meeting's board is already connected to the history.

This doesn't guarantee every item gets done. Discipline still matters. But it eliminates the format friction and the ownership gap that cause items to die before anyone has a chance to act on them.

### The 48-hour window

There's a practical observation I've made from beta testing: action items that get into a system within 48 hours of the meeting get done at roughly 3x the rate of items that don't.

The window isn't about urgency. It's about the fact that meeting context decays. The implicit understanding you had in the room about why this item matters and what "done" looks like fades within a day or two. Items that land in a system while the context is still fresh get enough framing to actually execute. Items that get typed up a week later are just tasks with no story.

Snap the board before you leave the room. The action items will outlive the meeting.