# Confirm The Outcome

Use this reference during Phase 3.

## Order

1. Definition of Done
2. Measure Results
3. Retrospect

## Definition Of Done

- Use `attachments/dod.md` as the checklist.
- Confirm unchecked items one by one instead of accepting a vague blanket yes.
- If a DoD item is confirmed not applicable, strike through the checklist text instead of leaving it as a normal unchecked item.
- Prefer this shape for not-applicable items: `- [ ] ~~Feature flags cleaned up (if applicable)~~`
- Add a short note only when the reason would not be obvious from the item text itself.
- Use alignment questions if "done" sounds implied rather than explicit.
- If the user says "done" quickly, ask a concrete evidence question so both sides know what was actually verified.

## Measure Results

- Write results in the dedicated `## Results` section of `attachments/success-metrics.md`, not inside the checklist item.
- Surface the exact metrics from `attachments/success-metrics.md`.
- Ask whether each metric moved and whether a real user ran it.
- Ask what direct user feedback was gathered and whether it supports or contradicts the product data.
- If product data exists without user feedback, mark the outcome as only partially confirmed.
- If answers are vague, use a product or shared-context alignment question to force specificity.

## Retrospect

- Write the retrospective in the dedicated `## Retrospect` section of `attachments/success-metrics.md`, not inside the checklist item.
- Draft what worked, what did not, and the next step:
  - iterate
  - pivot
  - close
