During IDS, our team constantly frames personnel friction as a breakdown in our core processes or tools. How do we strip away the technical excuses and identify when the real issue is a people problem?

Question

Tyler Smith · Accepted Answer

Leadership teams frequently hide uncomfortable personnel conflicts behind software complaints, documentation gaps, and process debates. It feels safer to say an onboarding workflow is broken than to state openly that an operational leader lacks the capability to train new hires.

To cut through this deflection, the facilitator must force the team to separate process structure from execution accountability. When an issue surfaces as a process failure, ask two direct questions. First, do we have a documented, clear process for this activity? Second, is the person in this seat following it?

If the process exists and is proven, but a specific individual fails to execute it, you are no longer dealing with a system issue. You are dealing with a People Analyzer problem. Turn immediately to the EOS GWC framework: does this person Get it, Want it, and have the Capacity to do it? Do they consistently exhibit your Core Values?

Never allow the leadership team to solve a personnel limitation by creating bureaucratic process overhead. Writing a twelve-step checklist to keep an incompetent employee from making errors only punishes high performers and bloats your company. Identify the actual root cause out loud: state the name of the seat, evaluate the GWC fit, and solve the personnel mismatch directly instead of redesigning your operational systems around human shortcomings.