Principle 16:
Every Route Must Conclude

Plain-English Summary

A OneRoute that does not explicitly end cannot be analyzed, governed, or improved. Every route must include a Conclude step that defines what ‘done’ means.

​

What this Principle Means

Conclude marks a defined end state. Without it, work can drift, repeat indefinitely, or silently hand off to something else. OneRoute requires closure so outcomes are measurable and comparable.

​

Why Closure Matters

Many failures occur not because work was done incorrectly, but because it never truly finished. Explicit conclusion allows accountability, learning, and reuse.

​

What Conclude Represents

• A stable end condition

• A handoff point to another route

• Completion of responsibility for this sequence

​

​​Concrete Examples

Human process: Ticket is resolved and closed.

Observed reality: Work stops but no one knows who owns the outcome.

Natural phenomena: System reaches equilibrium.

​

Mini Case: The Never-Ending Task

A task keeps resurfacing in meetings. Mapping shows no Conclude—only repeated Actions and Decisions. Defining a conclusion eliminates ambiguity.

 

How to Apply This Principle

1. Ask what ‘done’ means for this route.

2. Define the condition explicitly.

3. Insert a Conclude step when that condition is met.

4. If work continues, it is a new route.

​

Common Misunderstandings

• Assuming work ends naturally

• Confusing pauses with completion

• Treating handoffs as implicit

​

Quick Diagnostic Questions

• Where does responsibility end?

• How do we know this route is finished?

• What happens immediately after conclusion?

​

If You Only Remember One Thing

If you cannot point to the end, the route is incomplete.

​

Canonical Statement

Every OneRoute includes an explicit conclusion.