Work/Work & operations
Turn a walkthrough into a reusable SOP
Extract prerequisites, steps, exceptions, and a definition of done from a demonstrated process.
Here’s what it could look like.
An illustrative example to show the direction. Your details will make it different.
Walkthrough: Open Reports, choose Weekly orders, select Monday through Sunday, click Preview. If cancelled orders appear, turn off Include cancelled and preview again. Click Export CSV. Done means the date range and order count match the preview. CSV destination was not mentioned.
PREREQUISITE Access to Reports; confirm required role. 1. Open Reports and select Weekly orders. 2. Set Monday–Sunday for the intended week. Confirm dates before continuing. 3. Select Preview. 4. If cancelled orders appear, disable Include cancelled and preview again. 5. Check the displayed dates and order count. 6. Select Export CSV. 7. Open the export and confirm its dates and row count match the approved preview. GAPS TO RESOLVE Which time zone defines a day? Where should the CSV be saved? Does the row count exclude the header? DONE The export matches the approved preview and is stored in the agreed location.
A good way to get there.
- 01
Capture a real walkthrough, including common exceptions and points where the operator makes a decision.
- 02
Extract a first draft with prerequisites, observable actions, and expected screen states.
- 03
Ask someone unfamiliar with the process to follow it in an appropriate test environment.
- 04
Record missing steps and revise; keep a date and owner for future review.
The prompt behind this idea
Replace the bracketed details or make it yours using the form.
Turn [Add walkthrough] into an SOP for [Add audience]. Prerequisites: [Add prerequisites]. Definition of done: [Add done]. Use only observed controls and actions. Separate numbered steps, decision points, and exception handling. Do not invent button labels or assume permissions. Mark gaps as questions. Include a verification checklist and a short change log. For irreversible actions, specify a review checkpoint instead of silently automating them.
Give it a second look.
- A first-time operator can identify the next action.
- Exceptions are explicit.
- Unknown system behavior is not disguised as a step.
“A new teammate got stuck at step two. Add the information they need while keeping the rest concise; list what we must ask the process owner.”
Use a test environment for validation when steps could affect real records.
The capability to look for
An assistant that accepts images and can discuss visible details; confirm measurements and obscured details yourself.
Find a tool for the jobHow these ideas and prompts are made