I went straight to brainstorming features without anchoring on user problems first, which I could tell was the wrong move about halfway through.
Start by clarifying the goal and scope of the feature, then segment WhatsApp group users and identify key pain points. Brainstorm and prioritize solutions based on impact and feasibility, and finally outline success metrics and potential risks.
Pro tip: Anchor your feature in WhatsApp's core value of private, reliable communication, and consider how it scales across diverse markets and cultures. Show awareness of Meta's business model by linking the feature to engagement or monetization opportunities without compromising user trust.
Ask clarifying questions to understand the goal (e.g., increase engagement, solve a specific pain point) and constraints (e.g., platform, timeline). Define what 'group messages' entails and the target user segment.
Segment group users (e.g., family, friends, work, communities) and map their key challenges with current group messaging. Prioritize the most impactful and underserved needs.
Generate a range of feature ideas addressing the prioritized needs. Evaluate each on impact (user value, business value) and feasibility (technical, operational), then select the most promising one.
Describe the chosen feature in detail: how it works, user flow, and key functionalities. Outline a minimum viable product (MVP) to test core assumptions quickly.
Define metrics to measure success (e.g., adoption, engagement, retention) and identify potential risks (e.g., privacy, abuse, technical debt) with mitigation strategies.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.