A weekly growth review should resolve decisions, expose blockers and preserve learning. If the meeting consists only of reading numbers everyone could have checked beforehand, it is not using the team’s attention well.
Prepare a compact pre-read
Show the agreed metrics with definitions, the relevant time window and notable changes. Include experiment status and data-quality concerns. Avoid presenting incomplete cohorts as final results.
Ask owners to state the decision they need from the meeting. This distinguishes a useful discussion from a general update that can remain asynchronous.
Review the customer journey
Look for relationships across acquisition, activation, retention and monetization. A cheaper install is not automatically a win if the resulting users do not reach value. A new product release may explain changes that would otherwise be attributed to campaigns.
Use the meeting to connect those perspectives rather than let each function defend its own isolated metric.
Record decisions and uncertainty
For each item, state the action, owner and next checkpoint. If the evidence is insufficient, identify the smallest useful investigation. Avoid repeatedly postponing a decision without specifying what information would resolve it.
Write down why the choice was made. That prevents the team from revisiting the same debate without new evidence and helps future colleagues understand the context.
Protect room for learning
Discuss failed or inconclusive experiments without turning them into personal performance judgments. A well-designed test that disproves an assumption can prevent larger waste. Reward clear interpretation rather than only favorable charts.
End with a short list of priorities that fits actual capacity. The meeting should leave specialists more focused and the app owner better informed. Its success is measured in clearer execution during the following week, not in the number of slides reviewed.