What AI Amplifies First Is Your Worst Habits.
Capability is now cheap. What you do with it is not.
The organisation you give to AI is the organisation it accelerates.
That is the only sentence that matters before procurement begins. Capability is no longer the constraint. Process clarity is. The board does not yet see this. Some of the technology leadership team does, and most of them are not saying it out loud.
Remediation now happens at AI speed. Whatever debt the organisation chose to defer last year, it will pay for at several times the rate. Whatever boundary it chose not to draw, it will need to draw under load, in front of an auditor, with a customer impact already underway. The institutions adopting AI before bounding their own processes are not investing in capability. They are pre-funding a remediation programme they have not yet named.
The proof.
Andy Jassy’s 2025 letter to shareholders carries the cleanest external evidence we have. The Amazon Bedrock team rebuilt the inference engine in seventy-six days with six engineers. The original estimate was forty engineers and roughly a year. The new engine, Mantle, became the backbone of a service that nearly doubled month-over-month in March. It processed more tokens in a single quarter than in all prior years combined.
That compression ratio is the headline. What is underneath it is more interesting.
The engineers did not work faster because the tool was faster. They worked faster because the scope was bounded correctly. A separable group. A clear architectural decision, not a tweak, a different architecture (a complete rebuild, not a refactor). A defined outcome. Six very skilled engineers. The AI did not produce the discipline. The discipline produced the AI outcome.
The amplification is not selective.
AI is being framed as a capability investment across the industry. It is not. It is an amplifier of whatever clarity, ownership, and discipline already exist inside the organisation that adopts it.
Where clarity exists, the amplification is real. Where clarity does not, the amplification is also real.
The amplification does not pick.
The IBM Institute for Business Value’s 2025 survey of 1,300 senior AI decision-makers reported what most of us already suspect. Organisations that ignored their technical debt before adopting AI saw project returns drop by close to a third. Timelines stretched by more than a fifth. The population-level numbers from MIT’s 2025 study sit alongside it. Ninety-five percent of AI projects fail to reach production or deliver value. None of these figures measure the model. They measure the organisation around the model.
The honest question for the board, therefore, is not how much AI to adopt. It is what condition the organisation is in before the adoption begins. That question is harder to ask because the answer is uncomfortable. It is easier to fund a tool than to fund a process audit. Easier to declare an AI roadmap than to admit what the organisation does not currently know about its own estate.
Where the new model meets the old.
I have lived this in a different form already.
Some years ago, in a team I was leading, we adopted Domain Driven Design and event-driven architecture as the direction. The decision was correct. We had the mandate to stand up separate teams in the new domain space. We did, and the new model worked. The bounded contexts held. The events flowed cleanly. By any internal measure, the architecture was a success.
The failure mode was elsewhere. It surfaced at the seams.
Wherever the new domain touched the existing landscape, the old patterns tried to leak in. Legacy data models brought their assumptions with them. Legacy interfaces brought their semantics. Legacy teams brought their habits.
The new model was not under attack. It was being slowly translated back into the old one at every boundary.
We resolved it the way DDD anticipates this exact problem. Anti-Corruption Layers. Explicit translation between the new domain and the legacy estate. The ACLs did the work the architecture alone could not. They protected the new model from being absorbed by the old one.
The lesson was not that DDD was wrong. The lesson was that the architecture is never the only design decision. The boundary is. Where you do not draw it, the old pattern leaks into the new.
AI is the same problem at a different scale.
The model is not the question. What you build around it is.
Process clarity, ownership, audit, and the discipline to refuse scope creep are the institutional equivalent of an Anti-Corruption Layer.
Without them, the old organisation leaks into the new capability. Faster than before. Louder than before. With more board-level visibility than before.
What this means for large institutions.
In a large institution, the worst habit is rarely the obvious one. It is not the cost of change. It is not the duration of programmes. It is the compounding organisational liability that no balance sheet has yet been willing to recognise. The quiet rhythm by which decisions are deferred to preserve scope. The pattern by which urgent beats important on a schedule the institution refuses to name.
AI does not change that pattern. It runs it faster.
The institutions that prepare for AI by examining their own readiness, drawing their boundaries, and protecting their new capability from their old habits will spend less and finish more. The institutions that prepare for AI by signing procurement contracts will pay twice. Once for the tool. A second time, larger and less visible on the budget line, for the remediation the tool makes inevitable.
The tool does not change what you are. It changes how fast you become it.
If you found this useful, the likelihood is someone you know is asking the same question. Pass it on.