This guide gives you a reusable starting pattern. It is designed to help you see the work more clearly; it is not a substitute for judgment, source checking, or responsibility for the result.

01
Set up the task

Prepare the inputs before you ask for output.

The model only sees what you give it. Spend a few minutes naming the reader, desired result, and uncertain information. This makes a first draft easier to assess and reduces the need for decorative rewriting later.

A starting prompt

Give the task a useful brief.

Help me turn these project notes into a one-page decision memo.

Decision to make: [state one decision question]
Decision owner and audience: [who will decide and who will read]
Source notes: [paste notes with source labels and dates]
Known constraints: [time, budget, policy, technical, or relationship limits]

First, separate the notes into evidence, assumptions, options, and unresolved questions. Then draft a memo with: (1) decision question, (2) relevant context, (3) evidence with source labels, (4) options and trade-offs, (5) recommendation only where the evidence supports it, (6) risks and unanswered questions, and (7) the next confirmation needed from the decision owner. Do not invent facts, source links, costs, approvals, owners, or dates. Label any inference as an inference.

Replace every bracketed field with your real context. Read the output before reuse.

03
Work the system

Four steps that keep the result usable.

  1. 1

    Name one decision that an accountable person can actually make.

  2. 2

    Paste notes with their source labels and dates, rather than a polished summary.

  3. 3

    Ask AI to separate what is known from assumptions before it recommends anything.

  4. 4

    Have the decision owner verify the evidence, trade-offs, and next step before sending.

04

Begin with the decision, not the document

A memo becomes vague when it starts with a broad project recap. Write the exact choice the reader needs to make first. That gives every later section a test: does this fact, option, or question help the owner decide? If it does not, move it to an appendix or leave it out.

05

Give each claim a trail back to the note

Use short labels such as [Budget call, 12 Aug] or [Customer interview 04]. The model can then retain a trace beside important claims instead of converting several notes into a confident paragraph with no visible origin. This makes the memo much faster for a decision owner to verify.

06

Keep options and recommendations separate

An option describes a possible path and its stated trade-offs. A recommendation states which path appears best and why. The difference matters when the notes are incomplete: AI can organize options, but it should not turn a partial preference into an approved recommendation.

07

End with the question that unlocks the next move

A useful memo does not pretend every uncertainty is solved. Close with the smallest confirmation, evidence check, or owner decision that would allow work to move. A visible unresolved question is more useful than a made-up deadline or approval.

08

A worked example: build or buy

A product team deciding whether to build or buy a reporting component has notes from a spike, a vendor trial, and a finance conversation. The memo keeps the decision question at the top, groups the spike evidence under “options”, and leaves the recommendation conditional: “buy if the trial data confirms the query limit”. The owner can then act on one check instead of re-reading the notes.

09

Keep the memo a decision aid, not a record

The memo exists to make one decision easier. Every paragraph should survive the test “does this help the owner decide?”. Facts that only provide background belong in an appendix or the source notes. If the evidence is thin, say so and name the check that would settle it rather than forcing a confident recommendation.

Page-specific practice

Practice: turn one confirmed question into a decision memo

Use this page when a reader needs to understand a choice, not merely receive a status summary. Begin with one decision question and keep the record behind each important claim visible.

Start withA dated note set, the decision owner, the options actually discussed, and source labels for material evidence.
Useful outputA short memo with separate sections for context, options, evidence, recommendation, unresolved questions, and the decision still required.
Do not inferDo not turn a proposed option into an approved decision or fill missing evidence with plausible-sounding explanation.
Verify before reuseThe decision owner should reopen the cited records and confirm that the recommendation, trade-offs, and next action are represented accurately.
Before you use the output

Run a human check.

  • Can the reader identify one decision owner and one decision question?
  • Does every material claim retain a source label, date, or clear “needs verification” marker?
  • Are options described separately from any recommendation?
  • Did the draft avoid inventing a cost, date, approval, owner, or source?
  • Is the next confirmation specific enough for the decision owner to act on?
Reader-owned review trail

Keep your human check visible.

Mark the checks you have personally reviewed. This is a local reading aid—not evidence that a claim, commitment, or decision is correct.

0 of 5 checks reviewed0%

This checklist is stored only in this browser when storage is available. It is not sent to Knexio or used for analytics.

Field note

AI is strongest here when it makes missing information, structure, and options easier to see. The moment an output becomes a claim, commitment, or decision, bring a person back into the loop.

Page-specific workflow boundary

Choose this page when a confirmed decision needs explanation

This page turns an authorized choice into a reader-facing memo; it is not a tool for deciding on behalf of a team.

InputInput: confirmed decision, supporting notes, audience, trade-offs, and known limitations.
OutputOutput: a decision memo that explains what was chosen, why, what changes, and what remains uncertain.
Do not use it forDo not use it when the record contains only options or discussion; return to evidence review first.
Author & review record

Maintained by Workflow Library’s editorial desk.

This guide is published by Workflow Library, an independent educational project for practical AI workflows. The editorial desk reviews task scope, source visibility, stated limits, and the human checks readers need before reusing an output. It does not claim a personal credential, test result, or lived experience that has not been published and verified.

About the publication
Editorial recordOrganization byline
Published
Last reviewed