Make research actionable
Design research is most valuable when it leads to shared understanding. Analysis, synthesis, and sharing help us reflect on the data we’ve collected and determine a course of action that involves the broader team.
From data to insights
Articulating insights can involve different activities, but it’s primarily a time for everyone on the project team to work together to begin to map out larger patterns and themes.
At 18F this generally involves:
Making meaning always happens in relation to the research questions and/or problem statements identified during research planning. Some questions you might ask:
Involving the team
Finding patterns in research is a great time to involve partners and team members, especially people who were not involved in conducting the research. A collaborative approach helps to:
When inviting partners, think about how exposed they were to the research process and set clear expectations on how you would like them to engage. Be mindful of your ethical obligation to respect the people who participated in your research. For example, you might want to be careful when involving a CIO in analyzing data you collected while interviewing their employees.
Before conducting shared analysis or synthesis, make sure that any quote could be attributable to multiple participants so no one person can be identified as the person that said it. This is especially important if your stakeholders know your participants.
Making meaning out of research can involve any number of different methods. The most basic method is writing a summary of what you found. Write a brief summary of the data you collected that, when read together with your research plan, documents the research itself: the questions you started with, how you went about answering them, what you learned, and why it matters. Aim for true and useful, rather than comprehensive.
Outside of writing a summary, you should choose your methods based on the desired outputs and outcomes of your research. For example:
Whichever method you use, introduce it to your partner as well so they can build their research skills.
Any approved tool can be used. We’ve listed some of our approved, commonly used tools.
Insights into action
Turning insights into action helps us answer and communicate:
- What can we do to address the issues we identified?
- What impact do we think our changes will make?
- What do we need to do next?
Artifacts that we use to do this include:
- Presentations template
- Design Hypotheses
- Design Principles
- Mental models
- User scenarios
- User stories
- Journey maps
- Other creative outputs
These artifacts are tools for communicating the answers to your research questions and prioritizing opportunities for action. When choosing which artifacts to make, consider your audience and think about what will best create a shared understanding of your findings. For example, imagine you are describing an experience that is often a challenge for a specific group of users. In this case, personas accompanied by a journey map may be more effective than a set of design principles.
Making decisions based on the research
After each round of research, the whole team should identify how the research findings change the work planned for the next sprint. After discovery research, this could include prioritized areas for further exploration or prototyping. For a new or existing product, this could include new bugs identified, new features to explore, or a different design focus.
Communicating your proposals is critical to seeing them come to life; even the most beautiful artifact loses its power if it’s left on a shelf. Here are some good guideposts for sharing and socializing research in government.
Before you share
At this point it is a good practice to delete any recordings from the sessions to further protect the privacy of your participants (and be sure to ask that anyone you shared recordings with do the same).
We always try to make sure we are on the same page as the partner in protecting PII before publishing!
Understanding your audience
Our research often gets shared far beyond the project team. Depending on the project, stakeholders that care about our research could include:
Sharing research is all about storytelling. When packaging research, think about what role the audience plays in that story and what the outcomes will be for them. Being clear about who the audience is, what they need to understand, and how they might best understand it, helps us communicate our findings more effectively.
Presenting the work
The most common way we socialize our research is through presentations. These presentations can vary widely based on the audience. Here are a few presentation-building tips:
Keep in mind that a researcher’s job doesn’t end with a formal presentation. Insights from a research sprint should be used to inform decisions for the rest of a project and to revisit on an ongoing basis. Always look for lightweight ways to share research and advocate for the voice of users.
One of the ways we do this at 18F is sharing a “weekly ship” of what the team has worked on each week. This could be an opportunity to share a compelling quote or pain point uncovered between rounds of research synthesis.
Publishing on Github
While it is not mandatory, we often use GitHub to manage our projects. GitHub also allows us to keep the public up to date on our research findings. It is also a useful tool for communicating with potential vendors who may work on our projects in the future. Publishing findings can help vendors and the public better understand the problem a partner is trying to solve and how they are approaching it. It also signals that the partner wants to work with a vendor who is also willing to work in the open.
Handing off research responsibly
Research handoffs occur when wrapping up a round of research or an engagement, when vendors onboard, or when staffing arrangements change. Managing handoffs thoughtfully can help future researchers get up and running faster. At this point, ask:
In addition to the above considerations, providing an introduction or tour of the work is a helpful way to transfer knowledge to new team members or vendors. Consider writing a ReadMe document which new team members can read and refer to for project background, context, history, and quick links to important files or resources.