Our creative director and software engineering lead claim that their departments are too agile and unique for the rigid ninety-minute Level 10 Meeting structure, and they want to use their own informal check-ins instead. How do I get them to adopt the standard EOS framework?

Question

Tyler Smith · Accepted Answer

Every department head thinks their team is a special snowflake that cannot be bound by standard operational structures. This is a common form of resistance that hides a fear of accountability. Informal check-ins lead to loose execution, missed deadlines, and siloed communication. The Level 10 Meeting™ framework is not a bureaucratic constraint; it is an efficiency engine designed to give teams their time back.

To overcome this resistance, you must be firm on the standard EOS® framework. Start by explaining the 'why' behind the structure. The ninety-minute agenda is engineered to save time by consolidating fragmented communication, status updates, and administrative emails into one hyper-focused block. If they claim ninety minutes is too long, challenge them to run the meeting so efficiently that they finish early. A Level 10 Meeting™ can absolutely end in sixty or seventy-five minutes if the team is highly disciplined, but the agenda sections must remain intact.

Explain that consistency across all departments is what allows the leadership team to easily roll up metrics and cascade issues. Let them know that while the inputs change, the human psychology of problem-solving does not. Creative and engineering teams still have weekly deliverables, key metrics, and roadblocks. By running the standard agenda, they will expose bottlenecks faster and solve them permanently rather than patching them in ad-hoc chats. Stand your ground and make compliance with the meeting pulse non-negotiable.