You already have the docs. You've just never run them.
Every team ships work that started as a document. And every team has a story about the document that didn't hold up.
Sound familiar?
- The ticket that bounced back from engineering because the spec “didn't say”.
- The customer escalation that traced back to one line of policy nobody could interpret.
- The new hire who followed the onboarding guide exactly and still ended up stuck.
- The agent that confidently did the wrong thing, because its instructions let it.
- The review meeting where everyone approved the doc, and nobody walked it.
None of these were bad docs. They were untested ones.
If it describes how someone gets somewhere, you can run it.
| You have | Subjourney runs it as |
|---|---|
| PRDs and specs | The user's path through the feature, edge cases included |
| Service blueprints and journey maps | The customer's journey across every channel and handoff |
| Policies and SOPs | The staff member or customer trying to comply, step by step |
| Onboarding and support guides | The newcomer trying to get help or get started |
| Agent instructions and system prompts | The agent and the user it serves, working through real tasks |
- You have
- PRDs and specs
- Subjourney runs it as
- The user's path through the feature, edge cases included
- You have
- Service blueprints and journey maps
- Subjourney runs it as
- The customer's journey across every channel and handoff
- You have
- Policies and SOPs
- Subjourney runs it as
- The staff member or customer trying to comply, step by step
- You have
- Onboarding and support guides
- Subjourney runs it as
- The newcomer trying to get help or get started
- You have
- Agent instructions and system prompts
- Subjourney runs it as
- The agent and the user it serves, working through real tasks
Bring one doc. See where it breaks.
Pick the doc you're least sure about and run it.