Insights
Thinking on engineering transformation, flow measurement, and the organisational design questions nobody wants to touch.
Your AI Strategy Is Incoherent — Here’s How to Tell
Your CEO declares AI-first. Your CISO blocks every tool request. Legal takes 90 days to approve a $500/month licence. You haven’t picked a lane — and the inconsistency is costing you credibility, talent, and time.
You Don’t Have an Agile Problem. You Have a Power Problem.
Transformation programmes fail because they redesign process and leave the power structure untouched. Capital allocation, decision rights, incentive structures — the variables nobody touches are the only ones that matter.
Why Frameworks Fail
SAFe, LeSS, Spotify — all installed, none changed measurable outcomes. The missing variable isn’t the framework. It’s the structural reform that nobody wants to make.
When Teams Game Metrics: What Anomaly Detection Reveals About Culture
Identity swapping. Timestamp tampering. Bulk status changes at sprint boundaries. These aren’t data quality problems. They’re diagnostic signals about incentives, psychological safety, and power.
The Delegation Problem: Why AI Made Intent the New Bottleneck
AI made production cheap. But it made intent, validation, and accountability the new constraints. That’s an organisational design challenge, not a tooling one.
The Dashboard Delusion
Your delivery metrics report green. Your teams say they’re on track. Meanwhile, cycle times are rising, WIP is 3x capacity, and nobody can explain why. Dashboards don’t lie — they just show you what you asked for.
Specification-Driven Delivery: Governing What AI Builds
Five governance layers for AI-assisted delivery: context, enforcement, specification, proof, and review. How to maintain quality and accountability when code generation is no longer the bottleneck.
Resistance Is Relational, Not Just Personal
Resistance in Agile change efforts isn’t a personality flaw or a knowledge gap. It’s a relational signal — produced in the space between people, not inside one of them.
Process Behaviour Charts for People Who Hate Statistics
When your cycle time jumps from 14 to 18 days, is that a problem or just noise? Process behaviour charts answer this question with four simple rules. No statistics degree required.
Percentiles, Not Averages: Why Your Forecasts Are Wrong
Your average cycle time is 14 days. This number is meaningless. Percentile-based forecasting replaces the fiction of the average with a conversation about probability that leaders can actually use.
Flow Debt: The Hidden Liability in Your Delivery System
The gap between your proxy-based cycle time and your actual cycle time grows wider every quarter. Flow debt is governance theatre, quantified — and most organisations don’t know they’re accumulating it.
Brownfield First: Why You Can’t Just Let AI Rewrite Your Codebase
Before AI rewrites anything, you need to recover current behaviour. Characterisation tests, boundary mapping, incremental delegation — the scaffolding most organisations skip and discover the cost later.
AI Is an Amplifier — Your Engineering Culture Determines Your ROI
The orgs getting 10x returns from AI already had strong engineering practices before AI arrived. If your foundations are broken, AI amplifies the dysfunction. A diagnostic framework for what to fix first.
Want to know when new articles drop?