The T shaped generalist replaces the narrow specialist as the ideal team member

For most of the last two decades, the advice was clear: specialise. Go deep. Become the person who knows more about one thing than anyone else on the team. Build a reputation around a craft so narrow and so refined that nobody could question your seat at the table.

That advice made sense because execution was expensive. When building a polished interaction or writing clean production code took weeks of skilled human effort, the specialist's depth was genuinely irreplaceable. The team needed someone who could do the thing at a level nobody else could match.

But execution is getting cheaper by the month. And the bet that built an entire generation of product careers is starting to look like the wrong one.

The specialisation trap

Specialisation was a bet on execution staying expensive. That bet just lost.

When AI tools can generate a high-fidelity prototype in an afternoon, write functional code from a design spec, or synthesise forty user interviews into a pattern map, the specialist's advantage does not disappear entirely. But it narrows. The gap between what a deep specialist produces and what a competent generalist with AI tools produces has compressed in ways that would have been absurd to predict even two years ago.

I call this the specialisation trap. It is not that specialists are bad. It is that the conditions that made narrow specialisation the optimal career and team strategy have changed. The trap is continuing to invest in depth as if the economics of execution have not shifted underneath you.

But the trap has a mirror image. The generalist's advantage has widened at the same rate the specialist's has narrowed. A person who can move between research, design, prototyping, strategy, and stakeholder communication, who has deep judgment in one area but functional fluency across several, has become structurally more valuable. The handoffs between specialists were always where products lost coherence.

Every handoff is a translation. Every translation is a loss. The generalist reduces the number of translations a product has to survive.

Adobe and two kinds of contribution

At Adobe, I worked on a team that had both archetypes in sharp relief. We had a senior visual designer, one of the most talented people I have worked with, whose interface work was genuinely exceptional. Pixel-level precision. A deep understanding of typography, spacing, and visual hierarchy that bordered on instinctive. When she produced a screen, it was beautiful. There is no other word for it.

On the same team, we had a mid-level designer who was not exceptional in any single dimension. Her visual design was good but not remarkable. But she could do something the specialist could not. She could sit in a user research session in the morning, synthesise the findings over lunch, adjust the prototype by afternoon, and present a revised direction to stakeholders before the end of the day. No handoffs. No briefs. No waiting for someone else to translate her work into the next step.

The specialist produced higher-quality individual deliverables. But the generalist contributed more to the product. Her work moved faster through the system because she was the system. She did not need to wait for a researcher to interpret findings or a strategist to frame her recommendations. She held enough understanding across those domains to keep the work moving without the friction that handoffs create.

When AI tools started arriving on the team, the dynamic accelerated. The specialist's visual design advantage narrowed because AI could handle much of the execution she had previously owned. Generating layout variations, producing component states, building responsive versions of a screen. These were no longer tasks that required her specific depth. But the generalist's advantage widened because her judgment across domains was something no AI tool could replicate. The tool handled craft. She handled context.

I started thinking of this as the flex advantage. The value of being able to operate across the boundaries of your formal role, not because you are mediocre at everything, but because you are fluent enough in adjacent domains to reduce the coordination cost that specialists create.

Broadening as identity threat

A few years ago, I was mentoring a mid-career designer who was deep in interaction design. Genuinely deep. She could talk about state management, micro-interactions, and transition patterns with a precision that most of her peers could not match. But she had never touched user research. She had never been in a pricing conversation. She had never thought about how a design decision affected acquisition cost or retention metrics.

I suggested she spend six months broadening. Sit in on commercial reviews. Run a few research sessions herself instead of consuming someone else's report. She resisted, and I understood why. Her specialism was her identity. It was the thing she was known for, the source of her confidence in a room full of senior people. Broadening felt like dilution.

But six months later, her contributions in product reviews changed fundamentally. She stopped presenting interaction patterns as isolated craft decisions and started framing them in terms of what they meant for user retention, onboarding completion, and commercial conversion. She could speak to the implications of her work, not just the quality of it. The interaction design did not get worse. It got contextualised.

The broadening did not replace her depth. It gave her depth a voice. She had been producing excellent work that nobody outside the design team fully understood, because she could not translate it into the language that product managers, engineers, and commercial leads used to make decisions. Now she could.

The studio musician and the composer

There is a useful analogy from music. A session musician who plays one instrument at an extraordinary level gets hired for recording sessions. Walks in, plays the part, walks out. Valuable. But the musician who plays three instruments and can compose, who can hear what a track needs before anyone articulates it, runs the studio. The session musician waits for instructions. The composer shapes the outcome.

Product teams are filling up with session musicians. But the teams that ship coherent products, the ones where the output feels like a single mind designed it rather than a committee of departments, are led by people who can see across the full arc of the work.

That does not mean depth is irrelevant. A generalist without depth is just someone with opinions about everything and mastery of nothing. The T-shape matters because the vertical bar, the area of genuine expertise, is what gives the horizontal bar credibility. But the horizontal bar is what gives the vertical bar relevance.

What the bet actually was

The question is not whether specialists still have value. They do. The question is whether building a team primarily around narrow specialists, each handing off to the next, is still the optimal structure. Increasingly, it is not.

But AI is collapsing the cost of execution across domains. What remains expensive is judgment: knowing what to build, knowing when to stop, knowing how a design decision ripples through revenue, retention, and user trust. That kind of judgment does not live in a single discipline. It lives in the spaces between disciplines, in the person who has spent enough time in adjacent domains to see what the specialist, by definition, cannot.

The mid-career designer I mentored did not become less of a specialist. She became a specialist whose work mattered more, because she could connect it to the outcomes the organisation was actually measuring. That is not dilution. That is completion.

The specialist who only speaks one language will always need a translator in the room. The generalist who speaks three will sometimes be the one who decides what gets said.