Metrics Review Scorecard
By Alex Brown · Published · Updated
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.
Prompt template
## Metrics Review Scorecard Build this week's metrics scorecard. - Team or business area: [text: Growth team or Support] - Metrics this week: [textarea: Name and this week's value with last week and four weeks ago] - Targets: [textarea: Target for each metric] - Known events this week: [textarea: Launches or outages or campaigns or holidays] - Metric owners: [textarea: Who owns each number] - Review audience: [dropdown: Team meeting, Leadership, Board] 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.