One designer ran her portfolio yesterday.

Got BORDERLINE.

She replied:

"The areas around ownership language were fascinating."

She saw it immediately in her case studies.

"We improved the checkout flow."

"We increased conversion."

"We redesigned the onboarding."

All true.

But incomplete.

Here's why "we" language kills senior portfolios.

When I hired three designers in 2021, I was hiring for different roles.

Junior designer.

Senior designer.

Lead designer.

Each required different signals.

For the junior role, "we" was fine.

"We collaborated on the design system."

"We shipped the new dashboard."

Perfect.

That's what I wanted to see.

Team participation.

Learning.

Contribution.

For the senior and lead roles?

"We" was deadly.

Because I wasn't hiring participants.

I was hiring owners.

Let me show you the difference.

Junior version:

"We redesigned the checkout flow to reduce friction."

What this tells me:

- They were on a team

- They contributed to something

- Something got better

What it doesn't tell me:

- What they owned

- What they decided

- How they navigated constraints

- What tradeoffs they made

Senior version:

"Checkout abandonment hit 42%. Leadership approved $200K for full redesign. I proposed running A/B tests first - remove guest checkout requirements, keep existing flow. Abandonment dropped to 28% in 3 weeks. Saved $180K, bought 6 months to plan proper rebuild."

What this tells me:

- They owned the metric (42% abandonment)

- They made a decision (test before rebuild)

- They navigated constraint (budget, timeline)

- They managed tradeoff (quick win vs long-term fix)

- They delivered outcome (28%, $180K saved, 6 months)

That's 4 sentences.

All six hiring lenses visible:

1. Role fit (Senior IC, product decision-maker)

2. Relevance (e-commerce checkout)

3. Impact (42% → 28%, $180K saved)

4. Judgment (test before commit)

5. Influence (convinced leadership to change approach)

6. Low risk (delivered fast, managed budget)

Most case studies?

12 pages.

Zero ownership.

Process documentation from start to finish:

- Research phase

- Stakeholder interviews

- Competitive analysis

- User testing rounds

- Design iterations

- Developer handoff

That's method.

Not judgment.

Hiring managers don't care about your process.

They care about your decisions.

What did you personally own?

What problem were you solving?

What constraints forced your hand?

What did you choose and why?

What did you cut?

What worked?

What didn't?

These questions reveal judgment.

Process reveals compliance.

When you write "we," you hide accountability.

And senior roles require accountability.

Not "we achieved X."

But "I owned X, decided Y, delivered Z."

This doesn't mean taking credit for team work.

It means showing what you personally drove.

Example:

"I led a team of 3 designers and 2 researchers to redesign the dashboard. My responsibility was conversion optimization. I proposed adding social proof at checkout based on user testing showing trust issues. Conversion increased 18% in first month."

That shows:

- Team context (led 3 designers, 2 researchers)

- Personal ownership (conversion optimization)

- Decision made (social proof based on trust data)

- Outcome (18% increase)

You're not erasing the team.

You're showing what you owned within it.

This is the shift that unlocks senior roles.

From participant to owner.

The GPT catches this in Lens 4: Judgment, Ownership & Slope.

It's the lens most designers fail.

Not because they lack judgment.

Because they hide it behind "we."

Run yours:

https://sendfox.com/lp/m52q0x

Then look at your Lens 4 assessment.

If it flagged ownership language, now you know why.

Share your verdict below if you want.

Especially if you got flagged on Lens 4.

Curious how common this is.