There is a particular way some people hold their breath before they speak in meetings. Not the ordinary pause of someone collecting their thoughts. Something else. A scan. They are reading the room for permission, checking the faces of the people with authority before they commit to having an opinion. I noticed it for years, this pre-speech surveillance, and it took me longer than it should have to understand what I was looking at. I was looking at someone who had learned, in some previous context, that holding the wrong opinion at the wrong moment carried a cost they could not afford.
“High-control situations” is the term practitioners use for environments that restrict autonomy through a combination of ideology, social pressure, and punitive consequences for departure. It applies to high-control religious communities (the BITE model covers the full architecture of these groups, and once you read it you will recognize environments you thought were ordinary). It applies to abusive intimate partnerships, where the control is interpersonal rather than institutional but the mechanism is identical. And it applies, more than the tech industry likes to admit, to certain workplaces: the startup that runs on fear, the charismatic founder who has constructed a universe in which their judgment is the only valid data point, the company culture so totalized that employees apologize for having thoughts that diverge from the official narrative.
What these environments share is not their specific ideology. They share a method. Control of information, control of relationships, and systematic punishment of dissent, administered alongside enough warmth and belonging that leaving feels more dangerous than staying. When someone finally goes (or is expelled, which is its own category of wound), they carry the behavioral adaptations that kept them safe. Those adaptations do not dissolve when the environment does. They walk in through your door on their first day.
In computing, a permissions model governs who can read a file, write to it, execute it. Permissions are not suggestions. They are enforced at a level below the user’s control. A person who has spent years in a high-control environment has had their permissions managed externally: what they were allowed to think, who they were allowed to speak with, which of their internal states were valid and which were symptoms of disloyalty. High-control groups restrict information (no outside media, no contact with former members), relationships (shunning, accumulated social debt as leverage), and internal experience (confession structures, purity culture’s surveillance of thought). By the time someone leaves, the external permission structure has often been internalized so completely that they cannot reliably distinguish their own preferences from the ones that were installed.
This is what shows up at work. Not the theology, not the specific rules. The operating system.
The behaviors are consistent enough across contexts that once you know what you are looking at, you cannot un-see them. A constant, low-grade scan for what the person in charge actually wants, so the correct opinion can be produced on demand. Genuine distress at ambiguity, not mere discomfort, because high-control environments run on certainty and the absence of clear rules feels like danger. A disproportionate relationship to mistakes: in a high-control system errors carry moral weight, and a typo in a presentation can produce self-reproach that makes no sense unless you understand what it was trained on. Difficulty saying no. Difficulty believing that no will not produce punishment. And frequently, an extraordinary work ethic that is not entirely healthy: the loyalty-through-output dynamic, the belonging-through-sacrifice logic, the performance review that should feel like a win but does not land, because in the previous environment approval was always provisional, always the setup for the next demand.
The toxic workplace version is the one the tech industry is most responsible for and least willing to examine. I have been in rooms with founders who ran their companies on a controlled information loop: the story told publicly, the story permitted internally, and the actual state of affairs were three different things. Employees who noticed the gap were managed out or exhausted into compliance. The ones who stayed learned to see only what they were supposed to see. That is a high-control dynamic. It does not require a theology. It only requires power, consistency, and the threat of exclusion. Someone who spent two or three years inside that and then joins your organization has been trained to suppress their own pattern recognition, to distrust their own discomfort, to perform certainty about the official narrative even when it is visibly wrong. That training does not expire.
I have been autistic my entire career, even the years before I knew the word for it. In practice that meant I had already developed a habit of reading environments carefully and producing approximations of expected behavior, because the direct expression of how I actually processed the world was rarely what was wanted. I did not live through a high-control situation in the formal sense, and I want to be careful not to claim equivalence where there is only adjacency. But I have some understanding of what it is to spend a significant portion of your cognitive budget running a continuous scan: what is acceptable here, what will be punished, what do these people actually want versus what they say they want. That shared texture is what makes me notice the breath-hold. It is also, I suspect, what makes me take it seriously.
What does not help is moving fast.
The instinct in startup culture is to throw someone in the deep end. They will acclimate. For many people this is fine. For someone rebuilding their sense of what they are permitted to think and say, a fast environment is just another system to frantically reverse-engineer for rules, another authority structure to read, another test they cannot quite believe they are allowed to pass.
What does not help is asking for vulnerability before you have demonstrated that vulnerability is safe. “We have a culture of radical candor here” is potentially alarming to someone for whom radical candor was the thing that got people expelled. They will nod. They will perform it. They will not actually practice it, because they have no evidence yet that it is not a trap. They are in read-only mode: receiving, processing, not yet willing to write to the shared environment, because in the previous one, writes that fell outside the expected schema were deleted.
What does not help is treating their compliance as a signal. High-control survivors are often skilled at producing exactly what the room appears to want. The person nodding enthusiastically in the all-hands may genuinely agree, or may be performing agreement while running a threat assessment in parallel. The person who never escalates problems is not low-maintenance. They are someone who has not yet decided whether you can be trusted with the truth. Mistaking that performance for engagement is how you lose them quietly, and you usually only find out they were gone months before they resigned.
What actually helps is less exciting to describe but more useful to practice.
Consistency. The single most stabilizing thing a functional workplace can offer is the repeated experience of stated norms being enforced. If you say mistakes are learning opportunities, and then someone makes a mistake, and you treat it as a learning opportunity, that is one data point. The first of many needed before the capacity to trust stated intentions can begin to rebuild. One instance is nowhere near enough. Ten instances might begin to register. The timeline is genuinely slow, and the responsibility sits with the leader, not with the person doing the recalibrating.
Explicit permission. “I am asking because I actually want to know” is more useful than it sounds, said to someone for whom that sentence was historically untrue. “You are allowed to disagree with me” is more useful still, stated once, then demonstrated, then stated again, then demonstrated again. Explicit permission given freely and shown not to be a trap is how you begin to help someone replace an externally managed permission system with one they own.
Patience with the gap between output and affect. The person producing extraordinary results while visibly running on anxiety is not fine. They are doing what they were trained to do in a context that required constant performance of adequacy. “You don’t have to work this hard” is genuinely worth saying aloud. So is “I notice you seem worried about this, and I want you to know the stakes are lower than they might feel.” These sentences can seem obvious. They are almost never said.
The people I am writing about are not broken. The management literature, when it addresses trauma in the workplace at all, tends to do so with the clinical remove of someone describing a country they have never visited. But broken is the wrong frame entirely. These are people whose threat-detection system was calibrated in an environment very different from the one they are currently in, and the recalibration takes time and safety and the unremarkable experience of simply not being punished for having an opinion.
Some of the most precise thinkers I have worked with came out of high-control environments. The hypervigilance, when it has somewhere useful to go, becomes extraordinary attention to detail and atmosphere. The pattern recognition that once kept them safe, freed from the work of self-protection, can see what everyone else in the room is missing. The person who spent years learning to read a room can, when they finally trust a room, read it at a depth that is genuinely rare.
What wastes that is a leader who does not recognize what they are looking at, mistakes the silence for contentment, and later wonders why the quietest person on the team somehow always saw the problem coming before anyone else did.
The breath-hold before speaking: I still see it. What I know now is that the question is not why they are hesitating. The question is what it would take to build the kind of room where they did not have to.
That is the work. It does not fit in a sprint cycle and it does not map onto an OKR. But it is what separates a workplace from just another context where someone learned to be careful, and the people who have been through those contexts know the difference, even when they are not yet certain they are allowed to say so.
There is a related pattern worth examining separately, one that does not require a history of control to produce its effects. It operates not on people recovering from high-control situations but on capable people who never needed rescuing at all. It is about how workplaces grant access to the context that makes work possible, and who gets made to ask for it. Specifically: what happens when a highly capable woman is brought in for something important, and then systematically not given what she needs to do it.
That is Part 2, coming next week.
