In Edition #7, we examined how a system can operate within its approved boundaries while carrying an unresolved instruction. In Edition #8, we looked at the translation boundary: the point where a strategic decision becomes the signal presented for execution.
This week, we follow that signal into the measures we use to determine whether the work succeeded.
A directive can be completed while carrying a different meaning from the one leadership committed to. Every assigned task can be finished. Every approval can be recorded. The dashboard can show progress while leaving a consequential question unanswered: what, exactly, did that progress carry into existence?
Return to the expansion from Edition #8: an enterprise entering a new market while protecting its target margin. Leadership approves the initiative, and the operating plan assigns responsibilities across sales, finance, and operations.
Sales launches the campaign. Operations establishes delivery capacity. Finance reports performance. The launch happens on schedule, and the organization records the initiative as complete.
But suppose the instructions never resolved which objective takes precedence when customer acquisition and margin protection conflict.
Sales uses discounts to accelerate adoption. Operations adds capacity to support the resulting demand. Finance absorbs those choices into its forecast. Each team completes its work using an interpretation that appears reasonable within its own responsibilities.
The enterprise has executed. It has also committed resources around a trade-off that remained open in the originating signal.
Completion tells us that the work occurred. It does not, by itself, establish that the work preserved the decision.
This distinction matters because completed activity becomes the starting condition for subsequent activity. A pricing exception becomes a precedent. An added resource becomes part of the operating baseline. A forecast incorporates an assumption that future plans now treat as established.
The interpretation acquires organizational weight through use.
By the time leadership reviews the financial result, the original open choice may be difficult to distinguish from the decisions made around it. The organization sees the margin variance, the additional capacity, or the need for another approval. Recovering how those conditions arose requires tracing the work back through the signal that authorized it.
That investigation has a cost. So does revising the work already built around the assumption. Those costs form part of the Friction Tax: the accumulated financial and operational consequence of structural resistance moving through the enterprise.
A completion measure remains useful. It answers whether an assigned activity reached its defined endpoint. Fidelity asks a different question: how faithfully did the signal carrying the decision survive its passage into execution?
That question does not require deciding whether the strategy was correct. Leadership may have made a sound strategic choice. The issue is whether the expression sent into execution established the commitments, priorities, and boundaries needed to carry that choice.
When a workflow depends on a trade-off, someone or something must resolve it. If leadership leaves it open, the operating environment encounters it later, under conditions that may already involve committed capital, labor, or automation.
Examining the signal before execution surfaces that unresolved condition before further work depends on it.
We can then distinguish a decision that has been expressed from one that execution will still have to supply.
The question is larger than whether the organization finished what it was assigned. It includes whether the assignment carried what the organization intended to create.
Action does not create the signal. It carries it.
The standard is alignment.