Insights
Fresh thinking on flow, capacity and the economics of getting the right projects finished. Newest first.
Topics: Constraints and Bottlenecks · Resource Management · The Cost of Delay · Portfolio Decisions · Value and Business Cases · Planning and Estimating
-
Queuing Theory and the Variability Tax: Why Smoothing Your Work Beats Adding People
Read the piece: Queuing Theory and the Variability Tax: Why Smoothing Your Work Beats Adding PeopleQueuing theory shows why two teams at the same utilization can wait very differently, and why smoothing the work usually beats adding more people.
-
The Ceiling Behind the Ceiling: Why Elevating Your Constraint Returns a Fraction of What You Paid For
Read the piece: The Ceiling Behind the Ceiling: Why Elevating Your Constraint Returns a Fraction of What You Paid ForProject constraints usually mean scope, time and cost. Delivery speed is set by one shared resource, and elevating it just moves you to the next ceiling.
-
The Hiring Dip: Why Adding People to Your Constraint Makes You Slower First
Read the piece: The Hiring Dip: Why Adding People to Your Constraint Makes You Slower FirstBrooks's law says adding people to a late project makes it later. The hiring dip explains why, prices it, and shows when hiring into the constraint pays.
-
The Frozen Portfolio: Why an Annual Plan Commits Your Constraint on the Least Information You Will Ever Have
Read the piece: The Frozen Portfolio: Why an Annual Plan Commits Your Constraint on the Least Information You Will Ever HaveAnnual portfolio planning locks in your scarcest capacity at the exact moment you know the least, then holds it fixed while the year proves you wrong.
-
The Absorption Constraint: Why Your Finished Projects Are Not Earning Yet
Read the piece: The Absorption Constraint: Why Your Finished Projects Are Not Earning YetBenefits realization usually tracks whether value showed up. The real limit is whether the organization had the capacity to absorb the change at all.
-
The Shape of Delay: Why Two Projects Losing the Same Month Do Not Lose the Same Money
Read the piece: The Shape of Delay: Why Two Projects Losing the Same Month Do Not Lose the Same MoneyWSJF divides cost of delay by duration and treats delay as a constant rate. Most projects follow a curve instead, and the curve can flip your sequence.
-
Phantom Capacity: Why Your Plans Are Built on Hours That Do Not Exist
Read the piece: Phantom Capacity: Why Your Plans Are Built on Hours That Do Not ExistCapacity planning multiplies headcount by a calendar. Those hours vanish into leave, support and switching long before any project sees them.
-
Scope Creep: Why Projects Only Ever Grow, and What the Scope Ratchet Costs
Read the piece: Scope Creep: Why Projects Only Ever Grow, and What the Scope Ratchet CostsNobody approved doubling the scope. It arrived one reasonable addition at a time, and the ratchet only ever turns one way.
-
The Expedite Tax: Why Rushing One Project to the Front Delays Everything Behind It
Read the piece: The Expedite Tax: Why Rushing One Project to the Front Delays Everything Behind ItFast tracking project management compresses one schedule. Expediting a project to the front of a shared queue shortens it too, and the work behind pays.
-
Decision Latency: Why Your Projects Wait Longer for a Yes Than They Spend Being Worked On
Read the piece: Decision Latency: Why Your Projects Wait Longer for a Yes Than They Spend Being Worked OnAdvice on the decision-making process is about choosing well. In a portfolio the larger cost is how long the choice takes, and nobody measures it.
-
Theory of Constraints and the Non-Constraint Trap: Why Making Other Teams Faster Does Nothing
Read the piece: Theory of Constraints and the Non-Constraint Trap: Why Making Other Teams Faster Does NothingThe theory of constraints says one resource sets your pace. Flow Economics prices every project against it with value per constrained resource hour.
-
The Rework Spiral: Why Redoing Work Costs Far More Than Doing It Once
Read the piece: The Rework Spiral: Why Redoing Work Costs Far More Than Doing It OnceRework looks like ordinary progress on every meter a manager watches. The rework spiral prices what redoing the same work is actually costing you.
-
The Pause Penalty: What Shelving a Project Really Costs
Read the piece: The Pause Penalty: What Shelving a Project Really CostsPutting a project on hold looks free. The value clock keeps running, a project restart costs more than resuming would, and the capacity is rarely freed.
-
The Dependency Tax: Why Connecting Two Projects Costs More Than Either One
Read the piece: The Dependency Tax: Why Connecting Two Projects Costs More Than Either OneProject dependencies read as a free arrow on the plan. The dependency tax prices the merge bias, shared risk and hidden queue behind that arrow.
-
The Watermelon Report: Why Your Status Dashboard Goes Green Until the Week It Goes Red
Read the piece: The Watermelon Report: Why Your Status Dashboard Goes Green Until the Week It Goes RedA project status report template alone will not catch trouble early if it still tracks percent-complete. Buffer management is the number that does.
-
The Case for Smaller Projects: Why Batch Size Decides How Much Value You Capture
Read the piece: The Case for Smaller Projects: Why Batch Size Decides How Much Value You CaptureBatch size is usually a delivery habit, not a decision. Priced as an economic choice, the big batch costs more, and pays back later than the small one.
-
Full Kit: Why the Best Time to Start a Project Is When It Can Actually Run
Read the piece: Full Kit: Why the Best Time to Start a Project Is When It Can Actually RunProject initiation usually means a charter and a kickoff. Full kit asks a harder question: once the work starts, can it actually run, or will it stall?
-
How to Find the One Resource That Sets Your Delivery Speed
Read the piece: How to Find the One Resource That Sets Your Delivery SpeedBottleneck management usually means managing the busiest team. The constraint is different, and the clone test tells you which one you actually have.
-
Your Estimates Are Padded, and Your Projects Are Still Late
Read the piece: Your Estimates Are Padded, and Your Projects Are Still LateEstimation bias makes everyone pad toward the worst case. Aggregated buffers absorb that safety once, at the chain, not wasted task by task.
-
The Capacity Paradox: Why Busy Teams and Waiting Work Go Together
Read the piece: The Capacity Paradox: Why Busy Teams and Waiting Work Go TogetherWorkflow efficiency often ends up measuring how busy people are. Flow efficiency measures how much of a work item's life is spent being worked on.
-
The Utilization Trap: Why 100% Busy Is the Slowest Way to Run a Portfolio
Read the piece: The Utilization Trap: Why 100% Busy Is the Slowest Way to Run a PortfolioA road jams long before it is full, and so does a team. Why ninety-five percent busy is the slowest way to run a portfolio.
-
Little's Law and the Portfolio WIP Limit: Start Less to Finish More
Read the piece: Little's Law and the Portfolio WIP Limit: Start Less to Finish MoreA portfolio where everything has started is not moving faster. Little's law shows why: the fix is a work-in-progress limit, not more effort.
-
Resource Allocation: Stop Ranking Projects by How Big They Are
Read the piece: Resource Allocation: Stop Ranking Projects by How Big They AreResource allocation by project size puts the biggest promise first. Ranking by return per constrained hour puts the most valuable first.
-
Why Your Best People Should Do One Thing at a Time
Read the piece: Why Your Best People Should Do One Thing at a TimeMultitasking your scarcest specialist across three important projects looks like good prioritization. It delays all three, and the delay has a price.
