Architecture
Deciding what the environment is, not reacting to what was purchased.
Operating Theory · September 2026
The larger effect may be in organizations that do have IT. Governing a few strategic platforms is a different job from administering hundreds of applications and the integrations between them.
Under the pillar Zero Neo
In a mature environment, a large share of technology effort goes into application administration, integration plumbing, repetitive configuration, and vendor management. None of it is strategic and all of it is mandatory.
Each additional application multiplies that work, because it adds not only itself but its relationships with everything already installed.
If AI performs much of the configuration, workflow engineering, testing, observability, documentation, and maintenance, the function moves upward rather than disappearing.
Deciding what the environment is, not reacting to what was purchased.
Who may configure what, and how a change is reviewed and reversed.
A smaller attack surface to defend properly rather than a large one defended thinly.
Which system is authoritative for which record, enforced rather than assumed.
Working with the business to state outcomes precisely enough to build against.
Concentration risk, exit cost, and what happens when the platform has a bad quarter.
Reviewing what the system built, and catching drift before the business does.
The interesting possibility is that the AI era creates an incentive to consolidate technology rather than continue proliferating it, which is the opposite of what most roadmaps currently assume.
It is also the opposite of what platform vendors have historically been able to deliver, so scepticism is warranted until a real environment has been consolidated and run for long enough to see the maintenance curve.