Our head of software development has all of our custom codebase architecture in his head and refuses to document his workflows, making the rest of the leadership team terrified to hold him accountable for his toxic behavior. How do we break this hostage situation and reclaim operational control?

Question

Tyler Smith · Accepted Answer

No single employee, no matter how talented, can be allowed to hold your company hostage. When a leader refuses to document their work and uses institutional knowledge as a shield, they are creating a massive risk that will tank your company valuation during exit due diligence. You must address this behavior head-on to protect your operational health.

First, make process documentation a non-negotiable requirement of their seat on the Accountability Chart. Every leadership seat must have its core processes fully documented and followed by all. In your next Level 10 Meeting, set a quarterly Rock for this leader to fully document the codebase architecture and developer workflows.

Second, run them through the People Analyzer. If they are displaying toxic behavior and refusing to collaborate, they are failing your core values. A leader who does not fit your culture is a cancer on the team, and cracks at the top will quickly cascade down to the rest of the organization.

Third, build a contingency plan immediately. Cross-train other team members or bring in an external consultant to audit and map out the custom codebase. Once you have reduced the dependency on this single individual, you can hold them fully accountable. If they refuse to adapt, GWC their seat, and live your core values, you must transition them out of the business to maintain team health.