AI at the Gemba · lesson 7 · worksheet
From SOP to skill
paulducey.com/lean/course
DateThe job, and the SOP it comes fromName
Part 1. One job you have watched this month. List its steps and sort each one: K keep (sequence, spec, stop rule, record), C cut (history, approvals, rationale) or D do not encode (a weak control, or something no one has watched). Say why.
| # | Step | K · C · D | Why |
|---|---|---|---|
| 1 | K C D | ||
| 2 | K C D | ||
| 3 | K C D | ||
| 4 | K C D | ||
| 5 | K C D | ||
| 6 | K C D |
Part 2. The label. These go in the skill's header.
| Name (lowercase and hyphens, same as the folder) | |
| Description: what it does and when to use it, under 200 characters | |
| Owner, and the source SOP and revision | |
| Version, last checked at the gemba, review date |
Part 3. Test it, with the skill and without it. Run each more than once.
| Request | With the skill: triggered? invented a number? followed the stop rule? | Without it |
|---|---|---|
| One that should trigger it | ||
| One that should not | ||
| One with a missing input, or an out-of-spec reading |
Questions for the owner (the steps I did not encode, and why):
Paul Ducey · AI at the GembaFree to copy and use. paulducey.com/lean/course