Insights
What we think, written down.
Seven pieces of original writing. Most of it argues that the hard part of technology change is never the technology — which is also the reason our clients call us.
A series in three parts
The Willingness Problem.
Why organizations buy transformation and don’t get it — whether the organization is willing to change, why good plans fail anyway, and why the roadmap was obsolete before it was approved.
Part 1 of 3
AI Won’t Save You If You Can’t Change
Your biggest threat isn’t AI, it’s your comfort zone. The work itself has to change — this is about whether the organization is willing to.
ReadPart 2 of 3
Why Good Transformation Plans Still Fail (and the Uncomfortable Fix)
Continues the series on why organizations buy transformation and don’t get it — and what has to be true for the next attempt to land.
ReadPart 3 of 3
Your AI Roadmap Is Already Obsolete
Even a one-year AI plan is too long a horizon to bet on — the tooling you anchor to in month one is replaced by month twelve. Build capability, not a plan.
Read
Everything else
Standalone pieces.
AI
The Five Levels of AI
AI is not one tool but five layers — machine learning, neural networks and deep learning, generative AI, AI agents, Agentic AI. You cannot skip the layers; each builds on the last. Most organizations are stuck at level 1 or 2 while competitors race to level 5.
AI
Addressing Data Quality: The Key to Successful AI Initiatives
Companies spend millions on AI and roughly 80% fail. Everyone wants to be AI-first and nobody wants to fix the data — no governance, no lineage, unmaintained pipelines, duplicates everywhere.
Tooling
Why Your Jira Is Failing (AI Will Make It Worse)
An overbuilt Jira implementation cannot bend to a faster way of working, and AI just made that fatal. More than 90% of failed implementations build complexity before understanding the need — including a Fortune 100 instance with over 2,000 custom configurations.
Delivery
Agile and AI: Lessons from Group Policy
What Agile and AI change, and what they don’t. One feature, a team of about a dozen, over roughly two years, drove an estimated $57B in enabled revenue for Microsoft over its first thirteen years.
Two hours to find out whether we recognise your problem.
No deck, no obligation. We listen, we tell you whether we have seen this before, and we say what we think it would take. If a Jump Start is the right next step we will say so — and if it is not, we will say that too.