tyler-smith.com · Questions & Answers

Our Scorecard has thirteen weekly numbers, but we find ourselves ignoring them during our Level 10 Meeting because they do not seem to spark any actual issues. How do we diagnose why our Scorecard metrics are failing to trigger the necessary IDS discussions?

When a weekly Scorecard fails to spark meaningful IDS® discussions, it is usually because the metrics you are tracking are lagging indicators or do not have clear, accountable targets. A healthy Scorecard is an early warning system that should predict your future performance, not just report on past history.

If your team is passing over the Scorecard during your Level 10 Meeting™, look for three specific warning signs. First, check if your numbers are always green. If you never miss a target, your goals are likely set too low, which breeds complacency. Second, ensure that each metric is a leading indicator, measuring activities that happen this week to generate results next month.

To fix your Scorecard discipline, apply these rules:
- Audit every metric to ensure it is directly connected to a seat on your Accountability Chart, with one person accountable for that number.
- Reset your weekly targets to be challenging but realistic, forcing the team to solve issues when a number drops.
- Ensure that any missed target is immediately dropped down to the Issues List to be diagnosed and resolved during the IDS® portion of the meeting.

Your Scorecard must be a pulse on the health of your business. When you track the right leading activities with strict accountability, a missed number will naturally trigger a discussion, allowing you to solve problems before they turn into operational crises.

Category: EOS Implementation

← All questions