Legacy, modernised. House still standing.
Rebuild the foundation while the business runs. Validation-first, strangler-pattern, weekly deploys without customer-facing outages. The work that proved validation in regulated context.
Rebuild the foundation while the house is still standing.
ERGO Digital was an enterprise spinoff tasked with modernising the insurance giant's digital capabilities. Legacy systems had been running reliably for decades, but they couldn't support the speed and flexibility the market demanded.
Constraints were real. Regulatory compliance couldn't be compromised. Existing customer operations couldn't be disrupted. The team needed to deliver new capabilities while simultaneously modernising the foundation underneath.
Three movements, in order.
The work split into three phases. None original. The value was in choosing them, sequencing them, and refusing the fourth.
Strangler pattern
Incrementally replace legacy components. New capabilities built in modern stack, gradually absorbing legacy functionality. No big-bang rewrite.
Validation sprints
Before major architectural investments, rapid validation cycles to test assumptions. Avoided costly mistakes by validating direction before committing resources.
Continuous delivery
CI/CD pipeline enabling automated testing and deployment. Quarterly releases became weekly deployments, with zero downtime, in a regulated industry.
Validation in enterprise context.
This engagement demonstrated the value of the Validation Sprint in enterprise context. When the cost of being wrong is high, validation before commitment becomes essential, not optional.
The key insight: enterprise constraints don't prevent rapid validation. They make it more important. When you can't afford to be wrong, you need to validate faster, not slower.
"In enterprise transformation, the biggest risk isn't building the wrong thing. It's building the wrong thing for two years before realising it. Validation Sprints compress that learning cycle from months to days."
Jędrzej Tabaczyński
What stayed.
The transformation finished. The defaults remained.
Weekly release cadence
Smaller, more frequent releases reduced risk and enabled faster feedback. Quarterly was a memory.
A validation-first habit
Major architectural decisions began with a sprint, not a six-month plan. The pattern survived three leadership changes.
Strangler-pattern playbook
Documented, repeatable approach to legacy migration. Other ERGO units adopted the playbook for their own systems.
Feature-flag discipline
Feature flags became a default deployment tool. Risk-managed rollouts replaced risk-managed delays.
Modernising while the business runs?
Enterprise transformation requires both strategic patience and tactical speed. The constraints don't prevent rapid validation, they make it essential.