Prompt of the Day: Process Documentation — Turn Your Expert Knowledge into Clear Step-by-Step Instructions
You know the situation: you have been doing something for years, you could do it in your sleep — but when you need to explain it to someone, you realize: you never wrote it down. And when you try, it either turns into a novel or three bullet points that only you understand.
The problem is real: Studies show that up to 42% of organizational knowledge exists only in the heads of individual employees. When someone goes on vacation, gets sick, or leaves the team, that knowledge is lost. And onboarding new colleagues takes twice as long because everything has to be explained verbally.
The solution: You describe your process roughly — the way you would explain it to a colleague at your desk. The AI structures it into a professional guide with numbered steps, decision points, common mistakes, and tips. In 10 minutes you have a document that would normally take you half a day.
What you can use this for:
- Onboarding new team members — 'this is how we do it here' as an actual document instead of oral tradition
- Vacation coverage — your substitute knows exactly what to do without calling you
- Quality assurance — everyone does it the same way, not each person differently
- Reflecting on your own processes — writing it down often reveals improvement potential
- Learning to delegate — if you have documented your process, you can hand it off
- Preparing for automation — a documented sequence is the first step toward automation
How to proceed:
1. Pick ONE process: Not everything at once. Choose the process you get asked about most often or that is most critical.
2. Describe it roughly: Imagine someone standing next to you and you are explaining it verbally. Write it down exactly like that — with all the 'and then I also do...' and 'oh right, it is also important to...'.
3. Use the prompt: Copy the prompt below and insert your description. The AI does the rest.
Pro tips:
- Create a checklist: 'Turn the instructions into a compact checklist for printing — one page maximum.'
- Onboarding version: 'Write a version for someone on their first day of work with no prior knowledge.'
- Error analysis: 'What are the 5 most common mistakes in this process and how do you avoid them?'
- Automation potential: 'Which steps in this process could be automated? Suggest specific tools.'
You are an experienced process manager and technical writer. Your task: Transform my informal description into a professional, understandable step-by-step guide (SOP) that even someone with no prior knowledge can follow. **The process I want to document:** [Name the process, e.g., 'Monthly client invoicing', 'Onboarding new team members', 'Creating the weekly social media content calendar', 'Performing server backups'] **My informal description — how I would do it:** [Describe the process in your own words. Feel free to be messy, jump between steps, mention edge cases and tricks. The AI will organize it. E.g., 'So first I check the Excel list with open projects, then... oh wait, before that I need to verify whether...'] **Who will use these instructions?** [e.g., 'New team members with no prior knowledge', 'My vacation substitute who generally knows the process', 'Myself as a memory aid'] **What tools/systems are used?** [e.g., 'Excel, Outlook, SAP', 'Google Workspace', 'Jira and Confluence', 'everything manual/by phone'] --- Create a professional process documentation with: **1. Process Overview** - Process name - Goal: What is the result when the process is complete? - Frequency: How often is it performed? - Estimated duration - Required access/tools/permissions **2. Prerequisites** What must be completed or available before starting? **3. Step-by-Step Instructions** For each step: - **Step X:** Clear action instruction (one sentence, one action) - **Detail:** How exactly — where to click, what to enter, which format - **Decision point:** If there is an 'if... then...' scenario - **Common mistake:** What often goes wrong here and how to avoid it **4. Edge Cases and Exceptions** What to do when things do not go as planned. Typical deviations and how to handle them. **5. Quality Check** A short checklist (5-7 items): How do I know I did everything correctly? **6. Contacts and Escalation** Who do I contact for problems? When do I escalate? **Rules:** - Write so that someone with no prior knowledge can follow every step - Use numbered steps, not flowing text - Mark critical steps with a warning note - If something in my description is unclear, ask rather than guess - Avoid jargon or explain it in parentheses