We are planning an exit in three years, but our owner still steps in to solve technical issues and client disputes during our weekly Level 10 Meeting. How do we structure IDS to systematically transfer this tribal knowledge to the leadership team?

Question

Tyler Smith · Accepted Answer

Transferability is what drives enterprise value. Buyers discount or walk away from businesses that rely on the owner's intuition, personal relationships, and direct technical intervention to survive. If your weekly Level 10 Meeting consists of department heads presenting problems and the owner providing the answers, your company is running an owner-dependent hub-and-spoke model that will hurt your valuation during diligence.

To transfer tribal knowledge, the owner must intentionally change their role during IDS. Instead of jumping in to provide solutions, the owner must remain silent for the first several minutes of discussion. Force the department heads to identify the root cause and propose solutions using documented core processes.

When an issue involves an owner-held relationship or specialized technical knowledge, use IDS to build transferrable systems rather than one-off fixes. The resolution should not be that the owner calls the client to calm them down. The resolution must be:
- Define the core process that prevented the error from being caught earlier.
- Assign a To-Do to a specific department head to shadow the owner on the resolution call.
- Document the decision criteria so the team can execute independently next time.

Every weekly pulse should be viewed through the lens of institutional readiness. If an issue cannot be resolved without the owner in the room, the true root cause is lack of documented process or team capability. Solve the capability gap, and your business becomes both easier to run and significantly more valuable to a future buyer.