The Cummulative Flow Chart That Was Still Telling the Truth
A CTO’s old chart still looked fine to him. What had actually changed wasn’t the chart — it was what it was counting.
Team Conflict as Decision-Rights Problems
Corporate PO says one thing, local PO says another. Is it a loyalty test — or a decision nobody actually assigned?
The Process That Worked at 15 Developers Breaks at 50
More output, more frequency, less productive somehow. What changes structurally between fifteen developers and fifty — and why discipline alone can’t fix it?
The Missing 'So That': A Case Study in Distance
AI can write a user story. It can’t have the conversation that makes it mean something. A case study in distance.
Faster Delivery Doesn't Fix an Unclear Backlog
AI makes your team faster. It won’t tell you what’s worth building. Here’s why the backlog question still comes first
10x Productivity: What the Promise Leaves Unaccounted For
Your team’s “10x” AI-accelerated capacity isn’t stable — it fluctuates unpredictably. Is your planning accounting for that?
No time to change: When Knowing There's a Better Way Isn't Enough
Knowing there’s a better way isn’t enough. What stops teams from changing — even when the cost of staying stuck is obvious?
The Comfort of a Bad Outcome
Why do teams cling to broken processes? A UCL study explains more about software delivery than you might expect.
What 'Done' Really Means: The Definition That Changes Everything
A static Definition of Done produces static results. An evolving one creates productive crises that force teams to improve sustainably.
What Happens After Your Two-Year Agile Transformation (And Why Lasting Change Takes Longer Than You Think)
Two years of agile transformation delivers the structure. Lasting change requires building the capability to keep improving. Here’s the difference.