Find a useful approach
Browse standards, frameworks, notations, and teaching methods. Understand the problem each one was created to solve.
Browse all approaches →AI OUTPUT FIELD GUIDE
Choose the form.
Understand the work.
Some questions need a clear sentence. Others need a model, a diagram, or something you can explore.
Learn the approaches behind useful output: where they came from, when they help, and how to put them to work.
30 approaches · 90 short drills · useful with or without AI
One workshop, three useful views
Follow the registration steps
First check whether this person already has a confirmed registration. If so, return the existing confirmation. Otherwise require an email address, then check remaining places. Confirm when a place is available; add to the waitlist when the workshop is full.
1. Check for an existing confirmation.
2. If it exists, return it without reserving a place.
3. For a new registration, require an email address.
4. If a place is available, confirm and reserve one place.
5. Otherwise, add the new registration to the waitlist.Makes visible: Action order and conditions.
Leaves out: A paragraph makes overlapping cases harder to compare than a table.
Inspect the decision order
The duplicate check precedes validation and allocation for a new registration. This is an authored flow illustration, not a complete BPMN model.
Existing confirmation? · No: evaluate new request → New: email supplied? · Yes: evaluate capacity → Place available?
Makes visible: The order in which questions are considered.
Leaves out: The flow does not define every possible validation failure or operational retry.
Compare the cases
Read from the first row down. This teaching table uses first-match behavior. A real DMN table needs its hit policy declared explicitly.
| First matching condition | Outcome | Places consumed |
|---|---|---|
| Existing confirmed registration | Return existing confirmation | 0 |
| New registration, no email | Ask for email | 0 |
| New, email supplied, place available | Confirm | 1 |
| New, email supplied, no place | Waitlist | 0 |
Makes visible: The interaction between duplicate, email, and capacity conditions.
Leaves out: A table does not show the user interface or message delivery.
Start with your question
You can start from a task, a familiar name, or simple curiosity.
Understand a complicated subject Build a mental model you can explain and test.Explain something to another person Choose the structure and depth your reader needs.Write instructions someone can follow Make prerequisites, conditions, actions, and checks visible.Describe a system or process Show boundaries, relationships, order, and state without mixing them.Compare options and record a decision Connect a choice to reasons, evidence, and revisit conditions.Specify requirements and rules Turn intentions into explicit behavior and inspectable cases.
Explore. Learn. Apply.
Drill into the ideas
Change the view of a case, spot an ambiguity, or explain a result yourself. Every exercise includes a reasoned answer.
Open the learning desk →Take a structure with you
Use a manual template, an optional prompt, and a checklist to judge the result. Keep the conditions that matter.
Choose a task →A few good starting points
Plain language
Help the intended reader find, understand, and use the information they need.
Diátaxis
Choose documentation around whether someone is learning or working, and doing or understanding.
C4 model
Explain a software architecture through a small set of consistent levels of detail.
Worked examples
Study a complete solution with reasons before attempting a related problem.
A clearer answer still needs checking. This guide separates a useful representation from evidence that its contents are correct. Read the editorial method →