Enterprise Jira Migration Crisis
Migration scenario in. Strategy, risks, and comms out.
Describe the migration shape (source, target, scale, constraints) and get back a migration strategy, risk register, rollout plan, and a draft stakeholder memo.
Migration scenario
Output
What this lab does
Takes a real migration scenario — source, target, scale, hard constraints, and what's currently broken — and returns the kind of document a staff engineer would write after a half-day with the team: strategy, risk register, ordered rollout plan, draft stakeholder memo, and an honest section on what the team is underestimating.
Why the structure matters
Each section is built for a different audience reading the same scenario. The risk register is for the engineering manager. The rollout plan is for the working team. The memo is for leadership. The "underestimating" section is the senior-engineer gut check that keeps the rest honest.
How to read the output
- The "what you're underestimating" section is the highest-signal one — read it first.
- The risk register's likelihood/impact are calibrated for the scenario you gave, not for migrations in general.
- The memo is a draft. The voice should be edited to match yours before sending.