A better approach in sharing user research findings with a partner is “findings, consensus, and recommendations.” Share your research findings, develop a shared understanding of those findings with your partner, and then develop recommendations that are informed by the partner’s priorities and constraints.
I wrote this blog post with Jess from People For Research, about how to design the best research experience:
There’s no one perfect way to do user research. Every method has its pros and cons. The key is to design the research process. Just like anything else you might design (a website, a gadget, or a garden) it’s about:
Defining the problem(s) you want to solve
Coming up with a solution that works within the constraints of time and budget
Read the rest at People For Research.
Taking bigger risks at the start of the product life cycle usually pays off. At the start, you’re unlikely to have much data on your users and their behaviour, so prototypes will have a set of assumptions about your users to test
Design researchers should embrace less structure and more openness at the early stages of product design, and rigor and structure in the mature stages of product sales.
It’s so easy to focus on the ‘rigor and structure’ bit of the graph above – prototyping, testing, and optimising – and forget the rest. A/B testing and protyping is tangible, concrete work. But being open and creative is where we define the problem space by figuring out what we don’t already know.