The Non-Impedance Principle

A step that produces a good result but blocks what follows has failed.

This is the working definition of impedance in a system. Not failure at the local level — failure at the handoff. And it’s where most workflows, decision chains, and organizational processes quietly break down.

The Non-Impedance Principle is The One Rule applied to how you build and operate systems. It answers a specific question: how do you maintain alignment through complexity when the number of steps, people, and variables makes oversight impossible?

You don’t oversee every step. You govern the handoff between them.

Where systems lose alignment

Complex systems don’t fail dramatically. They drift.

A workflow where each step optimizes for its own output rather than its handoff produces friction that compounds invisibly. A decision chain where each choice is locally rational but doesn’t account for what it forecloses produces outcomes nobody designed and nobody can fully explain. An AI implementation where each prompt reaches for the final answer rather than the next clarifying input produces responses that sound right and miss the point.

The misalignment isn’t visible at the step level. It accumulates in the gaps between steps and surfaces as a system that doesn’t work — without a clear diagnosis of why.

The conventional response is more process. More documentation. More oversight. More meetings to align the people who were supposed to be aligned by the process.

None of that addresses the actual problem. The problem is that individual steps weren’t designed with their handoff as the primary obligation.

The principle in practice

The Non-Impedance Principle introduces one standard at every step of any system:

What does the next step need from this one in order to proceed without friction?

This question is deceptively simple. Answering it honestly requires understanding not just what you’re producing but what you’re handing off — and to whom, in what condition, with what information attached.

Applied to workflow design this means every step in a process is evaluated not by its output alone but by the quality of what it passes forward. A handoff that requires the next person to interpret, reconstruct, or compensate for missing information is an impedance point regardless of how well the step itself was executed.

Applied to decision-making this means every choice is evaluated not just by its immediate merit but by what it keeps open and what it forecloses. A decision that solves today’s problem by constraining tomorrow’s options may be locally correct and systemically damaging. Non-impedance asks: does this decision preserve the integrity of the steps that follow?

Applied to AI and chain-of-thought prompting this means each prompt has one job — not to produce the final answer but to produce the next useful input. The goal of a prompt is to not impede the next prompt. The output accumulates across the chain. Reaching for the conclusion at any single step collapses the chain and produces a response that skips the reasoning that would have made it reliable.

Designing for non-impedance

A system designed around this principle looks different from one designed around outcomes.

Outcome-designed systems work backwards from the goal. Steps exist to serve the destination. Quality is measured by proximity to the result. When things go wrong the diagnosis looks at whether the goal was right, whether people were motivated, whether the strategy was sound.

Non-impedance-designed systems work forward from the first step. Each step is designed to hand off cleanly to the next. Quality is measured at the handoff. When things go wrong the diagnosis looks for the impedance point — the step that failed its obligation to what followed — and fixes it there.

In SOPs this means writing each step not as an instruction for what to do but as a specification of what the next step needs to receive. The test of a well-written SOP is whether someone could execute each step knowing only what they’ve been handed and what the next step requires — without needing to understand the whole process.

In organizational decision-making this means every significant choice includes an explicit account of what it hands forward. Not just what it decides — what it sets up, what it constrains, what information it produces for the next decision-maker in the chain.

In personal planning this means your system is evaluated not by whether you reached the goal but by whether each day handed the next one what it needed. A day that was productive but left tomorrow’s priorities unclear has an impedance problem regardless of what it accomplished.

The diagnostic question

When a system isn’t working — personally or organizationally — the Non-Impedance Principle gives you a diagnostic tool more precise than most.

Don’t start at the outcome. Don’t start at the strategy. Start at the first step and move forward asking one question at each transition:

Did this step give the next one what it needed?

The first place the answer is no is the impedance point. Fix it there. Not at the goal level. Not at the motivation level. At the handoff.

This is slower than jumping to a macro diagnosis. It is significantly more likely to produce a fix that holds.