The Shrinking, and What It Was Actually For

This week I posted something on LinkedIn about a pattern I have spent most of my life not seeing in myself.

It got more private responses than most things I post, which usually means one of two things: either it was wrong in an interesting way, or it was true in a way a lot of people recognised but had not seen written down enough. Based on the messages, it was the second one.

Here is the short version, for anyone who missed it. Then I want to take it further than a LinkedIn post allows.

A substitute teacher once accused me of lying about a piece of work. “There was no way a ten year old could have produced it,” she said. She was the teacher, so obviously she was right, and I adjusted accordingly.

For most of my life, I thought I was average. I assumed everyone saw what I saw. The patterns seemed obvious. I could not understand why no one else was discussing them.

What never occurred to me was that my normal is not average.

My brain works in patterns. I can hold significant complexity without losing the thread. I can read a situation with a level of detachment from the emotions running through the room that most people find either very useful or mildly unnerving, depending on the circumstances. Often both at the same time.

It kept happening. At college, I was told I was not allowed to show concern about exams, because “if the other students see you concerned, it will destroy their confidence.” So I didn't. Obviously.

Every time, the pattern was the same. Soften it. Shrink it. Tuck it away so others felt better.

But you cannot change your core being without there being a cost. And the price, I can tell you, can be high.

And why the hell should I? was finally the question I asked.

That question changed how I saw the room. Not just my own pattern, but what the room's reaction to it had actually been measuring all along.

It had not been measuring whether I was right.

It had been measuring the distance between what I could see and what the room was ready to hear. Those are not the same thing. And for a long time, I let the room's discomfort function as a verdict on the first, when it was only ever evidence of the second.

What Was Actually Happening

When someone names a structural problem no one else has said out loud, and the room shifts, there are two reads on what just happened.

The first: the person overstepped. Said too much, too soon, too plainly. The room's discomfort is the evidence. The conclusion is that they need to soften, time things better, read the room.

The second: the room's reaction is not evidence about what was said. It is evidence about how rarely it gets said. A pattern that is obvious to one person and invisible to everyone else is not a communication failure. It is a capability gap, and the discomfort is the gap becoming visible. The conclusion is that the person read the room more accurately than the room was reading itself, and the discomfort belongs to the gap, not to them.

These two reads lead to opposite places. Most organisations default to the first, because it requires nothing from anyone except the person who spoke. The second requires the organisation to ask why a true thing, said plainly, produced that reaction. That is a harder question, and most rooms never get there.

What makes this insidious is how reasonable the first read seems in the moment. The room reacted. Something landed badly. The most available explanation is that the person misjudged the delivery. That explanation is almost always incomplete, and often wrong, but it has the advantage of being immediately actionable. Adjust the person. Move on.

The second read has no clean action attached to it. It asks the room to hold two things at once: that something landed awkwardly, and that it might also be right. That is harder to do than it sounds, particularly in organisations that have assumed that a smooth delivery is the same as sound judgment.

If you have spent years in environments that defaulted to the first read, what develops over time is not that you get worse at seeing. You get better at filtering. You build a translation layer between what you observe and what you say. It becomes automatic. And eventually you stop noticing it is there.

What It Actually Cost

The cost to you is real, and you probably already know most of it. The vigilance before you speak. The internal recalibration in the seconds between seeing something and deciding how much of it to show. The particular exhaustion of being several steps ahead of a conversation and managing, repeatedly, how far ahead to appear.

What is harder to account for is the cumulative cost of doing that well. Because the better you get at the translation layer, the less visible the effort becomes, to the room, and eventually to yourself. It stops feeling like suppression and starts feeling like professionalism. Like judgment. Like knowing when to speak and when to hold back. Those things are real. The problem is that the translation layer does not distinguish between them and the reflex.

The cost to the organisation is harder to see, because it is invisible by design. It does not show up as an absence. It shows up as something slightly less useful than what could have been there, and no one can measure a degraded version of a thing they never received in full.

Every time your pattern-recognition goes through that translation layer before it reaches a decision-maker, two things happen. The signal arrives later. And it arrives weaker, if it arrives at all.

Here is what that looks like in practice. In its raw form, an observation might sound like: “This restructure will not work. It puts two people who do not trust each other in joint charge of the same budget, and no one has addressed that.” Said plainly, at the point the structure is being designed, that is one sentence that changes a decision.

After the translation layer, the same observation comes out as: “It might be worth considering whether the reporting lines for the budget are entirely clear, just so everyone is aligned going forward.” Technically the same concern. Practically, it is background noise. It will not change anything, because it has been engineered not to sound like it should.

That gap, between the sentence that changes a decision and the sentence that becomes background noise, is not occasional. For someone running a well-developed translation layer, it is the default. Every room. Every meeting. Every conversation where something true got processed into something manageable before it left their mouth.

The structural problem named too directly in year one is often the same problem that surfaces as a crisis in year three. By then, no one remembers that someone once said something close to the actual answer. They remember the crisis, and the scramble to fix it. Neither of which had to happen.

And this is the part that rarely gets named: the organisation that created the conditions for the translation layer to form is often the same organisation that will, in year three, look for somewhere to put the cost of not having heard the signal clearly. It will not land on the dynamic that produced the silence. It will land on the outcome. On the decision that failed. On the restructure that did not work. The original signal, and the room that could not receive it, will not appear in that account at all.

That is not a small thing. It is the kind of cost that never appears on any reckoning of what the pattern took, from you or from the organisation, because by the time it is visible, it has been attributed to something else entirely.

What Self-Recognition Actually Feels Like

There is a particular quality to the moment when you first see the translation layer clearly. It does not feel like revelation. It feels more like recognition, the unsettling realisation that something you thought was a deliberate choice has been, for a long time, a reflex.

The tell, for most people, is the gap between what they say unprompted and what they say when asked directly. If someone asks you “what do you actually think” and your answer is noticeably sharper than what you had been offering, that gap is the translation layer in operation. The direct question changes the social calculation. You have been asked, so the responsibility for the answer existing is shared. Unprompted, you carry it alone, and the reflex adjusts accordingly.

Another tell is what happens under time pressure. When there is no time to construct the softened version, the direct version sometimes comes through, a flash of the unfiltered read before the translation layer catches up. If you have ever said something startlingly plain in a crisis, and then felt the immediate pull to walk it back, that retreat is the pattern showing itself. The direct version was the real one. The retreat was the apology for having let it show.

Neither of these is a flaw. They are what happened when all response taught you, time and time again, that the cost of volunteering the unfiltered read was too much in the eyes of others. The pattern formed for a reason. The question is whether the reason still applies, and whether the reflex knows the difference.

What Changes When You Stop Mistaking the Two

The discomfort in the room and the truth of what you said are two different things. They always were.

Seeing that clearly does not make every room wrong and you right. What it does is create a distinction that was not available before: the difference between choosing when and how to say something, and having that choice made for you by a reflex built a long time ago in a different room entirely.

The translation layer is not always wrong to engage. Reading the room is part of the work. Timing matters. Delivery matters. There are moments where the softened version is genuinely the right one, not because the direct version is too much, but because the moment is not yet right for it and you know that. The problem is not the judgment. The problem is when the reflex takes over, when the filtering happens regardless of whether this room, this moment, this relationship actually calls for it.

What shifts when you see the pattern clearly is not that you stop filtering. It is that the filtering becomes a choice again. You can look at a room and decide how much to show, rather than having the decision made before you have finished thinking.

That is a different way to operate. It is also, in my experience, a harder one in the short term, because it puts the responsibility back where the reflex had been quietly carrying it. But it is the only way to stop leaving the real read in the room you never quite said it in.

The question worth thinking about is whether you see clearly. You do. The question is what happens to what you see before it reaches the room, and whether that is still a choice you are making, or one that was made for you t long time ago and never revisted.

If this is feeling very pertinent for you, it is worth a conversation. The advisory work we do starts exactly there, not with what you should do differently, but with what the pattern actually is and where it came from.

BOOK A DISCOVERY CALL

If you want to test whether this pattern is running in you, or in someone you work with, we have built a short companion tool: The Translation Layer Check. It is two sets of questions, one for you, one for the room around you. Download the Translation Layer Check.

If any of this is landing, that is the point. The work is in seeing the pattern clearly enough to choose what to do with it.

— Suzi