The Team Code: How to Set Ground Rules Everyone Follows
A team working agreement is a short, co-created document where a team decides up front how it makes decisions, handles conflict, and disconnects — then captures the answers in a one-page "team code" everyone signs. Agreeing the rules together prevents friction instead of cleaning it up later, and the shared ownership is what makes people actually hold to it.
Most team friction doesn't come from bad people; it comes from unspoken, mismatched expectations. One person thinks decisions get made by whoever owns the task; another assumes everything goes to the manager. One treats a Slack message at 9pm as informational; another feels obligated to reply. Nobody discussed it, so everyone runs on their own private rulebook — and the clashes get blamed on personalities instead of on the missing agreement. A team working agreement fixes this by making the implicit explicit, together, before the conflicts happen.
Why unspoken rules cause most conflict
Every team operates by rules, whether or not they've been said out loud. The trouble is that unspoken rules are also unshared rules — each person filled in the blanks differently, and the gaps only become visible when they collide mid-project. By then it's a conflict, not a conversation. Deciding the rules in advance moves the discussion to a calm moment when no one's defensive, and it turns "that's just how Sam is" into "here's what we agreed." Writing it down and signing it adds the final ingredient: shared ownership, which is what lets the team hold each other to it without it feeling like the boss's policy.
How do we create team ground rules together?
You need the whole team, about forty-five minutes, and a single shared page. Do it together — that's the point.
- Run a short workshop, as a group. Get everyone in a room (or call). The agreement has to be built by the people who'll live by it; a code written by the manager alone is just a policy nobody owns.
- Answer how you make decisions. Talk through it explicitly. When do we decide by consensus, when does one owner call it, when does it escalate? Write down the actual answer your team agrees on, not a generic ideal.
- Answer how you handle conflict and how you disconnect. Two more high-friction zones. How do we raise disagreements — directly, in the moment, in a retro? And what's our norm on availability: are evenings and weekends off-limits, is there a response-time expectation? Name it.
- Capture it in a one-page code everyone signs. Distill the answers into a single page — short enough to actually be read. Then have everyone sign it, literally or symbolically. The signature turns a good discussion into a commitment the team can point back to.
A worked example
A team that keeps having low-grade tension runs the workshop. On decisions, they discover half the team was waiting for the manager to approve things the manager thought they owned — a bottleneck nobody had named. They agree: task owners decide within an agreed budget, escalate above it. On disconnecting, two people admit they feel they must answer late-night messages; the team agrees messages after 6pm carry no expectation of a reply until morning. It all goes on one page everyone signs. A month later, when someone fires off a late Slack, nobody panics — the code already said it could wait. The friction that used to get blamed on individuals just stopped, because the expectations were finally shared.
When a team working agreement is most useful
It's especially valuable for newly formed teams, newly merged ones, and remote or hybrid teams where norms can't be absorbed by osmosis. It's also a great reset for an established team whose recurring frictions all trace back to mismatched expectations. Keep it short — a code nobody reads is useless — and treat it as living: revisit it when it stops matching reality. And it only works if it's genuinely co-created; impose it from the top and you've written a policy, not an agreement.
The takeaway
Teams don't clash because the work is hard so much as because everyone's running a different unspoken rulebook. A team working agreement gets those rules out loud and onto one page — how you decide, how you fight fair, how you switch off — and the signatures turn it into something the team owns and upholds. Spend forty-five minutes writing it now and skip months of "that's just how they are."
This is one of Funstorming's 100 quests — bite-sized soft skills methods you actually put into practice, not just read about. Try it, then bring your result (or your sticking point) to the Funstorming community of practice (CoP), FunHub | Your Soft Skills Playground.
#funstorming #softskills