One-page target design for the refactor
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Big refactors drift when nobody can say in two sentences what the code should look like at the end.
First tasks
- Sketch the current structure of the affected modules on one sheet
- Write the two-sentence problem statement in terms of change cost
- List five things the refactor will not touch
- Ask two engineers from the affected code to review the page