Product Designer at Change.org
Product design at Change.org · Previously Zendesk · Designer Bridge 5 alumni
Research briefings are pretty common and valuable. It's important to communicate findings often, so coming up with a way to communicate this in a streamline manner both in-person and asynchronously is golden.
You'll need to have a forum for communicating the research you did not only with a room full of colleagues but also with the organization at large. It's important to make sure that the research findings are accessible to all people -- including people who are not in your presentation meeting. So, if you make a Keynote (make sure it is accessible online somewhere) ... or go straight to Google Slides. Document it somewhere so that people may access it.... See more
Every research project has a goal in mind. Make sure this is clearly communicated at the start of your presentation, so that people reading it understand the purpose it served. It is also good to be clear as to who your target audience was and why. List demographic data as well, if you want. Helps give more context. More context is always good.... See more
It's important you make clear the questions you wanted to answer and how they tie back to the goals of the project. This helps stakeholders understand how the research answered the questions the team or you had before qualitative research.
You don't need to include this but it should be available to the team. Show them what questions were asked and again relate them back to the questions you wanted answered.
Did the users you tested with interacting with any designs? If so, show it. Tie relevant questions to the screens.
So what are you going to do with your findings? Offer a recommendation on what the next steps are given the findings you have ... this could come in the form of a possible solution or additional steps to get the desired results you're looking for.... See more
Whether it's comments within the document itself or even a Slack channel, provide people in your organization a way to provide feedback or questions so that you might address them.
Each have their pros and cons. It largely depends on what you think best compliments your work style and where you think you'll find the most growth opportunities. I'll outline a few (but not all) of the pros and cons I've seen and heard about most...
Pros: Highly generative, work with a variety of clients / problem spaces, often good processes. Cons: Often detached from development, often not involved in problem & opportunity definition, no validation of design decisions.
Pros: Highly generative, productive, fast-paced, designers usually have ability to take multiple roles through product development. Cons: Processes often less-defined, often lacks user research, often times do not value design.
Pros: Well-defined processes, usually bigger problem space opportunities available, more stability, easier to find mentorship. Cons: Less productive, more bureaucracy, metric driven.