Enabling flow. The condition for sustainable throughput.
Why these rules exist
The Rules of Flow were not created to impose control — they were born to protect systemic execution. In project environments with statistical fluctuation and dependency, traditional metrics and instincts often lead us astray. These 11 rules reframe project work as a system of flow, not tasks.
At their core, the Rules of Flow:
- Reduce chaos by preventing local decisions from harming the system
- Align behavior with flow-based thinking
- Turn execution into a sequence of condition releases, not activity completions
The Impact of the Rules
When consistently applied, the Rules of Flow:
- Reduce firefighting and rework
- Shorten project durations by 30–50%
- Reveal and resolve hidden dependencies
- Clarify priorities and reduce noise
- Increase team accountability and autonomy without micromanagement
Most importantly: they enable flow, the true condition that unlocks sustainable throughput.
0 - Follow the rules.
Act by design, not instinct. Rules protect systemic flow.
The rules exist to protect others from the hidden consequences of your decisions. Breaking them creates unstable starting conditions for the system.
1 - Create exceptional value.
Work toward the system’s true goal: flow.
Value is measured by how well your output becomes someone else’s input — and enables movement.
2 - Focus. Avoid multitasking.
One task at a time releases better conditions. Start less. Finish more.
Multitasking delays flow. You don’t just slow yourself — you hold back the system.
3 - Focus on the critical path.
The constraint controls the system’s pace. Feed it clean, feed it first.
Delay or disruption at the constraint blocks everyone. Protect it with priority and precision.
4 - Your decisions create conditions.
Your output becomes someone else’s starting point (Every choice has ripple effects).
You don’t just complete a task — you release a condition that impacts global outcomes.
5 - Protect throughput.
System output must be protected through intentional design that absorbs variability.
Throughput degrades unless variation is absorbed. Don’t balance capacity — balance flow.
6 - Be effective, not efficient.
Local efficiency is irrelevant if the system doesn’t move.
Progress means flow — not polish. Release early, work small, and help the system breathe.
7 - Do it now.
Don’t hold the baton — flow breaks when one node stalls.
Acting late costs more than working slow. Protect others by moving when it’s your turn.
8 - Do the right thing.
Flow depends on truth. Bad data = bad decisions = broken outcomes.
Inaccurate reporting creates false conditions that damage the system. Say what’s real — early and clearly.
9 - Keep it simple.
Flow thrives on clarity. Confusion is friction.
Complex outputs slow others down. Make your handoffs readable, usable, and fast to act on.
10 - Plan the work. Beat the plan.
Plans are tools, not chains. Release conditions that unlock flow.
A rigid plan fails under variation. Adapt faster than the system slips.
