Rebuild or refactor?
Four questions, two paths. Follow your answers down the drawing; where they lean is yours to weigh.
- What still works?Leans towards change in place: Most of what users need still worksLeans towards a rebuild: Little of it works, or only the parts nobody needs
- What blocks change?Leans towards change in place: The blocks sit in a few places you can nameLeans towards a rebuild: The blocks run through the foundation
- How long is the platform supported?Leans towards change in place: Fixes still ship, or a supported version is within reachLeans towards a rebuild: Support has ended, with no supported version to move to
- What can your team carry?Leans towards change in place: Keeping it running while it changes underneathLeans towards a rebuild: Running the old one while a new one grows beside it
No single answer decides it, and neither path is quicker by default: how long either takes depends on your product.
Where each path leads
If your answers lean towards change in place: Move off an ageing framework without stopping the product
If they lean towards a rebuild: Rebuild a legacy web application without losing what works
The four questions in full, with an example of each path: Rebuild or refactor? A decision guide
The next guide: What does waiting add up to?
Lift your eyes and let us carry the rest.
Talk to us and see what carrying your product forward looks like.
Book a conversation
Prefer to write directly? contact@zefana.com