The Resumption Method

A pause should not erase the reason behind the work

Interruption is normal. Projects pause because another deadline arrives, a source needs confirmation, a decision-maker is unavailable, or someone has reached the advanced productivity technique known as sleep.

The Resumption Method records enough grounded context for the next responsible action: Orient → Decide → Act → Record → Resume. It is not a demand to document everything.

1. Orient before acting

Start with current state, not the most recent message. Review the objective, source and evidence, most recent human decision, active boundary, last action and receipt, and stated resume condition. If a source is stale, authority changed, or a boundary is unresolved, end in review or hold.

2. Make the decision visible

State what was decided, who had authority, what supported it, what was deferred, and what would require reconsideration. Finished-sounding text is not an approval receipt. If no decision exists, say so.

3. Take the bounded action

Use literal states: proposed, approved, in progress, completed, held, rejected, or superseded. Preparing a change is not publishing it. Confirm authority before an external, irreversible, sensitive, or high-stakes effect.

4. Record an honest receipt

Record the action, actual state, relevant artifact or destination, material revision, limitations, resulting boundary, and next review point. A saved file does not prove review. A passed test does not prove every workflow.

5. Leave a grounded Resume State

Name the next step, its owner, dependencies, and whether to continue, review, wait, hold, or retire. Do not manufacture momentum when the work needs a pause.

A specific Resume State might say: confirm the launch date with the named owner; if confirmed, return draft version three for review; do not publish or add pricing until both items are approved.