BoardSnap is an iOS app that reads working agreements whiteboards and turns communication norms, meeting expectations, decision rights, and availability standards into a structured agreement document the team co-signs.
Working agreements fail when they're imposed, not co-created. A list of norms someone wrote and posted to Slack gets ignored. A list of norms the team wrote together on a whiteboard and agreed to, line by line, gets followed — because every team member remembers being in the room when it was written.
The whiteboard is the medium that makes working agreements real. The process of negotiating the exact wording of 'we respond to Slack messages within four hours during core hours' — the debate about what 'core hours' means, the compromise on four hours vs. two hours — that's the team actually agreeing. Not just acknowledging.
BoardSnap captures what the team agreed to, not just what someone thought they agreed to.
Start by listing the specific friction points the team has experienced: unclear decision ownership, meeting bloat, async vs. sync confusion. Write these as the problems the working agreements are solving. This grounds the session in reality.
For each friction point, write an agreement: specific, behavioral, and measurable. Not 'we'll communicate better' — 'we'll post meeting agendas 24 hours in advance.' The specificity is what makes it enforceable.
Some agreements will have disagreement. Write the disagreement explicitly — what's the tension? — and work toward a compromise that both sides can live with. The compromise wording on the board is what becomes the agreement.
What happens when an agreement is violated? Write a clear process: direct conversation first, team discussion if unresolved, team lead if still unresolved. A working agreement without an escalation path is just a suggestion.
Mark some agreements as 'trial for one sprint' and others as permanent commitments. Trial agreements reduce resistance — it's easier to agree to try something than to commit to it forever. Mark them clearly on the board.
BoardSnap reads all agreements, the problem context for each, negotiation outcomes, escalation path, and trial/permanent designations. The output is a formatted working agreement document.
A working agreements document: the friction points the agreements address, each agreement in specific behavioral language, trial vs. permanent designation, an escalation process, and review cadence commitments. Pin it in the team's BoardSnap project so it's always available as context for future board sessions.
A fully remote team that had been struggling with async/sync boundaries. The working agreements covered response time expectations, meeting-free blocks, decision authority tiers, and documentation standards. BoardSnap captured all eighteen agreements across six categories. Three were marked as one-sprint trials.
Two teams that merged during a reorganization. Each team had different working norms — neither was wrong, they just needed to converge. The whiteboard session made the differences visible and generated a hybrid set of agreements. BoardSnap captured both the legacy norms and the new agreements side by side.
If you can't remember them without looking them up, you have too many. Aim for eight to twelve specific agreements organized into three to four categories. Fewer, more specific agreements are more effective than comprehensive coverage of every possible scenario.
A team charter covers the team's identity and purpose. Working agreements are operational — they cover the day-to-day mechanics of how the team works together. Most teams benefit from both. Build the charter first (mission, values, roles), then the working agreements (communication, decisions, meetings). See the team-charter use case.
Quarterly is a good default. Trial agreements should be reviewed at the end of the trial sprint — did they work? Should they become permanent, be modified, or be dropped? Snap the revised agreement board after each review.
Bring it up in the retrospective, not in a one-on-one. The whole team made the agreement; the whole team should address violations. If a specific agreement is consistently violated, that usually means it was unrealistic — revise it rather than enforcing something that doesn't work.
Snap the board, ship the action items in ten seconds.