We have a highly technical department head who remains completely silent during the IDS® portion of our Level 10 Meeting™, claiming that their department's issues are far too complex for the rest of the leadership team to understand or help solve. How do we break through this technical isolationism and force them to bring their issues to the table?

Question

Tyler Smith · Accepted Answer

This is a common barrier on leadership teams with specialized roles like engineering, software development, or legal compliance. When a leader stays silent because they believe their world is too complex for others, they are holding the company hostage to their specialized knowledge. It also means they do not trust the collective wisdom of the leadership team.

Your technical leader is confusing technical execution with organizational health and priority alignment. The job of the leadership team during IDS is not to write code or draft legal contracts. The job is to solve the business, operational, and people impacts of those technical challenges.

To break this pattern, the Integrator must challenge the silent leader directly. When an issue touches their department, or when they are silent during a cross-departmental debate, ask them specifically how this impacts their team or what resource constraints they are facing. They must learn to elevate and simplify. They must bring at least one departmental issue to IDS every single week, even if it is just a resource or timing constraint, until they build the habit of collaborative problem-solving.