A UX designer studies how people accomplish a task and helps improve the experience of doing it. The work can include research, journey mapping, information organisation, prototyping and usability testing. A strong beginner project shows how evidence changed a design decision, not just a collection of polished screens.

Observe a task before designing a solution

User experience includes what happens before and after a screen appears. Someone booking a workshop needs to understand the prerequisites, choose a session, register and know what happens next. A designer investigates uncertainty at each stage rather than assuming that a new colour palette will solve the problem.

Nielsen Norman Group describes usability testing as observing participants attempting realistic tasks. For a small practice study, ask a person to find a suitable workshop rather than instructing them to click the registration button. The first task exposes their reasoning; the second mainly tests whether they can follow directions. Record behaviour separately from your interpretation, and seek permission before recording anyone.

Make the reasoning visible

A journey map describes stages, goals, difficulties and possible improvements. It should not pretend to be research if it came entirely from your imagination. Mark an assumption-led map as a hypothesis, then update it when observation supports or challenges it.

A prototype lets you explore how an experience might work before full implementation. Start with paper or simple linked frames when layout and flow are still uncertain. Explain why each screen exists and what happens if the user makes a mistake. Accessibility matters throughout: understandable labels, logical headings and clear feedback are part of making a task achievable, rather than finishing touches added after the visual design.

Practice: a fictional college workshop booking flow

Invent a workshop listing with three sessions, each with a date, location, duration and prerequisite. Your goal is to help a first-year student choose an appropriate session and understand whether registration succeeded. Create an initial paper flow and write three neutral tasks, including one for a session that is already full.

If volunteers agree to participate, observe them without rescuing them immediately and use anonymous notes. If you cannot recruit anyone, conduct a structured self-review and label it as such. Do not call it user testing. Revise the flow based on one specific problem, such as a prerequisite hidden after registration. Present the earlier screen, the evidence and the revised design together. Success is a clearer explanation of the decision, not a fictional conversion increase.

Explore entry routes and team expectations

UX roles differ: some emphasise research, others interaction design or broader product work. Read job descriptions for tasks, expected evidence and collaboration responsibilities. The US BLS digital-designer profile provides broad occupational context, but local qualifications and employer requirements must be checked independently.

A useful starting portfolio contains a small number of complete studies with a question, constraints, method, findings and revisions. Include what did not work. Practise discussing your design with developers and explaining which behaviour is essential versus flexible. If you enjoy arranging visual components more than investigating task problems, compare UI design before choosing a longer learning programme.

Skills and evidence to build

Practical evidence for UX designer careers
Skill Practice output Quality check
Research planning Three neutral tasks and a consent-aware observation plan. Tasks describe a goal without revealing the intended interface action.
Synthesis A list separating observed problems from guesses. Every claimed finding can be traced to a note or clearly labelled assumption.
Interaction design A flow covering selection, registration and confirmation. The full-session and cancellation states have a sensible next step.
Communication A short before-and-after case study. The reason for the change is clearer than the decorative presentation.
A small workflow you can rehearse
  1. Frame

    Choose a participant goal and specify what you need to learn about the booking task.

  2. Observe

    Notice hesitation, wrong turns and unanswered questions without supplying the intended route.

  3. Revise

    Change the smallest part of the flow that addresses the evidence you collected.

  4. Recheck

    Try the revised task and record whether the original difficulty still occurs.

Review the evidence before presenting it
Observation
A participant reaches the confirmation page but asks whether a seat is actually reserved.
Interpretation
The confirmation message may not make reservation status sufficiently clear.
Design response
State the booking status and next step explicitly; evaluate the revised message rather than assuming it worked.

Common questions

Must a UX designer be good at drawing?

You need to communicate ideas, but detailed illustration is not the main requirement. Boxes, labels and arrows can explain an early interaction. Practise making the sequence understandable and discussing alternatives. A beautiful sketch is less useful than a rough flow that reveals a missing decision or a confusing step.

Can friends participate in a practice usability test?

They can help you learn the method if they reasonably resemble the intended users, but disclose the limited sample and relationship. Friends may be unusually supportive or know your intentions. Avoid treating their feedback as representative market evidence, and never manufacture participants to make a case study appear stronger.

How many screens should my first project contain?

Use enough to complete one meaningful task, including an error or exception state. Five purposeful screens can reveal more reasoning than twenty decorative ones. Choose the scope from the user journey rather than a portfolio template, and explain any parts that remain outside the exercise.

What is the difference between an opinion and a finding?

An opinion is a belief or preference; a finding is an interpretation grounded in evidence you collected. “The page feels crowded” is an opinion unless you explain the observed difficulty. A finding might describe participants overlooking a prerequisite and show how that affected their booking decision.

Should I learn a design tool before research?

Learn enough of a tool to express and test ideas, but do not postpone observation until you master every feature. Paper sketches can support early research. As the work develops, learn reusable components and interactive prototypes because they help you revise consistently, not because software proficiency alone proves UX ability.

Is UX work only about mobile apps?

No. Websites, internal software, service interactions and multi-step processes also involve user experience. For a beginner, choose a task you can understand and examine responsibly. A modest library or workshop service can produce a stronger study than a speculative redesign of an enormous product you cannot research.

How should I present a project with no measurable outcome?

Describe the actual output and the evidence available. You can explain that a prototype was revised after observations without claiming reduced support costs or increased registrations. Include the next evaluation you would run. Honest limitations help a reader distinguish your design reasoning from an invented success story.

What should I ask when considering a UX internship?

Ask which tasks you would perform, who reviews the work and whether you can observe research or usability sessions. Clarify access to users and expectations around portfolio sharing. These details reveal learning opportunities more clearly than a title that could describe anything from screen production to substantial product research.

A useful next step

To understand the visual-system side of product work, continue with UI designer careers. If requirements and stakeholder agreement interest you most, explore business analysis.

Sources and references