Five Whys, One Real Cause: A Story About Not Stopping Too Soon
An anonymized scenario showing how the 5 Whys finds the real cause of a recurring problem — and the trap of stopping at the first plausible answer.
Read more →Insights
Practical guidance on capital projects, governance, financing, and delivery for Indigenous and public-sector leaders.
An anonymized scenario showing how the 5 Whys finds the real cause of a recurring problem — and the trap of stopping at the first plausible answer.
Read more →An anonymized scenario about a Scrum team whose Product Owner had the title but not the authority — and what changed when that was fixed.
Read more →A composite story of two business cases for the same project — one that collapsed under scrutiny and one that survived — and what separated them.
Read more →Total cost of ownership counts everything a purchase costs over its life — not just the sticker price. Here is how to use it without overcomplicating things.
Read more →A kaizen event is a short, focused burst of process improvement by the people who do the work. Here is how one is structured and what makes it stick.
Read more →Velocity is a planning aid, not a scoreboard. Here is what it actually measures, how to use it well, and how it gets abused.
Read more →A project charter is the short document that authorizes a project and aligns its people. Here is what belongs in one and why it matters before any work starts.
Read more →Supplier qualification is where supply risk is either caught or invited in. Here is the difference between a disciplined process and a hopeful one.
Read more →Most 5S programs look great for a fortnight, then quietly slide back to clutter. The difference is almost never the first four S's — it is the fifth.
Read more →Story points are meant to help a Scrum Team forecast, not to grade developers. Here is the difference between estimation that informs and estimation that performs.
Read more →Scope creep rarely arrives as one big change. It seeps in through small favours. Here is how disciplined teams catch it early — and how the rest find out too late.
Read more →Most procurement 'strategies' are just a list of suppliers and a budget. Here is a practical checklist to build one that actually holds up under disruption.
Read more →