Our departmental Level 10 Meetings are running in departmental silos, where Sales and Operations solve problems internally that directly break the other team's workflow. How do we handle cross-departmental issues between separate Level 10 pulses without creating a bloated joint meeting?

Question

Tyler Smith · Accepted Answer

When departments run isolated Level 10 Meetings, local problem solving can accidentally sabotage adjacent teams. Sales invents a new custom service package to close deals during their IDS®, and Operations only finds out three weeks later when delivery fails.

Do not fix this by merging the meetings. A joint 15-person meeting destroys traction and drains payroll. Instead, install three structural guardrails:

- Route cross-functional root causes up, not sideways. If Sales identifies an issue that alters delivery commitments, client onboarding, or pricing, they cannot solve it unilaterally. The department head must bring that issue up to the leadership team Level 10 Meeting™ for leadership IDS®. The leadership team solves the policy, and the resulting decisions cascade back down to both department pulses.
- Send an ad-hoc subject matter guest. If Operations is solving a technical bottleneck that hinges on sales intake forms, the Operations manager invites one representative from Sales to sit in on their departmental Level 10 Meeting for that single IDS® agenda item. Once that issue is solved and the To-Do is assigned, the guest leaves the room.
- Leverage the Cascading Messages wrap-up. At the end of every departmental pulse, the team must ask: does anything we decided today impact another department? If yes, it is added to the cascading message list, and the department head is accountable for notifying their peer within twenty-four hours.

Departmental Level 10 Meetings exist to execute work within an Accountability Chart seat, not to rewrite company operating procedures in a vacuum. Keep the pulses separate, but enforce strict boundaries around cross-seat operational decisions.