ThinkWithPrompt by SynotticThinkWithPrompt

Write a UX case study for my design portfolio

Turns a past project into a scannable portfolio case study that shows your process, decisions, and impact, not just final screens.

Career & Job SearchFew-ShotStandardDesignWriteResearchFill-in Template

The prompt

Help me write a UX case study for my portfolio. Project: [PRODUCT, TEAM, TIMEFRAME] My role and what I personally did: [BE SPECIFIC - versus what the team did] The problem and why it mattered: [USER AND BUSINESS PROBLEM] Process: [RESEARCH, IDEATION, TESTING, ITERATIONS - what actually happened] Key decisions and what changed my mind: [2-3 MOMENTS] Constraints: [TIME, TECH, STAKEHOLDERS] Outcome: [RESULTS, METRICS, FEEDBACK - only real ones; or "not measured"] What I would do differently: [HONEST REFLECTION] Confidentiality limits: [WHAT I CANNOT SHOW OR NAME] Target roles: [e.g. senior product designer at B2B SaaS] Write: 1. A title and a one-line summary (problem, my role, result). 2. A TL;DR box for skimmers: role, team, timeline, outcome. 3. Sections: Problem, Approach, Key decisions (with the alternatives I rejected), Outcome, Reflection. Use first person for my work, "we" for team work. 4. Suggested visuals per section (e.g. before/after, journey map, test clip) and short captions. Rules: about 600-900 words; show judgment and trade-offs, not a generic double-diamond recital; never invent or inflate metrics - use [ADD METRIC] or describe qualitative impact; respect my confidentiality limits. Finally, give me 3 likely interview questions about this project.

Highlighted [brackets] are blanks to replace with your own details.

Fill in the blanks and use this promptMore Career & Job Search prompts

What to fill in

  • PRODUCT, TEAM, TIMEFRAME
  • BE SPECIFIC - versus what the team did
  • USER AND BUSINESS PROBLEM
  • TIME, TECH, STAKEHOLDERS
  • HONEST REFLECTION
  • WHAT I CANNOT SHOW OR NAME
  • e.g. senior product designer at B2B SaaS
  • ADD METRIC

How this prompt is built

This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.

Related prompts

Find more prompts like this