The work that doesn't show in the Portfolio

My third year working in product design, I believed something that I now recognise as both understandable and quietly destructive: that good work would win.

Not that politics didn't exist. I could see it. But I believed it was a separate track from the design work itself. You did the research. You ran the workshops. You built the prototypes, tested them, iterated, arrived at a solution that genuinely served the user better than what existed before. And then the quality of that solution would carry it through the organisation, past the competing priorities and the executive who had a different opinion and the PM who was attached to a feature that the research had just undermined.

The solution would win because it was better.

I was wrong about this more often than I was right.

The State of UX report that came out this year named something that most senior designers have known for a long time but rarely say plainly: designers are spending a significant portion of their working time on stakeholder alignment, internal negotiation, and the management of organisational dynamics. Not on design. On the conditions required for design to happen at all.

The framing in the report treated this as a problem to be solved. Which it partly is. But it is also simply the reality of how consequential design gets done inside organisations of any complexity.

The question is not how to eliminate politics from the design process. But the question of whether you treat political competence as a design skill or as a compromise of your professional identity matters enormously. The answer shapes your career in ways that craft alone cannot.

I spent too many years choosing the second option. It cost me influence I could have used to do better work.

The moment I remember most clearly came at a large enterprise, about four years into my career. I had been leading a redesign of a core workflow that was genuinely broken. The user research was unambiguous. The current flow required seven steps for a task that could be accomplished in three. Users were abandoning it at step four and finding workarounds that created downstream problems for the entire system.

The solution was not complicated. We had tested it. It worked. Three steps, clear labels, half the time.

But in the review meeting, a senior leader who had not been involved in the research asked why we were changing something that had been in the product for six years. It was not a hostile question. He just did not have the context. And I did not have the relationship with him that would have allowed me to answer it in a way that landed.

The redesign got delayed for two quarters while we built the context I should have built before that meeting.

Two quarters. For a fix that was ready in three weeks. But the delay was not his fault. It was a failure of preparation on my part, framed as resistance from the organisation.

What I learned slowly, and mostly through failure, is that organisational influence is a design problem in the same way that user experience is a design problem. It has stakeholders with different mental models and competing needs. It requires research into what people believe, not just what they say. It demands iteration, because the first framing rarely lands perfectly. And it has failure modes: move too fast and you lose people, move too slowly and the window closes.

The designers who navigate this well are not better politicians in the pejorative sense. They are better system thinkers. They have mapped the organisation the way they would map a user journey. They know where the decision points are, who owns each one, what each stakeholder's version of success looks like, and which conversations need to happen before the review meeting, not inside it.

This is not a natural talent. It is a learnable skill. But most design education does not teach it, and most design career conversations do not name it as something to develop deliberately. Which means most designers learn it the same way I did: by watching good work get delayed, diluted, or killed, and eventually asking why.

The portfolio problem is real. Everything that matters about political competence is invisible in a case study. You cannot show the coffee conversation that changed a stakeholder's framing two weeks before the presentation. You cannot show the six emails you sent to build a coalition before the roadmap review. You cannot show the moment you decided not to present a solution in a meeting because the room was not ready for it yet.

But those decisions are often what determined whether the work got to ship at all.

The work that shows in the portfolio is the work that survived the organisation. But what the portfolio cannot show is the designer's role in making that survival possible. And in most hiring conversations, that role goes entirely undiscussed.

I still believe good design should win on its merits. But I no longer believe it wins automatically. And the gap between those two sentences is where most designers lose years they cannot get back.

The merit has to be legible. The room has to be ready. And making the room ready is part of the job, whether it appears in the job description or not.