A crash course for turning findings from UX research into product hypotheses.

Image for post
Image for post
Thanks to absurd illustrations for cover image

Design research is still such a new field in product design, that the common myths are still floating around. The most common (and dangerous) misconception I hear is that user research can be a handicap, creating biases towards a narrow group of people and preventing designers from doing anything more than building marginally better solutions.

The faster horse problem.

In a way, this is true. If you’re simply taking the pains of a specific user and solving each directly, you’ll end up with a faster horse. …

Image for post
Image for post

Our team at MetaLab is piloting this new thing when we start on a new project, and it’s working really well. At the very start of the project—once we have a rough idea of what this product or feature looks like—our team block off a full day. Then we each go away individually and design the whole product in one day, solo. No wireframes, no user testing, no iteration, no feedback or sharing.

If this sounds wrong, it’s because it is. Good product design work is done by doing the exact opposite: starting broadly and exploring lots of potential solutions in really rough fidelity (sketching, wires), working collaboratively and getting feedback from each other early and often, and testing and validating our assumptions with users. …

Image for post
Image for post

A few weeks ago I was chatting with my coworker about a health app her team was working on. …


Konstantin Sokhan

Design director at MetaLab. Previously lead at Format. Ex-Torontonian. Full stack Dev. Co-creator of stockwallet.io. Lover of climbing and the great outdoors.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store