How to Connect the Dots from Inputs to Outcomes
summary
Built a vendor‑led product community for Amplitude users and nonusers, launched seven months ago on a dedicated space, focused on practitioners who share custom formulas, notebooks and dashboards. Initial months show low traction (cold start takes 5–6 months cold start), now members make real connections after 10–15 one‑on‑ones per week and content seeding. Success signals are qualitative — rising confidence rather than vanity growth — with proxies like weekly saved charts and the prevalence of 90% lurkers who consume but don’t post.
AI-written summary · about
chapters (13)
- 0:00Product communities intro
- 3:52Signs community adds value
- 9:11Reasons not to start community
- 12:01Vendor-user tension solved
- 15:09Valuable community types
- 16:16Identify target members
- 20:29Four pillars of community
- 22:56User journey mapping
- 27:53Community ecosystem
- 31:40Balancing needs
- 33:28Community building tips
- 37:58Cold start problem
- 38:20Q&A
related talks
40mPanel Discussion: What Users Really Want
42mFrom Zero to Data as a Product in 60 Days: Anatomy of a Successful Data Product Launch
22mPowering the Next Generation of Products
32mUsing Dashboards to Help Manage All Community Channels
36mCommunity Data: What to Measure and Why?
24mWhat and Why, How to Leverage Data Science and Research
25mStorytelling with Data
18mProduct Usage Metrics - Practical Lessons from the Trenches