Turn Three Versions of the Same SOP into One Best Practice
When the same job gets done three different ways, find the actual standard
You wrote an SOP six months ago, but now each team member has their own variant. Quality is inconsistent and new hires learn whichever version they see first.
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 who have multiple people doing the same task differently
How it works
The skill file does five things, in this order.
1. Record each person doing the full task. Get screen recordings or session notes from at least three people who do this job regularly.
2. Feed all recordings to Kimi with comparison instructions. Upload transcripts or descriptions together and ask Kimi to map where the methods diverge and why.
3. Identify which variations add value and which add risk. Ask Kimi to classify each difference as efficiency gain, quality improvement, workaround, or deviation.
4. Build the composite SOP with decision points. Have Kimi draft one procedure that incorporates the best steps and marks where legitimate choices exist.
5. Test the merged version with the original performers. Show the draft to all three people and ask Kimi to revise based on their objections and confirmations.
What comes back
A single SOP that captures real expertise from multiple people, not just one person's habits
The mistake to avoid
Do not assume the longest version is the best. Often the person who has done the job for five years has eliminated steps that were never necessary.
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 have recordings or descriptions of the same task performed by three different team members. I need you to compare these methods and help me build one authoritative SOP.
Task: {task_name}
Method A (performed by {person_A}):
{description_A}
Method B (performed by {person_B}):
{description_B}
Method C (performed by {person_C}):
{description_C}
Please do the following:
1. Create a step-by-step comparison table showing where these three methods differ
2. For each difference, classify it as: efficiency improvement, quality safeguard, personal preference, workaround for a tool limitation, or risky shortcut
3. Identify which steps appear in all three methods (core procedure)
4. Flag any step that only one person does but seems to prevent errors
5. Draft a unified SOP that incorporates the strongest elements from all three, with notes on where choice is acceptable and where consistency is required
6. Highlight any conflicting practices that need management decision before we can finalize the standard
Context about our operation: {business_context}
Quality requirements: {quality_standards}