· 6 min read
Red to Green: The First 30 Days of Rescuing a Programme
A programme in trouble rarely needs more people or a new plan on day one. It needs the truth, less work in flight, one owner and an honest decision.
15 articles on business.
· 6 min read
A programme in trouble rarely needs more people or a new plan on day one. It needs the truth, less work in flight, one owner and an honest decision.
· 7 min read
Why smaller, specialised AI models now beat ever-bigger ones on cost and practical value, and what that means for enterprise AI strategy.
· 5 min read
Approvers have learned to discount optimistic plans. The cases that get funded test their numbers against how similar projects really turned out.
· 7 min read
When autonomous AI agents go wrong: the business continuity and liability risks, and the controls leaders need before deploying them.
· 7 min read
AI business cases obsess over model prices, which are now a rounding error. What decides whether AI pays is the people checking its work, and what they miss.
· 5 min read
Cloud spend keeps rising, and organisations believe nearly a third of it is wasted. The fix is ownership and unit costs, not another dashboard.
· 5 min read
Most of your software is open-source code nobody vetted. Attackers know it. How to treat dependencies like the suppliers they are, without slowing teams down.
· 5 min read
Staff paste client files, patient notes and recordings into public AI tools every day. Why it matters, and why private AI is now the sensible default.
· 7 min read
A low rate prices an hour, not finished software. What really decides the cost of a development team: output, your own people's time, and the cost of waiting.
· 5 min read
Data programmes stall because they start with the data, not the decision. Start with the decision, and you need far less data, and get answers far sooner.
· 17 min read
A board-level guide to getting real value from cloud, AI and DevOps together, rather than more stalled transformation projects.
· 5 min read
Most pilots prove the technology works, then stall. A useful proof of concept tests whether people will use it, whether it pays, and when to stop.
· 18 min read
A practical guide for non-technical leaders to turn business goals and KPIs into clear, testable technical requirements.
· 19 min read
How leaders can tell costly scope creep from a smart strategic pivot, and govern changing requirements without derailing the programme.
· 7 min read
Programmes rarely fail by a little. The three predictable ways they lose money, and why a short Discovery need only prevent a sliver of it to pay.