When departmental heads bring issues to our Level 10 Meeting, they often present interpersonal friction disguised as procedural breakdowns. How do we run IDS to expose whether an issue is truly a broken process or an Accountability Chart misalignment?
When a recurring operational problem hits your Level 10 Meeting, leaders often debate process breakdowns because criticizing a workflow feels safer than addressing a colleague. The result is endless tinkering with standard operating procedures that changes nothing because the real issue is an Accountability Chart problem or a trust gap.
To drill down to the issue behind the issue during the Identify step, force the team to diagnose the problem through three distinct operational lenses: process, seat, or person.
First, examine the core process. Is there a clearly documented, simplified process that everyone was trained on? If no, you have a process issue. Build or simplify the workflow.
If the process exists and works, look at the Accountability Chart. Does the person responsible for this function have clear ownership of the five major roles for that seat? Often, two leaders share fuzzy accountability, creating territory battles that look like operational miscommunications. Clarify the single seat owner.
If the seat is clear and the process exists, you are dealing with a person issue. Run the individual through the People Analyzer tool. Do they genuinely get it, want it, and have the capacity to do it? Do they consistently exhibit your Core Values?
If the Integrator allows the team to propose solutions before determining whether the root cause is procedural, structural, or behavioral, you will treat symptoms forever. Identify the true driver, state it plainly without sugarcoating, and solve it at the root.
Category: EOS Implementation