> Markdown version of [/videos/100006-you-will-migrate-eventually-a-developer-approach-to-technology-adoption?t=1307](https://www.wearedevelopers.com/videos/100006-you-will-migrate-eventually-a-developer-approach-to-technology-adoption?t=1307). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# You Will Migrate Eventually: A developer approach to technology adoption

Technical debt is a high-interest loan drawn for execution speed, not an engineering failure. Discover how ING's phase-based tech adoption model scales backend architecture without drowning in legacy code.

- **Speakers:** [Luisa Rink](https://www.wearedevelopers.com/@luisa-rink), [Wouter Ligtenberg](https://www.wearedevelopers.com/@wouter-ligtenberg)
- **Event:** World Congress 2026 Europe
- **Published:** July 9, 2026
- **Duration:** 24:46
- **URL:** https://www.wearedevelopers.com/videos/100006-you-will-migrate-eventually-a-developer-approach-to-technology-adoption

## Summary

Technology adoption and evolution are inevitable, heavily influenced by Lehman's law which dictates that software must constantly change to survive. When ING scaled its SME banking offering by acquiring the fintech startup Lendico, engineering teams faced immense pressure to integrate core systems and launch new products rapidly. To prevent rapid prototyping from devolving into unmanageable legacy code, ING developed a phase-based Tech Adoption Model inspired by Lex Sisney's organizational physics. This framework treats technological migration not as an afterthought, but as an integral process mapped directly to the product lifecycle, allowing engineering teams to scale smoothly without drowning in early systemic shortcuts.

The framework moves through distinct stages, dictating varying strategies for architecture and technical debt. During the explore and pilot phases, development focuses on rapid prototyping and reusing global infrastructure—like authentication flows and customer data storage—while keeping initial test builds thoroughly isolated to avoid tying flawed prototypes into legacy stacks. As the product enters the build phase, engineers must continuously manage incoming feature requests, treating accepted technical debt as a conscious financial loan drawn for execution speed. This loan carries escalating interest rates and a strict repayment deadline that comes due during the scaling phase, where peak organizational value quickly bottlenecks infrastructure and forces teams to pause feature development to refactor backend latency and bugs.

As applications mature into the operational phase, teams must proactively reserve resource capacity for continuous, underlying system migrations, such as updating operational dependencies or migrating away from outdated repositories. Ultimately, the adoption framework stresses that all technology reaches an eventual end, demanding a distinct stage characterized by graceful shutdowns. Engineering teams must practice detaching emotionally from code they wrote to swiftly retire deprecated features, an approach demonstrated when ING rapidly rolled back an underperforming onboarding funnel to minimize negative customer impact and reallocate valuable developer capacity.

**Keywords:** technology adoption model, legacy system migration, organizational physics, technical debt management, rapid prototyping strategy, product lifecycle phases, graceful feature shutdown, software evolution laws, fintech stack integration, continuous system refactoring, engineering capacity planning, technology deprecation process, software scaling limits, infrastructure bottleneck mitigation

## Chapters

1. **Acknowledging the inevitability of software evolution and technology migrations** (00:17) — Because software environments constantly evolve, engineering teams must view architectural migrations as entirely normal operational requirements.
1. **Integrating an acquired startup and evaluating technical debt challenges** (04:13) — Scaling an acquired minimal product into a full banking portfolio exposes the severe limitations of temporary technical shortcuts.
1. **Visualizing product lifecycles through a technology migration model** (06:18) — A migration model based on organizational physics connects a product's timeline and business value to specific technical actions.
1. **Entering the sprout phase by reusing global technology stacks** (08:16) — Leveraging existing global components during the initial exploration phase eliminates early migrations and dramatically accelerates preliminary development cycles.
1. **Preventing early migrations with rapid prototyping in the piloted phase** (09:50) — Gathering early feedback through rapid prototyping allows teams to validate ideas quickly without committing to flawed, tightly coupled systems.
1. **Managing scope and intentional technical debt during the build phase** (11:42) — Product building requires strict scope control and documenting conscious technical debt as temporary speed loans that must be repaid.
1. **Balancing new features with system stability in the scaled phase** (14:21) — As organizational value peaks, teams are forced to refactor accumulated technical debt to prevent systemic outages and sustain further scale.
1. **Ensuring stable product maintenance during the operated phase** (17:31) — Maintaining mature products involves continuous, underlying infrastructure upgrades to preserve organizational value and prevent unexpected dependency failures.
1. **Retiring technical products with intention through graceful shutdowns** (19:10) — Recognizing when a feature causes negative impacts enables teams to execute immediate rollbacks and communicate graceful retirements efficiently.
1. **Key takeaways for navigating software evolution and technical debt** (21:47) — Adapting to inevitable technological changes requires managing debt intentionally, aligning strategies with lifecycle stages, and showing courage during deprecation.
1. **Managing feature scope and transitioning between technological adoption phases** (23:06) — Teams naturally transition between structural phases over time, but initial requirement planning must remain robust even as needs evolve.

## Related Moments

- [Evaluating tech stack migrations driven by industry hype](https://www.wearedevelopers.com/videos/1365-wearedevelopers-live-the-weekly-developer-show-with-chris-heilmann-and-daniel-cranney) (from " WeAreDevelopers LIVE - the weekly developer show with Chris Heilmann and Daniel Cranney")
- [Transitioning across tech stacks into mobile application development](https://www.wearedevelopers.com/videos/555-flutter-packages-and-plugins-a-look-under-the-hood) (from "Flutter Packages and Plugins - A Look Under the Hood")
- [Using failed adoption to drive necessary architectural improvements](https://www.wearedevelopers.com/videos/100233-when-human-meets-canary) (from "When human meets canary")
- [Adapting legacy product ecosystems and identifying technical red flags](https://www.wearedevelopers.com/videos/1700-ai-changed-the-game-how-vcs-rethink-product-talent-technical-moats) (from "AI Changed the Game: How VCs Rethink Product, Talent & Technical Moats")
- [Post-migration technical debt cleanup and sociotechnical reflections](https://www.wearedevelopers.com/videos/730-migrating-half-a-million-users-to-a-new-payment-service-provider) (from "Migrating half a million users to a new payment service provider")
- [How the inevitable march of time breaks software patterns](https://www.wearedevelopers.com/videos/647-defeat-that-legacy-monster-guerilla-refactoring-with-web-standards) (from "Defeat that legacy monster! Guerilla refactoring with web standards")

## Related Articles

- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [Ignore the Hype: How to Avoid Being Deceived by Technological Trends](https://www.wearedevelopers.com/magazine/528-ignore-the-hype-how-to-avoid-being-deceived-by-technological-trends)
- [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production)
- [MLOps – What’s the deal behind it?](https://www.wearedevelopers.com/magazine/125-mlops-what-s-the-deal-behind-it)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Senior Web Designer, Growth](https://www.wearedevelopers.com/jobs/ext/102722-senior-web-designer-growth) at **Intercom, Inc.**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [AI Software Engineer (Germany)](https://www.wearedevelopers.com/jobs/48317-ai-software-engineer-germany) at **Sunhat**
- [Senior Software Engineer, React (Investing & Trading)](https://www.wearedevelopers.com/jobs/ext/1937625-senior-software-engineer-react-investing-trading) at **Bitpanda**
- [Lead Software Engineer (f/m/d)](https://www.wearedevelopers.com/jobs/48296-lead-software-engineer-f-m-d) at **Personio SE & Co. KG**