One of our technical leaders stays completely silent during our weekly Level 10 Meetings™ because they believe their departmental issues are too complex or specialized for the rest of the leadership team to understand. How do we break down this intellectual silo during IDS®?

Question

Tyler Smith · Accepted Answer

This is a classic trap where technical experts protect their domain by declaring it too complicated for the rest of the leadership team to understand. When a leader acts as if their department is an island, they are holding back the entire business. They are also failing to exhibit the GWC™ (Get It, Want It, Capacity to Do It) required of a leadership team member, which demands that they solve problems for the greater good of the organization, not just their silo.

To break this silo, the Integrator must force the technical leader to translate their issues into plain business terms. When they drop an issue onto the board, they cannot use jargon. The Integrator should use a simple rule: if you cannot explain the problem to a non-technical manager in two sentences, you have not actually identified the root cause yet.

During the Identify stage of IDS®, have the technical leader explain the business impact of the technical problem. For example, instead of discussing database queries, explain that customers are experiencing a ten-second delay that is causing cart abandonment. Once the issue is framed in terms of revenue, customer satisfaction, or employee capacity, the rest of the leadership team can actively participate in solving it. If the leader resists, remind them that their job on the leadership team is to be a business leader first and a technical expert second. They must allow the team to help them solve.