Writing a good revision instruction

A revision runs on one clear instruction, up to 400 characters. The quality of the instruction decides the quality of the revision, and the rule is simple: one change at a time.

One change per revision

One change at a time keeps the map coherent. When an instruction asks for three things at once, the revision has to interpret how they interact, and the result drifts. Three changes means three revisions. Each one lands cleanly, and you can check the map between them.

What a good instruction looks like

The panel's own placeholder is a good model: "Keep Offboarding and Aftercare as a single workflow." It names the exact structures involved and states one outcome.

Two more in the same pattern:

• Split the proposal phase so each service sends its own proposal.
• Add a check-in email two weeks after delivery to the Offboarding workflow.

Each instruction names what changes, and nothing else. No background, no reasoning, no second request folded in.

Be specific about names

Refer to workflows, steps, emails, and forms by the names they carry on the map. The revision works from your map's structure, so the closer your instruction sits to the map's own labels, the less room there is for interpretation.

State the change. Name the structures. Stop there. That is the whole craft of it.