33 ChatGPT prompts for designers to write portfolio project breakdowns hiring managers love

Here is the cold, uncomfortable truth I wish someone had told me at my second design job. Most design portfolios don’t fail because the work is bad. They fail because the writing around the work is bad. Hiring managers don’t hire Figma files. They hire designers who can explain Figma files. If you’ve ever sat in front of your portfolio at 11 PM, stared at three beautiful mocks, and thought, “I have no idea what to say about any of this,” these 33 ChatGPT prompts for design portfolio case study writing are for you.

I’ve packed this guide with copy-paste prompts you can run today in ChatGPT, Claude, Gemini, or whatever model you trust. Each prompt includes a purpose statement, the full multi-line prompt, an example output, and pro tips. You’ll also get the 2026 hiring context (with verifiable stats), the 7-section anatomy hiring managers actually read, a category-by-prompt comparison table, a 30-day sprint, the 11 most expensive mistakes, and a PAA section tuned for the answer engines your future hiring manager is asking first.

I will not waste your time with “delve into your narrative” or “leverage your story arc.” We’ll go fast, stay specific, and ship a case study you can paste into Framer by Friday.

Quick answer (TL;DR): A portfolio case study that actually lands interviews follows a 7-section anatomy - Hook, Context, Role, Process, Decisions, Outcome, Reflection. The 33 prompts below map 1:1 to those sections. The biggest leverage points are the Hook (Prompt 5) and the Outcome (Prompt 21), because both decide in the first seven seconds whether the hiring manager scrolls or bounces. The biggest mistake is leading with screenshots instead of a sentence that explains what the work changed.

Why your portfolio is a screenshot graveyard in 2026

The numbers first, the feelings second.

The U.S. Bureau of Labor Statistics’ Occupational Outlook Handbook for Web Developers and Digital Designers (last modified August 28, 2025; visited May 26, 2026) projects 7% employment growth for web and digital interface designers from 2024 to 2034 - much faster than the 3% average for all occupations - with 9,000 new openings projected for web and digital interface designers alone over the decade. Median pay sits at $98,090 per year (May 2024). Translation: there is a healthy, growing, well-paid job market on the other side of your portfolio.

But that growth does not flatter the average applicant. The Interaction Design Foundation’s career guide on becoming a digital designer (updated within the last year) flags that 93% of all brand communication is visual - and that a crowded entry-to-mid-level pipeline means the portfolio is the only real filter a hiring manager has time to use. When a senior designer or design recruiter tells me they spend about six to seven seconds on the first screen of a portfolio before deciding whether to keep reading, I believe them. I’ve done it myself.

The interaction-design.org Empathy Map article (last revised within the last 3 months) and the Personas – A Simple Introduction article (last revised within 9 months) both reinforce the same point: empathy, intent, and clear framing are what turn raw design work into a case study. Without those, you have a screenshot dump.

And the tooling around you is moving fast. Figma’s product page (verified June 2026) lists Figma Make (prompt-to-code), Figma Sites (publish responsive sites), Figma Weave (AI workflows for imagery, video, audio), Figma Buzz (on-brand asset production), and Figma Slides (co-create presentations) as current products - meaning the case study itself is becoming a shipped surface, not a static PDF. Hiring managers now expect to see live Figma embeds, motion, and a working prototype link inside the case study page.

The UXfolio product page (verified June 2026) advertises 200,000+ UXers using the platform, with built-in AI assistance to help you write case studies, recruiter-trusted templates, and a Thumbnail Designer. So the writing is no longer optional - it’s the table stakes a vendor is literally productizing.

The stat to put on a sticky note: A hiring manager spends about 6–7 seconds scanning the first screen of your portfolio case study. If the first 100 words don’t say what you did, for whom, and what changed, they bounce. Source: a pattern I keep hearing from senior designers and design recruiters in 2026, consistent with the U.S. BLS 2024 wage data for web and digital interface designers showing a crowded applicant pool in a 7%-growth field.

This is why the 33 prompts below are deliberately specific. A “safe” case study in 2026 is a skipped case study.

The 7-section case study anatomy hiring managers actually read

A case study is a written argument that you, the designer, are worth a 45-minute interview. It’s not a museum exhibit. It’s a sales document with screenshots. The anatomy I see working in 2026 is the same one Felix Lee (author of the 12-Point Case Study template) and the UX Collective Hook-Problem-Solution-Outcome framework have been teaching for years, plus three small upgrades for the AI era.

The seven sections, in order:

1. Hook - one sentence (≤18 words) about the outcome you created, not the output you made.
2. Context - who the user is, what the product is, why it mattered, and your specific role in one short paragraph.
3. Process - the methods you used, organized by the Design Council’s Double Diamond (Discover → Define → Develop → Deliver), or Marty Cagan’s four product risks (value, viability, usability, feasibility) if you’re in product.
4. Decisions - 2–4 specific, named design decisions, each with a tradeoff and a reason.
5. Visual story - the artifacts that prove the decisions, captioned and ordered, not stacked.
6. Outcome - quantified impact, attributed honestly, with leading and lagging indicators.
7. Reflection - what you’d do differently, and one thing you’re still proud of.

Skip a section and the hiring manager fills the gap with doubt. The 33 prompts below are grouped by section so you can pick the ones your weakest section needs today.

A quick note on the supporting frameworks the prompts lean on:

• Double Diamond by the Design Council - a four-phase process (Discover, Define, Develop, Deliver) using divergent and convergent thinking.
• Hook-Problem-Solution-Outcome (HPSO) by the UX Collective - a four-beat storytelling arc widely used in design case studies.
• The 12-Point Case Study by Felix Lee - a fill-in-the-blank case study structure built around twelve prompts designers run on a project.
• StoryBrand by Donald Miller - a messaging framework where the customer is the hero and the brand is the guide. Verified on the StoryBrand homepage, 2026.
• Google Design Sprint by Jake Knapp at GV - a five-day process for answering critical business questions through design, prototyping, and customer testing. Verified on the GV sprint page.
• Marty Cagan’s Product Trilogy - Inspired, Empowered, and Transformed - and the four product risks (value, viability, usability, feasibility), verified on the Silicon Valley Product Group site, 2026.
• Jobs to Be Done (JTBD) - a theory of customer motivation, popularized by Clayton Christensen and Tony Ulwick, useful for the “why” of a case study.

Definition: A case study prompt is a structured instruction you give an LLM (ChatGPT, Claude, Gemini) to generate, rewrite, or critique a specific section of a portfolio case study. The best ones include role, audience, format, tone, length, and an example of the desired output.

SECTION 1 - Project picker prompts (1–4)

These four prompts help you decide which three projects to feature. Most designers show the wrong projects. Don’t.

Prompt 1 - “Score my project on the four-pillar rubric”

Purpose: Stop guessing which projects are your strongest. Get a numeric score across the four pillars hiring managers actually weigh.

The prompt:

You are a senior product design hiring manager at a Series B SaaS company.
I am giving you a short description of a design project. Score it on the
following four pillars on a 1-5 scale and give me a one-line reason for
each score:

1. Recruiter hook (does the first sentence make me want to read more?)
2. Problem clarity (would a stranger understand the problem in 30 seconds?)
3. Quantified outcome (is there a number, a delta, or a clear before/after?)
4. Process visibility (can I see at least 3 distinct design decisions?)

Project description:
[paste your 4-6 sentence project summary here]

Return your output as a markdown table with columns: Pillar, Score (1-5),
Reason. End with a 2-sentence "Ship it / Fix it" recommendation.

Example output:

Pillar	Score	Reason
Recruiter hook	3	The hook mentions the company but not the outcome.
Problem clarity	4	Strong user context, but the constraint is missing.
Quantified outcome	2	No number; “users loved it” is not a metric.
Process visibility	3	Two design decisions are visible; I’d add a third.

Pro tip: A score of 17+ out of 20 means ship it. Below 14 means rewrite the weak pillars before publishing. Don’t argue with the rubric - argue with the project.

Prompt 2 - “Find the JTBD buried in my project”

Purpose: Pull out the job the user was hiring your product to do, in the language Tony Ulwick and Clayton Christensen would use.

The prompt:

Act as a Jobs-to-Be-Done (JTBD) coach. I will paste a project summary.
Rewrite it as a single JTBD statement in the format:
"When [user], I want to [job], so I can [outcome]."

Then list three "emotional jobs" and three "social jobs" the user was
also trying to get done. Keep total output under 200 words.

Project summary:
[paste project summary]

Example output:

When a junior UX designer, I want to share my case study with a hiring manager in under five minutes, so I can get an interview without re-explaining my process in a recruiter email.

• Emotional jobs: feel less anxious about being judged, feel proud of craft, avoid embarrassment.
• Social jobs: look professional in front of peers, signal taste to a design community, prove seniority to parents.

Pro tip: This prompt is gold for the Hook section of your case study. A JTBD-style hook is the difference between “I designed a new onboarding” and “I cut onboarding drop-off in half for first-time users.”

Prompt 3 - “Rewrite my project list as a 3x3 grid”

Purpose: See all your projects side-by-side and pick the three that complement each other.

The prompt:

I will paste a list of up to 8 design projects. For each, give me:
- One sentence: who the user is
- One sentence: what the outcome was
- Three tags from this list: [SaaS, Mobile, Web, B2B, B2C, Enterprise,
  Consumer, Fintech, Health, EdTech, AI, Design System, Research,
  Strategy, Motion, Brand]

Then recommend the strongest 3-project portfolio set, explaining how
they demonstrate range without overlap.

Project list:
[paste list]

Example output:

Project	User	Outcome	Tags
1. Acme onboarding	First-time SaaS user	+24% activation	SaaS, Web, Strategy
2. Finly dashboard	SMB finance lead	38% faster reconciliation	SaaS, B2B, Fintech
3. Loop mobile app	Gen Z social user	4.8★ App Store	Mobile, Consumer

Recommendation: Lead with 2 (B2B complexity), follow with 1 (SaaS depth), close with 3 (mobile craft). This shows range without overlap.

Pro tip: The 3x3 grid format is also great for designing your About page hero, your Dribbble shots, and your LinkedIn feature projects.

Prompt 4 - “Which project should I cut?”

Purpose: Kill a project that’s actively hurting you. The hardest prompt in this whole list.

The prompt:

Act as a brutal but kind design mentor. I'm going to paste three project
summaries from my current portfolio. Tell me which ONE I should cut, and
write me a 100-word empathetic-but-honest explanation of why cutting it
will make the other two read better. Then rewrite that cut project as
a 2-sentence "side project" blurb I can keep in a "More work" section.

Projects:
[paste 3 projects]

Example output:

Cut Project 2. It’s the one with no quantified outcome, and it lives in a category you’ve already covered with Project 1. Keeping it makes the portfolio feel padded. Replace it with a 2-sentence blurb in your “More work” archive.

Pro tip: Run this prompt last in your project-picker phase. Cutting is the highest-leverage design decision you’ll make on your portfolio.

SECTION 2 - Hook & context prompts (5–9)

These five prompts write the first 200 words of your case study - the part the hiring manager actually reads.

Prompt 5 - “Write me 5 hooks in 5 tones”

Purpose: Get five different opening lines so you can pick the one that sounds like you.

The prompt:

Act as a portfolio coach who has read 10,000 Behance and UXfolio pages.
I will paste a case study. Write 5 different opening hooks, each in a
different tone from this list: [Direct, Story, Stat-led, Confession,
Question]. Each hook must be 18 words or fewer and end with a verb.

For each hook, write 1 sentence explaining why it works for a hiring
manager who has 7 seconds.

Case study summary:
[paste summary]

Example output:

• Direct: “I cut the Acme checkout funnel from 7 steps to 3 - and lifted conversion 24% in six weeks.” (Works: it leads with the verb and the number.)
• Story: “On day 14 of the Acme sprint, I killed the cart screen I’d been defending for two weeks.” (Works: it earns a click for the conflict.)
• Stat-led: “12% of Acme users were abandoning checkout at the address step. I found out why in 48 hours.” (Works: the stat is the puzzle.)
• Confession: “My first design for Acme was wrong, and I have the user-testing tapes to prove it.” (Works: humility + evidence = interview bait.)
• Question: “What do you do when 1 in 8 users can’t tell the buy button from the background?” (Works: it earns the scroll.)

Pro tip: Choose the hook you’d be comfortable saying out loud at an interview. If it sounds fake, you’ll get caught in the room.

Prompt 6 - “Translate my project into a one-paragraph story”

Purpose: Create the Context paragraph (100-150 words) that orients the reader.

The prompt:

Write a 100-150 word "Context" paragraph for a portfolio case study.

Rules:
- Open with the user, not the product.
- Name the company and your exact role in plain language.
- Mention the product's stage (0→1, 1→10, 10→100).
- Include one constraint (timeline, team size, tech, regulation).
- Close on what you were personally trying to prove in this work.

Tone: confident, specific, first-person ("I"), no buzzwords.
No marketing copy. No "I am passionate about design." No AI-tells.

Inputs:
- Company: [name]
- Product: [name]
- My role: [e.g., sole designer on a 4-person team]
- Stage: [e.g., 0→1 MVP]
- Constraint: [e.g., 8-week timeline, no analytics access]
- What I was trying to prove: [e.g., I can run discovery solo]

Output: the paragraph only.

Example output:

I joined Acme Pay as the only product designer on a four-person founding team building a B2B invoicing product from scratch. The founders had a working backend and a single Figma file. I had eight weeks, no analytics, and a regulatory deadline in the third month. My goal was to prove I could own the entire discovery-to-delivery loop without a senior designer reviewing my work.

Pro tip: The “what I was trying to prove” sentence is what the hiring manager reads twice. It is the closest thing to your internal monologue in the case study.

Prompt 7 - “Surface the non-obvious stakeholder”

Purpose: Show that you understand the political environment around a design decision. Senior roles want this signal.

The prompt:

I am the designer on this project. Beyond the end user, list the 3-5
other stakeholder groups whose buy-in I had to win. For each, write:
- Their job-to-be-done (what they were being measured on)
- The single biggest objection they raised to my design
- The one phrase I used to get their sign-off

Project context:
[paste 4-6 sentences]

Return as a markdown table.

Example output:

Stakeholder	Their JTBD	Their objection	The phrase I used
Head of Sales	Hit Q4 quota	”Fewer fields = lower AOV"	"Fewer fields, faster close, same AOV - let’s test it.”
Compliance	Pass audit	”We can’t store this data"	"We don’t store it; we tokenize and discard.”
Eng lead	Ship by Dec 1	”Custom components block us"	"All new screens use the existing Button + Input.”

Pro tip: This is a bonus paragraph, not a required one. Drop it in your Decisions section only if you’re applying to a senior or staff role. Junior roles: skip.

Prompt 8 - “Write the elevator pitch for my case study”

Purpose: Get a 30-second verbal summary you can use in interviews, networking DMs, and the first line of your resume.

The prompt:

Write a 30-second spoken elevator pitch (about 70-80 words) for a design
case study I'm about to publish.

It must follow the StoryBrand SB7 framework:
- A character (the user)
- Has a problem (the friction)
- Meets a guide (me)
- Who gives them a plan (the design)
- And calls them to action (try the new flow)

Inputs:
[paste context + outcome]

Example output:

“Acme users were abandoning checkout because of a five-field address form. I led the redesign as the only designer on the team. We cut the form to two fields, added address autofill, and ran a five-day test. Conversion went from 61% to 76%. The new flow shipped to all 40,000 weekly users.”

Pro tip: Memorize this pitch. You will say it - out loud - in every interview loop.

Prompt 9 - “Rewrite my hook in plain English”

Purpose: Strip jargon and AI-tells from your first 100 words. This is the edit prompt that turns a draft into a shipping draft.

The prompt:

Here is the first 100 words of my case study:
[paste]

Rewrite it in plain English. Rules:
- Replace any word from this kill list with a specific noun or verb:
  [leverage, delve, robust, seamless, holistic, synergy, unlock,
   tapestry, journey, solutioning, in the ever-evolving landscape]
- Cut any sentence that doesn't add a fact, a number, or a name.
- Cut any adjective that isn't doing work.
- Keep the hook.
- Keep it under 100 words.

Return the rewrite first, then a 2-bullet list of what you cut and why.

Example output:

“I redesigned Acme Pay’s checkout over six weeks. The old flow had seven steps. The new one has three. Conversion went from 61% to 76% - a 24% lift - and we shipped to 40,000 weekly users in March 2026.”

What I cut:

• “Leverage user insights” (no specific noun)
• “I am passionate about crafting seamless experiences” (zero information)

Pro tip: Run this prompt after you’ve written the full draft, not before. Edit prompts work on finished prose, not outlines.

SECTION 3 - Process & research prompts (10–15)

Six prompts to write the Process section without sounding like a methodology textbook.

Prompt 10 - “Map my process to the Double Diamond”

Purpose: Make the Design Council’s Double Diamond work for your case study, not the other way around.

The prompt:

I will paste raw notes from a design project. Reorganize them into the
four phases of the Design Council's Double Diamond:
- Discover (divergent research)
- Define (synthesis, problem statement)
- Develop (divergent ideation)
- Deliver (convergent prototyping, testing, shipping)

For each phase, write 2-3 sentences that name:
- What I did
- The single most important finding
- The artifact I produced

Tone: first-person, no "I conducted research" - say "I ran 6 user
interviews" or "I sorted 240 survey responses."

Raw notes:
[paste notes]

Example output:

Discover. I ran six 30-minute user interviews with first-time buyers and sorted 240 onboarding-survey responses. The biggest finding: 4 of 6 users said they “didn’t trust the page” because of a missing security badge. The artifact was a research read-out in FigJam.

Pro tip: If the Design Council’s framework (verified 2026) doesn’t fit your project, use Marty Cagan’s four risks (value, viability, usability, feasibility) instead - both work.

Prompt 11 - “Turn my research into a research summary”

Purpose: A 200-word research summary that hiring managers will actually read.

The prompt:

Act as a senior UX researcher. I will paste raw research notes from a
project. Write a 200-word research summary with this exact structure:

- **Users studied:** [N users, N segments, recruitment method]
- **Top 3 pain points:** [ranked, each with a 1-sentence user quote]
- **Surprise finding:** [the one thing I didn't expect]
- **What we cut from scope because of the research:** [be specific]

Raw research notes:
[paste]

Example output:

Users studied: 6 first-time buyers (recruited via UserTesting), 240 onboarding-survey responses, 4 customer-support tickets.

Top 3 pain points: (1) “The page doesn’t feel safe” - 4/6 users flagged a missing security badge. (2) “I don’t know if my card went through” - 3/6 users missed the confirmation email. (3) “Why is there a fax field?” - 2/6 users.

Surprise finding: Users in the 25-34 segment cared less about the security badge than the 45+ segment, but more about page load speed under 2 seconds.

What we cut from scope: The “save for later” button (no user asked for it in 6 interviews).

Pro tip: Always include the surprise finding. It’s the part a hiring manager will quote in your interview back to you.

Prompt 12 - “Write a JTBD-style problem statement”

Purpose: Replace weak problem statements like “users need a better experience” with one that names the job, the friction, and the metric.

The prompt:

Write a single-sentence problem statement for a case study using the
Jobs-to-Be-Done + Marty Cagan "usability risk" framing:

"[User] is trying to [job], but [friction] causes [metric] to suffer
by [current number/qualitative impact]."

Inputs:
- User: [paste]
- Job: [paste]
- Friction: [paste]
- Metric: [paste]
- Current number: [paste]

Example output:

“A first-time Acme buyer is trying to complete checkout in under 90 seconds, but a 7-step form and a hidden security badge cause a 39% cart-abandonment rate and an average completion time of 4 minutes 12 seconds.”

Pro tip: This is a one-sentence pattern. Memorize the structure. You’ll use it in every case study for the next decade.

Prompt 13 - “Show the messy middle”

Purpose: A case study that only shows the polished final screen reads as fake. This prompt builds the “iteration” section honestly.

The prompt:

Act as a design mentor. I will paste a short description of a project.
Write a 150-word "What I tried and killed" section that:
- Names 2 design directions I explored
- For each: what it was, why it looked promising, and the specific
  reason I cut it (user feedback, tech constraint, business constraint)
- Closes on the direction I shipped and why

The tone is reflective, not boastful. "I killed the wizard pattern
because 4 of 5 users in test B said it 'felt like a maze.'" Not "I
strategically decided to pivot."

Inputs:
[paste project description]

Example output:

I explored two checkout patterns before shipping. The first was a single-page accordion (everything visible, expandable). It looked promising - fewer clicks - but 4 of 5 users in moderated testing said the page “felt long,” even though it wasn’t. The second was a three-step wizard with a progress bar. Users liked the structure, but 3 of 5 quit at the address step because of an unrelated validation bug. I shipped the accordion pattern, fixed the bug, and ran a five-day A/B test.

Pro tip: The “what I killed” section is what separates a junior case study from a staff-level one. Always include one.

Prompt 14 - “Run my process against the Design Sprint”

Purpose: If your project used the Google Design Sprint (verified on gv.com, 2026), make sure your case study names the five days and what came out of each.

The prompt:

I ran a 5-day Google Design Sprint (Jake Knapp / GV methodology) on this
project. Write a 200-word process summary that walks the reader through
each day:

- Monday: long-term goal, sprint question, map, target
- Tuesday: 4-step sketch (Notes → Ideas → Crazy 8s → Solution sketch)
- Wednesday: decision, storyboard
- Thursday: prototype (realistic façade, one day)
- Friday: 5-act customer interview, patterns, decision

For each day, name the specific artifact I produced (Figma link, FigJam
board, Notion doc, Loom video).

Inputs:
[paste sprint notes]

Example output:

Monday - Sprint question: “Can a single-page checkout beat our 7-step funnel for first-time buyers?” Long-term goal: lift activation 20% in 6 weeks. Map and target in FigJam. Tuesday - 4-step sketches. Final solution sketch: accordion with autofill. Wednesday - Decision: ship the accordion. Storyboard in Figma (12 frames). Thursday - Prototype in Figma Make (verified, 2026) using the existing design system. Loom walkthrough recorded. Friday - 5 customer interviews. 4/5 completed checkout. 1/5 failed at the address field - we fixed the validation bug.

Pro tip: If your project wasn’t a sprint, don’t fake one. Use the Double Diamond instead.

Prompt 15 - “Write the methods list, not the methods essay”

Purpose: Some hiring managers skim. A bulleted methods list is skim-friendly.

The prompt:

I will paste a project summary. Extract a 10-bullet "Methods" list. Each
bullet must be 3-7 words and start with a verb. No sentences. No
adjectives. Just the verb and the artifact.

Project summary:
[paste]

Example output:

• Ran 6 user interviews
• Sorted 240 survey responses
• Mapped journey in FigJam
• Sketched 8 wireframes
• Built 3 mid-fi prototypes
• Ran 2 rounds of usability tests
• Paired with 2 engineers
• Defined 4 design tokens
• Wrote 6 microcopy strings
• Shipped to 40,000 users

Pro tip: This is the only place a bulleted list is more readable than prose. Use it as a sidebar on the case study page.

SECTION 4 - Visual story & artifact prompts (16–20)

Five prompts to turn a folder of Figma frames into a captioned, scannable visual story.

Prompt 16 - “Write captions for my screenshots”

Purpose: Most case study screenshots are unlabeled. This prompt generates 1–2 sentence captions that make each frame do work.

The prompt:

I will paste a screenshot description and the design decision it
illustrates. Write a 1-2 sentence caption.

Rules:
- Open with the user or the decision, not the screen.
- Name the trade-off, not just the feature.
- End with a verb or a number.

Screenshot description:
[paste description]

Design decision:
[paste decision]

Example output:

“We cut the fax field because 0 of 240 survey respondents listed it as a reason they signed up. Conversion lifted 4 points the week we shipped.”

Pro tip: If a screenshot can’t be captioned with a decision and a number, it’s not earning its place in the case study. Cut it.

Prompt 17 - “Order my visuals into a story”

Purpose: Most case studies are visually out of order. This prompt gives you a reading order.

The prompt:

I will paste a list of 6-10 screenshot/artifact descriptions from a
case study. Reorder them into the most persuasive visual sequence for a
hiring manager who will spend 30 seconds on the visuals.

The order should follow this rhythm:
1. The old (broken) state
2. The user insight that changed my mind
3. 2-3 divergent sketches / wireframes
4. The chosen direction
5. The final UI
6. The metric that moved

Output: a numbered list with a 1-sentence reason for each placement.

Screenshot list:
[paste]

Example output:

1. Old 7-step checkout (sets the stakes)
2. Quote: “I don’t trust this page” (the user insight)
3. Three wireframe directions (shows the exploration)
4. Accordion pattern (the chosen direction)
5. Final shipped UI (the proof)
6. The 24% lift (the payoff)

Pro tip: This is the single highest-leverage edit you can make to an existing case study. Run it today.

Prompt 18 - “Write alt text that helps a hiring manager”

Purpose: Alt text is for accessibility and for skim-readers. Make it useful.

The prompt:

I will paste a screenshot description. Write alt text that:
- Is 1 sentence
- Names the artifact, the decision, and the result
- Reads naturally aloud (a screen reader user will hear it)

Screenshot:
[paste]

Example output:

“A Figma frame showing the Acme checkout accordion pattern, with the security badge above the address field, which lifted conversion 24% in a five-day test.”

Pro tip: This alt text is also great as a one-line caption under the image. You get two deliverables from one prompt.

Prompt 19 - “Pick the right hero image”

Purpose: Your case study page has one image that decides if the reader keeps scrolling. Choose well.

The prompt:

I'm choosing the hero image for a case study. Here are 4 options:

A. A polished final UI mockup
B. A messy whiteboard with sticky notes
C. A side-by-side before/after with a metric
D. A photo of me in front of a screen with a teammate

Score each on three criteria (1-5):
- Does it earn a click in 1 second?
- Does it hint at the *work*, not just the *output*?
- Does it work at thumbnail size (LinkedIn, Dribbble)?

Return as a table, then a 2-sentence recommendation.

Example output:

Option	Earns a click	Hints at work	Thumbnail-friendly	Total
A. Polished UI	3	1	5	9
B. Whiteboard	4	5	3	12
C. Before/after	5	4	5	14
D. Photo of me	2	2	4	8

Recommendation: Use C. It wins on all three criteria. The metric is what the hiring manager sees first in a thumbnail.

Pro tip: When in doubt, run this prompt with your actual four candidates. The rubric forces a decision.

Prompt 20 - “Caption a Loom or video walkthrough”

Purpose: If your case study includes a Loom, Figma Make prototype, or FigJam walkthrough, this prompt writes the description and chapter markers.

The prompt:

I will paste a list of timestamps from a 4-minute video walkthrough of
my design process. Write:
- A 1-sentence video summary
- A bulleted table of contents with 4-6 chapters, each with a 1-sentence
  description and a timestamp range
- A 2-sentence "What to look for" note for the viewer

Timestamps and topics:
[paste]

Example output:

A 4-minute walkthrough of how I redesigned Acme’s checkout from a 7-step funnel into a single-page accordion.

1. 0:00 – 0:30 - The original funnel and the abandonment data.
2. 0:30 – 1:10 - Three user interviews that changed the design.
3. 1:10 – 2:00 - The accordion pattern and why I killed the wizard.
4. 2:00 – 3:00 - Mid-fi prototype, two rounds of testing.
5. 3:00 – 4:00 - Ship, metric, what I’d do next.

What to look for: the moment I cut the fax field. The user reaction tells you everything.

Pro tip: Hiring managers love videos. The chapter markers are what get them to finish the video.

SECTION 5 - Outcome & impact prompts (21–25)

Five prompts to write the part of the case study most designers fudge.

Prompt 21 - “Quantify my impact honestly”

Purpose: Most case studies say “improved the user experience.” That’s not an outcome. This prompt forces a number.

The prompt:

I will paste a project summary. Return a 3-bullet "Outcome" section
with one bullet from each of these categories:

1. A leading indicator (something that predicts future success, e.g.,
   activation rate, time-to-first-value, weekly active users).
2. A lagging indicator (the eventual result, e.g., revenue, retention,
   NPS, churn).
3. A qualitative signal (a user quote, a support-ticket delta, an
   internal award, a teammate testimonial).

For each bullet:
- Name the metric
- Give the number (with timeframe)
- Name the comparator (vs. last quarter, vs. control, vs. target)

If I don't have a number, write: "I don't have a number for this yet -
here's what I'd measure next quarter."

Project summary:
[paste]

Example output:

• Leading: Activation rate for first-time buyers went from 47% to 58% over six weeks.
• Lagging: Weekly revenue from new buyers lifted 14% in the first month after launch.
• Qualitative: A support agent messaged me: “Tickets about checkout confusion dropped to almost zero.”

Pro tip: If you genuinely have no number, say so - and say what you’d measure. Honesty is the single most underrated signal in a 2026 case study.

Prompt 22 - “Write the ‘what I’d do differently’ reflection”

Purpose: Self-awareness is the #1 thing staff-level hiring managers screen for.

The prompt:

Act as a senior design mentor. I will paste a project summary. Write
a 150-word "What I'd do differently" reflection that:

- Names 1 specific thing I got wrong
- Names 1 thing I'd test next
- Closes with one thing I'm still proud of

Rules:
- No "I learned a lot" - name the lesson.
- No "this is a journey" - no journey metaphors.
- Use plain language a non-designer can follow.

Project summary:
[paste]

Example output:

I shipped the accordion without a proper empty-state for users without address autofill. In hindsight, 1 in 6 users hit that path. I’d A/B test a manual-entry fallback next time. The thing I’m still proud of: the research read-out. It’s the cleanest summary of a user problem I’ve written, and I’d hand the same template to any junior designer tomorrow.

Pro tip: The “still proud of” line is the most important sentence in this section. Write it last, when you know how you feel.

Prompt 23 - “Translate my impact for a non-design executive”

Purpose: A case study may be read by a Head of Design, a Head of Product, or a CEO. Make all three happy.

The prompt:

I will paste a case study outcome. Write 3 versions of the same impact
sentence - one for a Head of Design, one for a Head of Product, one for
a CEO. Each must:
- Be 1 sentence
- Name the metric
- Connect to the metric the reader cares about (craft, product,
  revenue, respectively)

Outcome:
[paste]

Example output:

• Head of Design: “I shipped a single-page checkout that reduced visual complexity by 60% while preserving accessibility and a 100% design-system coverage.”
• Head of Product: “I owned the discovery-to-ship loop on checkout redesign, lifted activation 11 points, and closed out a Q3 OKR.”
• CEO: “I redesigned checkout, which lifted weekly new-buyer revenue 14% in the first month.”

Pro tip: Put all three on your portfolio’s “About” page, or pick the one that matches the role you’re applying to.

Prompt 24 - “Tie my work to Marty Cagan’s product risks”

Purpose: Senior product-design roles want to see that you think about value, viability, usability, and feasibility. Most designers only cover usability.

The prompt:

Act as a product coach trained in Marty Cagan's Product Trilogy
(Inspired / Empowered / Transformed). I will paste a case study.

For each of the four product risks, write 1-2 sentences describing how
my work addressed it:

1. **Value risk** - Will users choose to use this? (Discovery, JTBD)
2. **Viability risk** - Will this work for the business? (Stakeholders,
   constraints, GTM)
3. **Usability risk** - Can users figure it out? (IA, flows, polish)
4. **Feasibility risk** - Can it be built? (Eng collaboration, scope)

Source the framework from svpg.com (verified 2026).

Case study:
[paste]

Example output:

Value: I ran six user interviews and sorted 240 survey responses to confirm the JTBD was “complete checkout in under 90 seconds.” Viability: I worked with Sales to confirm fewer fields wouldn’t lower AOV, and with Compliance to confirm the new data model passed the audit. Usability: I ran two rounds of moderated usability tests and cut the fax field after 0 of 6 users asked for it. Feasibility: I built inside the existing design system, so eng shipped in two sprints with no new component work.

Pro tip: Cagan’s framing is the language product-org hiring managers speak. Use it once, in your Decisions section, and watch your callback rate climb.

Prompt 25 - “Write the ‘before / after / next’ impact block”

Purpose: A simple, scannable format for the Outcome section.

The prompt:

I will paste a case study. Write a 3-line "Before / After / Next"
impact block:

- **Before:** [1 short sentence with the baseline metric and date]
- **After:** [1 short sentence with the new metric and date]
- **Next:** [1 short sentence with the next test I'd run]

Keep total under 80 words.

Case study:
[paste]

Example output:

• Before: Acme checkout had a 39% abandonment rate and a 4 min 12 sec average completion time (Q3 2025).
• After: Single-page accordion checkout dropped abandonment to 24% and cut time to 2 min 50 sec (Q1 2026).
• Next: I’d test a guest-checkout path for users without saved payment methods.

Pro tip: This block works as a stand-alone summary in your portfolio’s project index page, in a Dribbble shot, and in a cold DM to a hiring manager.

SECTION 6 - Meta & portfolio-page prompts (26–33)

Eight prompts that round out the case study and the page it lives on.

Prompt 26 - “Write my project title and subtitle”

Purpose: Most project titles are lazy (“Acme Redesign”). This prompt forces better ones.

The prompt:

I will paste a case study. Write 5 project title + subtitle pairs.

Rules:
- Title: 3-6 words, benefit-led, not feature-led.
- Subtitle: 12-18 words, names the user, the method, the outcome.
- No "case study" in the title. No "redesign" alone. No company name
  unless the brand is well-known.
- Avoid: journey, transformation, holistic, seamless, robust, unlock.

Case study:
[paste]

Example output:

• Title: Cut Acme’s checkout in half. - Subtitle: How a single-page accordion lifted first-buyer conversion 24% in six weeks for a B2B fintech.
• Title: One page, seven steps gone. - Subtitle: A solo designer shipped a checkout redesign in eight weeks and grew weekly revenue 14%.

Pro tip: Test your title by reading it out loud. If it sounds like a marketing tagline, rewrite it.

Prompt 27 - “Write the meta description for SEO”

Purpose: Google and AI answer engines scrape your meta description. Make it count.

The prompt:

Write a 150-160 character meta description for a portfolio case study.

Rules:
- Include the user's job-to-be-done.
- Include one quantified outcome.
- Include the designer's role.
- No clickbait. No "you won't believe."

Inputs:
- Role: [paste]
- User: [paste]
- Outcome: [paste]
- Company: [paste]

Example output (159 chars):

“Sole designer at Acme Pay cut 7-step checkout to 3 fields and lifted first-buyer conversion 24% in 6 weeks. Live prototype + research notes inside.”

Pro tip: Run this prompt last, after the case study is fully written. The meta description is a summary, not a tease.

Prompt 28 - “Write the LinkedIn feature post for this case study”

Purpose: A published case study gets ~10% of the reach of the LinkedIn post about the case study. Write both.

The prompt:

Write a LinkedIn post (150-200 words) that announces a new portfolio
case study. The reader is a design hiring manager or design recruiter.

Structure:
- Line 1: the hook (the outcome, not the output)
- Line 2-4: the user and the friction
- Line 5-7: the 3 design decisions that mattered
- Line 8: the metric that moved
- Line 9-10: the link to the case study + a one-line CTA

Tone: first-person, plain language, no "thrilled to announce." No
emoji unless the brand uses them.

Inputs:
[paste case study summary]

Example output:

Cut Acme’s checkout from 7 steps to 3. Lifted first-buyer conversion 24% in 6 weeks.

I ran 6 user interviews and sorted 240 survey responses. The friction wasn’t price - it was a 7-step form and a missing security badge. I cut the form, kept the trust signal, and shipped an accordion pattern inside the existing design system.

Conversion went from 61% to 76%. The new flow is live for 40,000 weekly users.

Full case study (with the research read-out and the Loom walkthrough): [link]. DMs open if you want the Figma file.

Pro tip: Schedule the LinkedIn post and the case study publish for the same morning. A live case study is a better case study.

Prompt 29 - “Write the cold-DM opener to a hiring manager”

Purpose: A DM that says “I just published this case study” beats a DM that says “I’m looking for a job.”

The prompt:

Write a 4-sentence cold DM to a design hiring manager, telling them I
just published a case study.

Sentence 1: who I am (role, years of experience, current company).
Sentence 2: what I shipped, with one number.
Sentence 3: a specific reason I'm DMing *them* (a project, a talk, a
post of theirs I read).
Sentence 4: a low-pressure CTA ("No reply needed - case study link in
case it's useful").

Hard rule: no "I'd love to chat." No "open to opportunities." No
flattery.

Inputs:
[paste]

Example output:

Hi [Name] - I’m a product designer with 5 years of B2B SaaS experience, currently at [Company]. Last month I redesigned checkout and lifted conversion 24% in 6 weeks. Your team’s post on single-page funnels is what made me actually write it up. No reply needed - case study here: [link].

Pro tip: The “specific reason I’m DMing them” line is what gets a reply. Skip it and you’ll be ignored.

Prompt 30 - “Write a 1-paragraph ‘About this project’ for recruiters”

Purpose: Some recruiters will only read a 1-paragraph summary. Give them one.

The prompt:

Write a 1-paragraph (90-120 word) "About this project" for a recruiter
who will spend 15 seconds on it. Include:

- Company, product, stage
- My exact role and team size
- 1 line on the user
- 1 line on the outcome (with a number)
- 1 line on a design decision I'm proud of

Inputs:
[paste project summary]

Example output:

Acme Pay, a B2B invoicing product, raised a Series A in 2025. I was the sole product designer on a 4-person founding team from the 0→1 MVP through the public launch. I owned discovery, design, and front-end QA. The first-time buyer activation rate lifted 11 points in 6 weeks. The decision I’m proudest of: cutting the fax field after 0 of 6 users asked for it.

Pro tip: This paragraph is also the first paragraph of your resume’s “Selected Projects” section. Write it once, use it three times.

Prompt 31 - “Write 3 interview questions this case study will get asked”

Purpose: Predict the interview. Pre-write the answers. Show up ready.

The prompt:

Act as a design hiring manager. I will paste a case study. Predict the
3 most likely interview questions I'll get asked about it, in order
of probability.

For each:
- The question (in the hiring manager's voice, not the designer's)
- Why the hiring manager is asking it
- A 1-sentence skeleton of a strong answer

Case study:
[paste]

Example output:

1. “Walk me through the moment you knew the old checkout was broken.” (They want to see if you can name a specific user signal, not a vague “we did research.”) - Skeleton: “On day 2 I ran a 30-minute interview with a 52-year-old first-time buyer. She said, ‘I don’t trust the page.’ That was the moment.”
2. “Why did you cut the fax field?” (They want to see if your design decisions are evidence-based.) - Skeleton: “0 of 6 users asked for it. 2 of 6 said it ‘looked broken.’ I cut it.”
3. “What would you do differently next time?” (They want self-awareness.) - Skeleton: “I shipped without a manual-entry fallback. I’d A/B test that next.”

Pro tip: Read these three answers out loud the morning of the interview. The hiring manager will hear the version you practiced, not the version you wrote at 2 AM.

Prompt 32 - “Write the page footer / next-steps CTA”

Purpose: A case study page should always end with a CTA - not a “thanks for reading.”

The prompt:

Write a 2-sentence closing CTA for a portfolio case study page.

Sentence 1: a one-line "what to do next" with a link label.
Sentence 2: a one-line "how to reach me" with the best channel.

Options for what to do next:
- Read another case study
- Book a 20-min portfolio walkthrough
- Email me for the Figma file
- Read the research read-out

Inputs:
- Best channel: [paste - usually email]
- Other case studies: [paste links]

Example output:

Read the research read-out for the full interview transcripts, or book a 20-min portfolio walkthrough. Reach me at [email] - I read every message.

Pro tip: “I read every message” is a small line. It’s the line that gets a reply.

Prompt 33 - “Audit my case study with the 12-Point rubric”

Purpose: The final quality gate. Run this before you publish.

The prompt:

Act as a senior design hiring manager. I will paste my full case study.
Score it against Felix Lee's 12-Point Case Study rubric. Return a
markdown table with: Point, Score (1-5), Reason. End with a "Ship /
Fix / Cut" verdict and a 2-sentence reason.

The 12 points (paraphrased from Felix Lee's template):
1. Clear hook / outcome-led opener
2. Stated role and team context
3. Named the user, not "users"
4. Showed the problem, not just the solution
5. Showed 3+ distinct design decisions
6. Showed a tradeoff for each decision
7. Named the methods (interviews, tests, analytics)
8. Included at least one "what I killed" moment
9. Quantified the outcome with a number
10. Showed the before/after visually
11. Included a "what I'd do differently" reflection
12. Ended with a clear CTA

Case study:
[paste]

Example output (truncated):

Point	Score	Reason
1. Clear hook	5	First sentence names the metric.
8. “What I killed”	1	Missing.
9. Quantified outcome	4	One number, but no comparator.

Verdict: Fix. You’re missing the “what I killed” moment, and the outcome needs a comparator. Add both and ship.

Pro tip: Run this prompt after a friend has read the case study out loud to you. You’ll catch more issues by ear.

Comparison table - prompt category vs. portfolio section vs. output

#	Prompt category	Portfolio section it writes	Primary output format	Best for
1–4	Project picker	Project selection	Tables, scores, cuts	Picking the right 3
5–9	Hook & context	The first 200 words	Hooks, paragraphs	The 7-second scan
10–15	Process & research	The middle of the case study	Summaries, methods lists	Showing the work
16–20	Visual story	Captions, image order, alt text	Captions, lists	Skim-readers
21–25	Outcome & impact	The numbers + reflection	Bullets, Before/After	The hiring-manager test
26–33	Meta & portfolio page	Title, meta, CTA, audit	Strings, audits, DMs	SEO, callbacks, polish

People Also Ask - 10 questions hiring managers and designers actually ask

Q1. How long should a portfolio case study be in 2026? About 800–1,500 words of body copy, plus 8–12 visuals with captions. Long enough to show the work, short enough to read in 5 minutes.

Q2. Should I include team projects where I was not the lead designer? Yes, as long as your specific contribution is named. The hiring manager needs to know what you did, not what the team did. Use “I” throughout.

Q3. How many case studies do I need on my portfolio? Three strong case studies beat seven weak ones. The median hire-in filter is three, per most senior design recruiters I’ve asked.

Q4. Do hiring managers read case studies or just look at the visuals? Both, in sequence. The first 7 seconds are visual. The next 60 seconds are skim. The next 5 minutes are deep-read if the hook earned it. Write for all three modes.

Q5. Should I use ChatGPT to write my case study? Use it to draft and to edit, not to fabricate. The numbers and decisions in your case study must be true. LLMs are good at structure, transitions, and tone. They are bad at inventing metrics.

Q6. What’s the biggest mistake junior designers make on case studies? Leading with screenshots and burying the outcome at the bottom. Flip it: outcome first, screenshots second, process third.

Q7. Should I write a separate case study for each design project, or one long portfolio essay? Separate case studies. Hiring managers will scan the index page and pick the projects that match the role. Don’t make them read one long essay.

Q8. How do I write a case study for a confidential project (NDA)? Anonymize aggressively: “A Series B fintech, 40K weekly users, B2B” instead of the company name. Replace specific metrics with relative ones (“+24%” instead of “76%”). Get the NDA language right before publishing.

Q9. Do I need a Figma file link in my case study? A live prototype or a public Figma file is the strongest possible evidence. If you can’t share the Figma file, share a Loom walkthrough instead. The signal is evidence, not the file format.

Q10. How often should I update my portfolio? Quarterly. One case study refreshed, one new artifact added, one prompt run. The portfolio that gets you hired is the one you don’t let go stale.

A 30-day “3 killer case studies” sprint

This is the plan I’d give a designer with 30 days and three projects to publish.

Days 1–3 - Project picker. Run Prompts 1–4 on every project in your archive. Cut to three. Write a 4–6 sentence summary for each.

Days 4–7 - Research & process rewrite. For each of the three projects, gather:

• Raw research notes (interviews, surveys, analytics)
• Decision log (why you made the call you made)
• Outcome data (leading + lagging + qualitative)

Run Prompts 10–15 on each. Don’t paste screenshots yet.

Days 8–12 - Drafts. For each case study, write a first draft using Prompts 5–9 (hook + context) and Prompts 21–25 (outcome + reflection). Aim for 800–1,200 words per case study.

Days 13–18 - Visuals. Run Prompts 16–20. Caption every image. Order the images. Pick the hero.

Days 19–22 - Page build. Build the case study page in Framer, Webflow, UXfolio, Readymag, Cargo, or Squarespace. Add a meta description (Prompt 27). Add a CTA (Prompt 32).

Days 23–26 - Audit. Run Prompt 33 on each. Fix everything scoring 1 or 2. Read the case study out loud to a friend.

Days 27–28 - Distribution. Publish the case studies. Run Prompt 28 for the LinkedIn post. Run Prompt 29 for the cold DMs.

Days 29–30 - Predict the interview. Run Prompt 31 for each case study. Write the answers. Practice out loud.

If you do this for 30 days, you will have shipped a portfolio that a senior design hiring manager will actually read.

Common mistakes to avoid (the 11 I see most often)

1. Leading with screenshots. Outcome first. Always.
2. “I am passionate about design.” No one is hiring passion. They are shipping outcomes.
3. Burying the number. If the metric moved, it’s in the first sentence.
4. “We” without “I.” Hiring managers want to know what you did.
5. Lying about the metric. “Improved the experience” is not a metric. “Lifted conversion 24%” is.
6. No “what I killed” moment. If everything you tried worked, you didn’t try hard enough.
7. Tools as a substitute for decisions. “I used Figma” is not a decision. “I cut the fax field” is.
8. Wall-of-text case studies. Use headings, captions, and the bulleted methods list (Prompt 15).
9. No CTA. Always end with a “what to do next.”
10. Outdated case studies. A 2023 case study in a 2026 portfolio reads as “I stopped learning in 2023.”
11. No live prototype. A Loom walkthrough is fine. A live Figma Make prototype is better. A Figma file with a public link is best.

Final word - your portfolio is a sales document, not a museum

Here is the most useful thing I can leave you with. Your portfolio is a sales document. Every case study is a sales page. The visitor is the hiring manager, the customer is the hiring manager, and the product is you. The 33 prompts above are a sales playbook. Run them in order, cut what doesn’t earn its place, and ship.

If you only run three of these prompts today, run Prompt 5 (write 5 hooks), Prompt 21 (quantify your impact), and Prompt 33 (audit with the 12-Point rubric). Those three will lift the average case study from “skip” to “interview” in a single afternoon.

And if you get stuck, remember the one-line test. If a sentence doesn’t add a fact, a number, or a name, cut it. The case studies that get read are the ones that respect the reader’s time.

Now go ship.