---
name: metrics-review-scorecard
description: "Builds a weekly metrics scorecard showing each number against its target and trend, the likely cause of any move and the one action it triggers. Use when a team runs a weekly or monthly metrics review and needs a scorecard with trend, target status, causes of changes and actions. Do not use for building a dashboard or performing a statistical analysis. Related topics: data, business."
---

# Metrics Review Scorecard

Builds a weekly metrics scorecard showing each number against its target and trend, the likely cause of any move and the one action it triggers.

## When to use

Use this skill when a team runs a weekly or monthly metrics review and needs a scorecard with trend, target status, causes of changes and actions. Do not use it for building a dashboard or performing a statistical analysis.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Build one row per metric with value, two comparisons, target, status and owner, and state the status thresholds.
3. Separate leading from lagging metrics and flag moves larger than normal noise.
4. Test causes in order of data issues, calendar effects, known events and segment shifts, labelling each as confirmed, likely or guess.
5. Assign one action with an owner and date to each amber or red metric, or an explicit watch decision with a trigger.
6. Write three headlines, name the one metric that matters most and list questions to answer before the next review.

## Inputs

- **Team or business area** (free text, e.g. "Growth team or Support")
- **Metrics this week** (longer free text)
- **Targets** (longer free text)
- **Known events this week** (longer free text)
- **Metric owners** (longer free text)
- **Review audience** (choose one: Team meeting, Leadership, Board)

## Output

A scorecard table with status colours and thresholds, a cause and action list for amber and red items, three headlines and a short list of follow-up questions.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Metrics Review Scorecard

Build this week's metrics scorecard.

- Team or business area: {{Team or business area}}
- Metrics this week: {{Metrics this week}}
- Targets: {{Targets}}
- Known events this week: {{Known events this week}}
- Metric owners: {{Metric owners}}
- Review audience: {{Review audience}}

Create a scorecard with one row per metric: value, change versus last week, change versus four weeks ago, target, status (green, amber or red against defined thresholds) and owner. Say how status is set so the colours are not vibes, such as green at or above target, amber within 10 percent, red beyond that. Separate leading metrics from lagging results. For any metric that moved by more than normal week-to-week noise, offer a cause: first check data issues and calendar effects, then the known events, then segment shifts, and mark each cause as confirmed, likely or guess. Do not assume a cause that the data given cannot support. For each amber or red metric, write one action with an owner and date, or an explicit "watch" decision with the trigger for acting. Close with three headlines for the audience, the one metric that matters most this week, and questions to answer with data before the next review.

## Pitfalls

- Explaining every wiggle as a cause, when most week-to-week changes are normal noise.
- Setting colours with no defined thresholds, so status changes with the mood of the room.
- Listing actions without owners or dates, which the next review finds untouched.