Learn what research is for and how to ask questions that produce useful answers.

You can plan a small study that answers a real question rather than confirming an opinion.

• Separate what people say, what they do, and what they actually need
• Write research questions that are specific enough to answer
• Take structured notes that are still useful weeks later

Run interviews and usability tests without leading participants toward the answer you want.

You can run a research session that produces honest, usable findings.

• Recruit participants who match the audience you are designing for
• Moderate a session, stay neutral, and follow up on interesting answers
• Run task based usability tests and record exactly where people hesitate

Turn raw sessions into analysis and artefacts a team will actually use.

You can turn a pile of session notes into clear, prioritised design problems.

• Code qualitative notes and group them into themes with a severity rating
• Build personas, journey maps, and problem statements grounded in evidence
• Combine qualitative findings with analytics and support data

Build research into how a team works, so decisions are informed continuously rather than once.

You can run research as an ongoing practice that a product team depends on.

• Set up a repeatable research cadence and a searchable findings repository
• Choose between qualitative, quantitative, and mixed methods for a given question
• Present findings to stakeholders so they change decisions, not just slides