Working agreements built on a whiteboard — team norms captured in seconds.
Working agreements co-created on a whiteboard are more durable than those in a Confluence doc nobody reads. BoardSnap captures the agreements the team built together — in their words, on their terms.
Why agile coaches love this workflow
Working agreements are the operating system for how a team collaborates. When they're built on a whiteboard, through genuine debate about what behaviors actually matter, they stick. Teams who helped write their working agreements on a physical board live by them longer than teams who were handed a digital template.
BoardSnap preserves those agreements. Snap the working agreements board and get a structured list: each agreement, in the team's exact language, organized by category if you structured it that way. The agreements document is ready to display in the team room, pin in Slack, or add to the team handbook — the same day the session happens.
The exact flow
- Generate agreement topics through team discussion
Ask: 'What do we need to agree on to work well together?' Let the team generate the topics — communication norms, meeting behavior, code review standards, decision-making. Write each topic as it comes up.
- Draft agreements for each topic
For each topic, facilitate the team to a specific, behavioral agreement. Not 'be respectful' — 'assume good intent before escalating a disagreement.' Behavioral specificity is what makes agreements usable.
- Debate and refine each agreement
Working agreements only have value if the team genuinely agrees. Write the debates on the board — the refined agreement that emerges from debate is more robust than the first suggestion.
- Test each agreement against real scenarios
Ask: 'Would this agreement have helped in [specific recent situation]?' If yes, it's relevant. If no, revise or drop it.
- Snap the final agreements board
The BoardSnap summary is the working agreements document. Share it with the team through whatever channel they'll actually reference.
What you'll get out of it
- Agreements in the team's exact behavioral language — not generic norms
- Debates captured alongside the final agreements — the reasoning is preserved
- Agreements organized by category if the board used categories
- Same-day document ready to post in the team room and Slack
- Agreements revision history as the team evolves and re-negotiates
Frequently asked
How many working agreements should a team have?
Fewer is better. Eight to twelve specific, behavioral agreements that the team actually remembers is more valuable than thirty vague aspirations. Prioritize during the session — if the team can't rank their agreements, they have too many.
What's the difference between working agreements and a team charter?
A team charter covers the team's mission, values, and high-level ways of working — the 'why' and 'what.' Working agreements are operational — the specific 'how.' They complement each other. Many coaches build both.
What do I do when a team member consistently violates a working agreement they helped create?
Refer to the BoardSnap board — 'We agreed to X, and here's the board photo showing you wrote that agreement.' The physical record makes the coaching conversation concrete, not personal.
Agile Coaches: try this on your next working agreements.
Three taps. Action items in your hand before the room clears.