New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Research Synthesis Step 3: Compiling results #13216

sarahmonster opened this Issue Jan 5, 2019 · 0 comments


2 participants
Copy link

sarahmonster commented Jan 5, 2019

Note: this is to discuss and reference methodology for compiling and communicating results of our sitebuilding study. This isn't 100% set in stone just yet and will be tweaked as we finalise details.

Want to get involved? No prior research experience is necessary, and we'd ❤️ your help!


  • Key takeways (no more than ten)
  • Recommendations (to inform product decisions)
  • A mental model of sitebuilding for each identified segment
  • A customer journey for each identified segment

The above will be compiled into a single report—either as a PDF or a single-page site (more accessible) of no longer than 10-15 pages.

Report structure

Executive summary

Basically a one-page tl:dr;

Background information

Who we talked to, when, what we talked about, who did the talking, what we were trying to learn, goals of the research, etc.

Key findings

A short list of the most important findings of the study.


Actionable product recommendations that can be used to guide phase two.

Theme exploration

For themes identified in analysis, define and name each theme. Give some description about what you've learnt, stories and quotes within that theme, any contradictions within that theme, and explain what makes it interesting and relevant to the project.

Mental model & customer journey

These will be visual tools that can be used to refer back when making product decisions and to inform an understanding of the entirety of the customer experience.

@sarahmonster sarahmonster created this issue from a note in Phase 2 design (In progress) Jan 5, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment