tyler-smith.com · Questions & Answers

Our functional managers want to modify the standard Level 10 Meeting agenda and Scorecard layout to better fit their departmental workflows. Should we allow teams to customize the EOS tools or enforce strict uniformity across the company?

Do not allow teams to customize the tools. When departments start tweaking the EOS framework, they are rarely innovating. They are usually trying to avoid uncomfortable accountability or accommodate old operational habits.

The strength of EOS lies in its simplicity and universal application across the organization. The Level 10 Meeting agenda is engineered specifically to eliminate rambling updates, surface operational friction, and protect sixty minutes for IDS. When a manager suggests skipping the good news, combining reporting with discussion, or shortening IDS, they revert the meeting back to an inefficient status update.

The same rule applies to departmental Scorecards. Every department must track five to fifteen activity-based, weekly leading indicators with clear owners and weekly goals. Allowing a department to substitute monthly trailing metrics or subjective progress ratings destroys your ability to spot operational problems early.

Enforcing uniformity creates operational liquidity. When every team runs the exact same Level 10 Meeting format, leaders can sit in on any departmental meeting and instantly understand what is on track and where the breakdowns are happening. Cross-departmental issues get resolved faster because everyone speaks the same business language.

Tell your managers they must run the pure EOS tools as designed for at least two full quarters. Once a team masters the fundamentals and consistently hits eighty percent of their Rocks and Scorecard targets, they will realize that the standard tools work exactly as intended and the desire to customize will disappear.

Category: EOS Implementation

← All questions