In 2010, Eric Schmidt offered a data point that has never fully been absorbed by the organizations it was meant to describe: humanity was generating as much information every two days as it had produced in the entire span of civilization up to 2003. [[2022-09-24]] The number has only accelerated since. The result is not more intelligence in the organizations that work with that information. It is the opposite: an environment so saturated with data, decisions, notifications, options, and requests that the capacity for genuine judgment has become the scarcest resource in any technology organization.
The standard response to this condition has been additive: more process to manage the complexity, more meetings to maintain alignment, more tools to track what the old tools can’t track, more specialization to handle the volume of demands that generalists can no longer absorb. All of it is understandable. None of it addresses the actual problem. The problem is not that engineering organizations need better tools for managing their complexity. It is that they have accumulated a kind of complexity that no tool can manage — because the complexity is in what they do, not in how they track it.
The five patterns described here are each a form of missing organizational intelligence — not the technical kind, but the institutional kind: the capacity to perceive, evaluate, and respond accurately to what is actually happening. Engineering organizations that lack this intelligence are not failing technically. They are failing organizationally. And no amount of technical excellence compensates for the organizational intelligence that determines whether technical excellence compounds or eventually collapses under its own weight.
The Audit You’re Not Running
In 2023, productivity researcher Sahil Bloom described a practice he called the Simplicity Audit: a structured review of every environment — physical, digital, mental, and social — through a two-question filter. The principle: “Complexity is a silent killer of focus, clarity, and performance…we tend to add, but rarely subtract.” [[2023-03-15]] The filter applied to each item in each environment: “(1) Is this necessary? (2) Is this creating energy?” [[2023-03-15]]
A 2022 leadership reflection adds a dimension the productivity literature rarely captures: “The adversary understands that distractions do not have to be bad or immoral to be effective.” [[2022-11-17]] And: “The root cause of distraction is the human drive to escape discomfort. Distraction is then an unhealthy escape from discomfort.” [[2022-11-17]] And: “Strength is pressure management.” [[2022-11-17]] These three observations together describe the specific failure mode that the energy audit is designed to surface: not malicious complexity, not obviously wasteful activity, but the accumulation of things that are defensible individually and collectively exhausting — things that are pursued specifically because they feel productive while avoiding the harder, more important, more uncomfortable work.
The energy audit is not a productivity exercise. It is an organizational diagnostic. A standing committee that has never closed a relevant decision carries a net energy cost. A reporting structure that creates friction on every cross-functional question carries a net energy cost. A tool migration justified by capabilities that nobody uses carries a net energy cost. None of these appear as costs in any dashboard. But their depletion is exactly what explains why an organizationally full engineering team consistently produces less than its headcount and capability should generate.
A 2023 note makes the decision logic structurally explicit: “If you say no to a thing, then you’re saying no to one thing. If you say yes to a thing, you actually say no to every other thing during that period of time.” [[2023-04-15]] The yes/no asymmetry is not a prioritization framework — it is a description of how organizational energy actually works. Every yes is a finite allocation of collective capacity. The VP Engineering who says yes to a new monitoring platform, a process improvement initiative, a team restructure, and a revised reporting format in the same quarter has not made four decisions. They have made one decision to distribute organizational energy across four competing demands — and none of the four will receive what each individually requires.
Why Polish Blocks Transmission
In leadership culture, polish is capital. The well-prepared presentation, the certain forecast, the architectural recommendation delivered without visible hesitation — these signal competence, inspire confidence, and move decisions. The organizational incentive for polish is real and continuously reinforced.
The problem is transmission. A 2022 note carries an observation that reframes the relationship between imperfection and influence: “yet a torrent of truth came through that good, but imperfect, conduit—more than Joseph could communicate.” [[2022-09-29]] And its converse — why polish blocks reception: “I saw the imperfections in Joseph Smith … I thanked God … for I knew that I myself had weakness, and I thought there was a chance for me.” [[2022-09-29]] The imperfection is not what diminishes the message. It is what makes the message receivable. The listener who sees no weakness in the speaker concludes either that they are watching a performance or that there is nothing in the message for someone like them.
Leonard Cohen, as curated in a 2022 note, expressed the mechanism in the form it has been most quoted: “There is a crack in everything, that’s how the light gets in.” [[2022-10-15]] This is not a statement about accepting failure. It is a structural observation about transmission. Light — understanding, inspiration, genuine influence — does not pass through sealed surfaces. It passes through the gaps. An engineering organization whose leaders project total certainty has inadvertently sealed its transmission surfaces. The people below them have no gap to enter through. There is no place where they recognize themselves in the leader, no visible limitation that says “I have felt this too, and there is a path through it.”
A 2022 note names what genuine transmission produces: “they set fire in others because they are on fire.” [[2022-11-27]] Fire is not transferred by explanation or mandate. It is transferred by contact. The engineering leader who is genuinely engaged with the work — who has not sealed themselves behind the polish of authority — can set fire in engineers. The one who has prioritized polish over presence is broadcasting, not transmitting.
What Your Team’s Anger Is Trying to Tell You
Most technology organizations manage anger as a morale problem: note it in the engagement survey, assign an action item to the relevant manager, watch for improvement in next quarter’s numbers. The organization treats the emotion as the problem to be resolved — and in doing so misses the most important thing the emotion is carrying.
A 2022 note contains one of the most precise observations in this corpus: “The level of anger is equal to the level of loss.” [[2022-10-04]] This is not a psychological observation. It is a measurement principle. If an engineer is persistently and intensely frustrated with a process, the intensity of that frustration is a direct measure of the magnitude of what they value that the process is violating. The frustration is not a personality issue to be managed. It is a high-resolution signal pointing at something the organization cares about enough to fight for.
A 2023 note extends this into organizational theory: “ANGER is the deepest form of compassion…the internal living flame of anger always illuminates what we belong to, what we wish to protect and what we are willing to hazard ourselves for.” [[2023-03-15]] And: “Anger in its pure state is the measure of the way we are implicated in the world and made vulnerable through love in all its specifics.” [[2023-03-15]] The engineer most visibly frustrated with the on-call process is the engineer who cares most about system reliability. The principal engineer furious about estimation is the one who cares most about predictability and respect for craft. The signal is not the anger. The signal is what the anger illuminates.
A 2022 note: “the place you suffer is the place you care enough to act.” [[2022-10-15]] The places of suffering in your organization are the places of deepest values — the places where the gap between what is and what people believe should be is large enough to hurt. The engineering leader who systematically routes around this signal — who manages engagement rather than listening for values — is discarding the highest-quality organizational intelligence available.
The corollary applies to the broader attention environment: “You’re bringing a knife to a gun fight if you think you can use your self control to combat social media’s engineering to keep you wired.” [[2022-08-26]] The modern attention economy has industrialized distraction. Willpower is not the appropriate response to an engineered system. The same principle applies to organizational emotion: willpower — suppression, managed positivity, mandatory resilience — is not the appropriate response to genuine anger. Understanding what is being lost is.
Why Removing the Weight Makes People Unstable
Engineering organizations under sustained pressure tend to respond by diffusing accountability: shared ownership of failures, collective decision-making that spreads responsibility, retrospectives structured to identify systemic causes rather than individual judgment calls. Each of these has legitimate value in specific contexts. Applied broadly as a protection strategy, each produces the same result: people who are harder to blame and easier to lose.
A 2023 note carries the structural insight directly: “As long as we have a weight of responsibility in this church, all hell can’t push us over; but as soon as that weight is lifted off, most of us are easy marks by the powers that drag us down.” [[2023-01-01]] The mechanism is structural. Weight does not crush properly designed load-bearing elements — it stabilizes them. An engineer who is genuinely accountable for a service in production, with real authority and real consequences, has the structural stability that comes from being anchored by something that matters. An engineer who is “part of the team that owns it” has no such anchor. They are neither accountable nor resistant to drift.
A 2022 daily note states the formation principle: “You become a man when you become responsible for other people.” [[2022-08-26]] Not responsible for your own work. Responsible for other people. The upgrade in accountability — from personal excellence to genuine stewardship of outcomes that affect others — is what produces the specific stability that diffuse accountability cannot replicate.
A 2022 note on what genuine accountability builds: “That which we persist in doing becomes easier for us to do; not that the nature of the thing itself is changed, but that our power to do is increased.” [[2022-09-29]] The compounding argument for real accountability: the engineer who bears genuine responsibility for an outcome develops the specific capability that outcome requires in ways that the engineer who is “part of the team” does not. The weight builds the capacity to bear the weight. And: “If we are striving, if we are working, if we are trying, to the best of our ability, to improve day by day, then we are in the line of our duty.” [[2022-11-27]] Striving, in this formulation, is not heroic. It is the minimum condition of organizational health — and it is only available to people who bear something real.
The Register Your Organization Can’t Hear
A 2022 note carries a parable from a wildlife training program: dogs trained specifically to track mountain lions began pursuing deer, then coyotes, then rabbits — “How often are we led from the right track by distractions that cross our paths? Do we sometimes seek the available ‘rabbit’ when the big game is available up the path?” [[2022-09-24]] The dogs were excellent. They had simply been redirected, gradually, to something smaller. The limitation was not capability. It was the calibration of attention to the available rather than the valuable.
The organizational version of this pattern is named directly in a 2023 note: “How shortsighted it is, then, to choose a single key and endlessly tap out the monotony of a single note, or even two or three notes, when the full keyboard of limitless harmony can be played.” [[2023-01-01]] The single-key organization — the engineering team that has optimized entirely for velocity, or entirely for technical elegance, or entirely for process compliance — is not failing in its register. It is succeeding in one dimension while remaining structurally blind to everything the missing dimensions would have made visible.
A 2023 note defines maturity specifically in terms of range: “MATURITY is the ability to live fully and equally in multiple contexts.” [[2023-03-15]] And its converse — immaturity — is the exclusive domination of one temporal frame, one discipline, one mode of evaluation. A 2023 note: “As Huxley stated, we are all great abbreviators. None of us have the wit to know the whole truth.” [[2023-02-06]] The abbreviation is not a failure of intelligence. It is the structural condition of any finite mind. The question is not whether you abbreviate — you do — but whether you know what you are leaving out.
Samuel Johnson, curated in a 2022 note: “Integrity without knowledge is weak and useless. Knowledge without integrity is dangerous and dreadful.” [[2022-09-29]] The single-note engineer who has deep technical knowledge without the organizational intelligence to apply it wisely is dangerous. The leader who has integrity without sufficient knowledge of what their team actually faces is useless. The full keyboard requires both. And Uta Hagen, also curated in a 2022 note: “We must overcome the notion that we must be regular… it robs you of the chance to be extraordinary and leads you to the mediocre.” [[2022-10-12]] The mediocre is not the worst. The mediocre is what appears when exceptional capability is confined to a single key.
So, What Intelligence Is Your Engineering Organization Missing?
Five diagnostic questions — one for each gap.
First: Run the two-question filter on your last three major organizational commitments: Is each necessary? Is each creating energy? The ones that fail either test are not neutral additions. They are active subtractions from the capacity required for everything that passes the filter.
Second: When was the last time you said “I don’t know” or “I got this wrong” in a public leadership setting? If the answer is more than two quarters ago, the transmission surfaces have probably been sealed. The crack is not a weakness. It is the channel.
Third: What is your most senior engineer most frustrated about right now? The answer is not a morale problem. It is the location of something they value intensely that is currently being violated. That is organizational intelligence you are not yet using.
Fourth: Who in your engineering organization is genuinely, personally accountable — not “involved in the team that owns” it, but individually accountable — for the most important outcome you are trying to produce? If the answer is nobody specific, the organization is structurally unstable under pressure.
Fifth: What are the adjacent registers your engineering organization cannot currently hear? The product signal that technical optimization has made invisible. The human dynamics that process maturity has made illegible. The long-horizon risk that quarterly planning has made inaudible. The notes you are not playing are determining what you cannot build.
