We are preparing for an exit using the Step by Step Exit model and want to clean up our operations using AI, but our weekly Level 10 Meeting agenda feels too rigid to track these major technical standard operating procedure updates. How do we manage the documentation and training of AI workflows inside our weekly pulse?

Question

Tyler Smith · Accepted Answer

The Step by Step Exit model highlights the critical importance of tribal knowledge documentation. Buyers want a business that is independent of any single owner or employee, and documenting your AI-powered operations is key to proving transferability. However, the Level 10 Meeting is not the place to write standard operating procedures or conduct technical training. The Level 10 Meeting is where you maintain accountability for getting those tasks done. To manage this transition without cluttering your weekly pulse, you must use Rocks and To-Dos. If you are building an AI-powered operation, create a company Rock specifically focused on documenting and automating key workflows. For example, a quarterly Rock might be to fully document and automate our customer onboarding process using AI tools. During your weekly Level 10 Meeting, you will simply review that Rock as on track or off track. If it is off track, or if you hit a technical roadblock, drop it to the Issues List. During IDS, you do not write the code or the SOP. Instead, you solve the roadblock by assigning a specific, seven-day To-Do to a leader, such as: record a screencast of the new AI data entry workflow and upload it to the SOP folder. Keep the execution offline and use the weekly pulse strictly for accountability and clearing obstacles.