We have a vital Systems Documentation and Security Patching seat that is currently empty. Every time we try to assign it, the employee's productivity drops, and they threaten to quit because the work is repetitive. How do we resolve this without letting security slip or causing turnover?

Question

Tyler Smith · Accepted Answer

An empty seat that everyone avoids is a systemic vulnerability, not a personality clash. When an essential operational function is universally resisted, you have two choices. You can either change who does the work or change how the work gets done.

Begin by using your Level 10 Meeting™ to run this issue through IDS®. Do not try to force this seat onto a current employee who lacks the GWC™ for it. If they do not want it, they will neglect it, and your security will eventually fail. Instead, look closely at the conative requirements of the seat. Meticulous patching and documentation require a high Follow Thru score on the Kolbe A index. Most of your current creative tech team likely has a high Quick Start score, meaning they naturally resist routine maintenance.

First, strip the seat down to its barest five roles. Second, evaluate if this seat must be a full-time, internal W2 position. In an AI-powered operation, highly structured and repetitive IT compliance tasks are prime candidates for fractional outsourcing or automated workflows. You can hire a specialized, fractional security firm to own this seat on your Accountability Chart.

If you must keep it in-house, hire specifically for the conative profile needed. Use Predictive Index assessments to screen for candidates who thrive on process stability and low risk. Stop trying to convert your high-velocity developers into system documentation clerks. Define the seat, match the exact conative profile required, and hire an external specialist who actually wants the seat.