article
Modernisation needs subtraction
Replatforming a tangled estate without removing obsolete behavior merely gives old complexity a new invoice.
Emil Shirokikh · Published September 4, 2026 · Updated September 23, 2026 · 2 min read
Abstract
Modernisation succeeds when it narrows the system: fewer interfaces, fewer duplicated truths and fewer manual exceptions. Technology replacement alone cannot provide that discipline.
Retire before replatforming
Moving every obsolete path to a new stack preserves complexity and creates a larger migration bill. Modernisation should narrow the estate.
Portfolio exercise
Map capabilities, users, interfaces and records. Mark retain, replace, consolidate or retire; then migrate behind reconciled boundaries with an expiry date for duplication.
Evidence to retain
Report retired interfaces and manual exceptions alongside delivered replacement features.
Challenge the conclusion
Some duplication is necessary during transition. It needs an owner and an expiry condition.
Use this in a working session
Select one capability and require the team to name what disappears when its replacement launches.
BELTO editorial analysis. It does not describe a client engagement or claim a commercial result.
References
2 sourcesAuthor
Emil ShirokikhFounder
Founder of Belto Inc. Writes on engineering, venture building and applied intelligence.
Related
Read next
Most AI pilots should be killed sooner
The polite fiction around enterprise AI is that every pilot teaches something. Many teach only that nobody defined the decision, owner or failure cost.
AI agents need boundaries, not personalities
The market is decorating automation with human traits while neglecting permissions, reversibility and evidence.
A computer-vision demo is not a system
Benchmark accuracy says little about glare, drift, maintenance, latency or the operator who must act on an alert.