Made for Engineers
Recommend a Legacy System Migration Without Overselling It
Also useful for: Engineering Managers, people in Technology
120 min
Advanced
Decisions
Improve Operations
Need to Compare Options
Build a defensible legacy-system recommendation with explicit tradeoffs, uncertainty ranges, decision gates, and a phased path that limits avoidable disruption.
Create a free account to save your progress and use this Playbook.
Use this when
A legacy system is creating concern, investment is being discussed, and stakeholders need a clear recommendation without false certainty or technical overload.
You'll need
- System context
- Decision deadline
- Planning horizon in months
- Service criticality
- Failure and support evidence
- Migration estimates
- Delivery constraints
- Stakeholder needs
- Risk posture
You'll get
- Current-state exposure separated into facts, assumptions, and unknowns
- Migration, containment, and retention compared against consistent criteria
- Decision gates and disqualifying constraints documented
- Expected, adverse, and delay scenarios tested
- One recommendation tied to explicit conditions
- Phased delivery path with validation and rollback points
By the end of this playbook
You will have:
- Current-state exposure separated into facts, assumptions, and unknowns
- Migration, containment, and retention compared against consistent criteria
- Decision gates and disqualifying constraints documented
- Expected, adverse, and delay scenarios tested
- One recommendation tied to explicit conditions
- Phased delivery path with validation and rollback points
Sample
This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.
Sample input
I support a mission-critical order platform with four priority incidents in the past year and a database leaving standard support in nine months. One specialist holds most recovery knowledge. A vendor estimates $2.4 million to $3.1 million and 18 months for replacement, but data cleanup and internal labor are excluded. Peak-season changes are frozen for four months, and only two engineers are available. Leadership wants a recommendation before annual planning closes.
Sample assembled prompt
Recommendation: Fund immediate containment and a... Why this path wins: - Containment... - A phased migration addresses the... - The vendor estimate isn't... Decision conditions: - Approve phase 1... - Approve build phases after the... - Reconsider containment-only if the validated... Confidence: Moderate. The direction is supported, but total...