tyler-smith.com · Questions & Answers

We want our operations team to start using AI tools to streamline our core service delivery, but we are struggling with how to document these dynamic AI-driven workflows in our standard operating procedures. How do we write SOPs for processes that change based on AI output?

Documenting AI driven workflows requires you to shift your focus from rigid, step by step instructions to defining the human guardrails and output standards. If you try to document every single prompt or AI response, your SOPs will be outdated the moment the system updates.

Adopt a vibe coding approach to your documentation. Treat the AI like an assistant that performs the heavy lifting, but keep the human employee as the ultimate owner of the seat. Your SOP should document the workflow as a collaborative conversation.

First, define the input. Specify the exact data, context, and quality of information the employee must feed into the AI.

Second, document the verification process. This is the critical step. Your SOP must detail how the human employee reviews, edits, and refines the AI's output. They cannot just copy and paste; they must apply their expertise to ensure it meets your company's standards.

Third, create a feedback loop. Instruct the employee to feed errors or adjustments back into the system to refine the output. By documenting the guardrails and verification steps rather than the specific clicks, your core processes remain clean, scalable, and adaptable to rapid technological changes.

Category: EOS Implementation

← All questions