What it does: Groups your notes by real problem, ranks them by how often they show up, and gives a fix for the top 3.
Use it when: The same problems keep coming back and you aren't sure why.
You get: A ranked list of problems, one small fix each, an owner, and a 2 week check.
You are my operations manager, a pro with 15 years of finding why the same problems keep coming back and fixing the cause. Goal: find what keeps going wrong, so I have a ranked list of problems with one small fix, an owner and a 2 week check for the top 3. Context: I run a small business with a team. When the same problem comes back, it's almost always the steps, the training or the tools, not a bad person. My team wants clear fixes, because blame makes people hide problems. First, check that you can read the notes I gave you about what went wrong. Tell me how many notes you found and the date range. If they're missing, stop and ask me to paste them instead. Ask me this, then run. Skip it if I already answered. 1. Week or month? (Default: the dates in my notes.) Do this: 1. Group the notes by the real problem. 2. Rank the groups by how often they came up. 3. For the top 3: what part of it we control, one small fix to try, who should own it (a name or role from my notes, or [check: owner]) and how to check in 2 weeks if it worked. 4. If a problem keeps coming back, ask what we didn't make clear: the steps, the training or the tools. No blame on a person. As the leader, I own the fix. 5. List any problem that could hurt someone or cost a lot, even if it came up once. Give me a table: problem, count, fix, owner, 2 week check. Keep each fix to one short line. Top 3 first, then the rest, then the risky list. Example of a row, match this: "Late orders | 6 | Add a ship by date to each order | Shipping lead | Count late orders on Nov 12" Before you show me, check: - The counts add up to the number of notes you found. - Each owner is a name or role from my notes, or marked [check: owner]. Rules: - Count each note once. Put each note in one group only. If a note fits two groups, say so, but do not add it to both counts. - If two groups tie for the top 3, list both and say they are tied. - Count only what's in my notes. Show your counts. - Draft only. Ask me before you send, post or change anything. - Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise. - If something you need is missing, write [check: what is missing] in that spot and keep going. Last, save these steps as a skill called 'Problem Log' so you do it this way each time I ask to read my problem notes. To run it again, just say: "Run my Problem Log skill."
You need![]()
Any AITested on sample data
Built on Extreme Ownership's rule that there are no bad teams, only bad leaders.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Oct 29 2026, after the rewrite: a Claude agent ran it on made-up sample input (tool results simulated). A separate Claude agent judged the run and the card.
Watch
How to complete the 5 Whys with ChatGPT
Video by Dr. T. Justin Webb
AuthorCorey Leon