One task at a time
- Colin Li
Ask for a plan only after the design is approved:
Turn the approved design.md into an implementation plan in plan.md. Break it into small tasks. For each task: which file changes, the exact steps, and how I check with my own eyes that it worked before moving on. Number them. Put a checkbox on each one. Then stop and let me read it.
A plan of this size usually contains eight to twelve tasks. Read the list and apply one test to each task: can you check the result yourself in about a minute?
If you cannot: Task 3 is too big — I can't check it in one look. Split it.
Then approve the plan and have the tool work through it one task at a time:
Do task 1 only. Nothing else. Then stop and tell me exactly what to open to check it.
Check the result. Tick the box. Say next.
One task at a time keeps the cause of a fault identifiable. If several changes are made together and the page stops working, any of them could be responsible.
If the same task fails twice, stop rather than trying again. Say: Stop. Don't fix it. Explain in plain English what you think the problem is, and give me two different approaches with the trade-off of each.