▶️ How to structure the synthesis or insights of user testings?
▶️ How to structure the synthesis or insights of user testings?
Service Design Questions and Answers
Basics of Service Design
Basics of Service Design
Examples of good Service Design
Examples of good Service Design
Learning Service Design
Learning Service Design
Service Design and others fields
Service Design and others fields
Service Design tools, apps and methods
Service Design tools, apps and methods
Service Blueprints and Journey Maps
Service Blueprints and Journey Maps
Service Design as a career
Service Design as a career
Hiring service designers
Hiring service designers
Coaching and Service Design
Coaching and Service Design
Service Design portfolio
Service Design portfolio
Service Design workshops and facilitation
Service Design workshops and facilitation
Service Design and Ideation
Service Design and Ideation
Service Design and research
Service Design and research
Service Design and Presentations
Service Design and Presentations
Service Design Principles
Service Design Principles
Service Design projects
Service Design projects
Service Design Books
Service Design Books
Accessibility and Service Design
Accessibility and Service Design
Sustainability and Service Design
Sustainability and Service Design
Service Design in government
Service Design in government
Service Design Philosophy and Mindset
Service Design Philosophy and Mindset
Service Design in Switzerland
Service Design in Switzerland
My two cents
Here is one structure that I like to use to synthesise learnings made from user tests in a way that pushes the team to stay focused and practical:
Validated: things we had as the hypothesis that worked well during the testing. These are things we don't need to discuss further or change. If needed, you can further divide this into "validated and important" versus "validated but less important than what we thought"
To work on: things we need to adapt or decide on. These elements are validated as enough different people mentioned the same idea. If needed, you can further divide this into "To discuss and decide" for things where you could keep things as is and "To change or clarify in prototype" for things that you already know need to be changed.
Inspirations: things that are not validated but are nevertheless inspiring. These are elements that you can review and draw inspiration from.
Below you can see in a video a real-world case where I used this structure:
More Service Design questions and answers like this one
Check out all the questions about the field, user and desk research side of Service Design.