AI Blocks › Write down how work gets done
Define your metrics once and write a weekly update
Give it your numbers. Get metric definitions, an assumptions log, the weekly update and plain pictures.
Define your metrics once and write a weekly update is a free AI workflow for the job "Write down how work gets done". It guides your AI through several skills in order, passing each step's output to the next.
Free · No account · Made by AI Blocks · Level: beginner · Thinking: high
What it does
Two people say "conversion rate" and mean different things, so the weekly update starts an argument instead of a decision. The update itself is a table, and the one line that matters, that something changed, is buried in row nine. This workflow fixes the words before the numbers. It writes a definition for each metric: what it counts, what it excludes, where it comes from and how often. It logs the assumptions behind the analysis so a reader can see what was taken for granted. It writes the weekly update in a fixed shape: what changed, why, what we do about it. Then it translates the key figures into pictures a reader can hold, in the manner of Chip Heath's Made to Stick: a thousand new subscribers becomes a number of full buses, a percentage becomes one person in a room of ten.
You give it
- The metrics you track and where each comes from
- This week's numbers and last week's
- Who reads the update and what they decide with it
- Your current update, if you have one (optional)
- Codebase (optional)
You get
- A definition for each metric: what it counts, excludes, its source and timing
- An assumptions log for the analysis
- A weekly update: what changed, why, what we do
- The key figures as plain pictures a reader can hold
Use it when
- Two reports show different numbers for the same thing.
- Your weekly update is sent and not read.
- A leader asked "so what does that mean" after your last report.
Steps
- Metric definition writer: Tell it how a metric is worked out. Get one agreed definition as checked YAML your team can reuse.
- Analysis assumptions logger: Tell it about your analysis. Get every assumption logged with its risk, so reviewers see what could change the answer.
- Weekly status update writer: Paste what got done, what is stuck and what you need. Get a one-page status update.
- Visual numbers explainer: Paste your key figures and audience. Get each number turned into a picture the room can feel.
How to use it
- Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
- Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
- Paste the metrics and where they come from. It writes the definitions and the assumptions log.
- Paste this week's and last week's numbers. It writes the update and the plain pictures.
- Read the update once as the reader. Send it, and reuse the definitions every week.