Standard Operating Procedures (SOP) Catalog

Comprehensive index of all organizational SOPs with links, descriptions, and usage guidelines for repeatable workflows.

개요

Standard Operating Procedures (SOPs) document repeatable workflows that ensure consistency, reduce errors, and enable delegation. They're living documents that evolve as processes improve.

This catalog serves as the central index for all Kyndof SOPs. SOPs are organized by domain and maintained in the wiki at wiki/sops/. Each SOP includes step-by-step instructions, decision points, responsible parties (RABSIC), and success criteria.

How to Use This Catalog

Finding SOPs: Browse by domain below or search wiki for specific keywords.

Running SOPs: Click through to the full SOP document. Follow steps sequentially. Mark completion criteria before moving to next step.

Updating SOPs: If a process changes, update the SOP and increment version. Note what changed and why in changelog.

Creating New SOPs: Use the SOP template at wiki/sops/_template.md. Follow the structure: Purpose, Scope, Roles (RABSIC), Prerequisites, Steps, Success Criteria, Troubleshooting.

SOP Domains

SOPs are organized into functional domains. Existing SOPs are linked below; planned SOPs are listed for reference.

Available SOPs

현재 사용 가능한 SOP 목록입니다:

SOP	Department	Description	Link
SOP-001: Design Brief Intake	2000Atelier / Design	디자인 브리프 접수 및 처리	View SOP
SOP-020: Cutting Standards	2000Atelier / Production	재단 표준 프로세스	View SOP
SOP-100: Client Inquiry	Brand Ops / Sales	고객 문의 처리 프로세스	View SOP

SOP Standards & Tools

Document	Description	Link
SOP Writing Guide	SOP 작성 가이드라인	View
Numbering Convention	SOP 번호 체계 규칙	View
Review Process	SOP 리뷰 프로세스	View
SOP Template	새 SOP 작성 시 사용하는 템플릿	View

Planned SOPs (미작성)

아래는 필요하지만 아직 문서화되지 않은 SOP 목록입니다. 우선순위에 따라 점진적으로 작성됩니다.

Operations & Processes: Incident Response, Weekly Sync Workflow, Data Ingestion, Decision Log Maintenance, RABSIC Assignment

People & HR: Onboarding Checklist, Offboarding Checklist, Performance Review Cycle, Interview Process, PTO Request Workflow

Engineering & Development: Code Review Standards, Deployment Process, Hotfix Workflow, Database Migration, Security Vulnerability Response

Product & Design: Feature Specification, User Research Session, Design Review, Beta Testing Program

Sales & Customer Success: Customer Escalation, Sales Demo Workflow, Contract Review, Churn Analysis

Finance & Legal: Expense Reimbursement, Invoice Processing, Budget Approval Workflow, NDA Review

Marketing & Communications: Blog Post Publishing, Social Media Posting, Press Release Workflow, Brand Asset Usage

SOP Lifecycle

SOPs evolve through a structured lifecycle:

1. Pattern Detection (Automated)

When Process Intelligence (see CLAUDE.md) detects a repeating pattern in organizational data (interactions, decisions, tasks), it flags it for SOP creation.

Criteria for SOP Candidate:

• Pattern occurs 3+ times with 70%+ confidence
• Pattern is predictable (similar steps, triggers, outcomes)
• Pattern involves multiple people or cross-functional coordination
• Current execution is ad-hoc and inconsistent

Output: Pattern logged in .omc/patterns/process-patterns.json with maturity level.

2. SOP Generation (Semi-Automated)

When a pattern reaches maturity level 1 (Repeatable), Orchestrator can generate an SOP draft:

Generation Process:

• Extract common steps, decision points, and roles from historical data
• Structure using SOP template
• Identify RABSIC roles based on past executions
• Define success criteria and troubleshooting tips

Output: Draft SOP in wiki/sops/{pattern-name}.md marked as DRAFT.

3. Review and Refinement (Manual)

Process owner reviews draft SOP:

Review Checklist:

• Are steps complete and sequenced correctly?
• Are decision points and edge cases covered?
• Are RABSIC roles accurate?
• Are success criteria measurable?
• Is troubleshooting section useful?

Output: Approved SOP moved from DRAFT to ACTIVE status.

4. Execution and Feedback

SOP is used for the process. Users provide feedback:

Feedback Channels:

• Inline comments in wiki
• Retrospectives noting where SOP didn't match reality
• Issue reports when SOP fails

Output: Feedback logged for next revision.

5. Iteration and Improvement

Based on feedback and changing processes, SOPs are updated:

Update Triggers:

• Process changes (new tools, new requirements)
• SOP doesn't match reality (steps outdated)
• Consistent user confusion (steps unclear)
• Performance issues (process too slow or error-prone)

Output: Updated SOP with version increment and changelog entry.

6. Deprecation

When a process is no longer relevant, SOPs are archived:

Deprecation Criteria:

• Process no longer performed
• Process fully automated (no human steps)
• Process replaced by different approach

Output: SOP moved to wiki/99-archive/sops/ with deprecation notice.

SOP Template Structure

All SOPs follow consistent structure for findability and usability:

---
title: [SOP Name]
version: 1.0
last_updated: YYYY-MM-DD
status: ACTIVE | DRAFT | DEPRECATED
owner_role: [Role responsible for maintaining SOP]
---

# [SOP Name]

## Purpose
[Why this SOP exists, what problem it solves]

## Scope
[When to use this SOP, when not to use it]

## Roles (RABSIC)
| Role | Responsibility |
|------|----------------|
| R (Responsible) | [Who executes] |
| A (Accountable) | [Who approves] |
| B (Backup) | [Who covers if R unavailable] |
| S (Support) | [Who assists] |
| I (Informed) | [Who gets notified] |
| C (Consulted) | [Who provides input] |

## Prerequisites
[What must be true before starting]

## Steps
### Step 1: [Action]
[Detailed instructions]

**Decision Point**: [If applicable, decision criteria]

**Success Criteria**: [How to know this step succeeded]

### Step 2: [Action]
...

## Verification
[How to verify the entire process succeeded]

## Troubleshooting
| Problem | Solution |
|---------|----------|
| [Issue] | [Fix] |

## Changelog
| Version | Date | Changes | Author |
|---------|------|---------|--------|
| 1.0 | YYYY-MM-DD | Initial version | [Role] |

SOP Metrics

Track SOP effectiveness:

Execution Frequency: How often is each SOP used? Low usage might mean process is infrequent or SOP is ignored.

Completion Rate: Do people finish the SOP or abandon mid-way? Low completion suggests complexity issues.

Error Rate: How often does following the SOP result in errors or rework? High error rate means SOP is inaccurate or incomplete.

Time to Complete: How long does it take to execute? Track over time to identify improvement opportunities.

Feedback Volume: How many comments or questions does the SOP generate? High volume suggests unclear documentation.

Integration with Process Intelligence

SOPs are connected to organizational data via Process Intelligence:

Pattern → SOP: Detected patterns (maturity 1+) generate SOP drafts automatically.

SOP → Execution Tracking: Each SOP execution is logged as an interaction in the knowledge graph.

Execution → Pattern Refinement: Execution data feeds back to pattern detector to improve future SOP generation.

Delegation Readiness: When a pattern reaches maturity 3 (Managed), Process Intelligence assesses whether it can be delegated to an agent. If yes, SOP is converted to agent workflow.

Agent Delegation from SOPs

SOPs at maturity level 4 (Automated) are candidates for agent delegation:

Delegation Assessment:

• Are all steps automatable (no human judgment required)?
• Are inputs well-defined and structured?
• Are success criteria measurable programmatically?
• Is error handling straightforward?

Delegation Process:

1. Identify agent type (Back-Writer for sync, RABSIC-Engine for approvals, etc.)
2. Convert SOP steps to agent prompt/workflow
3. Test agent execution against historical cases
4. Deploy with human-in-the-loop for initial runs
5. Gradually reduce human oversight as confidence grows

Monitoring: Delegated processes are monitored for accuracy. If agent fails, escalate to human and revert to manual SOP temporarily.

SOP Best Practices

Keep SOPs Concise: One page ideal, two pages maximum. If longer, break into sub-SOPs.

Use Visuals: Screenshots, flowcharts, and diagrams clarify complex steps better than paragraphs.

Test SOPs with New Users: Have someone unfamiliar with the process follow the SOP. If they get stuck, clarify.

Version Control: Track changes over time. Knowing what changed and why helps troubleshoot regressions.

Link to Related Docs: Cross-reference policies, templates, and systems referenced in the SOP.

Assume Zero Context: Write for someone who has never done this before. Don't assume implicit knowledge.

Common SOP Anti-Patterns

Too Vague: "Review the data and make a decision" isn't actionable. Specify what to review and decision criteria.

Too Rigid: SOPs should guide, not constrain. Allow judgment for edge cases.

Outdated: SOPs that don't match reality create confusion. Review and update regularly.

No Owner: SOPs without clear owners stagnate. Assign role responsible for maintenance.

No Feedback Loop: If users can't report issues or suggest improvements, SOPs decay.

Why SOPs Matter

Organizations without SOPs reinvent processes every time, creating inconsistency, errors, and knowledge silos. When the person who "knows how to do X" leaves, the process dies.

SOPs capture institutional knowledge. They enable delegation, scaling, and quality control. New hires can execute processes without shadowing someone for weeks. Contractors can contribute without months of context-building.

But SOPs fail when they're static documents no one reads. They succeed when they're living artifacts integrated into daily work. Process Intelligence makes SOPs dynamic—they evolve as processes change, suggest improvements based on execution data, and eventually delegate to agents.

The goal isn't to bureaucratize work with endless procedures. It's to capture what works, eliminate what doesn't, and continuously improve how we operate.

---

관련 문서

• Communication Norms - SOPs for communication workflows
• Meeting Guidelines - SOPs for meeting types
• RABSIC Framework - Accountability in SOPs
• Process Intelligence - Automated pattern detection

---

원본 문서: Notion - Processes (SOPs) 최종 동기화: 2026-02-08