Principle 13:
Repetition Is Structural

Plain-English Summary

Whenever work repeats, that repetition is not accidental—it is structural. In OneRoute, all loops, rework, retries, and cycles must be represented explicitly using Repeat.

​

What this Principle Means

Repetition is often treated as error, inefficiency, or poor execution. OneRoute treats repetition as a design feature of the route itself. If something loops, the structure allows—or requires—it.

​

Why Repetition Must Be Explicit

Hidden loops distort cycle time, mask capacity demand, and frustrate improvement efforts. Explicit repetition makes cost, delay, and risk visible.

​

What Repeat Represents

Repeat is used when:

• A step or sequence returns to a prior point

• Completion depends on a condition changing

• Rework or retry is expected behavior

​

Concrete Examples

Human process: Reworking a document until it meets criteria.

Observed reality: Tickets cycling between teams.

Natural phenomena: Seasonal cycles, feedback loops, oscillation.

​

Mini Case: The Endless Review

A review process seems slow. Mapping reveals repeated Observe - Decision - Action cycles. The problem was not diligence—it was an unbounded Repeat with no exit criteria.

 

How to Apply This Principle

1. Identify where steps return to earlier points.

2. Use Repeat to make the loop explicit.

3. Define the exit condition clearly.

4. Measure frequency and duration of the loop.

​

Common Misunderstandings

• Treating rework as human failure

• Hiding loops in narrative text

• Using Decision when behavior is truly cyclic

​

Quick Diagnostic Questions

• Where does work come back to the same step?

• What condition ends the loop?

• How many times does the loop typically run?

​

If You Only Remember One Thing

If work repeats, the route allows it—model it explicitly.

​

Canonical Statement

All repetition in OneRoute is explicitly represented as structure.