Turn shared flows into practical manuals for the people who use them.
Guidelines creates per-role, task-oriented usage manuals from the flows a role actually takes part in, then tracks when their source material changes.
Product walkthrough
Guidelines, in context.
Demo project data shown for illustration.
Screen 01 / 02
Dispatcher operations guide
A role-specific manual keeps the exception queue and customer promise visible.
The working path
A focused loop around the same project context.
An operations lead needs a concise manual for support agents that explains how they work a returns flow, not a broad description of how the product works.
- 01
Choose an audience and the flows that belong in its guide, or generate one guide for every role that appears in a flow.
- 02
Read or edit the guide in Markdown, with a contents outline and flow provenance beside the manual.
- 03
Update stale guides against the changed flows or regenerate when the team wants a fresh take.
Using Guidelines
A guideline explains how one audience works the product; it is not the onboarding book. Guide sharing is per guide, while a project share can separately expose finished guides from the shared revision.
Continue exploring