How should an owner set weekly Scorecard targets and thresholds when our revenue and operational volume are subject to extreme seasonal swings or lumpy project cycles?

Question

Tyler Smith · Accepted Answer

When businesses with seasonal demand or long sales cycles adopt EOS, they often struggle with the Scorecard. They set a flat weekly revenue goal, miss it for eight weeks straight during a slow season, and eventually stop caring about red numbers because the target feels unrealistic.

The solution is to shift your Scorecard focus from lagging financial output to predictive activity metrics. Revenue may be lumpy, but the operational activities that produce revenue are entirely within your control every week.

If you run an enterprise sales cycle where contracts close unpredictably, stop tracking weekly closed revenue on your leadership Scorecard. Instead, track leading indicators such as discovery calls held, qualified proposals delivered, or contract drafts sent to legal. Those behaviors must happen consistently every single week regardless of whether a deal closes this Friday.

For businesses with extreme seasonality, use variable quarterly targets or trailing four-week rolling averages. When setting quarterly Rocks, the leadership team should define the weekly Scorecard thresholds specifically for that upcoming ninety-day cycle based on the seasonal plan. A target that never changes across summer rushes and winter lulls is lazy scorecard design. Keep the metric consistent, but adjust the target by quarter so a red score remains an authentic alarm bell requiring immediate IDS.