How do we stop our weekly Level 10 Meeting™ from stalling when we have to onboard a newly acquired business unit or merge two legacy teams into the same weekly meeting rhythm?

Question

Tyler Smith · Accepted Answer

Merging two teams into a single Level 10 Meeting™ is a recipe for ninety-minute bleed-over and operational drag. The solution is not to extend the meeting time. The solution is to strictly enforce the structural boundaries of your Accountability Chart. Do not force two distinct functional groups to share a weekly meeting just because you acquired them. If they have different daily operations, they need separate departmental Level 10 Meeting™ sessions. If you must run a combined meeting during an integration phase, you must aggressively curate the Scorecard and the Issues List. Only include metrics and issues that impact the entire combined unit. If an issue only affects one legacy team, push it to a separate sub-team IDS® session. Discipline is your only defense against meeting bloat. Ensure the Integrator runs the meeting with a stopwatch. Allocate exactly fifteen minutes for the reporting section, including the Scorecard, Rock review, and headlines. If a legacy team member begins explaining a metric or giving backstory during the review, cut them off immediately. Direct them to drop the item down to the Issues List. Keep the reporting tight so you have at least sixty minutes for IDS®. This forces the combined team to focus only on high-priority integration issues rather than getting bogged down in legacy details.