Ways-of-Working Agreement

Agree, as a team, the handful of rules that cause most friction when left unsaid: who decides what and how, which channel is for what and how fast people answer, and what happens when two people disagree. An optional section extends the agreement with team rituals and how to run them as experiments.

Team charters and working agreements have mixed research support from a thin base (Mathieu & Rapp, 2009). Vroom and Yetton's decision model has mixed support, validated mostly by its authors (Vroom & Yetton, 1973; Vroom & Jago, 2007). Disagree and commit is a practitioner heuristic (Bezos, 2017). SBI is practice, not research (Weitzel, 2000). Response times and review intervals are rules of thumb.

As a team member (not the manager): the agreement is written with the team, not for it, so your draft is a legitimate contribution. Fill it in alone, mark what you would change, and bring it to a team session or your one-to-one (9.1 Manager 1:1 Prep).

Use it when:

• A team is forming, merging or moving to hybrid or remote work.
• The same friction keeps coming back: late answers, decisions reopened, meetings that decide nothing.
• A retrospective shows that the problem is how you work, not what you work on.
• Use the optional Norms & Rituals Canvas section when you also want to design the rituals that keep the norms alive.

Skip it when:

• The friction is about who owns which work: use 4.2 Roles & Responsibilities Map.
• The issue is one conflict between two people: use 4.6 Conflict & Feedback Guide.

Teams run on norms either way. A team that writes its norms down can examine, enforce and change them; a team that does not is run by habits nobody chose. Team charter research found that early agreements on how to work together went with stronger performance trajectories, though the base is thin and the evidence mixed (Mathieu & Rapp, 2009). The decision modes here come from contingency thinking: Vroom and Yetton's (1973) model matched decision styles to situations, but its validation came mostly from its own authors. Principles such as disagree and commit come from Amazon's shareholder letters (Bezos, 2017): quotable and useful, but untested. The feedback step borrows SBI, a practitioner structure from the Center for Creative Leadership (Weitzel, 2000).

So the page does three jobs. Each principle must carry a real recent example, or it is decoration. Sorting decisions into modes keeps consensus from becoming the expensive default. Explicit response times exist because unstated expectations turn into resentment. The limit: an agreement only works if people point to it when a norm is broken.

Choose three principles the team actually wants to live by. For each, write what it means in this team and one real example from the last month.

Strong answer: "Write it down before we meet. Means: any proposal is shared in writing a day before it is discussed. Example: the budget change was posted on Tuesday, so Thursday's meeting took ten minutes." Not: "Respect" with no example.

Illustrative example: the company, roles and numbers are made up.

A six-person finance team at a Finnish food manufacturer works across two sites. Month-end is tense: questions arrive in four channels, and decisions made on one site are reopened on the other.

Section 1: "Write it down before we meet", "Ask early, not perfectly" and "Close the loop: say when something is done", each with a real example from the last close.

Section 2: changes to the month-end checklist move from consensus to "consult, then the controller decides", with two working days for comments. Only changes to the team's own working hours stay with consensus.

Section 3: team chat for quick questions (half a day), email for anything external or auditable (two working days), phone only when today's deadline is at risk. Core hours 9 to 14 at both sites.

Section 4: direct talk first; the team lead facilitates; the head of finance decides on priority conflicts.

Section 5: review at the first retrospective each quarter. At the first review, the team dropped one principle nobody could give an example of.