How many action items come out of a typical meeting?
Short answer
In a typical hour-long working meeting with a whiteboard, teams generate an estimated 5-15 action items — with retros and planning sessions at the high end and standups at the low end. In a typical hour-long retro, teams generate approximately 12-20 action items across the What went well / What didn't / Try next structure.
Action item counts vary significantly by meeting type, team size, and how structured the session is. Here are rough estimates by meeting format:
Daily standup (15-30 min): 0-5 action items. Most standups surface blockers and sync on status — few generate new commitments. When they do ("someone follow up with the API team on that timeout"), those items often don't get captured formally.
Sprint planning (1-2 hours): 8-20 action items. Story acceptance, dependency resolution, pre-sprint setup tasks, and team-level commitments. The whiteboard output tends to be dense.
Sprint retro (60-90 min): 12-20 action items. Typically the highest-density action item session. The three-column structure (What went well / What didn't / Try next) reliably surfaces a large number of items, and the Try Next column is entirely action items. Many teams generate more than they can act on.
Architecture or design session (60-90 min): 5-15 action items. Mix of design decisions to validate, implementation tasks to assign, open questions to research.
Strategy or planning session (2+ hours): 10-25 action items. High-level initiatives, owner assignments, deadlines for next steps, open items to resolve before committing.
Workshop (full day): 30-60 action items across all sessions. Workshop output is notoriously difficult to capture and act on — which is why post-workshop action item loss is a well-known facilitation problem.
Why this matters for tool selection
A team running 8 meaningful whiteboard sessions per week across these meeting types generates an estimated 60-120 action items weekly. If those items aren't captured in a structured, trackable format, a significant fraction evaporate. BoardSnap's tri-state action item list — generated automatically from the board snap — is designed to make sure every item from every session gets the same structure: open, in-progress, or done.
Caveat: These are estimates based on typical patterns, not published research. Actual action item counts depend heavily on team habits, meeting facilitation quality, and organizational culture.
Frequently asked
How does BoardSnap decide which items are action items?
BoardSnap AI reads the whiteboard content and identifies items that are phrased as tasks, commitments, or next steps — typically imperative verbs, named owners, or items in explicit 'To Do' sections. It applies a tri-state structure (open / in-progress / done) and generates subtasks where the main item is complex enough to warrant them.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.