What should I call myself in 2026?

A few years ago, if someone asked what I do, I would say product designer. It was close enough. People understood it. It put me in the right category.

It does not work anymore. Not because I stopped designing. I still design every day. But the work I actually do has not fit inside that label for a long time. And in 2026, it fits less than ever.

Here is what a typical week looks like. I review a product strategy with a founder. I redesign a key workflow. I write initiative documentation. I prep tickets for a sprint. I challenge an architecture decision. I test a shipped feature on a physical device. I sit in a stakeholder meeting and help the room decide what to build next. I prototype something in code to prove a point faster than a mockup would.

Which title covers that? Product designer does not. Product manager does not. Design lead does not. None of them do, because each one implies a boundary that the work itself ignores.

This is not new for me. I have been working across these boundaries for close to twenty years. What is new is that the boundaries themselves are disappearing for everyone.

When the handoffs disappear

AI made it possible for a designer to build functional prototypes without an engineer. It made it possible for a product manager to generate research synthesis in hours instead of weeks. It made it possible for a single person to cover ground that used to require a team of specialists working in sequence.

The disciplines did not merge because someone decided they should. They merged because the tools made the handoffs unnecessary.

When the handoffs disappear, the job descriptions built around them stop making sense. This creates a real problem, not just a semantic one. When a founder needs someone to help shape a product, they open a job board and see: product manager, UX designer, product designer, design lead, UX researcher, product strategist. These are all real roles. But none of them describe the person who does all of it as a single engagement, adapting to what the situation requires on any given day.

So the founder either hires three people when they need one, or hires one person under the wrong title and spends months realigning expectations.

Specialisation still matters

I think specialisation still matters. Someone who is deeply skilled at interaction design, or user research, or data modelling, will always be necessary. The shift is not that specialisation is dead. The shift is that more and more product situations require a person who can move between strategy, design, and delivery without stopping to hand things off.

There is no established title for that. "Full-stack designer" sounds like a frontend developer. "Product generalist" sounds junior. "Fractional CPO" sounds like you are selling a title, not a contribution.

I landed on "Product and Design Partner." It is not perfect. But it does something the other titles do not. It signals that the engagement is collaborative, not transactional. That the scope is the product, not a deliverable. And that the person across the table is a partner in the work, not a vendor executing a brief.

I am not especially attached to the words. If something better comes along, I will use it. But the underlying shift is real: the most useful people in product work right now are the ones who refuse to stay inside a single job description. Not because they are unfocused. Because the work demands it.

The titles will catch up eventually. They always do. In the meantime, the clearest thing I can say is this: I help teams build better products, and I do whatever that requires.