Download as PDF, PPTX
Uploaded byJeremy Horn
Problem Statement Definition
The document outlines a framework known as the 'opportunity statement' for product managers to define user needs and hypothesize solutions, based on observations and user data. It highlights a specific issue where 60% of job applicants do not receive responses from employers and proposes a solution of matching job openings to users' skills to enhance their likelihood of getting interviews. The document emphasizes the importance of structuring opportunities for better collaboration and alignment with business goals in product development.
More Related Content
Similar to Problem Statement Definition
Problem Statement Definition
- 1.
- 2. About me Product directorat Artsy 10 years product experience in marketplaces, mobile security, ed tech Former front end engineer, UX designer Fine art & computer science degree from the University of Chicago ENTJ
- 3. Reasonable sentiments areplentiful
- 4. Product managers find opportunitiesin feelings
- 6. The “opportunity statement”is a framework for defining user needs, validating assumptions, proposing specific solutions, and hypothesizing about measureable outcomes. We have observed that _____. We believe that if we _____. Then our users will achieve _____.
- 7. We have observedthat... Specific problems or opportunities backed by quantitative or qualitative data. User experience interviews Product metrics Support tickets Market research Surveys & focus groups
- 8. Looking for evidencein product data
- 9. We have observedthat in the last 6 months, 60% of our users applying to jobs have not heard back from a single employer.
- 10. We believe thatif we... User-centric solution that is hypothesized to address the observation. “5 Whys” “How might we…” “I wish…” Happy path sketching Analysis of similar products
- 11. Using the “5Whys” to hypothesize Users aren’t getting interviews… Why? Because they’re applying for jobs that aren’t a good fit… Why? Because they think the more jobs they apply for, the better their chances… Why? Because they don’t know that recruiters only have time for candidates who already have all the necessary skills and experience… Why? Because job sites let users search for and apply to any job, without consideration for fit. Aha!
- 12. We have observedthat in the last 6 months, 60% of our users applying to jobs have not heard back from a single employer. We believe that if we showed users a list of job openings where the required skills and experience matched those on their resume…
- 13. Then we willachieve... Projected measurable improvement defined in advance of the project. Addressable universe Ecosystem assets Impact of similar features Data science projections
- 14.
- 15. We have observedthat in the last 6 months, 60% of our users applying to jobs have not heard back from a single employer. We believe that if we showed users a list of job openings where the required skills and experience matched those on their resume… Then users would be deterred from applying to jobs for which they are not qualified and would receive an initial phone screen for at least 25% of submitted applications.
- 16.
- 17. ● Reduce wasteddevelopment time ● Structure, rigor, and actionable tasks to ideation and design exercises ● Shared conversation about prioritization ● Improved collaboration between product, design and engineering. ● Alignment to higher level business goals.
- 18. No opportunity isa 100% safe bet Were our assumptions about user needs correct? Is this solution feasible? Execution matters!
- 19. 1. Opportunity statementdefinition 2. Design studio & user testing 3. Requirements definition & feasibility assessment 4. Engineering production & launch 5. Product metrics tracking