Under Pressure, Every Department Becomes a Territory

In an ordinary week, the groups around a shared problem bring different and legitimate perspectives to it. Put the organization under pressure and those same perspectives stop being contributions and start being positions that each group defends.

Three months ago the people in the room with you were working together well enough that you did not think about it. Finance raised the cost questions, operations raised the questions about whether anything could actually be delivered, the people who deal directly with the public raised what it would feel like on their end, and whoever handles compliance raised the risks nobody else wanted to look at. The meetings were not always pleasant, but when they ended, most people left with a better picture than the one they brought in.

Then something went wrong. A budget got cut in the middle of the year, or an outside review started, or a failure became public and everyone above you wanted to know how it happened. Now the same people sit in the same room and the meetings feel different. A question about cost is heard by operations as an accusation. A concern from compliance is heard by the front line as another reason nothing can get done. Someone forwards an email with a single line added at the top, and three groups spend the afternoon discussing what that line was meant to say. Nobody in the room has changed their job, and nobody has become less capable. What has changed is how each group reads the others.

The mechanism is a shorter distance between a signal and a hostile reading of it

In a calm week, an ambiguous message gets the benefit of the doubt, mostly because nobody has time to think about it very hard. A short reply is read as a busy person replying. A delay is read as a delay. The reader has no particular reason to look for a motive, so they do not find one.

Pressure changes that. When people are worried about their budget, their standing, or their jobs, they start reading messages for what the messages might mean about those things. A short reply now looks like a rebuke. A delay looks like someone positioning. A question in a meeting looks like a group building a record in case the blame has to go somewhere. Each reading is a small step, and each one makes the next hostile reading a little easier, because now there is a pattern to fit it into.

Once that starts, each group does something that is entirely reasonable from inside it. They protect their own account of what happened. They write things down more carefully. They copy more people on messages. They stop offering the half-formed concern they would have mentioned three months ago, because a half-formed concern can be quoted back at them later. The groups are no longer comparing their versions of the situation to find the true one. They are each holding their version and defending it, and the problem that brought them into the room in the first place gets less attention than the question of who will be held responsible for it.

What the territory costs

The perspectives you need most go quiet first. The value of having several groups around a problem is that each one sees a part of it the others cannot. When people start defending positions, they share only what supports their position and keep back what complicates it. The concern from compliance that would have saved you a month, or the observation from the front line that the new process will not survive its first busy Monday, never gets said out loud, because saying it would hand another group an argument.

Your decisions start to track the loudest account, not the most accurate one. When every group arrives with a prepared version of events, you end up choosing between versions rather than looking at the situation. The group with the most polished account, or the most senior person, or the most recent conversation with you, tends to win. That is not a decision about the problem. It is a decision about which group you trust this week, and every other group in the room can see it.

The damage outlasts the pressure. The review ends, the budget settles, the public attention moves on. The readings people formed of each other during those months do not reset when the pressure lifts. Operations still remembers what finance said in March. The front line still believes compliance was protecting itself. Groups that used to trade information informally now route it through formal channels, and the formal channels are slower. You get the calm week back without getting back the working relationships that made the calm week productive.

Three moves

Name the pattern in the room before it hardens. People inside a territorial stretch rarely see it as territorial. They see it as the other group becoming difficult. Say out loud, early, that pressure changes how everyone reads everyone else, and that you expect it to happen here too. This does not stop it, but it gives people a way to describe what they are seeing without accusing a colleague, and it makes the hostile reading a little less automatic.

Put the shared problem on the table in a form no single group owns. When each group brings its own account, ask for the facts before the interpretations. What happened, in order, with dates, written in one place that everyone can see and correct. A single timeline that four groups have edited is much harder to defend a position against than four separate memos, and building it together pulls people back toward comparing their pictures rather than protecting them.

Protect the half-formed concern. Make it explicit that raising a possible problem early will not be held against the person who raised it, and then keep that promise the first time it is tested. The first time someone says "I am not sure, but I think this might break" and is treated as having helped rather than as having exposed their group, you will get more of those comments. The first time it is quoted back at them in a later meeting, you will not get another one until the pressure is over.

The part that is about you

You are under the same pressure the groups are. You have your own version of events to protect, your own boss asking how this happened, and your own reasons to prefer one group's account over another's. That makes it easy to become one more territory rather than the person who can see across all of them.

It is worth being honest with yourself about which group you have started trusting by default, and why. Sometimes the answer is that they have earned it. Sometimes the answer is that they are the group whose account makes your own position easiest to defend. The people in the other groups usually know which one it is before you do.

Three questions

Which group in your unit has started copying more people on its messages in the last few months, and what are they protecting themselves from?

What was the last concern someone raised early and tentatively, and how was it treated in the meetings that followed?

If you asked each group to write down, separately, what went wrong and why, how many different stories would you get back, and has anyone ever put them side by side?