Stand Up a Growth Team
By Sarthak Arora · From the Growth Strategy collection · Updated July 2026
This prompt turns a vague desire to "get serious about growth" into a concrete operating plan: the right team structure for your organization, a named core team of four to eight people, a defined sprint and meeting cadence, and a prioritized experiment backlog tied to one or two focus areas. You paste in your context and get a launch plan you can circulate to stakeholders and run next sprint.
When to use this
- Growth has plateaued and improving everything a little at once has stopped working
- Lots of activity, competing KPIs across the whole funnel, and no clear reason growth stalled
- Silos are fighting over resources and nobody owns growth across the organization
- You are ready to pilot one cross functional team on one or two high impact levers before any wider rollout
Fill in the variables
BUSINESS_TYPE
The model that shapes roles and levers, for example "subscription SaaS" (points to a product manager plus retention levers) or "direct to consumer ecommerce" (points to customer care plus conversion and reorder levers).
PMF_STATUS
Your evidence, for example "strong: retention past month two beats benchmark and 45 percent would be very disappointed to lose it" versus "unproven, still testing messaging."
BIGGEST_CHALLENGE
Pick the single dominant one, since it selects the structure. "We move too slowly" points to independent; "nobody owns growth" points away from it.
AVAILABLE_PEOPLE
Real names and disciplines plus how much time each can commit, for example "one developer at 20 percent, a designer full time, a data analyst shared with finance."
TIME_MONEY_TOOLING_CONSTRAINTS
For example "no dedicated budget, we already use Notion and Google Sheets, no analytics engineer on staff."
The prompt
Full method. Works on any model.
You are a senior growth operator who has stood up growth teams inside startups, ecommerce brands, SaaS companies, and marketplaces. You are evidence first: experiments over opinions, research over assumptions, focus over activity. Design a growth team and operating process fit for MY situation, then hand me a launch plan. CONTEXT: {{COMPANY_AND_PRODUCT}}; business type {{BUSINESS_TYPE}}; {{ORG_SIZE_AND_STRUCTURE}}; fit status and evidence {{PMF_STATUS}}; North Star Metric if set {{NORTH_STAR_METRIC}}; biggest problem now {{BIGGEST_CHALLENGE}} (one of: lack of focus, no ownership of growth, moving too slowly, misaligned goals, silos, scattered knowledge); candidate people and disciplines {{AVAILABLE_PEOPLE}}; constraints {{TIME_MONEY_TOOLING_CONSTRAINTS}}. GATE FIRST. If fit is unproven, recommend proving it before forming a team; a growth team runs short experiment sprints and cannot carry the longer job of finding fit. If the organization is under about four people, a formal team is overkill. If key inputs are missing or vague, ASK UP TO FIVE CLARIFYING QUESTIONS first, prioritizing fit evidence, the dominant challenge, the North Star Metric, and who can be freed up. Then STOP and wait for my answers; do not design a team on guessed inputs. METHOD: 1. FOCUS. Restate the North Star Metric (never revenue; revenue results from it) and name at most three levers. A lever is a specific area you improve through experiments, more concrete than the North Star and broader than one test. Fewer is better; scattered focus is the main growth killer. Give each lever its own backlog so like compares with like. 2. STRUCTURE. Map my dominant challenge to one model; state the tradeoff. → Independent (dedicated team under a head of growth, full time): best for a SPEED problem; weakness, others stop owning growth and rotating members is hard. → Cross functional (members from each department, lead reporting into product or marketing): best for an OWNERSHIP problem or shifting focus; weakness, competing home department priorities. → Mixed (cross functional members plus a small dedicated growth group under a head of growth): best for specialist unbiased leadership with shared responsibility; weakness, dual reporting and boundary ambiguity. Heuristic: a marketing led or product led org points to cross functional (lead sits there); a pure speed problem points to independent. Because a dominant challenge is often misdiagnosed, also name the RUNNER UP structure and one observable signal that would make you switch (for example, if ownership complaints persist after two sprints, move from independent to cross functional). 3. CORE TEAM: four to eight people by focus area, not a fixed roster. Draw from growth lead, product manager, developer, designer, data analyst, customer care (voice of the customer, strong for retention), conversion specialist, copywriter, and in B2B a sales contact. Split core contributors (run experiments, need full context) from stakeholders (informed or approving); if a stakeholder's sign off is needed to ship experiments, put them in the core team. Keep developers involved; they surface the best, most realistic ideas. 4. BALANCE AND LEAD. Mix planners (systematic, best at perfecting proven wins and longer bets) with explorers (fast, broad, best at new risky areas): assign explorers to short term risky experiments, planners to longer larger bets, and prefer committed members over a large disengaged group. Pick a lead who is customer centric, hypothesis first and data driven, a good delegator, and a storyteller who can sell the focus; no growth background required, since a conversion specialist, product manager, or growth marketer can grow into it. 5. PROCESS. Run a closed loop on each lever: research, prioritize, run experiments, analyze, feed the next ideas. Set sprint length (one to two weeks); separate planning and growth meetings under an hour; one simple documentation home (Sheet, Notion, or Airtable with backlog, running, and completed sections). Never brainstorm in the growth meeting; arrive with a prioritized backlog of at least thirty ideas per lever. 6. SCORING with ICE (Impact, Confidence, Ease), adjusted to my constraint: weight Confidence higher when ideas are too many, weight Ease higher when momentum lags, add a scalability factor when single use ideas keep winning. Attach guidelines so scores are not guesses. Write each hypothesis as: "Because we saw [A], we expect [B], due to [change C]. We are right if [criterion with a threshold AND a minimum volume]." Separate a growth experiment (documented, hypothesis, bigger risk and reward) from an optimization (small, low risk, logged separately). 7. CADENCE. Start with ONE pilot team on one or two levers to earn buy in before wider rollout. Review levers monthly; change them about once a quarter (some, like retention, span two to three quarters). A growth team does not override other processes or make demands of other teams. OUTPUT under these headings: Readiness verdict; Focus; Structure (recommended model, why it fits my challenge, runner up model, switch signal); Core team roster (roles, core vs stakeholder, planner vs explorer); Lead; Operating process; Starter backlog; Cadence and rollout plan; Self check. Format the starter backlog as five to eight entries, grouped by lever, each entry filled into this exact template: → Lever: [lever] | Idea: [one line] | Hypothesis: "Because we saw [A], we expect [B], due to [change C]. We are right if [criterion with threshold AND minimum volume]." | Impact: [1 to 10] | Confidence: [1 to 10] | Ease: [1 to 10] | ICE: [total] | Type: [experiment or optimization] SELF CHECK. Verify: fit is in place or flagged; the North Star Metric is not revenue; no more than three levers; team of four to eight; each lever has its own backlog; every hypothesis carries a threshold and a minimum volume. Avoid: rebranding marketing as a growth team; running eight focus areas at once; forcing a task tool to be the data record; making everything an experiment when small optimizations should ship; skipping the pilot to reorganize the company at once.
For the most capable models. Goal and quality bar up front.
You are a senior growth operator who has stood up growth teams inside startups, ecommerce brands, SaaS companies, and marketplaces. GOAL: design a growth team and operating process fit for MY situation, then hand me a launch plan I can circulate to stakeholders and run next sprint. Open with the readiness verdict and recommended structure in your first two lines, then supply the rest of the plan. CONTEXT: {{COMPANY_AND_PRODUCT}}; business type {{BUSINESS_TYPE}}; {{ORG_SIZE_AND_STRUCTURE}}; fit status and evidence {{PMF_STATUS}}; North Star Metric if set {{NORTH_STAR_METRIC}}; biggest problem now {{BIGGEST_CHALLENGE}}; candidate people and disciplines {{AVAILABLE_PEOPLE}}; constraints {{TIME_MONEY_TOOLING_CONSTRAINTS}}. PRINCIPLES that govern the plan: → Gate first. If fit is unproven, recommend proving it before forming a team; a growth team runs short sprints and cannot carry the longer job of finding fit. If the organization is under about four people, a formal team is overkill. → Focus. Restate the North Star Metric (never revenue) and name at most three levers, each with its own backlog. Scattered focus is the main growth killer. → Match structure to the dominant challenge: independent for a speed problem, cross functional for an ownership or shifting focus problem, mixed for unbiased specialist leadership with shared responsibility. Name the runner up structure and one observable signal that would make you switch. → Core team of four to eight by focus area, splitting core contributors from stakeholders, mixing planners with explorers, keeping developers involved, and led by someone customer centric, hypothesis first, data driven, and able to sell the focus. → Run a closed loop on each lever (research, prioritize, experiment, analyze, feed the next ideas) with a one to two week sprint, separate planning and growth meetings under an hour, and one documentation home. Score with ICE adjusted to my constraint and write every hypothesis as "Because we saw [A], we expect [B], due to [change C]. We are right if [criterion with a threshold AND a minimum volume]." Start with one pilot team before wider rollout. QUALITY BAR: excellent output gates on fit and organization size before designing; names at most three levers each with its own backlog; ties the structure to my dominant challenge and names a runner up plus switch signal; delivers a four to eight person roster splitting core from stakeholder and flagging planner versus explorer; fills every starter backlog entry with lever, idea, a written hypothesis carrying a success threshold and minimum volume, three ICE scores plus total, and experiment or optimization; and lands as a single pilot with a monthly review and quarterly lever change. BOUNDARIES: do not invent data, metrics, or people I did not give you. Do not pad with generic growth advice. Do not rebrand marketing as a growth team, run eight levers at once, force a task tool to be the data record, or skip the pilot. If a required input (fit evidence, the dominant challenge, the North Star Metric, or who can be freed up) is missing or vague, ask up to five focused questions and wait rather than guessing.
Five lines. Speed over rigor.
Act as a senior growth operator. Design a growth team and operating plan for {{COMPANY_AND_PRODUCT}}, org {{ORG_SIZE_AND_STRUCTURE}}, fit {{PMF_STATUS}}, top problem {{BIGGEST_CHALLENGE}}, people {{AVAILABLE_PEOPLE}}. Give me: a readiness verdict, at most three levers under a non revenue North Star, a structure matched to my problem, a four to eight person roster, and a starter backlog of ICE scored ideas. Non negotiable: if fit is unproven or the org is under four people, say so first; every backlog hypothesis must state a success threshold AND a minimum volume.
Want all 120 prompts in one workspace?
Every prompt in this library, organized by task. Free.
What good output looks like
- It gates on fit and organization size before designing anything, asks its clarifying questions and waits, and refuses to over build a team for a five person company
- It names at most three levers, each with its own backlog, picks a structure explicitly tied to your dominant challenge, and names the runner up structure plus the observable signal that would trigger a switch
Show 3 more quality checks
- The roster is four to eight people, splits core contributors from stakeholders, and flags a planner and explorer mix
- Every starter backlog entry fills the full template: lever, idea, written hypothesis with a success threshold and a minimum volume, the three ICE scores plus total, and whether it is an experiment or an optimization
- The rollout is a single pilot team with a monthly review and a quarterly lever change, not a reorganization of the whole company at once
Related prompts
- Map Growth Loops and Flywheels
Build the growth model that tells you which levers the team should work first.
- Pick and Test Growth Channels
Run the channel tests that fill an acquisition lever's backlog.
- Diagnose Activation and Churn
Find the retention lever with the most leverage before you point a team at it.
Free to use and share. If you republish a prompt, link back to this library.