Most consulting ends with a document. A good one, often — clear, well-argued, expensive. And then it goes in a drawer, because a document cannot enforce itself. The gap between “here is what you should do” and “here is the thing that does it” is exactly the gap where every recommendation quietly dies.
We close that gap on purpose. The last phase of every engagement is called harness, and it is not a metaphor. It is a running system: the invariants we found in discovery and wrote down in specification, now executing — applying the rules, surfacing the judgment calls, and recording every decision against the rule it followed.
Why “harness”
A harness holds something powerful in a known shape. It does not replace the horse; it directs it. That is the relationship we want between the system and the people who run the operation. The harness does the parts that are mechanical and tireless. The people do the parts that are judgment. Neither pretends to be the other.
Three phases, one artifact
- Discovery — find the invariants. Read the history; name the few rules that were always doing the work, and the one surface that is genuinely judgment.
- Specification — write them down, once, where everyone can see them. The spec is not documentation of the system; it is the system’s source of truth.
- Harness — ship the thing that runs the spec. The boundary between rule and judgment is now enforced, not described.
We would rather ship one operation that actually changed than describe ten that didn’t.