The missing piece in your portfolio

A few months ago I was working with a mid-level designer on his portfolio.

He had great work and his case studies were well structured. But something was missing from every project- there were no results. No data points. No evidence of impact. Nothing that connected his design decisions to what happened after the work shipped.

I asked him: what changed after this launched?

He took a minute then answered "well the new platform workflow I designed actually saved the team a significant amount of time every week. But I didn't think that was worth mentioning."

Think about it.

He had delivered a measurable business outcome 'time saved'. In any organization this directly translates to money saved and he decided it wasn't worth including in his portfolio.

This is not an unusual. It's something I see all the time.

Why designers miss their own impact

There are two reasons mid-level designers struggle to demonstrate business impact in their portfolios.

The first is access. This is the most common and one that I often struggled with. The PM has the data. The analytics team tracked it. The client got the report.

But then, the designer moves to the next project without ever connecting their work to its outcome.

And that's the second problem.

Designers who don't think of themselves as business partners don't ask for the data. They hand off the work and consider their job done.

Gaining access is a real challenge, but theres a more important mindset gap: most mid-level designers don't yet think of their design decisions as business decisions.

They should.

Every design decision you make has a business outcome:

A simplified onboarding flow reduces drop-off
A clearer IA reduces support tickets
A faster checkout flow improves conversion
A redesigned internal tool saves the team time- which saves the company money

You don't need a ton of metrics to show impact. You just need to start thinking about your work the way a hiring manager thinks about it.

What business impact actually looks like

Business impact doesn't always need to show a large amount of data points.

Here's what business impact looks like in a mid-level portfolio:

• "The redesigned workflow reduced the average task completion time from 12 minutes to 4 minutes."

• "User testing showed 4 out of 5 participants completed onboarding without assistance, compared to 2 out of 5 in the previous version."

• "The new design system reduced the time designers spent on production work by approximately 30% freeing the team to focus on higher-value problems."

• "Following launch the NPS score for this feature increased from 24 to 41 over the first quarter."

Not one of these required access to a company analytics dashboard. All of them required the designer to ask what changed because of my work?

Saving time is a business outcome.
Reducing confusion is a business outcome.
Improving a score is a business outcome.
Making a process easier for an internal team is a business outcome.

Ask yourself this one question

Go back to one project in your portfolio and ask:

What would have been harder, slower, more expensive, or more frustrating without my work?

That answer is your business impact. Write it down.

Then add it to your case study.

If you want help identifying and articulating the impact hiding in your existing case studies that's one of the things I look at directly in a portfolio review (video audit). I'll show you specifically where your business outcomes are buried and how to surface them before your next application.

→ Book your portfolio review — $95 "My callback rate doubled after Anthony's audit."

Talk soon, Anthony

P.S. I've been working on something for the past few weeks, a guide targeted for mid-level designers on how to reframe your existing case studies so hiring managers see exactly the level you're working at. More on that soon.