Modernization decision
Production Path Decision
Choose what to keep. Be precise about what must change.
Compare hardening, refactoring, re-architecture, replacement and stopping against the constraints of your actual product or estate.
What you receive
The result of this engagement.
A justified choice between retaining, hardening, refactoring or replacing, with the sequence and conditions for the chosen path.
- An option comparison covering retain, harden, refactor, re-architect, replace or stop as relevant.
- A defensible recommendation with cost/time assumptions and confidence limits.
- A transition sequence, boundary map and exit criteria for the chosen path.
When this helps
Recognize the situation.
- A rewrite is being proposed without a clear comparison of alternatives.
- A review has exposed problems, but the response is still disputed.
- You need a credible sequence that protects useful capability while addressing structural risk.
How the work unfolds
Evidence appropriate to the question.
Validate the baseline
Use a sufficient existing diagnosis or agree the additional investigation needed.
Compare credible options
Assess boundaries, cost and time assumptions, operational risk, reversibility and implementation dependencies.
Recommend a path
Explain the preferred option, rejected alternatives, sequencing and conditions for revisiting the decision.
Implementation handoff
From a chosen path to delivery planning
The handoff identifies the preferred option, rejected alternatives, boundary changes, sequence and exit criteria. Cost and time assumptions remain decision models with stated confidence, not delivery commitments.
Your engineers use that direction to plan and estimate. Further design is useful only where unresolved interfaces, data or operating boundaries need it; the path decision does not automatically require a full blueprint.
Scope & responsibility
Agree the depth. Keep the boundaries clear.
Scope of the engagement
This can follow a Sparkling assessment or use adequate evidence from another source. It does not require a prescribed prior purchase.
Appropriate reliance
Estimates are decision models with stated confidence, not delivery guarantees. Detailed design and implementation are agreed separately.
The agreed engagement sets the coverage, deliverables, responsibilities, timing and fees. Changes to that scope are agreed explicitly.
Practical questions
Before engaging us.
Will you recommend a rewrite?
Only if the evidence and option comparison justify it. Retaining sound architecture and hardening a specific area may be the better response.
Can our existing audit be the starting point?
Yes, if it provides an adequate and relevant baseline. We identify evidence gaps before agreeing the scope.
Related work
Related architecture contributions
Each contribution is available as a standalone service when the evidence and scope support it.
What is the decision you need to make?
Share the situation and the intended commitment. We will establish whether this scope fits.