Decision Thread
Keep the decision with the work
A Decision Thread connects the basis, alternatives, human decision, assigned work and returned evidence. It gives the next person a place to continue and keeps unresolved questions visible.
Map a critical workflowA decision stays connected to its evidence
Keep sources, alternatives, uncertainties, and objections with the question being decided.
Read every step
- Establish the basis. Keep sources, alternatives, uncertainties, and objections with the question being decided.
- Name the decision. An accountable person makes the decision and defines the work and its boundaries.
- Return the result. Return the work together with evidence, limitations, and any unresolved questions.
- Review and continue. Compare the result with the intended outcome. Preserve what changed and the next decision.
Make a decision possible to carry through
For an operations leader considering draft assistance, mapping would begin with the choice between manual work, reviewed drafts and automatic replies. Identify the policy, the strongest objection, the person who decides and the evidence needed before any expansion.
A useful mapping scope follows the decision into assigned work and back to review: who prepares a draft, who may send it, what source must accompany it and how missing information is returned. These are questions to resolve with your team, not claims of an automated workflow.
Map your own decision
Bring a material decision, a workflow owner and records your team is permitted to share. A scoped mapping engagement can return an annotated example, a decision and evidence template, a review cadence and next actions.
- Identify the basis, alternatives and unresolved objections.
- Name the human decider, the work owner and the evidence to return.
- Have the workflow owner check the map, mark missing links and agree how a decision cycle will be reviewed.
Acceptance concerns whether the map accurately represents your workflow and makes its gaps inspectable. Better decisions or reduced effort are not presumed.
Using the method
A Decision Thread can be a manual record. Mapping does not require a software subscription. Automation or a Parallax deployment is a separate scope.
Toolkit licensing requires an actual owned package and agreed rights. A proposal identifies the templates or materials supplied, permitted internal use and any follow-up support. Timing and capacity are agreed after scope review.
Review material-use and licensing boundariesTell us what needs to work better.
Map a critical workflow