gtmjosh
Improve the System
Chapters
  1. 01 · Establish a Review Rhythm
  2. 02 · Inspect Errors, Exceptions, and Overrides
  3. 03 · Compare Expected and Actual Outcomes
  4. 04 · Measure Adoption, Cost, Speed, and Quality
  5. 05 · Find Drift and Stale Definitions
  6. 06 · Test Changes Before Broad Release
  7. 07 · Roll Out and Roll Back Deliberately
  8. 08 · Update Owners, Documentation, and Training
  9. 09 · Capstone: Run the Quarterly Operating Review
Guide overview →

12 min · Interactive exercise

Chapter 1 of 90 complete

Establish a Review Rhythm

A fixed cadence, named attendees, and a standing agenda that reaches the quiet problems.

Three things, and they are unglamorous.

A cadence. Named, on the calendar, recurring. Quarterly works for most GTM systems, monthly for anything moving fast. The specific interval matters much less than that it is fixed, because a review that happens when somebody remembers is a review that stops happening the first busy month.

Named attendees. Not a distribution list. The people who own the things the review can decide to change, which by this point you have already named: the metric owners from 4a, the system owners from 3c, the decision owner from 2a.

A standing agenda. The same items, every time, in the same order. This is the part that gets skipped and it is the one doing the work.

Why the agenda has to be standing

An incident is loud and a drift is quiet. A review driven by whatever happened last will attend to the loud thing every time and never once look at the definition that has been slowly wrong for a year.

The standing agenda is a commitment to look at the quiet things on a schedule, made in advance by people who are not currently in an incident.

The principle

Worth stating almost directly, because a real operating guide puts it this well: sustainable analytics depend on clear ownership and safe administration, not only polished dashboards. The dashboard is the easy half.

GTM Lab

Saved locally
Operating Review and Improvement Plan · 0 of 9 sections started

Saved locally to your browser.

Put it on the calendar, and fix the agenda

Everything above is built and correct and nothing changes because of it. Set the three unglamorous things that fix it.

Sample situation

A system measured continuously and improved never

FIXTURE-MEASURED-NEVER-IMPROVED
Reports
Built, current, correct
Review cadence
When somebody remembers
What gets discussed
Whatever happened most recently
Changes made because of a report
None anyone can name
What it is not
A failure of will
Resets every run.
When does the review happen, and who is in it?
What is on the agenda?
Chapter 1 of 90 complete