email@email.com
On the instruction that travels, the context that is rarely left out on purpose, and what a team builds in the void.
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.
It was roughly six months of work. We had less than three months to do it, and 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. Not for receiving it, and not for what comes after it. 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. Every option in front of you is a version of passing weight to people who did not choose it either.
It was too late to call anyone on my team that night. And I knew that whenever I did, I would have to deliver it with clarity and compassion, and I did not feel like I had either one in me.
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 for Monday 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, when we could have built it with room.
I did not have good answers to any of them. I gave the context I had, and then I said something about pulling together and staying connected as a team, and I 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. A day off here and there when somebody covered for somebody, and that was most of the recovery anyone got. They did it without making anyone else pay for it, which is a kind of integrity that often goes unnoticed.
Incredibly, they somehow delivered on the date, and it went out into the world and made a modest impression.
About two weeks later I was flying home from a work trip. Economy seat, legs pinched up on the seat in front of me, sleep still in my eyes and a coffee in my hand. The message had just come through, so I read it at altitude, with nothing to do about it for another three hours.
The project was cancelled. All of it. The organization had decided something else mattered more.
My heart sank. I was going to need to tell the team that the product was no longer going to be used in the market, and the thought of that was gut wrenching because of the many sacrifices they had just made.
For years afterwards, that was the story I told myself. A leader caught in the middle, holding a date he did not choose, watching it get erased. Although true, it was not the useful part.
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 I was allowed to say.
An explanation with a hole in it does not stay empty. Twenty-three people filled it.
I thought my job that Monday was to deliver the decision well. My job was to deliver the reasoning well, and that was the thing I did not have.
Watch what actually moves through a chain of people.
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 will make sure to get right.
Context is not compact. It is a web of constraints, commitments, tradeoffs, 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.
So the further a decision travels, the more it arrives as a bare imperative. The tool ships. The manual does not.
And it is rarely a decision to leave it out. That is the part that matters. 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. Everyone in the discussion has it. It does not feel like information that needs to be packed, because at that level it is not information at all, it is context. It only becomes information one floor down, when it is missing.
Frederic Bartlett demonstrated the mechanism in 1932 with a simple procedure: one person reads a story, retells it to a second, who retells it to a third, on down a line.[1] Detail did not vanish at random. What survived was whatever fit a familiar shape, and the gaps got closed with material that made the story cohere. Serial reproduction does not produce a shorter version of the original. It produces a simpler one, bent toward personalized sense-making of the people who transferred it.
The bending has a direction. Lee Ross’s account of attribution is a useful frame: when the constraints acting on someone are not visible to us, we under-weight them and explain the outcome by what we can see instead.[2] It is not a mistake people can be talked out of. It is what judgment does with missing context.
Put those together and you have it. A decision travels, sheds its reasoning, and lands in front of people who now have to account for it. Absent the constraints, they build an explanation out of the materials available.
What they build is usually not a named villain. It is something more durable than that.
Prashant Bordia and colleagues studied the informal explanations circulating through a large hospital during a reorganization, and found that negative accounts substantially outnumbered positive ones, and that the people carrying them reported more change-related stress.[3] The study is correlational and cannot say which direction that runs. But the title the authors gave it sums it up: Management Are Aliens! Not a person who made an error. A stereotyped “other” on a different planet.
That is the shape the gap tends to take. Not a villain with a name, but a system, or leadership, or them. It is a more comfortable explanation than a person and a far worse one, because it cannot be tested, corrected, or forgiven. It just explains everything, and it pulls every real human being above you into itself.
Here is the part that should get a leader’s attention, because it is not a study of feelings.
Jerald Greenberg measured theft rates in manufacturing plants during a temporary fifteen percent pay cut.[4] Groups whose pay was cut stole significantly more than before, after, or than unchanged control groups. But the cut was explained two different ways. Where the reasoning was given 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 everywhere else.
Identical change. Four times the resignations. How people were treated and the context about the rationale that was given made all the difference.
A team’s account of why something happened determines their behavior, and if you do not supply the “why”, they will build one.
What It Costs
The explanation hardens, and it works backwards. Once a group settles on the idea that decisions come from a system that does not care, that reading is not confined to the decision that produced it. It becomes the default lens for the next ambiguous thing, and it reaches back to reinterpret things that already happened. You are not correcting an impression later. You are arguing with a settled theory of “how things get done here”.
Your standing as a relay. Deliver a decision you cannot explain and there are two readings of you available: the person who agreed with something indefensible, or the person with no influence over it. Neither leaves you better able to carry weight next time.
The information you would need to push back. A team that believes decisions are issued from an indifferent system stops assembling the specifics that would let you make a case upward. Why build an argument for someone whose leadership is not persuadable? When the questions and ideas stop flowing, it’s a slippery slope towards disengagement.
Everyone downstream of your downstream. The leaders reporting to you have to run this same pattern with less than you had, because they got your version and your version was already thin. If you have not given them the reasoning and the margin to carry it, you have not delegated the message. You have delegated the gap.
The reading that gets in the way is that the team is being cynical, or ungrateful, or has decided to think the worst.
That leads somewhere specific and useless: an attempt to correct the attitude. More context at the next all-hands, a word about assuming good intent, a reminder that we are all on the same side. It does not work, because the attitude is not the problem. It is the missing context and communication that started it all.
A useful takeaway here is that people did what judgment does with an unfinished explanation. They closed it. Given what I provided, the system was a reasonable inference. It was not fair and it was not irrational.
They were not thinking badly about the company. They were thinking correctly given the lack of context that I provided.
Three moves. There is no playbook for the call itself, and none of these make the decision easier to carry. What they change is how it’s delivered.
Go get the manual before you deliver the instruction. This is the one I missed entirely. The reasoning usually exists, and it is usually available, and the reason it did not travel is that the person holding it did not know it had to. So ask, explicitly and as a request rather than a challenge: help me understand what was weighed, so I can carry this properly to my team. That sentence is not insubordination. It is the job. And it is rarely convenient, which is exactly why it does not happen on its own.
Tell your team what you know and name the edge of what you do not. Not blame, not cover. What was decided and at what level, then the honest boundary: here is the part I understand, here is the part I do not, here is what I asked. A leader who says “I do not know why, and I asked” gives people something real to work with. A leader who explains confidently on thin information hands them a story that will not hold, and when it fails, the next inference is worse than the first.
Put a person in the gap before an abstraction gets there. The space fills by default with the system, so the countermeasure is to name a specific human being and extend good faith out loud: this was decided by someone I know, who is trying to do right by the business, and I believe the reasoning is real even though it sits outside what we can see from here. It will feel like a formality the first time you say it. It is not. It is the only thing competing with the version that assembles itself in the hallway afterward.
The version of this I told for years put me in the middle of a chain, holding a date I did not choose. That version is accurate and it is also flattering, because it makes the weight the story.
What I got wrong was smaller and more mine. There was real reasoning behind that decision, and I found out later how substantial it was. It did not reach my team because it did not reach me, and it did not reach me because I did not go and ask for it. I spent that weekend working on how to say a hard thing, and no time at all on whether I had been handed enough to say it with.
What I do differently is small. Before I carry a decision down, I go back up and ask for more why than I was given. Sometimes it is not available and sometimes I do not get an answer. I ask anyway, because the alternative is handing people an instruction with the manual missing, and then being surprised at what they assemble.
Mark D. Benson is the founder and principal writer of Resonant Vector™, the home of Pressure Intelligence™, and the host of Pressure Rising™. He is a senior executive, product and systems leader, and writer.
In his professional role, Mark leads SmartThings at Samsung, working at the intersection of strategy, technology, and large-scale human systems. His experience spans global teams, complex platforms, and environments where sustained pressure and high stakes are the norm.
Resonant Vector™ is an independent initiative, separate from his corporate role and not affiliated with Samsung or SmartThings. It reflects a personal commitment to learning in public, sharing practical insights, and contributing to healthier leadership practice over time.
More about Mark can be found at markdbenson.com.
