# From a Quick Note to a Finished Document

> [!NOTE] The central question
> What should the reader understand, decide, or do when they reach the end?

## Capture the thought

Write the sentence that made the document necessary. Preserve the question, observation, or decision before designing a structure around it.

## Name the reader and outcome

| Reader | What they need | Useful form |
| --- | --- | --- |
| Future you | Context and the next action | Decision note |
| Collaborator | Reasoning and evidence | Brief |
| Technical team | Constraints and behavior | Design document |
| Wider audience | A clear narrative | Report or guide |

## Shape the argument

```mermaid
flowchart LR
  Capture[Capture the thought] --> Question[Name the question]
  Question --> Evidence[Gather the evidence]
  Evidence --> Structure[Choose the structure]
  Structure --> Review[Read for the audience]
  Review --> Share[Choose the final form]
```

## Keep the support close

- [[Source Notes]]
- [[Open Questions]]
- [[Decision Record]]

## Review the difficult parts

- [ ] The opening states the real question
- [ ] Every heading helps the reader navigate
- [ ] Tables make comparisons easier
- [ ] Diagrams are explained in nearby prose
- [ ] Links have meaningful labels
- [ ] The smallest intended screen remains comfortable
- [ ] The exported PDF has deliberate page beginnings and endings

<!-- telescopo:page-break -->

## Choose the handoff

Share Markdown when the source should remain editable and portable. Share PDF when the reading experience and page design matter. Export a diagram as PNG or SVG when the visual needs to travel independently.