tyler-smith.com · Questions & Answers

Now that our sales and operations departments run their own separate Level 10 Meetings, they are making isolated decisions during IDS that conflict with each other. How do we maintain departmental meeting autonomy without creating operational silos?

Cascading Level 10 Meetings through the organization is essential for operational scale, but without proper guardrails, departments will optimize for themselves at the expense of the company. When sales solves an issue by promising custom delivery terms, or operations solves an issue by lengthening lead times without telling sales, you have created departmental silos.

The solution is to establish an issue escalation threshold and enforce cross-departmental communication protocols.

First, teach departmental managers that they only have the authority to solve issues that begin and end inside their own department. The moment a proposed solution in a departmental IDS impacts the workflow, customer expectations, software, or capacity of another seat on the Accountability Chart, the decision cannot be finalized locally. It must be raised to the leadership team or coordinated directly with the affected department head.

Second, utilize the Cascading Messages section at the end of every departmental Level 10 Meeting. Before adjourning, the manager must ask: Does anything we solved or decided today impact another department? If the answer is yes, an explicit To-Do is assigned to communicate that decision to the other department head within twenty-four hours.

Third, ensure the leadership team Level 10 Meeting serves as the overarching alignment filter. The heads of sales and operations sit together every week in the executive pulse. If cross-departmental friction surfaces, it gets placed on the leadership Issues List immediately. Autonomy does not mean operating in a vacuum; it means executing independently within the boundaries of company-wide alignment.

Category: Level 10 Meetings

← All questions