Your team has norms. You wrote them in a kickoff meeting. "We communicate openly. We respect each other's time. We make decisions together." Everyone nodded. The list went on a slide.
Then the hard week came. The deadline moved up. Two people disagreed and one of them went quiet instead of speaking up. A decision got made in a side conversation. Nobody mentioned the norms, because in that moment the norms were not real.
You do not have a team norms problem. You have a "norms that only work in calm water" problem. A team working agreement is worthless until pressure tests it. The good news is you can find out which of your norms survive before a real crisis does.
What a Team Working Agreement Actually Is
A team working agreement is a short set of norms your team agrees to live by. How you make decisions. How you handle disagreement. What you owe each other on time, prep, and follow-through.
The word that matters is "live." A working agreement is not the list you write. It is the behavior you fall back on when things get hard and people start pulling in different directions. If the agreement only shows up when the room is relaxed, it is not an agreement. It is a wish.
This is the line between a working agreement and a team charter template. A charter sets the structure — purpose, decision rights, who owns what. A working agreement sets the daily behavior — how you actually treat each other meeting to meeting. You need both. This post is about the behavior, the norms, the small habits that either hold under pressure or fall apart.
Team Norms Examples That Actually Hold
Most team norms fail because they are vague. "We trust each other" cannot be observed, so it cannot be kept or broken. A real norm is specific and visible. You can watch a meeting and tell whether the team followed it.
Here are examples of team norms that hold, each written so you could score it by watching one meeting.
Decision-making: We decide and move within one meeting. We do not revisit a closed decision unless new facts show up. The tell is how many times the same decision comes back to the table.
Idea flow: We acknowledge an idea before we challenge it. No reflexive "yes, but." We build with "yes, and." The tell is how many ideas die in the first ten minutes.
Disagreement: We raise it in the room within 48 hours, with the person, not in the hallway after. The tell is the gap between what gets said in the meeting and what gets said after it.
Time: We read the doc before the meeting. We start on time and end on time. The tell is how many minutes the first ten of every meeting spend catching people up.
Follow-through: What we commit to in the room actually happens. We do not relitigate last week's agreements. The tell is how many items on this week's list were also on last week's.
Notice what these have in common. Each one names a behavior, not a feeling. Each one has a tell — a thing you can count. That is the difference between a norm and a poster. For leadership teams especially, norms have to be this concrete, because senior people are skilled at sounding aligned while quietly going their own way.
Why Most Team Norms Don't Survive the First Hard Week
A norm written in a calm room is agreed in principle. It is not agreed in practice — because the team has not yet seen what keeping it looks like when it costs something.
The norms above will feel obvious in a kickoff. The team will sign off and move on. Then the first real test comes. Two people disagree on direction. The norm says raise it directly within 48 hours. One does. The other ducks it, pulls in a third person to take their side, and brings the disagreement to the next meeting framed as a team problem.
Now the team has a choice. Hold the norm and name the duck, or let it slide because naming it feels confrontational. Most teams let it slide. From that moment the norm is dead, even though it still sits on the slide.
This is why writing the agreement is the easy part. Living it is the hard part. And living it takes a team that has practiced what holding the line feels like — before the moment when holding the line is expensive. What a team writes about itself and what a team does under pressure reveals everything, and the two are rarely the same.
The One Move That Shows You Which Norms Are Real
You cannot find out which of your norms survive by asking people. They will tell you the answer they wish were true. You find out by putting the team in a situation with enough pressure that the real behavior comes out, then watching.
That does not mean waiting for a real crisis. By the time a real iceberg hits, the cost of finding out is the project itself. It means building a contained, high-pressure situation on purpose.
This is what an immersive simulation does. In the Save the Titanic experience, your team becomes the senior officers on the ship in the minutes after the iceberg strikes. Limited time. Limited information. 2,200 lives on the line. In three and a half hours, every norm gets tested in the open.
Your decision norm gets tested when nobody is sure who calls the shot. Your idea norm gets tested when someone offers a half-formed idea and the clock is running. Your disagreement norm gets tested when two officers want to go different directions and there is no time to be polite about it. You cannot fake any of it under that kind of pressure, which is the whole point.
Then you debrief. The debrief is where the read becomes useful, and it is the part most teams skip. A structured debrief turns what the team just did into a clear picture of which norms held and which cracked. If you want the structure, decision-making frameworks for teams shows the patterns a good debrief surfaces, so the team leaves with a working agreement built on what it actually does — not what it hoped it did.
How to Build a Working Agreement That Lasts
Start with the five norms above. Write your team's version of each in concrete language. Not "we communicate openly." Write "we raise concerns to the person directly within two days, not through back channels."
Then test it. Do not wait for a real crisis to learn whether it holds. Run a pressure test, watch the five norms, and debrief against them. Pair the test with a regular read on the team between crises — a simple team health check template that scores the same behaviors red, yellow, or green so a fracture line shows up while it is still small.
Then revisit on a cycle. A working agreement is not a fixed thing. It moves with new members, new pressure, and new stakes. The team that scored five greens in March can grow a red by June. The teams that stay strong are the ones that check behavior often and fix the reds early.
ArcelorMittal ran 710 leaders through the experience in partnership with Duke Corporate Education and came out making decisions 30 to 40% faster. That speed did not come from a better norms list. It came from leaders who had now seen, under pressure, what their team's actual patterns were — and could repair them on purpose. Bell MTS moved from $800 million toward $1.4 billion in revenue in a single year on the back of leadership teams that could finally see and fix how they worked together.
A working agreement gives your team the norms. A pressure test tells you which ones are real. Put them together and you stop being surprised by your own team — because you found the fracture lines in a simulation, not in the crisis.
Read next: A Team Health Check Template That Measures Behavior, Not Opinions