No tags match.
Most transformation governance protects the sponsor rather than the outcome. One test sorts governance from theatre: has the forum ever changed a decision?
Day rate is the worst available way to buy engineering, and procurement keeps using it because it’s the only number that fits in a comparison table. What to buy instead, and when the day rate is still right.
AI programmes rarely stall because the migration failed. They stall because the migration programme was quietly the operating model, and it ended. The case for a permanent platform team.
Uber burned its entire 2026 AI budget in four months, then capped its engineers per tool. The real failure was not the spending – it was the lack of visibility, and any line between token cost and the value actually shipped.
SpaceX’s $60 billion acquisition of Cursor turns a model-neutral developer layer into a single-owner dependency. Here’s what engineering leaders should re-underwrite before the deal closes.
In one month, the enterprise software industry bought its way toward agents that act rather than advise. The controls to govern them are running behind.
The Model Context Protocol has shifted from a technical curiosity to a default question in enterprise software evaluation. Following CircleCI’s June 2026 MCP server release and Databricks’ move to govern MCP services in Unity Catalog, this article explains what MCP changes for integration cost, vendor lock-in, and AI governance, and sets out the practical procurement questions technology leaders should write into their evaluations.
At WWDC 2026, Apple unveiled a rebuilt Siri powered by a custom Google Gemini model reported to carry 1.2 trillion parameters, at a reported cost of roughly $1 billion a year. This article argues the deal is a template rather than a surrender: Apple rented the frontier model but kept the customer relationship, the data path, the context layer, and the interface. It sets out the four-part playbook enterprises should copy – task-level model bake-offs, gateway architecture that keeps providers swappable, owned small models for routing economics, and treating context as the proprietary asset – alongside the dependency and concentration risks of renting without an exit.
After every major outage the same advice circulates: go multi-cloud. For most organisations, the resilience that matters is an architecture decision, not a procurement one.
A CloudBees survey of more than 200 enterprise technology leaders found that 81% reported an increase in production issues linked to AI-generated code, even as 92% remained confident their code was production-ready before shipping. This article examines the verification gap created when AI generates code faster than teams can validate it, the rising and largely untracked costs that follow, the absence of clear governance ownership, and the practical steps engineering leaders can take to close the gap.
AI data centres are projected to consume more energy than Germany and France combined by 2030, yet most enterprise AI strategies are still built on the assumption that compute is cheap and limitless. This article examines the energy and infrastructure constraints that are closing the brute-force compute era, and sets out the practical architecture shifts – task decomposition, context discipline, evaluation-driven model selection – that organisations need to make now.
