Between our foundational session days, how do we handle the specific homework of mapping our Tribal Knowledge and identifying potential AI automation candidates without stalling our weekly progress?

Question

Tyler Smith · Accepted Answer

The key is to integrate these homework assignments directly into your existing EOS rhythm rather than treating them as separate, overwhelming projects. We do not stack new initiatives on top of your daily duties. Instead, we use your established meeting structures to drive this work forward.

During our sessions, we will define specific Rocks dedicated to documenting Tribal Knowledge or mapping workflow automation candidates. These Rocks are assigned to individual leadership team members who own the accountability for their completion over the ninety-day cycle.

In your weekly Level 10 Meeting, you will report on the progress of these Rocks. If a roadblock arises, such as struggling to extract a critical process from a key employee, you drop it down to the Issues List and IDS it right there.

To support this work between sessions, we utilize our dedicated Circle workspace. This platform serves as a central hub where we document session summaries, track Rock progress, and share templates for Step by Step Exit disciplines.

- Focus on one critical workflow at a time rather than trying to automate your entire operation at once.
- Keep your documentation simple and high-level to avoid getting bogged down in minutiae.
- Use the Circle workspace to ask questions and get feedback between our scheduled full-day sessions.

By following this structured approach, you build a highly leverageable and sellable asset without distracting your team from running the daily business.