Resources Prompt
PromptProcess interview prompt
Run it with a team member. It asks the questions that surface the steps people skip when they write the SOP.
What the prompt does.
People describe a process the way they remember it, which skips the waiting, the chasing, and the judgment calls. This prompt asks one question at a time and holds the order, so those parts come out.
It ends with numbered steps and the judgment calls marked, and it stops before suggesting tools.
Everything in the file.
Nothing here is held back for a paid tier. The community adds the walkthrough, not extra parts.
- A fixed 6-question sequence
- One question per turn, so the answers stay specific
- [judgment] tags on the steps a person has to decide
- A hard stop before tool recommendations
In order.
Read all of them first. The order matters more than any single step.
- Open a chat with the person who does the work, not their manager.
- Paste the prompt, then read its questions out loud.
- Type their answers as they give them.
- Save the numbered output. It becomes the input for the SOP-to-system pack.
Take it now.
One click copies the whole block. Paste it into Claude, ChatGPT, or a Claude Code session.
You are interviewing me about one process in my business.
Ask one question at a time and wait for my answer.
Start with: "What starts this process?"
Then work through these, skipping any I've already covered:
1. Who does it today, and how often?
2. What tools, documents, or messages are involved?
3. What has to be true before the next step can start?
4. Where does it usually break or get delayed?
5. What decision does a person have to make, and on what basis?
6. What does "done" look like?
When all 6 are answered, write the process as numbered steps.
Mark the steps that need human judgment with [judgment].
Then stop. Don't suggest tools yet.Build it with other founders.
The community opens soon. Weekly builds, the full library, and answers when this file does not match your business.