How do we update our Core Processes in the EOS Process Component to reflect steps handled by AI tools without creating confusing or fragile SOPs?

Question

Tyler Smith · Accepted Answer

The purpose of the Process Component is to keep your core business operations documented at a high level using the 20/80 rule. When you introduce AI workflows, your SOPs should document the system dependencies and human inspection gates rather than technical code or individual prompt text.

Structure the updated Core Process documentation around four clear operational elements:
- Input: The specific raw data, trigger, or customer request required to start the step.
- Tool: The automated workflow or AI assistant responsible for executing the transformation.
- Verification: The precise criteria the human supervisor checks before the step is deemed complete.
- Seat: The seat on the Accountability Chart responsible for monitoring the output and handling exceptions.

Do not hardcode specific prompt language or API configurations into your primary operational manuals. Keep those technical details inside a version-controlled technical repository. Your high-level process documentation should simply state what gets automated, the quality standard expected, and who verifies that standard. This ensures your operations remain durable, system-dependent, and fully understandable to team members and future buyers.