Twitch broadcaster interviews before feature roadmap
Interview current, churned, and adjacent creators before building the roadmap, then turn their pain into ranked feature bets.
Why this can grow a startup
Twitch’s gaming pivot was not just a founder taste call. Emmett Shear described calling existing broadcasters, former broadcasters, and adjacent creators who recorded gaming videos but had not tried live broadcasting. The team asked why they broadcast, what broke, what competitors did better, and what one thing they would change. Then they brought proposed solutions back to the same audience before building. This works because creators often cannot state the product solution directly, but they can reveal the job, the friction, and the point where they would switch. The second interview pass prevents the team from mistaking a complaint for the right feature.
Source-backed example
Shear said Twitch interviewed roughly 30 to 40 broadcasters across several classes of creator, then used a spreadsheet of feature ideas and importance levels to validate what to build next.
Source-reported evidence
Source: Mixergy: Emmett Shear on the TwitchTV pivot · Browse Mixergy: Emmett Shear on the TwitchTV pivot tactics
The research pass covered about 30 to 40 interviews and produced ranked feature ideas, including options creators would switch services to get.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Customer Research, Product, Creator Economy is relevant to creator interviews, roadmap research, churned users and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Customer Research and Product, using evidence from Mixergy: Emmett Shear on the TwitchTV pivot as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.
SOURCE HUB
More tactics from Mixergy: Emmett Shear on the TwitchTV pivot
Explore related GrowthDex examples and evidence connected to Mixergy: Emmett Shear on the TwitchTV pivot.
Open Mixergy: Emmett Shear on the TwitchTV pivot source hub