Back to portfolio
Community & GrowthSimulated project

Growth Manager portfolio brief

A simulated community & growth exercise for Growth Manager. Treat it as realistic practice, not real client or protocol work.

Objective

Choose one product and map its acquisition-to-retention funnel

Expected deliverables

Growth modelExperiment backlogFunnel dashboardExperiment briefCohort reviewGrowth decision memo

Recommended workflow

  1. Choose one product and map its acquisition-to-retention funnel
  2. Write three experiments tied to one bottleneck
  3. Analyse a public incentive campaign and state what the data cannot prove
  4. Review the result against the rubric, then package it as a case study.

Constraints and safety

  • Use only public sources or clearly simulated data.
  • Never include seed phrases, private keys, or wallet secrets.
  • Redact private user, company, security, legal, or compensation information.
  • State every assumption you make.

Tools in practice

Product analytics
Define events and funnels, compare cohorts, and test whether acquisition turns into activation and retention.
Dune
Instrument acquisition and activation funnels, segment users, and evaluate experiments without treating token-driven spikes as durable growth.
Amplitude or Mixpanel
Define events and funnels, compare cohorts, and test whether acquisition turns into activation and retention.
SQL or spreadsheets
Structure the records behind growth model and experiment backlog and make review status visible.
CRM and lifecycle tools
Structure the records behind growth model and experiment backlog and make review status visible.
experiment documentation
Draft, review, and maintain growth model and experiment backlog, with owners, source links, and change history.

What a strong submission shows

  • A growth model for a real dApp
  • Three experiment briefs
  • A cohort analysis
  • A failed-experiment review that changes the next decision

Weak submission patterns

  • A list of campaign ideas with no bottleneck
  • TVL or wallet growth with no retention context
  • Attributing market beta to one campaign

Review rubric

  • Accuracy of claims and sources
  • Relevance to the target role
  • Decision quality and trade-offs
  • Completeness of the deliverable
  • Clarity of communication
  • Honest limitations and next steps

Present it as a case study

  • Explain the problem, sources, decisions, ownership, constraints, output, review, and what you would change.
  • Show the final artifact before the process notes.
  • State what you owned and what belonged to other people.
  • Label the work as simulated, and keep any real contribution clearly separate.

Interview questions this project helps you answer

  1. A token incentive drives wallets up and retention down. How do you interpret it?

  2. How do you choose between improving activation and acquiring more users?

  3. Describe an experiment result that looked positive but should not be scaled

Turn this into an application