Skills

UX Design Case Study

12 weeks · 0 milestones

Complete UX project documented from research to final design as a professional portfolio case study. Triad: concept/ideation artifact (problem framing and research plan: the problem statement, who it affects, what is currently known, and the research approach), technical execution artifact (complete UX artefacts across the project: research data and synthesis, design iterations showing development, final prototype, and usability test results after final design), documentation/critique artifact (case study document covering the full process with critical reflection: what was learned at each stage, what design decisions were driven by what evidence, what measured outcomes were achieved or what would be measured — minimum 2,500 words across all case study sections). Studio critique: portfolio review by a senior UX designer or UX design director with documented written feedback on the research-to-design chain, quality of synthesis, and professional readiness of the case study as a portfolio piece. Proof: case study document or portfolio entry, supporting research and design artefacts, documented critique feedback. Verifier: senior UX designer (minimum 5 years experience) or design director.

Part of: Creative & Design · Proves for: PG

Milestone map

3 milestones

Complete end-to-end UX project across all five phases

6–8 weeks (full project)

Select a real design problem from your research, a client engagement, or a substantial speculative project. Apply the full UX design process: discovery research (minimum six participants), synthesis, information architecture or user flow design, interactive prototype, and usability testing (minimum five participants). Document evidence of each phase before moving to the next.

Proof required

Submit evidence of each project phase: (1) research data summary (participant count and methods), (2) synthesis artefact (affinity map or equivalent), (3) architecture or flow diagram, (4) prototype link or export, (5) usability test findings summary (participant count, three tasks, completion rates).

What gets checked

All five phases are documented — not just the prototype
Research and testing used real participants, not colleagues or self-test
Phases are connected — synthesis findings demonstrably informed the prototype direction

Common mistakes

Project skips or abbreviates phases without documented evidence
Prototype was not tested with real users
Synthesis did not inform the design — phases were executed in parallel rather than sequentially

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Verify all five phases are documented with evidence — ask for research participant count and usability test count separately
Check research used real participants — ask how they were recruited
Ask student: how did your synthesis findings change your initial design direction?

You'll sign in first, then come straight back here.

Write UX case study documenting process and design decisions

2 weeks (writing + editing)

Write a UX case study document (minimum 1500 words) covering your project. Document the process, not just the outcome: include your initial problem framing, what research revealed that changed your thinking, one specific design decision with alternatives considered and reasoning, what usability testing revealed and what you changed, and what you would do differently. Include screenshots or artefact exports.

Proof required

Submit your UX case study document (minimum 1500 words with embedded screenshots or artefact exports as a PDF).

What gets checked

Case study documents process — design decisions are explained with reasoning and alternatives
At least one specific design decision is explained with alternatives considered
Case study honestly addresses what usability testing changed — not only what worked

Common mistakes

Case study is a portfolio piece describing the final design without process documentation
Design decisions are stated without alternatives considered or reasoning
Case study doesn't address what usability testing changed

Powstik Guide

A 1,500-word UX case study with real artefacts.

Steps

State the problem and your role.
Show research, then design, then testing.
Explain each key decision.
End with results and what you'd change.

Template

Problem:        My role:
Research:
Key decisions and why:
Testing and results:
What I'd change:

What gets sent back

Under 1,500 words.
Final screens only, no process.
Role unclear.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Check case study documents process decisions — ask student to identify one specific design decision they nearly made differently
Verify at least one design decision is explained with alternatives considered
Ask student: what changed most between your initial design direction and the final prototype, and why?

You'll sign in first, then come straight back here.

Present case study for critique and revise with documented changes

1 week

Present your UX case study to a UX practitioner, hiring manager, or design lead in a review session (minimum 25 minutes). The reviewer should challenge your process decisions, research validity, or design reasoning. Document specific challenges and revise the case study incorporating at least two specific changes from the review. Produce a revision note (minimum 200 words) documenting what changed and why.

Proof required

Submit: (1) review session record (date, reviewer, specific challenges — minimum half page), (2) revised case study with tracked changes or explicit revision note (minimum 200 words documenting what changed and why).

What gets checked

Review record documents specific challenges to process or design decisions
Revision note identifies at least two specific substantive changes made from review feedback
Revisions improve the honesty or specificity of the case study — not just polish

Common mistakes

Revisions are cosmetic — formatting or typo fixes rather than substantive improvements
Review focused on portfolio presentation rather than process quality
Revision note describes changes without explaining why they improve the case study

Powstik Guide

A critique of your case study, with your response.

Steps

Book a qualified reviewer, not a classmate.
Present the work and your intent.
Write down every challenge raised.
Decide what you'll change and why.
Record the revisions you made.

Template

Reviewer:        Role:        Date:
Challenges raised:
-
My response and changes:
Revised version attached: yes / no

What gets sent back

Record under half a page.
Peer-only review.
No response or revision.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Confirm review challenged process decisions or design reasoning — not just presentation quality
Verify revision note identifies at least two substantive changes with reasoning
Ask student: if you were hiring a UX designer, what would you look for in a case study that this one now demonstrates?

You'll sign in first, then come straight back here.

Part of

UX Research & Design →

Related outcomes

Milestone map

3 milestones

Complete end-to-end UX project across all five phases

6–8 weeks (full project)

Proof required

What gets checked

All five phases are documented — not just the prototype
Research and testing used real participants, not colleagues or self-test
Phases are connected — synthesis findings demonstrably informed the prototype direction

Common mistakes

Project skips or abbreviates phases without documented evidence
Prototype was not tested with real users
Synthesis did not inform the design — phases were executed in parallel rather than sequentially

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Verify all five phases are documented with evidence — ask for research participant count and usability test count separately
Check research used real participants — ask how they were recruited
Ask student: how did your synthesis findings change your initial design direction?

You'll sign in first, then come straight back here.

Write UX case study documenting process and design decisions

2 weeks (writing + editing)

Proof required

Submit your UX case study document (minimum 1500 words with embedded screenshots or artefact exports as a PDF).

What gets checked

Case study documents process — design decisions are explained with reasoning and alternatives
At least one specific design decision is explained with alternatives considered
Case study honestly addresses what usability testing changed — not only what worked

Common mistakes

Case study is a portfolio piece describing the final design without process documentation
Design decisions are stated without alternatives considered or reasoning
Case study doesn't address what usability testing changed

Powstik Guide

A 1,500-word UX case study with real artefacts.

Steps

State the problem and your role.
Show research, then design, then testing.
Explain each key decision.
End with results and what you'd change.

Template

Problem:        My role:
Research:
Key decisions and why:
Testing and results:
What I'd change:

What gets sent back

Under 1,500 words.
Final screens only, no process.
Role unclear.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Check case study documents process decisions — ask student to identify one specific design decision they nearly made differently
Verify at least one design decision is explained with alternatives considered
Ask student: what changed most between your initial design direction and the final prototype, and why?

You'll sign in first, then come straight back here.

Present case study for critique and revise with documented changes

1 week

Proof required

What gets checked

Review record documents specific challenges to process or design decisions
Revision note identifies at least two specific substantive changes made from review feedback
Revisions improve the honesty or specificity of the case study — not just polish

Common mistakes

Revisions are cosmetic — formatting or typo fixes rather than substantive improvements
Review focused on portfolio presentation rather than process quality
Revision note describes changes without explaining why they improve the case study

Powstik Guide

A critique of your case study, with your response.

Steps

Book a qualified reviewer, not a classmate.
Present the work and your intent.
Write down every challenge raised.
Decide what you'll change and why.
Record the revisions you made.

Template

Reviewer:        Role:        Date:
Challenges raised:
-
My response and changes:
Revised version attached: yes / no

What gets sent back

Record under half a page.
Peer-only review.
No response or revision.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Confirm review challenged process decisions or design reasoning — not just presentation quality
Verify revision note identifies at least two substantive changes with reasoning
Ask student: if you were hiring a UX designer, what would you look for in a case study that this one now demonstrates?

You'll sign in first, then come straight back here.