Insights
Short and long-form reflections on the practical craft of turning strategy into outcomes, written from a personal point of view.
Most enterprises that set out to build their own AI capability are quietly funding a science project. The smarter default is to buy, integrate, and reserve building for the few places it earns its keep.
Read the articleMost stalled work is not short of effort. It is short of one name against the outcome. Shared ownership is just a polite word for no ownership.
Done badly, governance is theatre that slows everyone down. Done well, it is the architecture of the decisions an organization owns: who decides what, by when, and who lives with the result.
Most strategies don't fail at the whiteboard. They fail in the weeks afterwards, when nobody owns the cadence that turns intent into motion.
When the path is unclear, a leader's job is not to fake certainty. It is to make the uncertainty smaller for everyone else.
Trust is not a soft nicety. It is the load-bearing infrastructure that lets an operating model run without constant escalation.
Being AI-ready is less about models and more about the operating model. The bottleneck is rarely the technology: it is adoption, governance, and measurable value.
A transformation office that collects status is a tax on the program. A useful one removes the friction that stops work from finishing.
A pilot proves the model can work in a clean corner. Scaling proves whether your organization can. Those are different problems, and most companies only fund the first.
A dashboard can glow green while the business gets no better. The problem is not the data. It is that we measure motion and call it progress.
Waiting for everyone to agree is not patience. It is a way to avoid deciding, dressed up as inclusion.
Reorganizations move boxes and rename them. The operating model is how decisions, work, and information actually flow, and that often survives the reorg untouched.
Automating a messy process does not fix it. It just lets you run the mess at scale, faster, and with less chance of anyone noticing.
Two transformations with the same plan can end very differently. The order you do things in is the variable that decides which one you get.
A steering committee that only shares status is not steering. It is watching, with snacks.
You cannot bolt intelligence onto a foundation you do not trust. Before AI readiness is a model question, it is a data and ownership question, and that part is boring on purpose.
Vision is cheap and abundant. What is scarce is the discipline to ship the unglamorous version that actually works.
The most expensive delays in any process do not happen inside a team. They happen in the silence between two teams, where work waits and no one is watching.
Change makes the current model work better. Transformation replaces the model. Confusing the two is why so many programs stall halfway.
Centralize and you gain leverage but lose speed. Federate and you gain context but lose coherence. The skill is not picking a side; it is knowing which to apply where.
Every workaround you keep is a small loan against the future. Operational debt rarely breaks anything. It just quietly caps how fast you can grow.
Anyone can launch a new initiative. The rarer and more valuable act is killing the ones that no longer matter.