The most consequential leadership decisions in engineering organizations are rarely the ones made in strategy reviews or planning sessions. They are made implicitly, continuously, and without a meeting: the decision about what counts as traction versus distraction is made every time a calendar is or isn’t protected. The decision about whether strategy actually transmits to the team is made every time a leader speaks from information rather than conviction. The decision about what the organization’s process level is diagnosing is made every time a new approval gate is added without asking what misalignment created the need for it. The decision about which performance areas actually matter is made every time excellence is claimed everywhere and therefore exists nowhere. The decision about where leadership responsibility ends is made every time a leader looks away from something within their blast radius.
None of these decisions require a meeting. None of them appear in a decision log. All of them are being made, every day, by every engineering leader — and the decisions being made in their absence are almost always the wrong ones.
This article names five of them. Not to add ceremony or process. To make explicit what was always implicit — because the decision made consciously, even once, is categorically different from the one that accumulates by default across a thousand small unexamined moments.
The Decision You’re Making Every Time You Don’t Pre-Commit
Nir Eyal, as curated in a 2022 productivity note, drew a distinction that reframes the entire modern conversation about focus: “What is the opposite of distraction? It’s not focus, it’s traction, any action that pulls you TOWARD what you said you were going to do. Any action that is the product of forethought is Traction, anything else is distraction.” [[2022-08-07]] The corollary inverts the usual framing: “Everything can be traction so long as you planned for it. ‘The time you plan to waste is not wasted time.’” [[2022-08-07]] A three-hour lunch with a key technical stakeholder is traction if it was pre-decided. A Slack dive into an interesting thread is traction if it was scheduled. The content of the action is irrelevant to its classification. The only variable is whether it was the product of forethought.
The same note: “the antidote to impulsiveness is forethought.” [[2022-08-07]] The engineering leader who feels perpetually scattered, who ends every week wondering where the time went, who cannot explain why the things on the strategic roadmap never advanced — is experiencing the result of a decision made by absence: the decision not to pre-commit. Every hour that is not pre-committed becomes reactive allocation, which by definition allocates toward the most urgent thing in the environment rather than the most important thing in the strategy.
A 2022 decision framework: “10, 10, 10 — What are the consequences if I do this in 10 minutes, 10 days, 10 years.” [[2022-08-11]] This is not a time management tool. It is a pre-commitment tool — the ten-year question surfaces whether this action is traction or urgent distraction masquerading as priority. A 2023 note: “If you don’t schedule the things that are important for you, your time will be filled with BS.” [[2023-06-18]] The decision is made by whoever fills the calendar first. If leadership doesn’t pre-commit, the environment does — and the environment has no strategy.
Why Your Strategy Stays in the Room
A 2022 leadership note captures the mechanism of failed strategy transmission in a single observation: “reason doesn’t get people to act, emotions do.” [[2022-08-29]] And its corollary: “simple is sticky.” [[2022-08-29]] These are not observations about persuasion or rhetoric. They are descriptions of the physics of transmission. Technical information — architecture diagrams, strategy documents, roadmap presentations — operates in a medium that does not reach the part of the brain that changes behavior. That part is reachable only through conviction: the personal, visible, embodied expression of a belief that the speaker would stake something on.
Gian-Carlo Rota, as curated in a 2022 note: “A good teacher does not teach facts, they teach enthusiasm, open-mindedness, and values.” [[2022-08-07]] The teacher who teaches facts has not taught anything durable. The teacher who transmits enthusiasm has changed something structural in the learner. The engineering leader who delivers roadmaps is teaching facts. The one who is visibly, personally convinced that the architectural direction is correct — who stakes credibility on it, who talks about it with personal investment in the outcome — is transmitting enthusiasm. The distinction is everything.
A 2022 note: “the lesson is inside the learner, if we think the lesson is in the manual we are in trouble.” [[2022-08-11]] The strategy is not in the document. It is in the change it produces in the people who need to execute it. And: “As a leader, you have to SELL the idea to people that you can take them where they want to go.” [[2022-08-21]] Sell means: make the case with enough personal conviction that the other person can feel your belief in the destination.
Theodore Roosevelt, as curated in a 2022 note: “Far and away the best prize that life offers is the chance to work hard at work worth doing.” [[2022-09-20]] An engineering team that believes this about what it is doing is structurally different from one that does not — and that belief transmits from leadership, not from the product requirements document. A 2022 note: “Better things are caught than taught.” [[2022-09-15]] The decision about whether your strategy stays in the room or actually moves through the organization is the decision about your personal conviction level. It is made every time you present without personal stakes — every time you share information instead of transmitting belief.
What Your Process Is Trying to Tell You
A 2022 daily note contains one of the most operationally precise sentences in this entire corpus: “process is the excretion of misalignment.” [[2022-08-29]] The metaphor is not incidental. Excretion is the body’s mechanism for removing what the system cannot metabolize — the byproduct of cellular activity, not a designed output. Process is the organizational byproduct of trust and alignment failures. It does not produce alignment; it accumulates where alignment was absent.
The implication is diagnostic rather than prescriptive. Every process gate your organization requires is scar tissue from a trust or alignment failure. The CAB meeting that exists because a deployment went catastrophically wrong. The multi-level approval chain that exists because an architect made an unauthorized decision. The mandatory security review that exists because something shipped without one. Each was a genuine solution to a genuine problem at the time. Each has encoded that problem permanently in the organizational structure. Every new layer of process added to address dysfunction adds scar tissue rather than healing the wound.
The same note: “If you’re part of the system you’re trying to change, you’re part of the problem.” [[2022-08-29]] The engineering leader who adds process to address their own team’s misalignment has not fixed anything — they have created a self-referential loop. And: “simple is sticky.” [[2022-08-29]] Complexity is the memorial to past dysfunction. Simplicity is the evidence of sustained alignment.
A 2022 note: “80% of an organization’s success relies on an organization’s systems not people.” [[2022-08-21]] This is correct but it does not mean: add more process. It means: design systems for the people you have and the alignment you are committed to maintaining — not for the failures of people who are no longer there. William Blake, as curated in a 2022 note: “I must Create a System, or be enslav’d by another Man’s; I will not Reason and Compare: my business is to Create.” [[2022-08-07]] The engineering leader who creates their team’s system deliberately is operating with agency. The one who inherits processes and never audits them has been enslaved by whoever designed the system before them.
A 2023 note: “Track and measure. You measure, performance improves. If you don’t track, how do you know you ever did anything. These numbers are life threatening.” [[2023-05-08]] Measurement is the inverse discipline: measurement surfaces where alignment is and isn’t; process responds to where it wasn’t. Both are necessary. Only measurement tells you whether the process is working or whether it is simply accumulating.
The Mediocrity You Haven’t Named Yet
A 2022 productivity note contains the question that most engineering leadership teams have never answered explicitly: “What have you strategically chosen to be mediocre at? What have you chosen to fail at?” [[2022-08-05]] This is not rhetorical. It is the prerequisite for every excellence claim in any organization operating under real resource constraints. If you have not named what you are mediocre at, you have not claimed excellence at anything — you have claimed adequacy everywhere, which is a different and considerably less defensible position.
The same note draws the distinction that makes the question precise: “Consultants have a recipe, but masters have a cookbook.” [[2022-08-05]] The consultant executes the known method. The master understands the method well enough to know when not to use it — and to design the alternative. The master’s advantage is not breadth of knowledge but depth of selection: they know which techniques they own deeply and which they have consciously set aside.
A 2022 note: “average is the enemy.” [[2022-08-11]] Average is not the floor; it is the trap. Average is what happens when excellence is spread uniformly across a domain that requires concentration. The team that is averagely good at security, averagely good at reliability, averagely good at developer experience, and averagely good at product velocity is genuinely excellent at none of them. And: “If a reason doesn’t stop everyone, then it is an excuse.” [[2022-08-11]] The reason your organization cannot invest in security posture is usually not the reason — it is an unexamined consensus that has solidified into structural rationalization for unacknowledged mediocrity.
A 2022 note: “you either win or you learn.” [[2022-08-23]] The only condition under which mediocrity is genuinely unacceptable is when it was never acknowledged. The VP Engineering who names their team’s deliberate mediocrity zones has not lowered the bar — they have made the investment portfolio legible. The one who never names them has a portfolio that no one can read, which means it cannot be managed, improved, or defended. The decision is already being made. The only question is whether it is being made deliberately.
Where Your Responsibility Actually Ends
A 2022 daily note states a claim about leadership responsibility that most professionals would instinctively resist: “Every man is responsible for everything he does but also responsible for everything everyone else does.” [[2022-08-23]] This is not a statement about legal liability. It is a statement about the structure of positional power. A VP Engineering has the capacity to change outcomes that extend beyond their direct reports. A principal engineer has the capacity to influence architectural decisions across teams. A CTO has the capacity to set organizational conditions that determine how dozens of careers develop or stall. That capacity is not neutral. It generates obligation.
A 2023 note frames the question at its sharpest: “Are you prepared for/have you even considered the individuals who may pass, die, or suffer or kill themselves if you don’t accept your calling and take seriously your responsibility.” [[2023-06-18]] The framing is extreme — and deliberately so. The casualties in engineering organizations are rarely literal but they are real: the engineer burned out by a broken on-call rotation that the VP knew about and didn’t change. The team that shipped security vulnerabilities because the risk conversation was deferred for three quarters. The engineer who left, carrying institutional knowledge and unresolved disillusionment, because a known toxic dynamic was quietly tolerated at the leadership level. These are not abstract harms. They are the measurable consequences of a leader who was within the blast radius and looked away.
A 2022 note / President John Taylor: “Remember that it is no kindness to a transgressor for his local authority to ignore or overlook or try to cover up his iniquity… God will require it at your hands.” [[2022-09-15]] The principle applies precisely in organizational terms: the leader who knows about a problem and ignores it has not been kind. They have transferred the cost to everyone else in the blast radius, plus compound interest for the time the problem was not addressed.
A 2022 note: “As a leader, you have to SELL the idea to people that you can take them where they want to go.” [[2022-08-21]] The blast radius extends forward as well as backward: the leader who is not actively creating the conditions under which engineers can develop, advance, and do meaningful work is failing in the forward dimension of the responsibility. The blast radius is not only the harm that could be prevented. It is also the good that could be created and isn’t.
The decision about where your responsibility ends has already been made — by your position, by your knowledge, and by your capacity to act. The only question is whether you have examined it.
So, Which Decisions Has Your Engineering Organization Already Made?
Five questions — one for each of the decisions that were already being made before this article was read.
First: Audit your calendar from last week. What percentage was pre-committed — the product of forethought — versus reactive? That ratio is the ratio between traction and distraction. It is not a judgment. It is a measurement.
Second: Think about the last strategy you presented. Were you sharing information or transmitting conviction? Would an engineer in the room have been able to tell which it was?
Third: List your three most significant process requirements. Trace each backward: what trust or alignment failure produced it? Is that failure still present — or is the process a scar on tissue that has already healed?
Fourth: Name your organization’s deliberate mediocrity zones. If you cannot name them, they were inherited rather than designed — and an undesigned mediocrity portfolio is one that cannot be managed.
Fifth: Name one person in your blast radius whose trajectory you have the positional power to improve but have not acted on. The inaction is already a decision. Name it explicitly, and then choose again.
The decisions that were already made are not permanent. They are re-decidable — the moment they become visible.
