A beginner UX research project should answer a narrow question with a method that can actually provide useful evidence. Learn to plan a small study, obtain informed participation, ask neutral questions, and separate observations from interpretations. This roadmap investigates how people choose a community workshop. Your output is a research plan and a careful findings summary, not a claim that a few conversations reveal the needs of an entire population.

Choose a question and a suitable method

Use the fictional question: what information do adults look for before deciding whether to book a local practical workshop? This is an exploratory question about decisions and past experiences. Short interviews can help investigate it. Asking participants to rank a polished interface would answer a different question, and a large survey would require a clear design and recruitment strategy of its own.

Write what the study will and will not cover. Exclude sensitive personal matters and do not collect information simply because a form makes it easy. GOV.UK’s research-planning guidance recommends agreeing objectives and approaches Source 1. Use that as a foundation, then specify the evidence you hope to gather: examples of recent choices, information sought, and points where a decision stalled.

Invite a small number of adults who have recently considered a workshop or similar local activity. Explain that this is a learning project, participation is optional, and they can stop. Keep recruitment criteria relevant to the question rather than selecting only people who share your preferences. Avoid recruiting children or vulnerable participants for a casual beginner exercise without appropriate arrangements.

Prepare a plain-language consent note covering purpose, activities, recording, access, retention, and withdrawal arrangements. GOV.UK’s informed-consent guidance explains these practical considerations Source 2. Treat that guidance as research practice, not a substitute for legal requirements in your jurisdiction. If you do not need audio recordings, take anonymised notes instead and agree that approach with participants.

Run a pilot conversation with a willing adult and ask whether the questions are understandable. Check that your notes can capture evidence without interrupting every sentence. Revise the guide before the main sessions. A pilot is a test of your method, not evidence you should silently mix into a different study design.

Ask about experience without steering

Begin with “Tell me about the last activity you considered booking.” Follow with what they needed to know, where they looked, and what influenced the decision. Avoid “Would a beautiful app make this easier?” because it introduces your solution and invites politeness. Ask for concrete examples before opinions about hypothetical behaviour.

For practice analysis, use three explicitly fictional notes: participant A checked travel time before price; participant B could not find required equipment; participant C wanted to know whether beginners were welcome. These are invented examples for learning the method, not actual research findings. They suggest information categories to investigate, but they do not establish how common each concern is.

Keep a note identifier for each observation. Write “B searched for equipment requirements” separately from “The page needs an equipment section.” The first records an observation; the second proposes a design response. GOV.UK’s analysis guidance describes reviewing observations and finding patterns Source 3. Preserve the trail so another reader can question your interpretation.

Synthesize a useful, bounded recommendation

Group the fictional notes into practical access, preparation, and suitability. Draft a tentative recommendation: show travel details, equipment expectations, and beginner suitability before booking. Pair it with a limitation: the example has only three invented cases, so it demonstrates analysis structure rather than user evidence. When you conduct actual sessions, report the real recruitment and methods honestly.

Create a findings sheet with observation, interpretation, confidence, and next action. Include disagreement and missing evidence rather than forcing every participant into a single persona. A useful next study could test whether people can find the proposed information in a prototype. It should not simply ask whether they like your recommendation.

Submit your research question, recruitment criteria, consent process, discussion guide, anonymised evidence, synthesis, and limitations. Keep identifiable notes out of a public portfolio. The skill you are demonstrating is a reasoned path from a question to evidence and a proportionate decision, including the ability to say what remains unknown.

Practice sequence
  1. PlanDefine the uncertainty and choose a method.
  2. PrepareRecruit appropriately and explain participation.
  3. ListenAsk neutral questions about concrete experiences.
  4. SynthesizeConnect evidence to a bounded recommendation.
Practice decisions and evidence
Checkpoint What to produce How to review it
Question Information needed before booking Method investigates real decisions
Consent Purpose and data-use explanation Participant understands optional involvement
Notes Observation with anonymous identifier Interpretation remains separate
Finding Tentative information priorities Limits and next study are explicit
Evidence before advancement
Observation
B looked for equipment requirements.
Interpretation
Preparation uncertainty may block a decision.
Next test
Can a participant find the equipment information in a prototype?

Common questions

How many participants do I need?

There is no universal number that makes every research question valid. For this learning project, a small set of relevant interviews can teach planning and analysis, but it cannot estimate population prevalence. Explain recruitment and limitations. Choose a larger or different study when the decision requires stronger coverage or quantitative estimates.

Can I interview friends?

Friends can help you pilot questions, and some may fit the recruitment criteria. Acknowledge the convenience sample and the possibility that familiarity changes responses. Do not claim they represent all users. Where possible, recruit people with relevant recent experiences and create conditions where disagreement with your assumptions feels comfortable.

Do I need to record every interview?

No. Record only when it serves the study and participants understand and agree to the arrangement. Anonymised notes may be sufficient for a beginner exercise. Plan access and deletion before collecting anything. A recording is not automatically better evidence if you cannot manage it responsibly or find the relevant observations afterwards.

What is a leading question?

A leading question suggests a preferred answer or embeds your assumption. Asking whether a clearer page would be helpful is likely to attract agreement. Ask what the person did, what information they sought, and where they struggled. Follow their account before introducing possible solutions or showing a design you want them to praise.

Can fictional notes be presented as research?

No. Fictional notes are useful for learning analysis structure, but label them clearly and never describe them as interviews you conducted. A portfolio can honestly show a simulated synthesis exercise. If you later collect real evidence, document the actual method and replace the simulation with appropriately anonymised material.

Should I make a persona after every study?

Only when that representation helps the team make a decision and is supported by the evidence. A small exploratory study may be better communicated through needs, observations, and unanswered questions. Inventing a detailed biography can make weak evidence look authoritative. Keep the output proportionate to what you actually learned.

How do I handle conflicting participant accounts?

Keep both accounts and examine the context rather than averaging them into a vague statement. Different travel arrangements, experience levels, or activity types may explain the difference. Treat those explanations as hypotheses until supported. Disagreement can reveal the next useful research question and prevent a design that serves only one situation.

What belongs in a public research case study?

Include the question, method, recruitment rationale, anonymised evidence examples, analysis process, recommendations, and limitations. Remove identifying details and respect the agreed use of the material. Explain what changed because of the evidence. A transparent account of uncertainty is more credible than claiming a small study validated an entire product.

Continue your learning

Wireframing Roadmap: Turn a User Task into Clear Screen Layouts. Usability Testing Roadmap: Observe Tasks and Turn Findings into Improvements.

Sources and further reading