Joseph here.

A lot of experienced designers treat their portfolio like a gallery.

Here are the nice screens.

Here is the process.

Here is the double diamond.

Here is the timeline.

Here are the artefacts.

Then they hope the hiring manager will connect the dots.

The problem is, at senior level, the hiring manager is not only looking for craft.

They are looking for judgement.

They want to see what you owned.

What decisions you made.

What trade-offs you managed.

What changed because you were in the room.

How you influenced stakeholders.

How you handled constraints, pivots, deadlines, politics, messy teams, technical limits, and business pressure.

That is the real material.

And many designers save all of that for the interview.

They think:

“I’ll explain the stakeholder management when I speak to them.”

“I’ll talk about the trade-offs in the interview.”

“I’ll explain the business impact if they ask.”

But that is backwards.

Those things should be inside the case study because they are what help you get the interview in the first place.

Pretty screens can show craft.

A strong case study shows why you are safe to trust at the next level.

That is the difference.

This becomes even more important if you are senior, lead, staff, principal, or director level.

At that point, the question is not just:

“Can this person design?”

It becomes:

“What level of decisions can this person own?”

“What kind of risk can they manage?”

“What kind of ambiguity can they handle?”

“What kind of business problem can they help us solve?”

And this is where a lot of portfolios fall short.

Some show process, but not decisions.

Some show output, but not ownership.

Some show metrics, but not the connection between the design work and the outcome.

Some show beautiful screens, but not the level of thinking behind them.

And some have real impact buried inside the work, but the designer doesn’t know how to pull it out.

That last one is more common than people think.

A lot of experienced designers tell me:

“I don’t have metrics.”

“The project is under NDA.”

“It was a team effort.”

“The business context is too complex.”

“All my best projects are old.”

Those are real constraints.

But they are usually solvable.

You can anonymise the company.

You can mask details.

You can use percentages instead of raw numbers.

You can focus on the decision you owned.

You can explain the before and after.

You can show how your work changed time, effort, risk, conversion, adoption, retention, cost, or confidence.

And if there are no clean numbers, you can still build a defensible estimate.

That is something I help clients do with what I call impact math.

It starts with simple ingredients:

Who used the product?

How often did they use it?

How long did the old workflow take?

How long did the new workflow take after your design?

From there, we can estimate time saved, cost reduced, risk lowered, or value created.

Then we sanity-check the number so it does not sound ridiculous.

The point is not to bluff.

The point is to speak in a language hiring managers, product leaders, founders, and executives can understand.

I’ve used this kind of thinking myself when presenting work to senior leaders, including CEOs, chief digital officers, chief transformation officers, managing directors, and global bank leadership.

It is also part of how my work has ended up featured in places like Harvard Business Review and MIT Sloan.

Designers sometimes worry that talking about business impact makes the work feel less human.

I see it differently.

It helps people understand the value of the human work.

Inside The Backdoor, the first thing we fix is one core case study.

Not the entire portfolio.

One story.

We pull out the decisions, trade-offs, influence, constraints, impact, and actual level of thinking behind the work.

I’ve had clients who procrastinated on case studies for months, sometimes years.

Then in 30 to 45 minutes of guided work, we get to a clearer number, a clearer story, and a case study they can actually use in their portfolio, resume, LinkedIn, and interviews.

That first case study becomes proof.

Proof of your value.

Proof of your level.

Proof that your experience is not just “years in design,” but the ability to solve the kind of problems a company is actually hiring for.

That is what we build inside The Backdoor.

I’m taking 6 designers for the June intake.

Full details are here:

https://docs.google.com/document/d/1mci8w5E9so_a5hjT1zIqjYM6W5EKfUooGmWtaUJLe_0/preview

If this feels like the help you need, reply “I’m in” and I’ll send you the enrollment details.

Joseph