Prepare
Choose a recurring real task. Prepare its objectives and result requirements, authorized inputs, current practices, participating roles and known exceptions, with sources, versions and gaps.
RESEARCH & PRACTICE / PEOPLE & AI · Problem pathway
Document a task for human–AI collaboration
Start with the required result, then connect tasks, roles, handover conditions and checks.
Produce
Draft the relationships supporting the result, closed-loop tasks, role responsibilities and handover conditions. Identify actions for possible AI assistance, acceptance checks and exception handover.
Check
Check inputs, outputs, owners and completion criteria. Trial complete, missing, conflicting and out-of-scope inputs; record human review, rework and unresolved issues, then examine the business result.
Supporting knowledge
The six types describe resource roles. Select and combine them for the task.
Models · R1
Four-Way SOP: Connecting Performance, Business Processes, Functional Tasks, and Actions
Identify the business and performance results that the work is intended to support.
Start with customer outcomes and economic results, then connect the key business processes, closed-loop tasks, and specific actions that support them. Four-Way SOP provides a supporting structure that can be developed downward and checked upward. It helps people understand why a task is needed and helps an organization see what still needs to be verified after a process is complete.
Methods · R1
How to Use Four-Way SOP: Connecting Business Results, Processes, People, and Daily Work
Break one business process into closed-loop tasks and specific actions.
Start with one path to business results, then clarify processes, resources and partners, role responsibilities, and daily actions. A hypothetical brand design company shows how Four-Way SOP can help startups test revenue paths, find and develop people, and preserve working methods for collaboration between people and AI.
Methods · R1
From Job Responsibility Analysis to Role Handbooks: Helping Contributors Understand Their Work
Clarify role responsibilities and organize multiple tasks in a work handbook.
Start with the result a business needs, then turn responsibility analysis into role handbooks that clarify tasks, conditions, authority, deliverables and collaboration. A hypothetical requirements documentation role shows how a handbook is applied to a real task and improved through trials.
Models · R1
What needs to be handed over before a process can move to the next step?
Check handover outputs, entry conditions and acceptance responsibilities.
Separate the previous process's deliverable, the acceptance decision, and the conditions for starting the next process. Explain how to handle handover problems and how a shared objective sets limits on what each stage can call complete.
Methods · R1
From SOP to Skill: Where AI Can Help and How to Verify and Accept Its Outputs
Select possible AI assistance and define inputs, acceptance and exception handover.
Start with a specific piece of work, assess where AI is suitable, and agree on inputs, outputs, acceptance criteria, and human takeover. Integrate the Skill into business collaboration while keeping business judgment and responsibility clear.
Methods · R1
We followed the SOP. Why aren’t we seeing business results?
Review actual results to distinguish action, collaboration and business-assumption issues.
Clarify customer and economic outcomes first. Then trace gaps along the actual business-outcome chain, distinguish business conditions from work mechanisms, and use evidence to choose the SOP improvements needed.
Review and improve
Record results, deviations and knowledge or steps that need revision.
Practice → evaluation and review → revised knowledge and Skills