Why taking time to agree how you work is not a luxury—it is a performance discipline
Most teams are assembled around what they need to achieve. They are given a target, a deadline, a set of responsibilities and, if they are fortunate, enough resources to begin. Then everyone gets to work.
What is often missing is a deliberate conversation about how they will work together.
How will decisions be made? What does good communication look like? When is consultation essential, and when should someone simply act? How will the team challenge ideas, raise risks and deal with disagreement? What does ownership mean in practice? Which behaviours will help people do their best work—and which will quietly undermine it?
These questions can sound secondary when the pressure is on. They are anything but. A team that does not discuss how it wants to work does not avoid creating norms. It simply creates them accidentally.
The fastest voice becomes the dominant voice. Silence is interpreted as agreement. Responsiveness becomes confused with commitment. Meetings multiply because decision rights are unclear. Frustrations are discussed privately rather than resolved directly. Some people over-function, others step back, and the team gradually builds a culture no one consciously chose.
Taking time out to clarify and agree how the team will work is therefore not a retreat from performance. It is how performance becomes possible.
Every team already has an operating system
A team is not just a collection of capable individuals. It is a social system. Its results depend not only on the quality of each person’s contribution, but on how well those contributions combine.
That combination is governed by an informal operating system: the assumptions, habits and expectations that determine how work moves between people. In some teams, the operating system is explicit. People know who owns what, where information lives, how decisions are recorded and how concerns should be raised. In others, it exists as a patchwork of personal preferences and unspoken rules.
The difficulty is that people arrive with very different definitions of “normal.” One person sees a same-day response as basic courtesy; another protects long periods of focused work and checks messages twice a day. One leader invites debate but expects the team to unite quickly once a decision is made. A colleague may interpret continued disagreement as healthy scrutiny. One person thinks asking for help demonstrates good judgement; another worries it will be seen as a lack of competence.
None of these preferences is inherently wrong. The problem is assuming they are shared.
When expectations remain invisible, people explain one another’s behaviour in personal terms. A delayed response becomes disengagement. Directness becomes aggression. Caution becomes resistance. Speed becomes recklessness. Instead of recognising a difference in working assumptions, we make a judgement about character.
This is one reason seemingly small tensions can become surprisingly expensive. The task may be straightforward; the meaning people attach to one another’s behaviour is not.
Clarity reduces the tax of coordination
Ambiguity consumes attention. When people are unsure who can decide, how much detail is required or whether they are expected to consult, they spend valuable energy interpreting the system around the work.
They send messages “just to check.” They attend meetings “just in case.” They copy more people into emails to protect themselves. Decisions are revisited because it is not clear whether they were actually made. Work is duplicated because ownership is fuzzy. Important issues wait because everyone assumes someone else is handling them.
This is the coordination tax: the time and cognitive effort required to navigate unclear ways of working.
A good team agreement reduces that tax. It gives people reliable answers to recurring questions. Not rigid rules for every possible situation, but useful defaults: where decisions are made, when escalation is appropriate, what “done” means, how quickly different channels should be answered, and how the team keeps one another informed.
The value is not bureaucracy. It is freedom from unnecessary ambiguity.
Paradoxically, clear working agreements make teams more adaptable, not less. When the basic mechanics are understood, people can use their judgement where it matters. They do not have to renegotiate the relationship every time the work changes.
Agreement creates the conditions for candour
The most valuable information in a team is often the hardest information to share: a concern about a decision, an early warning that delivery is slipping, an admission that someone does not understand, or a view that challenges the prevailing consensus.
People do not assess the safety of speaking up from a values statement on the wall. They assess it from repeated social evidence. What happens when someone says, “I think we are missing something”? Does the team become curious or defensive? When a mistake is disclosed, is the first response blame or learning? When a junior colleague disagrees, does their contribution receive the same consideration as a senior person’s?
Teams can make these expectations discussable before the difficult moment arrives. They can agree that challenge is an obligation, not an act of disloyalty. They can define how to disagree without becoming disagreeable. They can separate scrutiny of an idea from judgement of the person offering it. They can make it legitimate to say, “I need help,” “I see a risk,” or “I have changed my mind.”
This does not manufacture psychological safety through a workshop. Safety is built—or damaged—through everyday behaviour, especially the behaviour of those with the most status. But an explicit agreement gives the team a shared standard against which that behaviour can be noticed and corrected.
It turns candour from a personality preference into a collective practice.
The conversation matters as much as the document
There is a temptation to solve ways of working by downloading a template, filling in a few boxes and publishing a team charter. The resulting document may be tidy and almost entirely irrelevant.
The real value lies in the conversation.
When team members discuss what helps them contribute, they learn about one another’s pressures, preferences and working rhythms. When they debate how decisions should be made, hidden assumptions become visible. When they name behaviours that damage trust, they create a language for addressing them later. The process produces mutual understanding as well as practical clarity.
That means the agreement should not be written by the leader and presented for endorsement. Power matters. If the most senior person defines the rules, speaks first on every question and treats silence as consent, the team may comply without truly agreeing.
A better process invites independent thought before group discussion, gives everyone a voice and makes differences legitimate. The leader participates, but does not monopolise. Where hierarchy creates a genuine constraint—such as formal accountability for a decision—it should be stated plainly rather than disguised as consensus.
Agreement does not mean every person gets their preferred way of working. It means the team understands the choices it has made, the reasons for them and what each person can reasonably expect from the others.
What great teams make explicit
A useful working agreement is short enough to remember and specific enough to influence behaviour. It usually addresses a handful of practical questions.
Purpose and priorities. What is the team here to achieve? When demands compete, what takes precedence? Without a shared view of priorities, people can work hard in opposing directions.
Roles and ownership. Who is accountable for which outcomes? Where do responsibilities overlap? What does ownership require beyond completing an assigned task?
Decision-making. Which decisions are individual, consultative or collective? Who has the final call? How will decisions and their rationale be recorded? A team should distinguish between having a voice and having a veto.
Communication. Which channels are used for urgent matters, routine coordination, complex discussion and formal decisions? What response times are reasonable? What information should be pushed proactively rather than requested?
Meetings. What deserves a meeting? What preparation is expected? How will the team ensure that discussion produces a decision, action or learning rather than merely occupying time?
Challenge and conflict. How will people raise concerns? What behaviours keep disagreement productive? When should an issue be addressed directly, and when should it be escalated?
Reliability and support. How will people signal that a commitment is at risk? When should they ask for help? What does the team owe someone who is overloaded or stuck?
Learning and review. How will the team reflect on its performance, discuss mistakes and improve the way it works? What evidence will show whether the agreement is helping?
The best answers are behavioural. “We communicate openly” is an aspiration. “We raise material risks as soon as we see them, even when the picture is incomplete” is a usable commitment. “We respect one another” is admirable but vague. “We challenge the argument without questioning the person’s motives” gives people something they can practise.
A working agreement must remain alive
No team can design the perfect operating model in one sitting. New members join. Pressure changes. Dependencies emerge. A practice that worked during a stable period may fail during rapid growth or crisis.
The agreement should therefore be treated as a hypothesis, not a constitution.
Teams can begin with a small number of commitments, use them for several weeks and then review: What is helping us? Where are we still losing time? Which agreement is routinely ignored—and why? What conversation are we avoiding? What needs to change for the next phase of work?
This review is crucial. An agreement that is never revisited becomes corporate archaeology: evidence of good intentions from another time. A living agreement becomes a tool for collective self-correction.
The team should also use it in the moments that matter. When a meeting drifts, someone can point back to the agreed purpose and decision process. When a concern surfaces late, the team can examine whether its norms made earlier disclosure difficult. When conflict becomes personal, the group can return to its commitment about challenge. The document earns its value when it changes what happens next.
The leader’s role is to make the implicit discussable
Leaders often feel pressure to provide answers. In this context, their greater responsibility is to create the conditions in which the team can produce clarity together.
That means protecting time for the conversation even when operational demands feel urgent. It means being honest about what is negotiable and what is not. It means listening for the voices that are absent, not only the voices that are loud. Most importantly, it means modelling the agreed behaviours when doing so is inconvenient.
If the team agrees to welcome challenge but the leader punishes dissent, the real norm is punishment. If it agrees to surface risks early but reacts harshly to bad news, the real norm is concealment. If it agrees to protect focus but the leader sends indiscriminate late-night requests, the real norm is permanent availability.
Culture is not established by the commitments a team announces. It is established by the behaviour it repeatedly rewards, tolerates and corrects.
Time out creates better time in
The objection to this work is almost always the same: “We are too busy.” Yet busyness is precisely why the conversation matters.
Teams under pressure cannot afford chronic misunderstanding, duplicated effort, hesitant decisions or preventable conflict. They cannot afford to have their most thoughtful people remain silent because the rules of engagement are unclear. They cannot afford to depend on mind-reading.
An hour spent clarifying how the team will decide, communicate, challenge and support one another can save many more hours of friction. More importantly, it can improve the quality of judgement, strengthen accountability and make it easier for people to contribute at their best.
Great teamwork is not the product of goodwill alone. Nor does it emerge automatically when talented people share a goal. It is designed through explicit choices, tested through experience and sustained through honest review.
The question is not whether your team has a way of working. It already does.
The question is whether it is the way of working you would choose.
