Portfolio Case Studies

Observe

See the communication problem

A portfolio page shows beautiful final images, but no brief, process, role, or design reasoning.

• What to notice

  A case study should not show every exploration. Select evidence that supports the story.

• Why it matters

  Clients and employers need to understand how you think, not only what the final image looks like.

Takeaway: A portfolio case study explains the problem, process, decisions, result, and learning behind the final work.

Understand

Understand the principle

A portfolio case study explains the problem, process, decisions, result, and learning behind the final work.

Clients and employers need to understand how you think, not only what the final image looks like.

Takeaway: A case study should show how you think, not just what the final mockup looks like.

Understand

Study the visual model

Read the image from first attention to final detail. Then compare that path with the labeled decision model below.

Context

Problem, audience, role.

Process

Research, exploration, decisions.

System

Rules and applications.

Result

Outcome, learning, next step.

Takeaway: Use the model as a diagnostic, not a decoration recipe: A case study should not show every exploration. Select evidence that supports the story.

Try

Follow a worked decision

• Situation

  A portfolio page shows beautiful final images, but no brief, process, role, or design reasoning.

• Designer move

  Add a short project context, selected process evidence, decision captions, and final applications.

• Result

  The viewer can understand both the quality of the work and the designer's judgment.

Takeaway: Good portfolio writing makes design decisions legible.

Try

Run the studio method

Structure the case study around context, challenge, role, process, system, final applications, and outcome.

• Frame: Clients and employers need to understand how you think, not only what the final image looks like.
• Explore: Rewrite one project into a short case-study outline with screenshots and decision captions.
• Test: A case study should not show every exploration. Select evidence that supports the story.
• Revise: change one variable, compare the versions, and keep the stronger evidence.

Takeaway: Structure the case study around context, challenge, role, process, system, final applications, and outcome.

Critique

Diagnose weak decisions

Name the visible problem before proposing a fix. This keeps critique specific and useful.

• Showing only final mockups.
• Including too much process without a story.
• Hiding your role in a team project.

Takeaway: A strong designer can name the mistake and the fix.

Apply

Use the review rubric

Ask first: A case study should not show every exploration. Select evidence that supports the story.

• State the problem, audience, role, and constraints.
• Show selected process, not every file.
• Caption decisions with why they mattered.
• End with outcome, learning, or next step.

Takeaway: Your design is ready to move forward when you can point to evidence for every criterion.

What should a case study reveal?

• Only final mockups with no context.
• The design thinking and decisions behind the final work.
• Every unused file.
• No role or objective.