Simple Feature Board
Does listening to user feedback improve product outcomes?
Research supports responding thoughtfully to customers, but it does not prove that buying a feature board causes growth. These four studies measure different settings and outcomes; their limitations matter as much as their headline results.
Updated · By Simple Feature Board
At a glance
| Study | Sample | Measured finding | Boundary |
|---|---|---|---|
| Gokgoz, Ataman & van Bruggen (2025) | 460 apps; 1,075,704 reviews; 3,255 updates | Ratings benefited from responsive updates addressing recurring requests | App-update evidence, not a randomized feature-board trial |
| Chang & Taylor (2016) | 39 independent samples | Ideation participation improved financial performance and time to market | Results varied by development stage and context |
| Gu, Bapna, Chan & Gupta (2022) | 3,056 mobile-game users | Submission-only treatment: 43% longer observed lifetime; 24% longer sessions | Game-content submissions, not SaaS feature requests |
| Poetz & Schreier (2012) | 103 product ideas | 8 of 10 ideas above the top customer-benefit threshold came from users | One product-development setting, not a universal 80% rule |
Responsive updates and app ratings
Zeynep Aydin Gokgoz, M. Berk Ataman and Gerrit H. van Bruggen: “If it ain’t broke, should you still fix it? Effects of incorporating user feedback in product development on mobile application ratings.” International Journal of Research in Marketing, 2025 (online 2024).
Across 460 apps, 1,075,704 reviews and 3,255 updates, responding promptly to recurring requests concerning new content or smooth operation was associated with improved ratings. Ignoring feedback carried rating penalties. This does not establish that any particular feedback tool causes better ratings. Practical implication: group repeated problems and respond with relevant changes, not just more updates.
Original study: International Journal of Research in Marketing
Customer involvement is especially useful during ideation
Woojung Chang and Steven A. Taylor: “The Effectiveness of Customer Participation in New Product Development: A Meta-Analysis.” Journal of Marketing, 2016 (online 2015).
The analysis combined 39 independent samples. Customer participation during ideation improved new-product financial performance and accelerated time to market, with especially useful effects for small firms. Participation during development could instead slow progress. There is no single uplift percentage that applies to every company. Practical implication: invite input before deciding what to build, while keeping implementation decisions focused.
Participation can help retention — in a specific experimental setting
Zhuojun Gu, Ravi Bapna, Jason Chan and Alok Gupta: “Measuring the Impact of Crowdsourcing Features on Mobile App User Engagement and Retention: A Randomized Field Experiment.” Management Science, 2022 (online 2021).
The experiment involved 3,056 mobile-game users. Submission-only users had 43% longer average observed lifetime, 24% longer sessions and a 14% lower abandonment hazard. The treatment concerned user-submitted game content, not feature requests; combinations of participation features did not simply add their benefits. Practical implication: test participation in your own product rather than forecasting these percentages as SaaS returns.
Users can contribute unusually valuable ideas
Marion K. Poetz and Martin Schreier: “The Value of Crowdsourcing: Can Users Really Compete with Professionals in Generating New Product Ideas?” Journal of Product Innovation Management, 2012.
Executives blindly evaluated 103 product ideas. Eight of the ten exceeding the study’s top customer-benefit threshold came from users; two came from professionals. This 80% describes that selected group, not all useful ideas in all businesses. User ideas can complement professional expertise, but feasibility still needs assessment. Practical implication: evaluate an idea’s merit separately from who proposed it.
What this means for a small SaaS team
Our interpretation: collect input early, group recurring problems, make deliberate decisions and explain the outcome. A board is infrastructure for that process, not the process itself. Track whether accepted changes solve the reported problem and combine volunteered feedback with direct research. These studies do not test Simple Feature Board and should not be presented as a guarantee of revenue, retention or ratings.