📘 How do growth teams actually run?

What you’ll learn

1. How Growth Teams Are StructuredCompare functional, independent/embedded, centralized/decentralized, and pod-based growth-team structures and justify a choice for a given company stage.A growth team is a cross-functional group aimed at a shared growth goal, spanning product, engineering, marketing, data, and design so experiments can cross silos. Companies choose along several axes: independent (standalone) vs. embedded (seeded into product teams), and centralized vs. decentralized, often starting centralized and decentralizing as skills spread. Larger orgs use matrixed pods owning specific funnel areas or growth loops. Across every structure, a senior executive sponsor is the prerequisite that gives the team authority to act across boundaries and protects it from being blocked or raided.
2. The Growth Lead & Required SkillsDefine the growth-lead role as process and metric ownership and identify the skills and roles required to staff an effective growth team.The growth lead owns the team's operating system—setting the focus area, curating the idea backlog, enforcing hypothesis quality, running the growth meeting, and keeping the analyze-ideate-prioritize-test loop turning—rather than functioning as a generic people-manager. Effective teams blend product managers, engineers, data analysts, marketers, and designers, and favor 'T-shaped' members with one deep skill plus broad literacy to minimize hand-offs. Data fluency is foundational, since growth decisions are settled by evidence and bad measurement yields confident nonsense. Hiring screens for curiosity, quantitative reasoning, and tolerance for frequent failure alongside craft depth.
3. Operating Cadence & RitualsDesign a growth team's operating cadence—weekly growth meeting, experiment review, retrospectives, and planning—to sustain high experiment velocity.A growth team's output is learning, and learning rate depends on experiment velocity, which Sean Ellis frames as high-tempo testing. A reliable cadence sustains tempo: the anchor is a weekly growth meeting (roughly an hour) that reviews the focus metric, last cycle's tests and lessons, selects this cycle's experiments, and checks the idea pipeline—with data and templated ideas prepared beforehand so the hour is for decisions. Each completed test gets a structured review yielding a ship/iterate/kill decision. Nested longer-horizon rituals—retrospectives on how the team works and quarterly planning that sets focus areas—prevent both directionless busyness and strategy that never ships. Concrete velocity goals protect the tempo.
4. The Experiment Pipeline & Idea BacklogBuild an experiment pipeline that captures ideas, converts them to testable hypotheses, prioritizes with ICE, and recycles learnings.Growth teams run on a shared idea backlog where anyone can submit ideas in a standard template (idea, hypothesis, target metric, evidence). Raw ideas are converted into falsifiable hypotheses that name a mechanism, a single primary metric, and a prediction. Because ideas always exceed capacity, the team ranks them with Sean Ellis's ICE framework—Impact, Confidence, Ease—to force an explicit, debatable ranking rather than deferring to seniority. Prioritized ideas flow through pipeline stages (backlog, up next, in progress, completed) with work-in-progress limits. Crucially, each completed test's learnings are documented and fed back into the backlog and future confidence scores, which is what makes a growth team compound.
5. Metrics, Accountability & Psychological SafetyConnect a value-based North Star metric, its input levers, and OKRs to accountability, and apply Edmondson's psychological-safety and failure-taxonomy research to a growth team.A growth team aligns on a North Star Metric—a value-based output popularized by Sean Ellis and formalized in Amplitude's North Star Playbook—and decomposes it into a few controllable input metrics that experiments target. OKRs (originated by Andy Grove at Intel, popularized by John Doerr's 'Measure What Matters') make accountability concrete by tying quarterly objectives to measurable key results. Because most experiments fail, the team's health depends on Amy Edmondson's psychological safety: a shared belief that interpersonal risk-taking is safe, which pairs with (not replaces) high standards. Edmondson's failure taxonomy distinguishes intelligent failures (good tests worth celebrating) from preventable ones, and recognizing common dysfunctions—vanity metrics, HiPPO decisions, feature-factory drift, blame cultures—helps teams avoid them.
6. Guided Project: Team Operating-System Memo (Case Memo)Produce a complete team operating-system / rituals memo covering structure, metrics, cadence, pipeline, and culture for a specific product.This guided project walks through writing a team operating-system memo—the artifact a growth lead hands the team and stakeholders to align on how the team works. Section 1 fixes structure and mandate (model, rationale, executive sponsor, roster, scope). Section 2 defines metrics and accountability (North Star, input levers, OKRs, owners). Section 3 specifies the operating cadence and experiment pipeline (rituals, hypothesis template, ICE prioritization, pipeline stages with WIP limits, velocity target, learning capture). Section 4 makes culture concrete (psychological-safety behaviors, intelligent-vs-preventable failure handling, dysfunctions to avoid) and schedules a review to revise the operating system itself. The result is an opinionated, defensible case memo, not generic best practices.

Questions this course answers

Grounded in trusted sources

• Sean Ellis & Morgan Brown, 'Hacking Growth: How Today's Fastest-Growing Companies Drive Breakout Success' (Currency/Crown, 2017)
• Andrew Chen, 'How to build a growth team – lessons from Uber, HubSpot, and others' (andrewchen.com, slide deck with Brian Balfour / Reforge)
• Sean Ellis & Morgan Brown, 'Hacking Growth' (Currency/Crown, 2017)
• Brian Balfour, 'Building Growth: Product, Process, and Team' series (Reforge blog, reforge.com)
• Sean Ellis, 'How to Do High-Tempo Testing' (GrowthHackers.com)
• Amy C. Edmondson, 'The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth' (Wiley, 2019); 'Psychological Safety and Learning Behavior in Work Teams,' Administrative Science Quarterly (1999); 'Strategies for Learning from Failure,' Harvard Business Review (April 2011)

Every Wunder lesson is built from real, reputable sources — never invented.

Related courses