Feeling buried under process and back-to-back meetings? Your team may not need another tool. It may need a shared, precise account of how good work moves.
The clearest working agreements are small enough to remember and specific enough to settle a real decision. They explain where ideas begin, who shapes them, when critique happens, and how the team knows a piece of work is finished.
What is a way of working?
A way of working is the repeatable pattern behind everyday collaboration. It includes the rituals people see—reviews, planning, decision logs—and the assumptions underneath them: who owns a call, how quickly a response is expected, and when focus time is protected.
Unlike policy, it should remain editable. Teams learn; the model should absorb that learning without losing its shape.
Four principles that carry the work
Strong models answer a few durable questions before they enumerate habits.
Name the purpose
Connect every ritual to an outcome. A review exists to sharpen a decision, not to fill a slot.
Make ownership legible
Show who recommends, who decides, and where informed disagreement belongs.
Protect attention
Choose communication channels by urgency so deep work is not treated as spare time.
Build in reflection
Review the model after real projects, while the friction is still specific enough to fix.
Build your model in five passes
1. Audit the week you actually have
Start with calendars, handoffs, and decisions from the last ten working days. Mark where work waited, where a meeting shortened a loop, and where a quiet hour produced more than a crowded afternoon.
2. Choose the principles you can defend
Turn the patterns into four or five statements with edges. “We communicate clearly” is too soft; “we document decisions where the work lives” is observable.
3. Set explicit working agreements
- Communication: which channel serves which level of urgency.
- Planning: when priorities are shaped, named, and revisited.
- Decisions: who has the final call and how context is recorded.
- Recovery: how the team handles overload before it becomes attrition.
4. Pilot with one real project
Run the model in a project that matters but is not existential. Note every exception. Exceptions often reveal a missing principle more clearly than a workshop does.
5. Retire what adds ceremony
A model should become lighter as the team becomes fluent. Remove recurring steps that no longer change a decision or improve the work.
“The best operating model is not the most complete one. It is the one people can still use on a difficult Thursday.”
Rhea Solomon · Work practice editor
Adapt it for distributed teams
When people do not share a room or a time zone, agreements must carry more context. Name the response window for each channel, keep decisions next to the work, and let asynchronous review be a designed process rather than a delayed meeting.
Distributed work also needs intentional overlap. Reserve the scarce shared hour for debate, synthesis, or care—the things whose texture disappears in a thread.
Choose principles over process
Process describes the expected path. Principles help people choose when the path no longer fits. A healthy team needs both, but only one of them survives a novel problem.
The leader’s role is to make change safe
Leaders make the model credible by following it in public: sharing context before asking for a decision, protecting quiet time, and changing a ritual when the team can show it no longer earns its cost.
Measure progress without noise
Track evidence that reflects the work itself: time from question to decision, the number of unresolved owners, and whether people can name the week’s priority in the same language.
intentclear ownershipprotected attentionhonest reflectionvisible decisions
Begin at the center. Add only the agreements that protect it.
Revisit these signals every six weeks. The goal is not a perfect score; it is a smaller gap between the work the team describes and the work people experience.