Unit 13 · Phase 1

The Flow Problem

Why everything feels stuck

Pulse Works office, Wednesday morning. The team's task board shows seven items stuck in "In Progress." Nothing has moved to "Done" in four days. Ren stares at it. Tetsu is on a call at his desk. Saki arrives for a cross-team sync and immediately notices the board.

Ren (蓮) "I don't get it. Everyone's busy. The schedule says we should have three deliverables finished this week. But nothing's actually done."

Saki (咲希) "Being busy isn't the same as making progress. Look at your board — everything is in progress, nothing is flowing through. You have a flow (the movement of work through a system from start to finish) problem."

→ Flow is the First Way in The Phoenix Project: work should move smoothly from left to right, from idea to delivery. When everything is "in progress" but nothing finishes, the system is clogged.

Ren (蓮) "But we've got the right activities assigned to the right people. The plan looks fine on paper."

Tetsu (哲) "Paper doesn't show wait states. I finished the spatial mapping module two days ago. It's waiting for my code review. I'm the only reviewer. I'm also building the gesture engine and debugging the CRM integration."

→ Tetsu is describing a bottleneck: three workstreams depend on one person. No matter how fast the rest of the team works, the system's throughput is limited by Tetsu's capacity.

Ren (蓮) "So the problem isn't that people are slow. It's that work is piling up in front of you."

Tetsu (哲) "I didn't say that."

Ren (蓮) "You didn't have to. The board says it for you."

Saki (咲希) "There's a concept for this. The Three Ways — it's a framework from a book called The Phoenix Project. The First Way is about flow: making work move smoothly from left to right. The Second Way is about feedback (creating short loops so problems are caught early and information flows back upstream). The Third Way is about learning (building a culture of experimentation and continuous improvement, where failure is a teacher, not a punishment)."

→ The Three Ways provide a systems-level view: optimize flow, amplify feedback, and foster continuous learning. They complement PMBOK's process-oriented approach with a focus on how work actually moves.

Ren (蓮) "So right now we're failing at the First Way. Work goes in but doesn't come out. What do we do about it?"

Saki (咲希) "Start by making the bottleneck visible. Then limit how much new work enters the system until existing work flows through. And create feedback loops so you see blockages as they form, not after they've caused delays."

→ Saki is prescribing the first steps: visualize the constraint, limit work in progress, and establish rapid feedback. These build on schedule management and resource planning from prior units.

Ren (蓮) "Where did you learn about The Three Ways? That's not exactly standard PMBOK."

Saki (咲希) "I read widely." She paused, then reached into her bag. A slightly worn paperback. The Phoenix Project. "You might find it useful."

She handed it over without making eye contact. Ren noticed a page was dog-eared — Chapter 31, about The Three Ways. She'd been thinking about his project before she arrived.

Concept Discovery — The Three Ways

1 The First Way: Flow. When Ren looked at the board and saw seven items stuck in "In Progress," he was seeing a flow failure. The First Way says: optimize the movement of work from left to right — from concept to completion. Work piling up in front of Tetsu isn't a people problem; it's a system problem. The schedule showed tasks assigned and sequenced, but it couldn't show that three dependency chains converged on one person. Flow thinking asks: where does work wait? What causes the wait? How do we remove the wait — not by making Tetsu faster, but by changing how work moves through the system?
Tip If your "In Progress" column is always full but "Done" is empty, you don't have a speed problem — you have a flow problem. Start by counting how many items are waiting versus how many are actively being worked on.

2 The Second and Third Ways: Feedback and Learning. Saki's suggestion to "create feedback loops so you see blockages as they form" is the Second Way in action. Without feedback, Ren didn't know Tetsu's code review queue was growing until four days had passed. The Third Way — learning — means treating each flow failure as an experiment: what caused it, what can we change, and how do we verify the change worked? This connects directly to resource planning: if the team had reviewed Tetsu's allocation weekly (feedback) and adjusted assignments based on what they learned (learning), the blockage might never have formed.
Phoenix Project Connection In The Phoenix Project, the protagonists discover that most delivery delays aren't caused by slow workers but by invisible queues, unmanaged handoffs, and the absence of feedback. The Three Ways provide the mental model to see — and fix — the system.

← Budget Battles Seeing the System →