All issues

Growth Playbook

The weekly reporting cadence that ends "how are we doing?"

A step-by-step playbook for replacing ad-hoc status questions with one scheduled report the whole team runs on — tools optional, cadence mandatory.

DashboardLim · Systems desk

2026-06-175 min read

TL;DR

  • A report nobody has to request is worth ten dashboards people have to remember.

  • Cadence beats coverage — a thin report every Monday outperforms a rich one sometimes.

  • Every metric needs an owner whose name appears next to it.

"How are we doing?" is the most expensive question in a growing company — every answer is thirty minutes of someone assembling numbers by hand, and every silence is a decision made blind.

This playbook is the cadence we install to retire the question. It works with whatever stack you already run.

Step 1: pick the verdict metric

One number opens the report and everything else explains it. Revenue, qualified calls, orders shipped — the test is whether the week can be judged by it alone.

Step 2: assign owners, not observers

Every metric in the report carries a name. Not a team — a person. The report is a commitment device, and commitments belong to people.

  • Verdict metric — owned by the founder or GM — the number the week is judged on

  • Channel metrics — owned by whoever spends the budget

  • Ops metrics — owned by whoever ships the work

Step 3: schedule it, then defend the schedule

The report lands Monday 7am, before anyone asks. Automated delivery is what turns reporting from a favour into infrastructure — and it is a smaller build than most teams expect.

The first month, the numbers will be embarrassing and the formatting will be ugly. Send it anyway. Cadence compounds; polish can follow.

The report is the meeting now. We start from the same page or we don't start.

Agency client · after week six