BoardSnap is an iOS app that reads kickoff meeting whiteboards and turns goals, scope definitions, owner assignments, timelines, and open questions into a complete kickoff document ready for immediate distribution.
Kickoff meetings set the entire trajectory of a project. What gets aligned in the kickoff tends to stay aligned; what gets left ambiguous tends to cause conflict six weeks in.
Whiteboards are the right surface for kickoffs. The team builds the scope together — writing it down in real time forces clarity that slides and pre-built decks don't. Who owns what gets decided with everyone watching. The timeline gets drawn, not assumed.
But the kickoff doc needs to be in everyone's hands by end of day. Not three days later, after someone has had to reconstruct what was actually decided from a blurry photo.
One sentence: what this project is for and what success looks like. This is the north star that everything else on the board connects to. Don't start drawing scope until the goal is written and agreed.
Two columns. In scope: what this project will deliver. Out of scope: what this project explicitly won't do. The out-of-scope column is often the most valuable — it prevents scope creep by making exclusions explicit.
Each in-scope item gets one owner. One person, not 'the team.' Write the owner's name or initials. If something doesn't have an owner, it's not in scope yet.
Weeks or dates across a horizontal line. Major milestones above the line; dependencies below. The visual shows the critical path at a glance.
Any unresolved issues that surfaced during the kickoff go in a dedicated section. Who resolves each one, and by when? Open questions without owners become blocker action items.
One snap. BoardSnap returns the kickoff document: goal, scope (in/out), owner table, milestone timeline, and open questions as action items. Send it before anyone checks their phone.
A complete kickoff document: project goal statement, scope definition (in and out of scope), owner table with deliverables and assignments, milestone timeline with dependencies, and open questions with owners and resolution timelines. Open questions become tri-state action items. The document is complete enough to be the project's official kickoff record.
A design agency's kickoff with a new client. The board defined three deliverables, identified two out-of-scope items the client had assumed were in scope (preventing a later conflict), and captured six open questions with resolution timelines. BoardSnap's document was in the client's inbox within fifteen minutes of the meeting ending.
A product team's kickoff for a Q2 feature build. The whiteboard captured the goal, scope, four owner assignments, a six-week milestone plan, and three open questions for engineering. The document replaced the usual forty-eight-hour wait for the meeting notes.
For any project over two weeks, yes. The whiteboard is what forces clarity — you can't be vague when you're writing on a shared surface. Meetings that use slides for kickoffs tend to have lower clarity and higher scope-creep rates.
Run the virtual portions first (intro, background, context), then do a quick in-person board session for the scope and ownership decisions — even if the 'in-person' is one person at a whiteboard in a video call. Or run it hybrid: physical board for the in-room team, shared screen for remote. Snap the board at the end.
Sixty to ninety minutes for most projects. Two hours for complex multi-team projects. Kickoffs longer than two hours usually mean the project isn't ready to kick off — the scope isn't defined enough to fill the time productively.
They become action items in the BoardSnap project — owned, dated, and tracked. The project AI chat can surface them: 'What open questions from the kickoff are still unresolved?' — useful for the first status meeting a week later.
Snap the board, ship the action items in ten seconds.