A portfolio is not a museum of everything you have ever touched. It is evidence that you can think clearly, make decisions, and produce useful work. Three strong case studies beat fifteen shallow project tiles.
Use the five-part case study
- Problem: What was broken, unclear, slow, expensive, risky, or underperforming?
- Context: What constraints mattered: timeline, team, budget, data, stakeholders?
- Approach: What options did you consider and what did you choose?
- Result: What changed because of the work?
- Learning: What would you repeat or do differently next time?
If the work is confidential, write around it
You can still show judgment without revealing private data. Replace company names with category labels. Use ranges instead of exact numbers. Blur client details. Describe the problem and decisions while keeping sensitive specifics out.
“At a B2B SaaS company, I led a pricing-page rewrite for a mid-market segment. The work required aligning sales, product, and legal around claims we could prove. The final page increased qualified demo requests by [add %].”
What each role should emphasize
- Product/design: problem framing, user evidence, decision tradeoffs, usability or business result.
- Marketing/content: audience insight, positioning, channel choice, conversion or pipeline result.
- Operations/customer success: process before and after, stakeholder alignment, time saved, quality improved.
- Data/engineering: question, model or system choice, edge cases, reliability, adoption, business impact.
- Early-career/coursework: constraints, your exact contribution, what you would improve with more time.
Your challenge
Pick one project and write 300-600 words using the five-part structure. Add one visual if it helps. End with a short line that says what this project proves about how you work.