Portfolio: The Second Project No One Counts

Designing projects — and then designing them again

Designers don’t just design projects. At some point, we are expected to design projects about those projects.

Once the client work is finished, another kind of work quietly begins.

Less visible. Less defined. Often more demanding.

You reconstruct decisions that were made under pressure. You turn messy reality into a clean narrative. You explain things that once felt intuitive. You polish outcomes shaped by compromises no one sees.

This second project — the portfolio case — is rarely counted as work.

But it is one.

Why portfolio cases often feel harder

Client work happens in context.

There are deadlines, constraints, stakeholders, and shared responsibility.

Portfolio work happens in isolation.

You are both the designer and the client. The editor and the critic. The one who did the work — and the one who has to justify it.

There is no clear brief. No agreement on what “enough” looks like. No moment where someone tells you: this is done.

And unlike client work, portfolio work has no guaranteed outcome.

Press enter or click to view image in full size

The work behind the work

The “obvious” advice — and where it breaks

There is, of course, an obvious answer to all of this.

If you want to maximize your chances, you study the niche you’re aiming for. You learn how that industry thinks, what it values, how it talks about success. And then you build portfolio cases that match that mental model as closely as possible.

This advice is not wrong. It’s rational. It’s efficient.

And for some designers, it works. But it quietly assumes a few things.

That you already know where you belong. That your role is clearly defined. That the niche itself is stable enough to adapt to.

And that’s not always the reality.

But what if …

What if you are a generalist and your strength is not depth in a single narrow domain, but the ability to move between contexts?

What if you’re still figuring out where you fit — or shifting directions entirely?

What if the niche you’re trying to adapt to changes faster than you can realistically rebuild your portfolio for it?

At some point, “just tailor your cases” stops sounding helpful and starts sounding exhausting.

Because adaptation has a cost.

Turning lived experience into a polished story

Real projects are rarely linear.

They are full of wrong turns, partial solutions, unfinished ideas, and trade-offs.

Portfolio cases demand the opposite: clarity, confidence, coherence.

So designers rewrite history.

Not to lie — but to make the work legible. To translate lived experience into something that fits familiar structures.

Problem. Process. Solution. Impact.

What disappears in the process is often the hardest part of the work: uncertainty, doubt, negotiation, failure.

Simplifying for clarity — and simplifying for the funnel

There’s an uncomfortable distinction that rarely gets named.

Simplifying complex work so it can be understood — that’s part of good communication.

Simplifying it so it fits a hiring funnel, so it can be processed quickly, compared easily, and filtered with minimal cognitive effort — that’s something else.

At its extreme, portfolio work stops being about making your thinking clear and starts being about making decisions easier for someone else.

Sometimes, uncomfortably so.

Yes, this is efficient.

And yes, there is very little an individual designer can do to change it.

That doesn’t make it feel any less frustrating.

Unpaid, invisible, and emotionally expensive

Portfolio building is rarely acknowledged as labor.

It’s unpaid.

It’s done between jobs, after hours, or during periods of uncertainty.

It consumes time, focus, and emotional energy.

And yet, it’s treated as a prerequisite.

As something designers are simply expected to do.

Good work is no longer enough. You also have to explain it. Package it.
Re-present it — beautifully.

Effort without guarantees

What makes this second project particularly heavy is the absence of feedback and assurance.

You can spend weeks refining a case study and never know whether it helped — or hurt.

The effort exists. The thinking is there. But the outcome is often silence.

And sometimes, even a carefully crafted portfolio is not enough to convince someone else.

An open question

Portfolio work has quietly become part of the job.

A parallel track that runs alongside real projects — and sometimes overshadows them.

It raises a difficult question:

At what point did designing portfolios stop being documentation and start becoming a burden designers are simply expected to carry?