The hardest part of building a portfolio isn't the design. It's deciding what to put in it.
Include too much, and you overwhelm people. Include too little, and you seem inexperienced. Choose the wrong projects, and you attract the wrong opportunities.
This guide will help you make those decisions with confidence.
The quality over quantity principle
Here's the counterintuitive truth: fewer projects usually means a stronger portfolio.
When you show everything, you're asking visitors to do the work of figuring out what you're good at. Most won't bother. They'll skim, get confused, and leave.
When you curate ruthlessly, you control the narrative. Every project reinforces the same message: "This is what I do, and I do it well."
The ideal number: 3-5 projects.
That's enough to show range and depth without overwhelming anyone. If you have more than five strong pieces, pick the five that best represent where you want to go—not just where you've been.
How to choose which projects to include
Not all projects deserve a spot in your portfolio. Use these filters:
Filter 1: Would you want more work like this?
Your portfolio attracts similar opportunities. If you include a project you hated, you'll get more projects like it.
Only show work you'd be excited to do again.
Filter 2: Can you explain your contribution?
If the project was a team effort (most are), be clear about what you specifically did. "I worked on this" isn't enough.
If you can't articulate your role, either figure it out or leave the project out.
Filter 3: Does it show something the others don't?
Each project should pull its weight. If two projects demonstrate the same skill, keep the stronger one.
Look for variety in:
- Type of work (strategy, execution, research, design, development)
- Context (client work, side project, full-time role, freelance)
- Outcome (launched product, increased metrics, solved problem)
Filter 4: Is it recent enough?
Old work can undermine you. If your best project is from five years ago, people will wonder what you've been doing since.
Aim for at least one project from the last 12-18 months. If you don't have recent work you're proud of, make something.
Writing project descriptions that convert
A good project description does three things:
- Establishes context quickly
- Shows your thinking and process
- Demonstrates impact or outcome
Here's a simple structure that works:
The challenge
What problem were you solving? What constraints existed? Set the scene in 1-2 sentences.
"The checkout flow had a 67% abandonment rate. The team had three weeks to ship improvements before the holiday rush."
Your role
What specifically did you do? Be precise. Avoid vague phrases like "collaborated with" or "helped develop."
"I led the UX research—five user interviews, a competitive audit, and a review of session recordings. Then I designed and prototyped three concepts for the team to evaluate."
The approach
This is where you show your thinking. What decisions did you make? What trade-offs did you navigate? Why did you choose this path over others?
"We prioritised reducing form fields over adding trust signals. Testing showed users were confident about security but exhausted by the number of steps."
The outcome
Numbers are powerful here, but qualitative impact counts too.
"Abandonment dropped to 41%—a 26-point improvement. The changes shipped two days early."
Keep the whole description under 200 words. If people want more detail, they can ask in the interview.
Supporting content: beyond projects
Projects are the core of your portfolio, but they're not the whole thing. Consider adding:
An "About" section
Who you are, what you do, what you're looking for. Three sentences is plenty.
Write in first person. Sound like yourself. Skip the corporate buzzwords.
A skills list (maybe)
Skills lists can feel generic, but they help with searchability. If you include one:
- Be specific ("React, TypeScript, GraphQL" not "web development")
- Only list skills you'd be comfortable discussing in depth
- Skip obvious ones (Microsoft Office, "communication")
Testimonials (if you have them)
A sentence or two from a client, colleague, or manager can build trust quickly. Make sure they're specific.
"She turned a vague brief into a product our users actually love" is better than "Great to work with."
Contact information
Make it impossible to miss. Email in the header, footer, and About section. People should never have to hunt.
What to leave out
Just as important as what you include:
Old work you've outgrown. If it doesn't represent your current skill level, it's working against you.
Projects you can't discuss. If an NDA or your memory prevents you from explaining the work, skip it.
Everything you've ever done. Your portfolio isn't a CV. It's a highlight reel.
Lengthy company descriptions. People can Google "what does Acme Corp do" if they care.
Filler projects. No weak pieces to round out the numbers. Three strong projects beats five mediocre ones.
Keeping your portfolio current
A portfolio isn't a one-time project. It needs maintenance.
Set a reminder every quarter to:
- Add recent work
- Remove anything that no longer represents you
- Update your About section if your focus has shifted
- Check that all links still work
Twenty minutes every few months is enough to keep things fresh.
Getting started
If you're staring at a blank page, here's your next step:
- List every project you're proud of
- Apply the four filters above
- Pick your top 3-5
- Write one description using the structure provided
- Then do the next one
You don't need to finish in a day. Progress beats perfection.
Or, if you want to skip the blank page entirely, try Curvit. Upload your CV and get a portfolio structure in seconds. Then refine from there.
Your work deserves to be seen. A thoughtful portfolio makes sure it is.