How to Run Retrospectives That Actually Improve Team Performance
Most retrospectives produce action items that go nowhere. Here’s the five-element structure that separates theatre from genuine improvement
From Diagnosis to Direction: What Comes After Recognising the Lags
Recognising that you have platteaud in your improvement journey is only the start. Here’s what the practical path to sustained improvement actually looks like.
Momentum Lag: When "We're Doing Scrum" Becomes the Ceiling
Momentum Lag occurs when framework adoption is treated as destination rather than foundation, causing productivity gains to erode without continued systematic improvement.
Value Lag: When Process Conformance Replaces Problem Solving
Over the past two weeks, I’ve explored patterns that signal agile transformations have plateaued. Week 1 introduc…
Behavioral Lag: When Practices Change But Patterns Don't
Behavioral lag occurs when organisations adopt new practices but communication patterns don’t evolve, causing both sides to revert to old habits under pressure.
Has your agile transformation stopped delivering returns? Three Lags That Signal Your Transformation Has Plateaued
Three patterns explain why agile transformations plateau: behavioral lag, value lag, and momentum lag between adopted practices and business results.
Designing a Communication Infrastructure That Reduces Friction
How to reduce communication friction with availability windows, distributed decisions, and distinguishing real constraints from behavioral patterns you’re compensating for.
I Want to Speak to a Human Who Can Make Decisions
The story about a MOT that revealed a systemic problem in how organisations deal with decisions.
Communication Friction: Are Your User Stories Growing?
When user stories grow from cards to paragraphs, you don’t have better requirements—you have communication friction you’re compensating for with text.
The Skills You Optimized For Are Now Your Bottleneck
How “give it to the most capable developer” creates structural dependencies, and why your technical strengths now bottleneck team capability.