A common ask: “The new platform must include everything it includes today - we’ll improve it later”. The current platform is usually the result of years of iteration, exceptions, and undocumented decisions. Rebuilding it one on one sounds safe, but it often means recreating complexity, technical debt - and missed opportunities. And the truth? That “later” rarely comes - and the cost of copying the past is huge.
Lessons I’ve learned:
Replatforming is finally there! Time to solve EVERYTHING. You start gathering requirements, but the finish line keeps moving. Nobody wants to compromise. Every feature is a must-have...
Lessons I’ve learned:
Keeping daily operations going is not the same as transforming them. I’ve seen strong teams underestimate how much change demands in terms of time, focus, and mindset. That’s when transformation gets stuck. Companies are excellent at running their business - but running change is a different skill altogether.
Lessons I’ve learned:
Headless, API-first, MACH - it’s the new standard. But one pattern keeps repeating: companies try to go composable everywhere at once. Swapping a monolith for five SaaS tools sounds modular - but it can explode your scope, budget, and timelines. Not everything needs to be replaced right now.
Lessons I’ve learned:
