The Swap Test

Pick a behavior your leadership team believes it has. Not a value. A behavior, specific enough that you could point at a person doing it. Bad news travels up within a day. Nobody leaves a decision meeting without an owner and a date. The quality gate holds when the quarter is short.

Now take the five people who make that behavior happen and move them to a different division. Does the behavior still happen 90 days later?

That is the swap test, and it is the only question about culture that has a usable answer. Most leaders have never asked it because they have never had to separate a behavior they have from the people who are personally carrying it. Those look identical from the corner office. They price very differently.

What the buyer already knows

A business whose performance depends on particular people is valued as a business that depends on particular people. Nobody says this out loud in the room. It shows up as a discount, a longer earnout, a retention package written for four names, and a multiple half a turn below the comp set. The diligence team is running the swap test with a spreadsheet attached, and they are running it on you.

The same dependency eats the current quarter. When a standard is held in place by a person rather than a structure, that person spends their week holding it. They are in the escalation, the exception review, the meeting that would have gone sideways. The founder or CEO who cannot leave for two weeks without something breaking is not overworked by accident. They are the load-bearing wall.

The quarter that gets consumed by firefighting and the multiple that comes in light are the same problem, read at two different time horizons. This is why we do not lead with culture when we talk to an operator. Culture is our diagnosis of why. Key-person dependency is what he can feel.

Three levels, one behavior

A behavior can hold at three levels.

Individual. One leader does it, reliably, on her own.

Team. The leadership group does it together, as a collective, without any one person driving.

System. Structure, incentives, and norms hold it in place. It survives if the people change.

The Breakpoint Grid scores a single behavior across these three levels and across three stages of the knowing-doing chain, Know, Commit, and Do.

Nine cells, each scored based on evidence gathered from structured interviews with the client’s own leaders. Reading down the levels is the vertical read, and it is where the swap test lives. The System row is the swap test, formalized. It asks whether the behavior is a property of the organization or a property of the roster.

Four patterns come out of that reading, and each one means something different.

Individual holds, Team drops. Your people know what to do alone, and something in the group dynamic prevents them from doing it together. The problem is in the room, not in the person.

Team holds, System drops. The most dangerous result, because it looks like health. The behavior is real right now, and it is being carried by relationships, history, and goodwill. It is durable as long as the current group stays intact, which means it lasts until the first departure, the first acquisition, or the first reorg.

Individual holds, System drops. Good people fighting their own structure. They produce the behavior in spite of what the company pays for, and they burn out doing it.

System holds, Individual drops. The scaffolding is right, and someone cannot execute against it. This is the only one of the four that is a personnel problem, and it is the one most often diagnosed when the answer is actually one of the other three.

I have watched a leadership team score a 4 on Team and a 2 on System for the same behavior and hear it as good news. That score is a countdown.

What a relief-in-place teaches

There is a moment in infantry rotations called a relief-in-place. Your platoon hands its sector to the platoon coming in. You walk them through the ground, the routes, the people, and the standing orders. Everything you know goes on paper or into their heads over about 72 hours.

Almost none of what mattered transferred. The written standards went across intact and then quietly loosened over the next month, and the ones that survived were the ones the outgoing platoon had enforced when enforcement cost them something. When enforcing meant redoing work at midnight. When it meant correcting a friend in front of the squad. Those standards had a price attached; everybody had watched the price get paid, and that is what the incoming platoon inherited, whether or not anyone briefed it.

A standing order is a claim. What gets enforced at cost is the system.

Running it

Five moves, in order.

Name one behavior. It should finish the sentence “We know we should ___, but under pressure we don’t.” If you cannot picture someone doing it, it is a value, not a behavior, and you cannot test it.

Run the swap test backward. Take the last three times the behavior actually happened. For each one, name who made it happen. If the same name appears twice, you have your answer without any further work.

Find what the system pays for. Not the stated reward. The revealed one. Who got the headcount. Whose deadline moved. Whose exception got granted on the bad quarter, and how quickly. This is the kind of thing the Execution Audit is built to surface, and it is uncomfortable in a way that values workshops are not, because the evidence comes from the client’s own people describing what they witnessed.

Change one tolerated exception. Not the values statement. One exception, chosen because it is the one everyone in the building can already name.

Then watch the behavior under load. Not in the calm. Pressure lives in the Do column by definition, and a behavior that has only been observed in a good quarter has not been observed.

None of this produces a culture. It produces a structure that gives rise to the behavior, and the behavior repeated across a group is what people were calling culture the whole time. The word was always the output.

So run the test on your own calendar this week. Whatever you cannot delegate, whatever you had to personally be in the room for, whatever would have gone differently without you, all of that is the list of behaviors your company does not actually have yet.

What is on yours, and how long has it been there?