Our lead systems architect has been with us for five years and possesses all the intellectual property for our legacy database in his head. He refuses to document his work, misses core values, and treats our junior developers like idiots, but we are entering tech due diligence next year and cannot risk him walking out. How do we handle this toxic Right Seat, Wrong Person situation when we are hostage to his technical knowledge?

Question

Tyler Smith · Accepted Answer

Holding yourself hostage to a toxic employee is a recipe for a failed exit. Buyers do not just look at your code. They look at your key-man risk. If a single developer can crash your company by walking out, your business is unsellable.

This is a Right Seat, Wrong Person issue. He gets and wants the seat, but he violates your core values. You must address this immediately, but do it strategically. Use a thirty-day review to address his core values violations. Be crystal clear about the behavioral changes required.

Simultaneously, make documentation a non-negotiable role in his seat description. If he refuses to document the database structure, he is no longer performing the roles of his seat.

Use the next ninety days to systematically extract the knowledge from his head. If you must, hire a fractional systems architect or use AI-assisted code documentation tools to map your legacy code. Once the technical knowledge is secured and documented, you have eliminated your key-man risk.

If he fails to align with your core values after his thirty-day review, you must transition him out of the company. Protecting your culture and removing structural single points of failure will dramatically increase your valuation and make your tech diligence run smoothly.