When reviewing our Scorecard, how does an Integrator use the thirteen-week trailing history to tell the difference between a random one-week anomaly and a systemic operational defect?

Question

Tyler Smith · Accepted Answer

Looking at a single week of Scorecard data in isolation leads to emotional overreactions. A metric turns red, panic sets in, and leadership wastes thirty minutes debating a non-issue. Conversely, teams ignore slow-moving disasters because a metric hovers just slightly below target each week without anyone noticing the cumulative decay.

The thirteen-week view provides context. An Integrator should apply three specific filters to evaluate off-track numbers:

- The three-week rule. A single red week is an anomaly. Two consecutive red weeks is an operational alert. Three consecutive red weeks is a broken process or a capacity failure. If a number is red for three weeks in a row, it automatically drops to the Issues List for deep IDS, regardless of whether the owner claims it is under control.
- Trend line velocity. Look at the slope of the thirteen-week data. If a measurable is green this week but has dropped steadily over the past six weeks, trouble is coming. A metric that declines from ninety-five to eighty-two while the target is eighty is technically green, but operationally decaying. The Integrator must identify that downward velocity before it breaches the threshold.
- Correlation with downstream metrics. If your leading sales activities dropped four weeks ago, look at your project pipeline and cash collections this week. If the downstream metrics are softening, the initial dip was not an isolated blip; it was the start of an operational chain reaction.

Use the thirteen-week horizon as an objective radar screen, not just a historical log.