How to write a graphic design case study that wins better clients.
Show more than the final visuals. Give a higher-value buyer credible evidence of the problem, your decisions, your contribution and what changed.
Write a graphic design case study in this order: client context, business problem, constraints, your role, approach, key decisions, design response, implementation and verified evidence. Use a short answer at the top, descriptive headings, images that prove specific points and an honest boundary between your contribution and the wider result.
A beautiful portfolio can earn attention. A well-written case study helps a serious buyer decide whether to trust you with a more important problem. It shows how you think when the brief is incomplete, stakeholders disagree or a design choice needs a reason beyond taste.
The aim is not to make every project sound transformative. It is to make your relevance, judgement and evidence easy to understand.
Portfolio project vs design case study
| Portfolio project | Client-winning case study |
|---|---|
| Leads with polished final images | Leads with the client problem and useful change |
| Describes what was made | Explains why important decisions were made |
| Uses a broad “we” | Defines your role and collaborators |
| Claims a successful outcome | Names the evidence and its limitations |
| Appeals to anyone who likes the style | Helps a similar buyer recognise relevant capability |
The nine-part graphic design case study structure
1. Use a title built around the problem or change
“Brand identity for Acme” identifies the output. “Clarifying Acme’s offer for its move into enterprise sales” gives the buyer a reason to care. Keep the client or sector visible where permission allows, but lead with the commercially relevant situation.
2. Give the short answer first
Open with a 50 to 90 word summary that identifies the client, problem, your role, response and strongest verified result. This helps a time-poor buyer and gives search and answer systems a clear, self-contained description of the project.
[Client type] needed to [valuable change] because [recognised problem]. I led [your role and process], resulting in [design or strategic output]. The work was [implemented or adopted evidence] and [verified outcome, if available].
3. Explain the client context
Give only the background needed to understand the decision. What did the organisation sell? Who was it trying to reach? What had changed? Why did the work matter at that point? Avoid copying the client’s entire history.
4. Define the problem before the brief
A brief might ask for a new identity. The underlying problem could be inconsistent presentation after rapid growth, a proposition that buyers misunderstood or several acquired services that appeared unrelated. State which part was agreed at the start and which part emerged through diagnosis.
5. Name the constraints
Good design is judged within constraints. Record the non-negotiables that shaped the work: legacy recognition, accessibility, production limits, multiple markets, stakeholder needs, technical requirements, regulation, timing or budget. Constraints make your judgement more visible.
6. Separate your role from the team’s work
Say whether you led strategy, facilitated workshops, wrote copy, designed the identity, directed other specialists or implemented applications. Credit collaborators and client teams. Precise attribution is more credible than implying sole ownership of a shared result.
7. Show the decisions, not every step
Do not publish a chronological diary of calls, sketches and software screens. Select the moments that changed the direction. Explain the evidence considered, the alternatives, the decision and its consequence for the design.
If you want to lead this kind of work more consistently, see how to offer brand strategy as a graphic designer.
8. Connect the design response to the problem
Every image should prove a point. Explain how typography, colour, hierarchy, language, imagery, motion or system rules express the approved direction and work in the required contexts. Include captions that add information instead of repeating “logo design” or the client name.
9. Close with evidence and the next relevant step
Report what happened after delivery: launch completed, team trained, system adopted, templates used, stakeholder decision made, enquiry quality changed or a measured commercial result recorded. State the source and period when publishing a number. Then link to the service that helped create the result, not a generic contact page alone.
Use an evidence ladder instead of inventing results
Commercial metrics are valuable, but designers rarely control every factor behind revenue, conversion or growth. Use the strongest evidence available and label it accurately.
| Evidence level | What you can responsibly show |
|---|---|
| 1. Delivery | Approved strategy, completed identity, applications delivered, launch completed |
| 2. Adoption | Team training completed, templates in use, system applied across named touchpoints |
| 3. Client observation | Attributed client feedback about clarity, confidence, consistency or buying conversations |
| 4. Behaviour | Measured change in qualified enquiries, proposal acceptance, engagement or task completion |
| 5. Commercial result | Verified revenue, margin, market or conversion change with period and relevant context |
Do not turn a client comment into a universal fact. “The sales lead reported clearer conversations in the first month” is bounded evidence. “The rebrand transformed sales” needs much stronger proof.
Which images belong in a design case study?
- One context image: show the old experience or environment when permission allows.
- One decision image: use a diagram, approved principle or route comparison that reveals the thinking.
- One system image: show how the elements work together, not only an isolated logo.
- Two or three application images: choose the touchpoints most relevant to the client problem.
- One use image: show the identity implemented in the real organisation where possible.
Give files descriptive names, useful alternative text and visible captions. The page should still communicate the case without images, while the images provide evidence the text cannot.
What if the project is confidential or the client is small?
Ask for case study permission during contracting and agree any approval process. If the name is confidential, describe the organisation precisely enough to establish relevance without exposing protected details, such as “a UK compliance software company preparing for enterprise procurement”.
A small client can still demonstrate valuable capability. Relevance beats fame. A detailed case about resolving a buyer problem is more persuasive to a similar prospect than a famous logo beside work you cannot explain.
Case study SEO and generative-search checklist
- Give the page one unique URL, title, main heading and meta description.
- Use the buyer’s plain-language problem in the title, opening summary and at least one subheading.
- State the client type, sector, service, role and outcome in visible text.
- Answer likely buyer questions directly and keep each answer self-contained.
- Link from the relevant service page and to the next useful guide or offer.
- Use Article and breadcrumb structured data that matches visible page content.
- Keep dates, claims and project status accurate when the case is updated.
No markup can compensate for a thin or generic story. The useful, specific evidence is the part that makes the page worth finding and citing.
Common questions
What should a graphic design case study include?
Include the client context, problem, constraints, your role, the process, key decisions, selected design work, implementation and verified evidence. Make clear what you did, what others did and which outcomes can genuinely be attributed to the project.
How long should a design case study be?
Make it as short as possible while giving a relevant buyer enough evidence to trust your approach. A concise 600 to 1,200 word case study with a clear summary, scannable sections and purposeful images is often more useful than a long project diary.
Can I write a case study without client results?
Yes. Use the strongest evidence you actually have: approved decisions, reduced ambiguity, stakeholder alignment, successful delivery, adoption, client feedback or observed use. Label early indicators clearly and never invent performance data.
Make your strategic contribution easier to prove.
BrandOS turns approved client decisions into clear, practice-branded outputs you can use to lead the work and document how the identity was shaped.
Explore the guided process →