How do you adapt and iterate your research process based on changing project goals and user needs?

Research plans look brilliant in the lab. But reality will throw curve balls at you and often you won't have much runway to make adjustments. So pressure test your research plans early with scenario planning that uses 'what must be true' assumptions. E.g Legal will allow us to engage with existing customers. This gives you time to identify fall back plans ahead of time.

Adapting and iterating your research process is vital to maintain relevance and accuracy. User needs, project goals, and market landscapes change. Flexibility ensures your design stays aligned with evolving dynamics, delivering solutions that truly resonate with users.

My experience working with Matt on adapting and iterating our projects current resource process was incredibly helpful as we thoroughly planned to refine each step based on real time feedback from our stakeholders.

Additionally, it is important to establish success metrics and data collection methods from the beginning. This allows you to objectively evaluate progress and make adjustments as necessary. Adopting a continuous test concentration is also essential; Being willing to test your ideas quickly with low-fidelity prototypes can save valuable time and resources in the long run. Finally, remaining agile and responsive to changes in the project environment or users' needs will ensure that your research process remains relevant and effective regardless of the situations.

Choosing the right research methods is like picking the perfect tool for the job. Begin by crystalizing your research objectives, understanding your audience, and assessing available resources. Match methods to your project's scope and timeline, focusing on approaches that generate practical insights. This ensures your research is not just effective but also a precise fit for your unique design challenges.

It is essential to consider the stage of the project you are at. One-on-one interviews and focus groups are particularly useful in the early stages when you are trying to understand problems and opportunities. Questionnaires and surveys are best suited for later phases when you need to validate hypotheses or assess the prevalence of certain attitudes or behaviors. Prototyping and usability testing, in turn, are crucial for iterating and refining design solutions. It is also valuable to consider combining different methods to obtain a holistic view of the research problem. For example, you might start with qualitative interviews to explore an issue and then use quantitative research to measure the extent of the identified issue.

Very true! Our Project found out very quickly that "One size does not fit all". Matt's guidance taught us about listening to the customer, asking the difficult questions. We were able to deliver with deeper understanding and gained stakeholder trust in our new research method.

Flexibility is key: As you delve deeper into your project, you might discover new information or aspects that you hadn't considered initially. Being flexible and adaptable with your research questions allows you to explore these unexpected but potentially valuable avenues. Stay focused: While refining your questions, it's crucial to maintain a balance. Ensure your research stays focused and doesn't become too broad or all-encompassing. Clearly defined questions will lead to more concise and insightful findings.

I agree with this so much! Communication and collaboration in my experience with project stakeholders is incredibly important. We gained trust and 'buy in' via knowledge of individual goals, expectations and opinions.

If you are changing your research plan and have not primed your sponsor ahead of time it's going to suck. So loop the sponsor in during the research design. Include setting expectations of fall back plans and associated costs and time impacts. It's much better to have these chats up front before the research has been kicked off as you can mould expectations with less emotional fallout

Stuff ups, potatoe moments and wins. Capture them all and transparently share them with the wider design team. Often it's the small logistics you don't immediately think of that can trip you. E.g How will participants get into the building after hours when the lobby is closed.