tyler-smith.com · Questions & Answers

We have five different departmental Level 10 Meetings running weekly, but our managers are operating in silos and never share cross-functional dependencies unless an issue blows up into a crisis. How do we keep departmental meeting pulses aligned without creating cross-department meeting bloat?

Do not create new cross-departmental meetings to bridge the gap. That is the default corporate reaction, and it creates massive meeting bloat that pulls managers away from execution.

Keep alignment tight by mastering two existing EOS® disciplines: the Cascading Messages step and clean issue escalation.

At the end of your weekly leadership Level 10 Meeting™, use the Cascading Messages segment to explicitly define what departmental managers need to know this week. Agree on what must be shared, how it must be framed, and who delivers it. Department heads then open their own departmental Level 10 Meetings with those exact points during their headlines.

For bottom-up alignment, teach managers how to handle cross-functional issues in their own IDS® sessions. When a departmental issue touches another team, the department head has two choices:

- Resolve it horizontally outside the meeting directly with their peer if it is a simple operational handoff.
- Escalate it to the leadership team Level 10 Meeting™ if there is a resource conflict, broken process, or lack of agreement between departments.

Integrators should also audit departmental Issues Lists quarterly. If you see customer success and product engineering repeatedly debating the same bug turnaround times, step in. That is not a departmental issue; it is a cross-functional breakdown that needs to be solved at the leadership table once and for all.

Category: Level 10 Meetings

← All questions