PORTFOLIO POSITIONING
He thought he had a case-study problem.
The bigger problem was positioning.
A design-system story was hiding a broader organizational-change story.
CLIENT Senior Product Designer · CHALLENGE Portfolio positioning · FOCUS Case-study rewrite · COLLABORATION Two revisions over one week
Quentin had more than 15 years of product design experience across SaaS, design systems, and complex product environments. After more than a year of searching, hundreds of applications, and dozens of interviews, he still had no offer. He had also received plenty of portfolio feedback—and much of it conflicted.
The difficulty was deciding which story the portfolio needed to tell.
My first job wasn’t to rewrite everything. It was to figure out what was actually being undersold.
The visible problems were real. They just weren’t the main problem.
Quentin’s concerns were understandable: too much text, visuals that weren’t carrying enough of the story, sections that were difficult to order, and pressure to demonstrate AI experience in a project that wasn’t fundamentally about AI.
Those were presentation problems. The bigger issue was how the work positioned him.
What the portfolio emphasized
Design system · Components · Implementation
What the project also demonstrated
Organizational problem-solving · Executive buy-in · Cross-functional alignment · Adoption · Systems-level change
Seen narrowly, the case study looked like a component and implementation story. Seen at the level of the problem Quentin recognized, it showed work across teams, decisions, and ways of working.
The portfolio was describing the artifact. The stronger story was the organizational change Quentin was leading around it.
We changed where the story started.
Before: The story began with the design system and what Quentin built.
After: The rewritten story began with the organizational problem, why it mattered, Quentin’s role, and the cross-functional change required.
Rather than introducing the artifact first, the rewrite established the organizational problem Quentin was responsible for solving. The design system no longer had to carry the whole meaning of the project on its own.
The solution didn’t become more impressive. The reader finally understood why it mattered.
The strongest part wasn’t only what he built. It was getting people behind it.
Once the reader understood the problem first, the design system became evidence of Quentin’s response rather than the definition of the project.
The new structure brought scattered signals into one coherent account. Quentin had identified the problem, secured buy-in, aligned people across product, design, and engineering, driven the initiative, helped create shared ownership, and supported adoption.
A design-system deliverable can sound like execution work. Adoption reveals the organizational work around it: bringing people into the decisions, creating advocates, and establishing a shared way to move work forward.
Building the system was only part of the story. Getting people to work differently around it was the more revealing signal.
The numbers didn’t change. Their meaning did.
The rewrite did not increase the numbers. It established Quentin’s decisions, ownership, and organizational context first, making the outcomes easier to interpret. Rather than appearing as isolated figures, they now had context for how Quentin’s work contributed to them.
Strong positioning did not require turning contribution into sole credit. It required giving supported outcomes the context they had been missing.
Quentin’s reflection
“I didn’t realize how much I did until I framed the problem and solutions correctly. I first thought I simply suggested a small change but in reality I initiated and led the transformation of a large company delivery system.”
Nick did not manufacture a bigger story. The process helped Quentin recognize the scope he had already owned. The work didn’t become more senior. His understanding of what the work demonstrated became clearer.
Months later, Quentin checked back in.
Months later, Quentin told me he had found a Design Ops role at Schneider.
“Positioning was the main issue.”
I can’t claim a portfolio rewrite caused a job offer. Hiring is more complicated than that. What stood out was that Quentin’s later reflection echoed the diagnosis we had worked through together: the experience was there. How that experience was positioned was what needed to change.
His portfolio project contained substantial organizational-change and systems-level work, and he later found a Design Ops role. The connection is worth noticing, but it is not evidence that the rewrite caused the role or determined the hiring decision.
Sometimes your portfolio isn’t underselling the quality of your work. It’s underselling what kind of work you actually do.
Quentin’s project was not only a design-system story. It also demonstrated organizational change, adoption, cross-functional alignment, systems thinking, initiative, and broader operational impact. The portfolio became stronger when the story was told at that level.
That is the value of positioning diagnosis. It identifies the category of work the portfolio should make visible—not merely the sentences that need cleaning up.
Great portfolios don’t exaggerate experience. They make the right experience easier to recognize.
Explore another transformation
Amandeep Singh — Strong research became a clearer portfolio story. →
Pets at Home — A screen-led process became a decision-led story. →
Think your portfolio is underselling your work?
UX Portfolio Rewrite
I help you figure out what your portfolio should actually say, then write it.