Review and improve

What changes today

The delegated work is reviewed against What done looks like.

The response is not the result yet.

The result becomes progress only when review improves the outcome note or confirms a usable deliverable that is saved or linked where the work lives.

You are creating

A reviewed progress mark in the outcome note.

Before review, the AI response is only delegated work.

After review, one of these things is true:

the outcome note is clearer
the context is better
the next action is more specific
the deliverable is saved or linked where the work lives
the result is rejected, and the note now explains what must improve before the next delegation

Copy this into your note

Use a review notes section to practice the review process. Once comfortable, this section can be skipped in favor of editing What done looks like or the attached context directly.

## Review notes
[brief notes about what's good/bad that can be used to improve the outcome note]
- [What helped]
- [What needed fixing]
- [What the note or context likely failed to make clear]
- [What should improve before the next delegation]

Answer in your note

What's good? Ensure future delegations maintain this standard.
- What part of the delegated result might be best?
- Does the What done looks like section reflect what was done well?
What's bad? Prevent the same errors in the next delegation.
- What missing context or unclear detail might have caused the problem?

Examples

Weak review:

The result looks useful.
The note does not change.
The next action is still unclear.

Better review:

The result is compared against What done looks like.
Useful details are promoted into the note.
A recognized gap leads to a clearer What done looks like section, better context, or improved next action.

Decision path:

Result state	What it means	What to do next
Not useful yet	The output exposed a gap.	Improve the What done looks like section, context, or next action before delegating again.
Almost useful	The output is directionally right but incomplete.	Add necessary details to the What done looks like section. Avoid revising the deliverable directly.
Useful enough	The output matches your intent and expectations.	Save or link the deliverable from the outcome note.

Checkpoint

The delegated result was reviewed, and the note improved or the deliverable was saved/linked where the work lives.

Same loop, bigger outcome

For a small outcome, with practice, the first delegation may produce a usable deliverable.

For bigger, more complex, outcomes, expect the first loop to provide useful insights, not complete the final outcome. The reviewed result should make the note better enough to continue: clearer outcome, better context, or better next action.

Repeat the loop when the output reveals missing context, a bigger deliverable, or a next sub-outcome.