Phoenix Project Lessons For DE
The Phoenix Project is 13 years old. Data teams still run their backlogs the way it warns against.
The book’s core warning applies to data work almost word for word: unplanned work eats the planned work, and nobody sees it happening.
For a data team, unplanned work has friendly faces. A “quick pull” for sales. An exec dashboard by Friday. A backfill after someone’s schema change. Each one small, each one urgent, none of them in the queue.
In Michelin-star kitchens, orders land on one rail, in sequence. Nobody cooks from something shouted across the pass. The rail is the point: demand is visible, ordered, and finite.
What that looks like for a data team:
- One intake. Every request lands in the same queue, including the CEO’s.
- Order by business demand, and say no out loud.
- Cap work in progress. 2 pipelines in flight beat 6 half-built.
- One protected slot for debt, every sprint.
Teams I’ve seen adopt this roughly halve their cycle time within a quarter.
How does work actually enter your data team’s queue?
Fractional Data Architect helping startups and scaleups build data platforms that scale.
More about Thomas Nys →