KPI Anomaly Agent

Each week, the agent runs when the metrics refresh. That gives leadership an explanation while the change is still current, rather than waiting until the end of the quarter to ask what happened.

• Schedule: Weekly

• Trigger: The metric refresh

Next, the agent pulls the metrics that have moved outside their normal range. It leaves ordinary variance alone, so the rest of the workflow focuses only on changes that need an explanation.

• Scope: Metrics outside their normal range

• Exclude: Metrics still within normal variance

For each metric that moved, the agent pulls the calls on the deals driving the change. Looking at the deals underneath the number helps it find the likely cause, which is usually concentrated in two or three deals.

• Scope: Deals driving the metric change

• Include: Calls on those deals

The agent compares each metric with its trend and lists the ones outside their normal range. For every anomaly, it states the size of the deviation and leaves out anything that falls within normal variance.

Using the calls on the deals behind each anomaly, the agent offers the likeliest cause for the change. It names the deals behind the explanation and clearly marks the cause as a hypothesis rather than a finding.

Finally, the agent posts the anomaly and its likely cause to the leadership Slack channel. The metric, deviation, explanation, and deals behind it arrive together, so executives can see what moved and what likely caused it.

• Channel: The leadership Slack channel

• Include: The anomaly, deviation, likely cause, and deals behind it