It didn't happen dramatically. There was no single moment where I put down my stylus and walked away. It happened the way most quiet losses happen — gradually, then all at once.
I opened my laptop one morning and scanned my tabs. Confluence. Google Docs. Sheets. Claude. A calendar full of reviews, stakeholder calls, workshops. I tried to remember the last time Figma had been one of those tabs — not to review someone else's work, but to make something myself. Something with my own hands, my own decisions, my own cursor moving across a frame.
I couldn't remember. And when I went to check, it had been more than a quarter.
That's when it hit me: I had become a designer who didn't design anymore.
The Shift Nobody Announces
Nobody tells you when you become a design leader that your software stack is going to change completely. That the tools you built your identity around — the ones you got fast in, the ones you could feel yourself thinking through — are going to be quietly replaced by a different set of tools that have nothing to do with making.
My stack now is Confluence for documentation. Google Docs for thinking out loud. Sheets for tracking. Claude and GPT for synthesising, questioning, preparing. Design thinking workshops instead of design work. A calendar structured around other people's outputs, not my own.
None of this is wrong. This is the job. Stakeholder management is the job. Systems thinking is the job. Making sure nothing breaks and nothing goes overboard — that's the job. The work of a design leader is mostly invisible work: the conversation before the meeting, the reframing that saves a project from going in the wrong direction, the question asked at the right moment that opens up a space the team didn't know existed.
But nobody tells you that invisible work feels different from making. That there's a particular kind of satisfaction that only comes from building something with your own hands — and that when it disappears from your day, you don't immediately notice. You're too busy. And then one morning you check your tabs and realise it's been three months.
The Meeting I Couldn't Show Up For
There was a specific moment where I felt this most sharply. I was in a review — stretched across multiple other projects, not close to this particular work — and my team member was presenting designs they had built. Questions started coming in from stakeholders. Hard questions. The kind that require you to defend a decision with precision.
Normally, I would have had their back. I would have known the reasoning, the alternatives considered, the user context behind each choice. I would have been able to step in, add weight to the argument, fill the gaps.
Instead, I found myself observing. Listening, yes. But not feeling the work the way I used to feel work I was close to. I had templates running in my head — the standard questions to ask, the usual things to check for — but the deeper instinct, the one that comes from immersion in the actual problem, wasn't there. I had to ask my designer to answer first, then build on what they said. In a room where I was supposed to be the most senior design voice.
I couldn't articulate why I disagreed with some of the feedback being given. I felt it — some part of me knew something was off — but I couldn't access the words. The instinct was still there. The vocabulary to defend it wasn't.
Later, I noticed something even more uncomfortable: my first instinct when I had a gap wasn't to sit with the question. It was to open Claude or ChatGPT and prompt my way to an answer. The thinking muscle I used to trust — the one built from years of doing the work — had started outsourcing its warm-up sets.
"I Just Want to Stay a Designer"
Not long after that meeting, someone on my team said something to me directly: they didn't want to move into management. They just wanted to design. They wanted to stay an IC.
My honest answer surprised even me.
I told them: I get it. I genuinely do. Management is roughly fifty percent people work and fifty percent everything else — and in that split, the hands-on craft time drops to nearly zero unless you deliberately protect it. By the time something goes wrong on a project and you need to step in, you've been out of the making for a quarter. And a quarter away from the work means your outputs, when you return to them, are going to feel rusty in ways you don't expect.
But I also told them this: people management gives you something the craft alone never could. It gives you perspective at scale. It gives you observation skills sharpened by watching other designers think. It gives you emotional intelligence — real emotional intelligence, not the kind you learn in a workshop, but the kind that comes from being in a room with someone who's frustrated or lost or trying to prove something, and figuring out what they actually need to hear.
There are boons and there are costs. The only wrong move is to pretend the costs aren't real.
What I Found Instead
I've been figuring out how to stay close to design without pretending I'm still a practitioner in the same way I was five years ago. It looks different now.
I look for problems nobody is looking at. The gaps between teams, between products, between what's being built and what users are actually experiencing. That kind of problem-finding scratches the same part of my brain that design used to scratch — the part that wants to understand something broken and figure out how to fix it.
I run workshops with my team — not to teach them what I know, but to build them past what I know. There's something clarifying about having to explain your thinking out loud to someone else. It forces you to locate the gaps in your own reasoning. I learn more in those sessions than I expected to.
And I look for the design work that hides in non-design surfaces: client proposals, RFP responses, user journey documentation, briefings. You are still a designer when you're structuring a proposal. You are still a designer when you're mapping a conversation's emotional arc. You are still a designer when you're in a room with a client and you're reading what they can't say out loud.
The medium changed. The thinking didn't.
The One Thing AI Can't Do
I want to say something about AI here, because it's impossible to talk about design identity in 2026 without talking about it.
A lot of the identity loss designers are feeling right now isn't just about moving into leadership. It's about watching AI absorb the execution layer of the work — the wireframes, the component documentation, the iteration cycles — and wondering what's left. If AI can generate a UI in seconds, what exactly are you for?
Here's what I've come to believe: AI executes what you tell it to execute. It does not know when to listen. It does not know how to listen. It cannot read the expression on a client's face when they say "yes" but mean "I'm not sure." It cannot feel the silence after a demo that tells you something didn't land. It cannot sit with a user's frustration and understand, from the texture of it, what they actually need versus what they're asking for.
Those nonverbal, non-promptable things — that's where design lives. Not in the frames. In the listening.
Which means the identity loss is real, but the identity isn't gone. It just moved. From making to seeing. From building to understanding. From executing to asking better questions than anyone else in the room.
For the Designer Who's Starting to Worry
If you're moving into leadership and you're scared of losing your design identity — that fear is worth listening to. It means you care about the craft. Don't let anyone tell you that caring about the craft is a junior designer's concern.
But also know this: you don't lose the designer. You expand around it. The skills that made you good at the work — curiosity, empathy, systems thinking, the ability to hold a problem from multiple angles — those don't disappear when you stop opening Figma every day. They show up in how you run a meeting. In how you read a room. In how you ask a question that nobody else thought to ask.
You are always going to be a designer. The problem identification, the solving, the learning — that's still entirely in your hands. What AI accelerates is the repetitive execution. What it cannot touch is the judgment that tells you what's worth building in the first place.
Keep doing your thing. You'll find your way through it. Just don't wait three months to check your tabs.