Five People Follow the Same SOP by Friday

You documented the SOP but each person still does it their own way. Half the team never opens the document and the other half interprets it differently.

That is the gap this drop closes. It is a operations skill built for Kimi, and it takes about ten minutes to set up the first time. After that it runs in under a minute.

Who should use it

Operations managers rolling out new procedures to three or more people

How it works

The skill file does five things, in this order.

1. Test the SOP with one junior person first. Watch someone unfamiliar with the task follow your written procedure without help and note every question they ask

2. Build a one-page checklist from the full SOP. Give Kimi your complete procedure and ask for a short checklist that covers decision points and quality checks only

3. Record three common mistakes in a troubleshooting guide. Document the errors you saw during testing and ask Kimi to write a quick-reference guide showing what went wrong and how to fix it

4. Create a certification quiz with real scenarios. Have Kimi generate five scenario questions based on your SOP that require judgment, not just memorization

5. Schedule weekly reviews for the first month. Ask each team member to report one thing that was unclear in the SOP and update the document after each session

What comes back

A tested procedure with a quick checklist, troubleshooting guide, and quiz that gets your team to consistent quality in weeks, not months

The mistake to avoid

People follow checklists more than manuals. Pin the one-page version where they work and keep the full SOP as backup reference only.

Running it

Paste the prompt block into a new Kimi chat and attach your files in the same message. Kimi's long context means you should upload everything at once rather than in batches, splitting the input is what causes it to lose cross-references between documents.

Where this fits

On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.

In the file

I need to turn this SOP into rollout materials for my team.

Full procedure:
{paste your complete SOP text}

Errors observed during testing:
{list 2-3 mistakes you saw when someone tried to follow it}

Please create:

1. A one-page checklist (maximum 12 items) covering only critical decision points and quality checks

2. A troubleshooting guide with three sections:
   - What you see (the symptom)
   - What went wrong (the cause)
   - How to fix it (the solution)

3. Five scenario-based quiz questions that test judgment, not memory. Include:
   - A realistic situation they will face
   - Three plausible answer options
   - The correct answer with a brief explanation

4. A template for weekly review sessions asking:
   - What step was unclear
   - What you did instead
   - Suggested improvement

Format everything so I can copy it directly into our team workspace.