Process Experiments
Part of Email and message workload
Choosing when to move a long message thread into a decision record
Recognise when a thread needs a findable answer, distinguish pending from settled decisions and record the current outcome.
Move a message thread into a decision record when others need a stable answer they can use without re-reading the exchange. That point may come before the thread is long: a short discussion can settle a choice that changes other people’s work. A long discussion with no decision needs a clear pending status, not a record that presents a suggestion as final.
Recognise the handover point
A thread needs a clearer home when people repeatedly ask which option was chosen, newcomers need the full history, the subject has changed or replies keep restating positions. A decision that affects a process, handover or future deliverable also needs to be findable beyond the original recipients.
Identify the discussion’s current state before writing the record:
| State | Next move |
|---|---|
| The authorised person has made a choice | Record the decision and tell the thread where it lives. |
| The owner is known but input is missing | Record the open question, missing input, owner and next decision date as pending. |
| Authority is disputed | Resolve who may decide before marking any option final. |
| The issue concerns carrying out an earlier choice | Keep the earlier decision and move the new task or obstacle into the work record. |
Extract the answer, not the transcript
Draft a short record where the affected work is managed. Include the decision question, status, owner, date, chosen option if settled, main reason or trade-off, and next action. Keep only the context needed to use the answer. A reference to the original discussion can provide detail, but the record should make sense without it.
If the choice is still open, label it pending and say what is needed next. For example: “Pending: operations lead to confirm by Friday whether the revised handover covers weekend support.” If the thread contains incompatible answers, ask the authorised person which one governs. The latest message is not necessarily the decision.
Redirect and maintain the record
Reply to the thread with the current position and the record’s location. If a proposed summary still needs confirmation, identify who must confirm it and by when. When a rapid exchange would help resolve an open issue, bring the relevant people together and update the record afterwards.
If the authorised owner later changes the decision, amend or supersede the record and state what changed and when. Someone who missed the thread should be able to find the current answer, tell whether it is final and know what to do next.
Checklist: Is your message thread ready to become a decision record?
- ✅ A decision has been made by the authorised personYes
- ✅ The decision affects future work, processes or deliverablesYes
- ✅ New team members can understand the outcome without reading the full threadYes
- ✅ The record includes the decision, owner, date, reason and next stepsYes
- ✅ The original thread is redirected to the recordYes
