PRESSURE PATTERN #11

Missing Manual

An explanation with a hole in it does not stay empty.

Read this online Was this forwarded to you? Subscribe to Pressure Patterns and get the next one in your inbox.

Pressure: People will not wait for a reason. They will build one.

Ten o’clock on a Thursday night in October, in a hotel room. I had spent the day presenting to clients and the evening traveling. I was worn through, and a long way from home.

The phone rang. An executive several levels above me told me what had to happen. A piece of software we had not planned to build that year was now required, finished, before the end of December, because the company had made a public commitment with a date attached to it.

Roughly six months of work. Under three months to do it. A good share of those weeks fell across the holidays.

I sat there. I took it. I clarified the instructions. I hung up the phone.

There is no playbook for how to handle that type of call. You are holding a date you did not set, a scope you did not size, and a rationale you have been given about two sentences of.

What made it worse was that months earlier, some of the engineers had asked to start that work. One of them made the case plainly, that if we were going to need it, we should build it while we had time to plan ahead. It was deprioritized in favor of other high priority things. Now it was back, with an aggressive date attached.

The news could wait until Monday, so I scheduled the meeting and bought myself the weekend. That got me a better version of myself. But it was not free. I agonized over that meeting for two days.

Mid-afternoon on Monday. Nine people with me in person, fourteen more online. I told them what had happened and what we needed to do.

The first thing that came back was not words. People looked down at their hands instead of at me. Long exhales. They had seen this movie before.

Then the questions started, and they were good ones. Why was this decided. Why now. Why did our request to start this months ago go nowhere. I did not have good answers to any of them. I gave the context I had, said something about pulling together as a team, and could hear how thin it was while I was saying it.

Then they went and did the work. Cancelled family plans. Worked through Thanksgiving. Worked on Christmas Eve. They did it without making anyone else pay for it, which is a kind of integrity that often goes unnoticed.

Two weeks after it shipped I was on a plane home, sleep still in my eyes and a coffee in my hand, reading a message that had just come through. The project was cancelled. All of it.

The team didn’t blame me. I was grateful for that, but I should not have been. What they concluded instead was that the system did this, which is worse. Not a person who made a decision. The system.

A person can be wrong, can be argued with, can turn out to have had a reason. A system cannot.

And there was a reason. I learned parts of it much later, and it was more substantial than anything I said that Monday. The people who made the decision were not withholding information. In their context, the reason was crystal clear like the air they were breathing, so it did not occur to them that it had to travel with the instruction.

I had one phone call and I used it to receive a date. I did not ask what was behind it, or who had weighed what, or what business conditions it hinged on.

An explanation with a hole in it does not stay empty.

Pattern: Instructions survive the trip down. Reasons often do not.

An instruction is compact. Build this, by this date. It is portable, it survives every retelling intact, and it is the part anyone under pressure makes sure to get right.

Context is not compact. It is a web of constraints, commitments, and things somebody knows that you do not. It is expensive to carry and it degrades at every handoff, because each person passes on the version they received, minus whatever they did not fully understand, minus whatever they are not free to say.

And it is rarely a decision to leave it out. At the altitude where a decision gets made, the reasoning is not an attachment to the instruction, it is the water the instruction is swimming in.

What fills that space is rarely a person who made an error. It is something more durable. A system, or leadership, or them. Which is worse, not better, because an abstraction cannot be tested, corrected, or forgiven.

Here is the part that is not about feelings. Jerald Greenberg measured theft in manufacturing plants during a temporary fifteen percent pay cut. Same cut everywhere. Where the reasoning was explained thoroughly and with evident care, both the sense of unfairness and the theft rate came down. Where the same cut arrived with a thin explanation, nearly a quarter of that group quit during the pay-cut period, against five percent or less elsewhere.

Identical change. Four times the resignations. The difference was the context given and the way that people were treated.

Shift: The context and care with which you communicate is a choice, not a handoff.

I used to think owning the message meant standing behind a decision I had not made, saying it with conviction, absorbing the discomfort so my team did not have to. That is not owning anything. That is relaying with a straight face.

Owning the message means owning the context. Going and getting the reasoning. Bringing back as much of it as I am allowed to carry. Then making genuine margin for people to ask about it until they understand it, which is not a few minutes at the end of a meeting but days.

It buys two things. People who understand why are more engaged, which most of us already believe. And people who understand why solve the problem better, which fewer of us act on. A team that knows what the real constraint is will find paths through it you would never have handed them. A team holding only a date can do one thing, which is work harder.

The last decision you announced but did not make: how much of the reasoning did you actually have, and how much of it did you go and get?

Owning the message is not standing behind a decision. It is refusing to hand anyone an instruction you cannot explain.

This pattern is part of the library of leadership content at Resonant Vector published by Mark Benson to help leaders and teams thrive under pressure.