We have a department head who engages actively when reviewing their own metrics and Rocks, but tunes out completely and stays silent the moment the conversation shifts to other operational departments during IDS. How do we address this siloed behavior?

Question

Tyler Smith · Accepted Answer

When a department head only speaks up about their own vertical, they are acting like a manager defending a silo rather than an enterprise leader running a business. On an EOS leadership team, you do not just represent your seat on the Accountability Chart. You share collective responsibility for the entire organization, its profitability, and its long term value.

This behavior usually stems from one of two things: either the leader believes it is politically dangerous to comment on another leader's territory, or they lack the business acumen to think beyond their functional specialty. Both root causes must be eliminated.

The Integrator needs to address this directly outside the meeting during a quarterly conversation or a 5-5-5. Make the expectation clear: silence during IDS is unacceptable. If an operational issue touches capacity, customer experience, or cash flow, every single seat in the room must have a point of view.

Inside the Level 10 Meeting, the facilitator must systematically draw them into debates outside their comfort zone. If an operations issue is on the table, do not just look at the head of operations. Ask the finance leader: If we hire three more technicians to solve this bottleneck, what does that do to our gross margins? Ask the head of sales: How will our current clients react if we pause onboarding to fix this quality issue?

Force cross-functional inquiry until it becomes second nature. If a leader consistently refuses to think about the business as an interconnected system, they do not possess the capacity or GWC to sit on an executive team.