User Research and Market Analysis Assignment Submission
A walkthrough of how one submission turned interviews and surveys into a single prioritised problem
✳The problem they went after
Raw interview notes rarely tell you what to build. This submission starts where most product analysis assignments start, with a pile of conversations and survey responses, and works the harder problem sitting behind them: turning that material into validated evidence about what users actually do and where the pain sits.
✳What they actually did
The work runs user interviews and surveys as a structured method, then moves into synthesis: SWOT analysis, goal setting, and an explicit link from observed user pain to business impact. Personas turn loose archetypes into something concrete enough to argue about. The final step applies a framework to pick one problem to solve, testing candidates against two bars at once, real user pain and meaningful business relevance.
✳What you can take from it
Worth stealing
- Interview and survey methodology run as one system
- SWOT plus goal setting to frame the findings
- Personas built to ground prioritisation, not to decorate
- Final test: enough user pain and business relevance
Read this if
New to research assignments and unsure how to end with a decision
The transferable bitResearch, then synthesis, then a single prioritised problem, with each stage feeding the next rather than sitting as a standalone deliverable. That sequencing is the transferable part. If your write-ups tend to end in a list of findings and no decision, this shows what the closing step is supposed to look like.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
