Growth Meeting Cadence: Focus on Learnings, Not Updates

WHY IT EXISTS Meetings are expensive in both time and money. A recurring team meeting must have a high ROI. Most meetings fail by focusing on low-value status updates—the "what"—which are better communicated asynchronously. This cadence was designed to prevent that waste and make the one recurring growth meeting the highest-leverage hour of the week.

THE MENTAL MODEL Treat the weekly growth meeting as a learning synthesizer, not a status report. The goal isn't to review what everyone is doing, but to extract, discuss, and spread the learnings from experiments across the entire team. This compounds knowledge and ensures everyone is working on the most impactful initiatives based on validated insights, not just ideas.

HOW IT WORKS The process is built around asynchronous preparation to maximize meeting efficiency. Before the meeting, team members are expected to review the public experiment pipeline and key metrics dashboards. If they have learnings from a completed experiment, they add them to a shared document using a standard template. The meeting itself then focuses almost entirely on discussing these submitted learnings. The owner of a learning presents it, and the team challenges its validity and discusses how to apply it elsewhere.

WHEN TO USE IT This structure is ideal for teams that operate on a continuous experimentation cycle, such as growth, product, or marketing teams. It creates a feedback loop where learnings from one experiment directly inform the hypotheses for future ones, accelerating progress and increasing the team's overall impact.

WHEN NOT TO USE IT This format is less effective for teams that don't run frequent experiments or for meetings with a different purpose, like project kickoffs, all-hands, or 1-on-1s. The structure is specifically optimized for extracting insights from a high-tempo testing environment, not for general project management.

ONE CANONICAL EXAMPLE A team holds its growth meeting on Monday. On the prior Friday, an automated reminder prompts everyone to add their learnings to a shared document. Over the weekend and Monday morning, team members review the doc, the experiment pipeline, and metrics. The first 40-50 minutes of the meeting are spent with individuals presenting their learnings, followed by group discussion to validate the insight and brainstorm applications. The final 10 minutes are for reviewing top-level metrics. Status updates are handled entirely outside the meeting via tools like Slack and a shared pipeline tracker.