Our weekly scorecard targets feel like they are built on quicksand because market conditions are shifting rapidly. How can we use sensitivity analysis to set stable ranges for our scorecard goals rather than single arbitrary targets?

Question

Tyler Smith · Accepted Answer

Setting static, arbitrary targets for your weekly scorecard can lead to frustration when market conditions inevitably shift. If your goals are too rigid, your team may stop taking the scorecard seriously once a target becomes unattainable.

Using Sensitivity Analysis for Scorecard Ranges

To prevent this, you can use sensitivity analysis to establish realistic target ranges rather than single, fixed numbers. This approach makes your scorecard more resilient to minor market fluctuations and ensures that your team only spends time solving problems that actually threaten the health of the business. This is especially useful for a [seasonal business scorecard](/qa/seasonal-business-scorecard-goals) or when you're [setting scorecard targets without historical data](/qa/setting-scorecard-targets-without-historical-data).

Here's how to implement this range-based approach:

1. Identify Baseline Performance: Start by determining the baseline performance required for your business to remain profitable and healthy. This baseline represents the bottom of your acceptable range. Falling below this line signals a critical issue.
2. Determine Optimal Target: Next, define your optimal target, which represents strong, efficient performance. This is the goal you are striving for under ideal conditions.
3. Define Green, Yellow, and Red Zones: By defining these two points, you create clear zones on your scorecard:
• Green Score: This means you are on track, meeting or exceeding your optimal target.
• Yellow Score: This indicates that while you did not hit the optimal target, you are still within an acceptable tolerance level, above the baseline. There's no need to panic, but perhaps an eye should be kept on the trend. This helps avoid [arguing over why numbers were missed](/qa/how-to-review-scorecard-under-five-minutes).
• Red Score: This means you have fallen below the baseline, which immediately triggers the IDS® process in your Level 10 Meeting™. This indicates a significant problem that needs immediate attention.

This range-based system encourages a proactive approach to problem-solving, focusing resources on genuine threats rather than minor deviations. For more on optimizing your metrics, consider [how AI can optimize EOS Scorecard metrics](/qa/ai-in-optimizing-eos-scorecard-metrics-and-accountability).

AI never sits in the room during your Level 10 Meeting. It works before the meeting to prep the data and after the meeting to capture and track what was decided. The 90 minutes stay human: with your leadership team, the scorecard, the issues list, and the IDS conversation.