How to Name a Tension

Something is off. You have felt it for a fortnight. You cannot say what it is without sounding like you are complaining about a person, so you say nothing, and it gets worse.

That is a tension, and learning to name one is the most portable skill in this entire body of work. It is also the one nobody teaches, because it sounds like it should be obvious.

What a tension is

A tension is the gap between how things are and how they could be.

That is it. It is not a conflict. It is not a complaint. It is not necessarily anybody's fault. It is information: you have noticed a difference between the current state and a better available state, and that noticing is worth something to the group.

Two things follow from that definition, and both are load-bearing.

A tension is yours. You felt it. You do not need anyone to agree it is real before you can raise it. Nobody gets to tell you that you are not sensing what you are sensing.

A tension is not a proposal. You do not need a solution to raise one. "I don't know what to do about this" is a complete and acceptable thing to say. Requiring people to bring solutions is how organizations train themselves to only surface the easy problems.

Why people do not name them

Because the untrained version comes out as an accusation.

You feel: handovers between design and build keep failing.

It comes out as: "Design keeps throwing things over the wall."

Now you are in a conflict about whether design is careless, instead of working on handovers. Everyone defends. Nothing changes. And you learn that raising things makes it worse, so next time you wait longer.

The skill is getting from the felt thing to a workable thing without routing it through blame.

The three sentences

Name it in this shape. It is deliberately mechanical, because mechanical is what you need when you are activated.

1. What I observe. Concrete, specific, checkable. No adjectives about people.

2. What it affects. The work, not your feelings about the person. (Your feelings are real. They are just not the lever.)

3. What I want to happen next. Which can be "I want us to look at this", not a solution.

Worked through:

Observe: "In the last three projects, the build team got the designs on the day the sprint started, and each time there were questions that took two or three days to answer."

Affects: "So the first half of every sprint is spent waiting, and we have missed the last two delivery dates."

Next: "I want us to look at how handover works. I don't have a fix in mind."

Compare that to "design keeps throwing things over the wall". Same tension. Completely different conversation. Nobody has to defend themselves to engage with the second version, which means people can actually engage with it.

Getting from feeling to observation

Most of the work is here, and it happens before you open your mouth.

Ask: what did I actually see? Not what it meant. What happened, on what date, that a camera would have caught. If you cannot find a single concrete instance, the tension may be about you rather than about the organization. That is worth knowing too, and it is not a failure.

Ask: what is the pattern? One instance is an incident. Three is a pattern, and patterns are what structures can fix. If it happened once, say so honestly: "this happened once and I want to flag it before it becomes a pattern."

Ask: whose is it? Sometimes the honest answer is "I am tired and everything looks like a problem this week." Naming that to yourself first will save you a meeting.

Separate the person from the structure. Almost every tension that presents as a person problem is a structure problem wearing a person's face. Nobody defined who answers design questions during a sprint, so nobody does. That is not carelessness. That is an unassigned role.

Where to take it

A role holds it. If the tension is about something that clearly belongs to a role, take it to that person directly, in the three sentences. Most tensions end here and never need a meeting.

A governance meeting. If it is about how the work is organized rather than the work itself, it is a governance tension: a role that does not exist, an authority that is unclear, a policy that is producing the wrong behavior. See the article on governance and operations meetings.

A restorative conversation. If the tension really is between two people and their relationship, structure will not fix it and pretending otherwise wastes everyone's time. That is a different process, and this corpus has good material on it.

The mistake is putting a person-tension in a governance meeting, where it becomes a policy proposal aimed at one individual, and everybody knows it.

Where it goes wrong

Saving them up. Ten tensions raised at once is not ten tensions, it is a grievance. Raise them one at a time, close to when you notice them, while they are still small and boring.

Naming it to the wrong person. Telling three colleagues at lunch is not naming a tension. It is building a coalition, and it makes the eventual conversation much harder.

Requiring solutions. If your group only accepts tensions that arrive with a proposal, you will only ever hear about problems that are easy to solve. The hard ones will stay silent until they are expensive.

Treating "I have no tensions" as good. A group where nobody senses a gap is not a healthy group; it is usually a quiet one. Ask what people have stopped bothering to mention.

What good looks like

Somebody says, in a normal voice, in a normal meeting: "In the last three retros we agreed an action and none of them got done. That means retro feels pointless and attendance is dropping. I want us to look at it."

No one is accused. Nobody is surprised. It took forty seconds. And it is now a thing the group can work on rather than a thing three people privately believe.

Try this week

Write down the vaguest bad feeling you currently have about your organization. Then force it through the three sentences. Refuse to write an adjective about a person.

Notice what happens to the feeling when you make it concrete. Sometimes it dissolves, because it was tiredness. Sometimes it sharpens into something obvious that nobody had said out loud.

Both outcomes are worth the ten minutes.