[Below is my screenshot of badoo users’ highlighted pain points or requests on Google App store]
The topics represent common themes in user feedback, with the numbers indicating the count of reviews or mentions associated with each.
Prioritization should focus on high impact areas first. So, based on the data provided, I'll be using;
MoSCoW Framework
I'll categorize the 10 topics into Must-have, Should-have, Could-have, Won't-have. This filters out non-essentials quickly and ensures core viability.
So, I'll be using the mention counts as a proxy for Reach and pain severity (higher mentions = bigger user impact)
| MUST-HAVE (non-negotiable for retention & ratings improvement) | SHOULD-HAVE (important, high value if time allows) | COULD-HAVE (nice-to-have, low risk if deferred) | WON’T-HAVE (For now) | | --- | --- | --- | --- | | Match Quality (712) | In-App Purchases (287) | Relationship Goals (155) | None, all have some mentions, but defer low ones if capacity is tight. | | Account Management (578) | Value for Money (238) | Customer Support (133) | | | Ad Experience (472) | Distance Filtering (197) | | | | Account Verification (308) | Message Limits (196) | | |
Define 4-5 key criteria relevant to Badoo (dating app in markets like Nigeria):