BoardSnap is an iOS app that reads team charter whiteboards and turns mission statements, team values, operating principles, role definitions, and mutual commitments into a structured charter document the team co-owns.
Team charters written by one person and sent to the team don't work. Nobody co-owns a document they didn't help create. The charter that lives in a Notion page nobody visits and a Slack channel nobody reads is every team's first failed cultural experiment.
A team charter built on a whiteboard — together, in real time — is different. Every line was written or approved by someone in the room. The process of agreeing on the wording of 'we are committed to X' is itself the commitment.
BoardSnap captures what the team built so it doesn't live only in the whiteboard photo that nobody revisits.
One or two sentences: why this team exists and what it's responsible for. Not corporate-speak — actual language the team uses. Write multiple drafts and let the team vote with dots.
Three to five values, each with a one-line behavioral definition. Not 'we value transparency' — 'we share information before we're asked.' Specific behaviors, not abstract nouns.
Each role on the team, with what it owns. Avoid overlap and gaps — if two roles both claim ownership of a decision type, resolve it now. DACI or RACI models work well on a whiteboard.
How does the team work? Meeting cadence, decision-making process, how disagreements get resolved, communication norms. Write them as statements the team can be held to.
What does each team member commit to the others? What can team members expect of each other? This is the most personal section — it requires real conversation, not just writing.
BoardSnap reads the mission, values, roles, operating principles, and commitments as a charter document. Publish it immediately while the session's energy is still present.
A team charter document: mission statement, values with behavioral definitions, role and responsibility map, operating principles, and mutual commitments. The document is structured as a living agreement — pin it in the BoardSnap project so it's always accessible as context for future boards.
A newly assembled product team built their charter in a two-hour offsite session. The whiteboard produced a mission statement (third draft, not first), four values with specific behavioral definitions, and seven operating principles. BoardSnap's document was published to the team Notion page within the hour.
An existing team that had been reorganized around a new product area. The old charter no longer applied. The new charter whiteboard session helped the team rebuild trust and alignment. BoardSnap captured the output — a document the team referenced explicitly for the next six months.
A team charter covers the team's identity and purpose (mission, values, roles) as well as how it operates. Working agreements focus specifically on the how — communication norms, meeting expectations, decision processes. The charter is broader; working agreements are more tactical. See the working-agreements use case for the operational specifics.
For teams that have low trust or significant disagreement, yes — an external facilitator keeps the session productive. For cohesive teams, a designated team member can facilitate. The key is that the team lead participates as a team member, not as the authority, so the charter is genuinely co-owned.
When the team changes significantly (new members, reorganization), when the mission changes, or when the charter isn't being followed. Annual check-ins are a minimum. Snap each revision — the evolution of the charter is itself a record of the team's growth.
Yes. Use BoardSnap's pinned context feature to pin the charter in the team's project. Every future board in that project is analyzed with the charter as background context — the AI summaries are automatically calibrated to the team's stated values and commitments.
Snap the board, ship the action items in ten seconds.