They knew where they wanted to go. Not where to start.
MS Mode runs on a platform that carries most of the stack. They want to move away from that monolithic setup towards an ecosystem with a separate content management system and best-of-breed solutions that work together.
What they did not have was a starting point. Which parts to move first, what the move buys them, what it costs, and whether staying put was the better answer for some of it.
So they asked us for a roadmap and a business case they could take to the board.
Score the landscape, then let the matrix set the order
A composable journey is a sequence of decisions, and each one costs money. We built the framework to make those decisions comparable, and we made them together with the MS Mode team rather than for them.
Build the framework and score it
We listed every capability you need to run an e-commerce operation, then walked through all of them with the team and formed one shared view: which solution covers what, and how well.
Plot impact over effort
The scores went into an impact-effort matrix. Highest impact for the lowest effort at the top, the rest in line behind it.
Sequence and cost it
Which solutions to replace, in what order, how long each step takes, and how much budget it needs.
Write the decision document
One document for the board: the roadmap, the reasoning behind the order, and the budget the execution needs.
Four questions per capability
Coverage
Which solution fulfils this capability today, and is that the solution you think it is?
Promise
Does that solution live up to what it was bought to do, in practice and not on paper?
Satisfaction
Are the people who work with it every day satisfied with it? Their answer counts as data.
Replaceability
How hard would it be to swap it out for something else in a composable landscape?
Three artefacts, one decision
Capability scorecard
Every e-commerce capability, the solution behind it, how well that solution performs, and how replaceable it is.
Impact-effort matrix
Every candidate for replacement, placed on impact and effort. The order of the roadmap comes straight out of it.
Roadmap and decision document
Sequence, duration and budget per step, written so the board can approve it and the team can start on it.
A framework of our own, and a blueprint we did not invent
We have sat on the client side of this decision. That is the perspective we bring to it.
E-commerce Capability Framework
Every capability an e-commerce operation needs, with a score, a satisfaction read and a replaceability read per capability.
MACH reference architecture
We used the MACH Alliance reference framework as the blueprint for how the services in a composable landscape integrate.
More of our work
All cases →
Thinking about leaving your monolith?
We score your landscape with your team, put impact next to effort, and hand you a roadmap with a budget on it. Then you decide what moves and what stays.