Working Agreement
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
A team practice from agile and organizational development, in which members jointly define how they will work together and hold each other to it. The core proposition is that unstated expectations are the main source of friction, so writing them down converts private assumptions into shared commitments. The key qualification is that the agreement must be reviewed and revised, since a document written once and ignored adds ceremony without changing behavior.
SCAFFOLDING EFFECT
Reduce cognitive load
- Expectation surfacing: write down the assumptions the team has never stated aloud. - Commitment step: have each member explicitly agree to the rules. - Review cycle: revisit the agreement regularly and revise what no longer fits.
Anchor fast decisions
When expectations stay implicit, each person acts on their own version and interprets the same event differently, so friction appears without any disagreement about the work itself. Writing the rules down makes the differences visible while they are still cheap to resolve. Joint authorship also creates ownership, which raises the cost of quietly ignoring the agreement later.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- atlassian.comhttps://www.atlassian.com/team-playbook/plays/working-agreementsverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS