A growth operating system fits on one page

Artefact 1: the KPI tree

One page that links the number the board cares about to the numbers the team can move. Revenue splits into traffic, conversion and order value. Traffic splits by channel. Each leaf has an owner and a weekly target.

Artefact 2: the experiment log

A shared list of every test: hypothesis, change, start date, result, decision. It stops the team repeating tests, and it turns a year of work into evidence instead of memory.

Artefact 3: the board report

One page, read in minutes. The KPI tree, the three biggest movements and why, the experiments that ran, and the decisions needed. No dashboards of vanity metrics.

The weekly meeting

Thirty to sixty minutes, same time each week. Review the KPI tree, review experiment results, decide the next tests. Each action has a name and a date.

• Numbers first, opinions second.
• Every result ends in a decision: scale, stop or retest.
• Decisions are written in the log before the meeting ends.

Where it breaks

It breaks when tracking cannot be trusted. That is why the Install step in my method starts with measurement. A cadence built on untrusted numbers produces confident arguments, not growth.