5 minutes read

How Many Projects Should a Design Portfolio Have?

The number of projects matters less than most designers think. What matters more is whether your work matches the opportunities you’re trying to attract.

four archetypes

The myth of the perfect number

Most portfolio advice starts with a number. Three projects. Five projects. Eight projects.

The problem is that hiring managers and clients are rarely counting.

What they’re really asking is much simpler: can this person do the kind of work we need?

A designer with two highly relevant projects can be a much stronger candidate than someone with ten unrelated case studies. If you’re applying for a fintech role and your portfolio shows two excellent fintech products, that may be all someone needs to see. If you’re trying to attract SaaS clients and your portfolio is full of restaurant branding projects, the issue isn’t the number of projects. It’s the lack of relevance.

The first thing people evaluate is usually the content itself. Does it feel relevant to their goals? Does it resemble the kind of work they need done? Does it give them confidence that you can deliver?

Only after that does the number of projects start to matter.


More projects can help, but only if they add something

Once you’ve established credibility, additional projects can strengthen your portfolio.

They can demonstrate range, consistency, experience across industries, or deep expertise within a specific niche.

But more isn’t automatically better.

Five projects that all tell the same story are rarely more valuable than two or three strong projects that closely match the work you’re trying to attract. The goal isn’t to hit a specific number. The goal is to build confidence.

Every project should answer a question, reinforce a strength, or make your positioning clearer.

Many designers assume they need a huge portfolio before applying for jobs or approaching clients. In reality, a small portfolio with highly relevant work can often outperform a much larger one.


Real projects vs passion projects

Designers often debate whether portfolios should contain real client work or passion projects.

The reality is that they can signal different things.

Real projects can show how you worked within real constraints, collaborated with stakeholders, handled changing requirements, and operated within a professional environment.

Passion projects can show what genuinely interests you, what you choose to work on when nobody is assigning tasks, and what you’re capable of creating when you’re free to explore ideas without external limitations.

They can also reveal parts of your personality that client work sometimes cannot. The industries, products, hobbies, or ideas you choose to spend time on often say something about who you are and what you care about.

Neither is automatically better.

A strong passion project can reveal creativity, initiative, taste, and technical ability. A strong client project can demonstrate reliability, adaptability, and experience working through practical challenges.

The question isn’t whether a project was real or fictional. The question is what it tells someone about you.


The uncomfortable truth about what hiring managers care about

A lot of portfolio advice presents hiring decisions as if they’re based on a universal checklist.

Some people will tell you hiring managers care about process.

Others will say they care about problem-solving.

Others will say they only care about outcomes.

The uncomfortable truth is that every hiring manager is different, every company is different, and every role is different.

Some people genuinely want to see detailed thinking, rationale, and process documentation.

Some people don’t care about any of that and only want evidence that you can produce strong work.

Some will focus on visual quality. Some will focus on business results. Some will focus on industry experience. Some will focus on personality and communication skills.

It can also depend on your discipline. What a product design manager is looking for may be very different from what a startup founder, creative director, marketing lead, or freelance client is looking for.

You can’t always know in advance.

That’s why chasing a single definition of the “perfect portfolio” is usually a losing game.


Build for the opportunities you want

Instead of asking how many projects should be in your portfolio, ask a different question:

Do the projects I show make me look like the right person for the opportunities I’m pursuing?

That’s usually the question that matters most.

A portfolio with a handful of highly relevant projects can outperform a portfolio with dozens of unrelated ones. Not because the number doesn’t matter at all, but because relevance almost always matters first.

The strongest portfolios are rarely the biggest.

They’re the ones that make it easy for the right client, hiring manager, or company to see themselves in the work.

Tom from Volt

Menu

Made in Framer