Task Library
Mine six months of SOP Amendment Proposals for patterns – repeatedly-patched SOPs, missing processes, proposal friction – and convert each pattern into a system-level fix.
Category: Knowledge System Maintenance
Use this when the 6-month recursive review cycle opens – run this analysis first, because its patterns are the evidence the maintenance-article audit needs.
Inputs
- The complete SOP Amendment Proposal tracker for the past six months: approved, rejected, and returned proposals
- SOP version histories and changelogs for the same period
- The five-process map from /knowledge-system-maintenance
Steps
- Export every proposal from the past six months from the shared tracker – including rejected and format-returned ones; failures carry as much signal as approvals.
- Categorize each proposal three ways: by affected SOP, by problem type (outdated tool step, missing step, wrong sequence, unclear language), and by outcome (approved, rejected, returned).
- Hunt the known pattern shapes: same SOP amended repeatedly – structural weakness; it needs a rewrite or layer separation, not more patches; clusters around work no process covers – a candidate new process for the hub; repeated format rejections – proposal friction; fix the template, the examples, or the training, not the proposers; near-zero proposals overall – pipeline failure, not perfection; SOPs do not stop drifting just because nobody files paperwork.
- Quantify the basics so trends compare across cycles: proposals per SOP, approval rate, median time from submission to decision.
- Convert every confirmed pattern into exactly one action: a proposed new/modified process for /knowledge-system-maintenance, a queued SOP rewrite with owner, or a pipeline fix (template, queue, review cadence). A pattern observed but not actioned is trivia, not analysis.
- Write up findings and actions as the evidence package for
audit-this-maintenance-article-every-6-months, and file the actions through the SOP Update Protocol where they change documented process.
Definition of done (QA checklist)
- 100% of the period's proposals reviewed and categorized – including rejections and returns
- Metrics computed (proposals per SOP, approval rate, median decision time) and compared to the prior cycle where one exists
- Every identified pattern paired with exactly one concrete action and owner
- Zero-proposal or low-flow finding treated as pipeline failure and actioned accordingly
- Findings handed to the 6-month article audit as its evidence base
- Linked back to the definitive article and relevant siblings
- Complies with Blog Posting Guidelines (if it publishes content)
Example(s)
- /knowledge-system-maintenance – Process 5 prescribes this pattern review to spot needed new processes and proposal friction across the amendment history.
- Example needed – run the Meta-Article Prompt (/meta-article-prompt-template) after the first 6-month pattern review and link the meta-article here.
File in the zip: skills/knowledge-system-maintenance/review-past-6-months-of-sop-amendment-proposals-for-patterns.md. Download the Task Library zip.
Index: Task Library. Article guidelines.