Everyone on my leadership team is too busy running daily operations, and nobody wants to take ownership of the tribal knowledge capture and process documentation seat. How do we assign accountability for this seat when everyone claims they do not have the capacity?

Question

Tyler Smith · Accepted Answer

If everyone is too busy to own process documentation, you have an accountability problem, not a capacity problem. In EOS®, we do not let critical functions drift just because they are tedious. Tribal knowledge is a massive value gap that will destroy your valuation during a buyer's due diligence. You must assign this seat to a single owner on your Accountability Chart.

The first step is to recognize that the owner of the seat does not have to do all the actual writing. The seat owner is simply accountable for ensuring the work gets done. They are responsible for the outcome, which is a fully documented library of core processes. They can delegate the actual drafting and technical writing to subordinates, virtual assistants, or AI-powered transcription tools.

Look at your leadership team and determine who has the highest GWC™, or Get It, Want It, and Capacity, for organization and systemization. This is usually your Integrator or your Operations leader. If indeed no one on the current team has the capacity to even oversee it, you must restructure the seat. You may need to hire a technical writer or an operations assistant who reports directly to your Integrator to sit in this seat.

Do not leave the seat blank or split it among multiple people. One name must go in the box. If you let this seat remain unassigned, your documentation will fail, your tribal knowledge will remain locked in people's heads, and your eventual exit will be messy and heavily discounted. Choose one leader to be accountable for the outcome and hold them to it.