Most of what a technology leader does that matters is invisible. Not because it is hidden — but because it operates in registers that standard leadership frameworks do not measure. The decisions you make about your own emotional state, the direction in which you measure your progress, the unconscious performance you give every time you walk into a room — these shape what your team believes, how they behave under pressure, and what they conclude is possible, more powerfully than any strategy you put on a slide.
This article is not about leadership principles. It is about the five mechanisms through which you are already shaping your engineering organization — without necessarily knowing it, and without necessarily intending to. Each one operates below the level of decision. Each one is learnable. And each one, left unexamined, becomes the invisible curriculum your team is studying every day.
The Story You’re Telling About Your Own Decisions
John Bargh, one of the leading researchers on unconscious behavior at Yale, spent decades documenting a finding that most leaders would prefer not to be true: the conscious mind does not generate behavior. It narrates it, after the fact.
The mechanism is precise. Your brain processes information, generates an action, and then — in the milliseconds that follow — produces a plausible story about why you chose that action. That story feels like memory of intention. It is not. It is constructed explanation. Bargh quotes the neuroscientist Michael Gazzaniga: “Gazzaniga argued that the conscious mind makes sense of our unconsciously generated behaviors after the fact, creating a positive, plausible narrative about what we are doing and why. Obviously, there is no guarantee that these after-the-fact accounts are accurate.” [[Untitled 5]] And: “We all feel the subjective experience of will, but this feeling is not valid evidence of having willed ourselves to behave a certain way.” [[Untitled 5]]
The organizational implications are significant. When a leader says they made a decision for strategic reasons, they are almost certainly reporting a post-hoc narrative, not the actual cause. The cause is far more likely to be a mixture of habitual pattern, social pressure, emotional state, and prior unconscious processing — which the conscious mind has already tidied into a coherent story that sounds like deliberate strategy.
Naval Ravikant, in The Almanack of Naval Ravikant, identifies the mechanism that corrupts the narrator most reliably: “What we wish to be true clouds our perception of what is true. Suffering is the moment when we can no longer deny reality.” [[Untitled 6]] Desire is the variable that most reliably distorts the post-hoc account. When you want something to be true — when you want the project to be on track, the team to be aligned, the technical decision to have been correct — the narrator produces a story that confirms what you want. The confirming story feels like assessment. It is, in most cases, sophisticated wish fulfillment.
The practical question for leaders is not “how do I make better decisions?” but “what are the actual drivers of my behavior, and do they reflect what I claim to value?” The answer almost never comes from further introspection, because introspection accesses the narrator, not the actual cause. It comes from behavioral observation — specifically from the pattern of decisions made under pressure, in private, when there is no audience to perform rationality for.
Why Achievement Never Delivers What You Think It Will
Dan Sullivan and Benjamin Hardy, in The Gap and the Gain, name the specific cognitive trap that turns high achievement into a reliable engine of dissatisfaction. They call it the GAP: measuring yourself against an ideal, rather than against where you started.
The structure of the trap is architectural. The ideal — by definition — is always positioned just beyond where you are. As you move toward it, it moves. Every accomplishment resets the measuring point. The standard of success keeps relocating itself so that no matter what you achieve, you are perpetually behind. “The GAP makes every experience a negative, which means you’re worse off than you were before that experience. The GAP makes any form of progress a letdown. Whatever you’ve done isn’t enough because the ‘standard of success’ keeps moving. The GAP makes you a tyrant.” [[Untitled 7]]
The alternative is measuring backward, from where you started: “The way to measure your progress is backward against where you started, not against your ideal.” [[Untitled 7]] The same facts — the same accomplishments, the same distance traveled — produce completely different emotional and behavioral outcomes depending on which direction you face when you assess them. Facing toward the ideal, you are permanently behind and perpetually driven by deficiency. Facing backward from your starting point, you are permanently in a state of gain and permanently motivated from abundance.
This matters for engineering organizations because GAP leaders create GAP cultures. The engineering leader who measures every sprint against an ideal that keeps moving — the perfect system that was never built, the velocity that was always theoretically achievable — trains the team to experience every increment of progress as insufficient. The team internalizes the standard. Engineers who would otherwise experience genuine satisfaction from shipping working software begin to feel it as a letdown, because the leader has installed the wrong measuring direction as the cultural default.
Kim Holderness, in Everybody Fights, surfaces the same dynamic in relationships through the “secret contract”: “Your partner doesn’t complete you; you are already complete.” [[Untitled 4]] The leader who believes the team, the product, or the organization will eventually reach a state of completion is operating on a structural illusion. There is no completion. There is only the compounding of gains measured backward, or the perpetual deficit of a standard measured forward.
Leo Babauta, writing about time and attention, captures why the trap is self-sealing: “it doesn’t matter how much you get done, doing more doesn’t solve the problem of not enough time. I have had fantastically productive days, where I’ll get 20-30 tasks done with zero procrastination or distractions… and I still feel like I need to do more.” [[How to make the most of yoru 24 hours]] The feeling of insufficiency is not a signal about actual performance. It is a signal about measuring direction. Change the direction; the facts remain identical; the experience transforms.
There Is No Backstage
Michael Port, in Steal the Show, makes an argument that most professionals resist: “I always am in a role, lovely—for you, for them—even for myself. Yeah . . . Even when I’m alone, I am still in a role—and I myself am the most exacting audience I have ever had.” [[Steal the Show]] This is not a metaphor. It is a description of how behavior actually works. You are always performing — in every meeting, in every Slack message, in every architectural review, in every moment of visible pressure or visible calm. The performance does not stop when no one senior is watching. If anything, it intensifies, because the most exacting audience is the one inside.
The practical consequence: there is no backstage where your real values live separate from your performed ones. What you do when you think no one is paying attention is your real leadership — and in an engineering culture, someone is always paying attention. John Bargh’s cocktail party research demonstrates the mechanism at the neural level: the brain automatically processes self-relevant information before conscious awareness engages. In a meeting room, every member of your team is continuously scanning your body language, tone, and emotional state — unconsciously, automatically, without choice. “All the choices you make in your life signal to people, This is what I want you to know about me.” [[Steal the Show]] Every signal you send is being received and interpreted, whether you intended to send it or not.
This has a precise implication for engineering leadership. The value of a “safe to fail” culture cannot be established by announcing it. It is established by what happens visibly — and what happens in the room when no one powerful is watching. If leaders visibly punish failure in front of the team, the announced value is overwritten by the performed one. If they visibly absorb bad news with curiosity rather than blame, that is the culture being taught, regardless of what any values document says.
Garrett White’s Wake Up Warrior framework captures the identity dimension: “We are who we pretend to be, therefore, we need to be careful who we pretend to be.” [[MISC]] The performance becomes the person. The role becomes the character. This is not a threat — it is an opportunity. The leader who deliberately constructs the performance they want to give, who treats every visible moment as a conscious choice about what they want to model, is building their team’s culture intentionally rather than leaking it by accident.
The Direction You Face When You Measure
Engineering cultures have a measurement problem that has nothing to do with metrics. It is a directional problem: the organization consistently faces forward — toward the ideal state, toward the roadmap, toward the gap between current and target — and this orientation systematically converts every accomplished thing into evidence of inadequacy.
Dan Sullivan’s gap/gain framework applies directly. “When you’re in the GAP, you ‘need’ something outside of yourself. You’re driven externally. You’re reactive to what’s going on outside of you. In the GAIN, you don’t ‘need’ anything outside of yourself. You’re driven internally. You take what happens outside of you to transform and improve yourself.” [[Untitled 7]] The GAP orientation is not just psychologically corrosive — it is strategically disabling. A team that experiences every sprint as evidence of how far they still have to go cannot build the kind of intrinsic motivation that produces the best technical work.
Kim Holderness, in Everybody Fights, describes the practical version of measuring backward: the postgame analysis. “We now make it a practice to Monday morning quarterback our fights. We do a postgame analysis to determine what went right, what went wrong, and which bad habits we need to break so we can do better next time.” [[Untitled 4]] The retrospective is an organizational tool for GAIN-orientation — looking backward at what happened, extracting the learning, and measuring the delta between where the team started and where it now sits. Retrospectives that do nothing but identify gaps from ideal are GAP-oriented. Retrospectives that identify what the team learned and how their capability has expanded are GAIN-oriented. The same format produces opposite effects depending on the direction it faces.
Garrett White’s business maturity framework in Wake Up Warrior names the leadership disposition that enables gain-orientation: “You have learned to turn every aspect of your life into an opportunity for learning and growth regardless of the outcome – understanding that the moment you Blame, you are now losing power and expansion. No matter if the result is Good, Bad, Ugly or in-between, you are now ruthlessly committed to claiming creative ownership to everything you create.” [[Business]] Ownership — of results regardless of their valence — is the mechanism that converts outcomes into gains. The leader who claims ownership of failures as learning, not as evidence of the gap between current and ideal, installs gain-orientation as the team’s default posture toward its own history.
Your Mood Is Your Most Expensive Management Decision
The most consequential management decisions most engineering leaders make are never written in a strategy document. They are made every morning before the first meeting: what emotional state am I bringing into the room, and what am I going to do about it?
Kim Holderness, in Everybody Fights, documents the research with unusual directness: “Scientists have studied this phenomenon and confirmed that it’s true: our moods are contagious, and, in a shock to no one, bad moods are more contagious than good moods… simply observing someone through a one-way mirror as they have a stressful experience increased the likelihood that the subject’s stress hormone levels would rise.” [[Untitled 4]] Your emotional state is not a private experience contained inside you. It is a continuous broadcast that your team members absorb physiologically — not metaphorically, not as a cultural vibe, but as a measurable biological response. When you walk into a sprint review visibly stressed, the team’s cortisol levels rise. When you walk in grounded and curious, the conditions for genuine creative exchange improve. You are doing this whether you intend to or not.
Naval Ravikant, in The Almanack, identifies the mechanism: “Humans are wired to feel what the other person deep down inside feels.” [[Untitled 6]] This wiring is not a feature of emotional people or a weakness of sensitive people. It is universal. Your most technically-oriented engineer is absorbing your emotional state through the same circuitry that has kept humans alive in social groups for two hundred thousand years. The signal is ancient, automatic, and bypasses all the rational filters that people believe protect them from it.
Dan Sullivan’s gap-thinking applied to leadership produces the most concrete form of this: when a leader is chronically measuring themselves in the gap — when they carry the persistent low-grade anxiety of perpetual inadequacy — that anxiety radiates outward and becomes the team’s ambient operating condition. “If I’m in the GAP, I become a tyrant and a bully to my son, rather than his biggest fan and supporter.” [[Untitled 7]] Sullivan is describing a parent, but the mechanism is identical in a team setting. GAP-leadership produces defensiveness, risk-aversion, and a generalized anxiety about performance that the team experiences as their own but originates with the leader.
Garrett White’s Wake Up Warrior business framework names the emotional dimension of leadership as the most lethal weapon a leader carries: “Your emotions have become the most lethal weapon you carry.” [[Business]] Not in the sense of aggression — but in the sense that emotional state is the highest-leverage input to organizational culture that any leader has, and it is operating at full power regardless of whether they are consciously wielding it. The question is not whether to use it but whether to use it deliberately.
So, What Is Your Team Learning From You Right Now?
Five questions — one for each mechanism — that surface what is actually being transmitted.
First: What story are you telling about your last major decision — and what would a behavioral audit of that decision reveal about the actual cause? The narrator is always confident and always constructing. The audit looks at the behavior, not the explanation.
Second: Which direction are you facing when you assess your team’s progress? Toward the ideal that has not been reached, or backward from where the team was six months ago? The same facts; completely different culture.
Third: What is the performance you’re giving when no one senior is in the room? The culture is not built in the all-hands. It is built in the decisions made at 9pm, in the code review no one will credit, in the way the leader responds to the first bad news of the week.
Fourth: What emotional state are you walking into the room with — and what are you doing to take responsibility for it as an environmental design decision? Your mood is your most consequential infrastructure choice. It runs 24 hours a day, costs nothing to improve, and shapes everything downstream.
Fifth: What is your team measuring, and in which direction? The retrospective format you use teaches measurement direction. The stories you tell about wins and losses teach measurement direction. The way you respond when someone shares an accomplishment teaches measurement direction.
These are not rhetorical questions. They are diagnostic instruments. The leaders who build engineering organizations that sustain high performance over time are those who have examined all five — not once, but as a continuing practice of the self-awareness that makes intentional leadership possible.
