The panic wasn't about the presentation. It took me a while to realise that.
A designer on my team — someone I had hired nine months earlier, someone who had spent five years studying architecture before making the switch to product design — froze before a workshop where they were supposed to present their work. Not a client pitch. Not a board review. A workshop. The kind of room where there is no wrong answer, where the whole point is to think out loud together.
But they froze. Anxiety, underconfidence, a visible sense of questioning themselves — all of it present in the room before a single slide had been shown. I noticed something was off, but I didn't push on it then. I waited until we were one on one.
"I just feel like I need to perform," they said. "Like I have to prove I belong here."
The Irony of It
Here's what made this particularly striking: architects are some of the most rigorously trained presenters in any professional field. Five years of studio culture. Years of standing in front of critics — not colleagues, critics — defending every decision, every proportion, every material choice. Fielding hard questions from people whose job it is to find the weakness in your thinking. Architecture school doesn't just teach you to design. It teaches you to stand behind your design with your whole body, your whole argument, your whole self.
This was not someone who didn't know how to present. This was someone who had presented hundreds of times under far more pressure than a workshop.
So the panic wasn't about presenting. It was about something else entirely.
A Month Later
We were reflecting on their growth — one of those honest check-in conversations where you try to look at the journey, not just the deliverables. They had recently presented to a large internal group, including some of the most senior stakeholders in the firm. The subject was how they had used AI tools to build and deliver a dashboard concept in under a day. The client had been impressed. The senior stakeholders had been impressed. By any measure, it had gone well.
And yet. The same look. The same hesitation. Quieter this time — not panic, but its echo. The question still sitting underneath everything.
I asked them directly: what is it? If you've already done the thing successfully, what's still making you feel like you haven't?
The answer, when it came, was one of the most honest things anyone on my team has said to me.
"As an architect, I never feared presenting. I could do it in my sleep. I'd studied for five years — I had the foundation. But product design? I did a six-month course. I've been learning on the job. I feel like I'm still building the base, and I'm being asked to build the floors before the base is finished. How can I present with confidence when I'm not sure I've earned the right to be confident yet?"
The Whiteboard
I picked up a marker and drew three columns.
"Tell me what an architect does," I said. "Not the technical parts. The actual process of the work."
They thought about it. "You identify where the opportunity is. You research — you talk to people, you understand the site, the context, the brief, the expectations. And then you execute and communicate your ideas."
I wrote it down. Identify. Research and understand. Execute and communicate.
Then I wrote the same three things in the column next to it. Under the heading: Product Designer.
I didn't say anything. I just let them look at it.
After a moment, they smiled. Not a surprised smile — a relieved one. The kind that happens when something you already half-knew finally gets said out loud by someone else.
"There's no difference," they said.
"There's no difference," I confirmed.
What Design Actually Is
Here's the thing that the six-month course didn't teach — and couldn't teach, because it's not a thing you can put in a curriculum.
Product design is not a hard skill discipline. It is a thinking discipline. The tools change. The domain changes. The users change. The materials — whether those materials are pixels or components or satellite data or healthcare workflows — change constantly. A designer who joins a new company, a new product, a new industry is always going to be learning. That's not a gap in their foundation. That is the foundation.
Every product a designer touches requires new research, new understanding, new material knowledge. You are never going to be a hundred percent sure. You are never going to reach the point where the next problem feels fully familiar. The discipline is specifically structured to resist expertise of that kind — because if you already know the answer, you'll stop asking the question, and the question is everything.
An architect who has spent five years learning to identify problems, research deeply, and communicate ideas with clarity and conviction has not been studying architecture. They have been studying design. The medium was buildings. The discipline was the same.
This is why I have now hired two architects into product design roles. Not despite their backgrounds. Because of them.
The Real Qualification
There is a common belief in the industry — spoken quietly, believed widely — that designers who came from non-traditional backgrounds are somehow provisional. That they're working toward a legitimacy they haven't quite earned yet. That there's a moment in the future where they'll finally qualify.
That moment doesn't exist. Because the qualification was never about the degree or the years or the specific software you learned first.
Being a designer is about the way you think. The way you process information when confronted with a problem you've never seen before. The way you organise complexity into something a room full of people can understand and respond to. The way you listen to what a user can't say directly and translate it into something that helps them.
If you can do that — if you can take a messy, ambiguous problem and make it clear enough for others to act on — you are a designer. The tools are learnable. The hard skills are learnable. Figma can be learned in weeks. What cannot be learned quickly is the instinct to ask the right question before you start building. That instinct is what design school is actually trying to develop. And it can develop in architecture school, in engineering school, in a journalism degree, in five years of working in customer support, in any context where you've had to understand people and communicate clearly on their behalf.
If you can explain it, you are a designer.
A Note on Imposter Syndrome — for Everyone
I want to be clear that this isn't only a career-switcher problem. The designer who studied interaction design for four years and is now building geospatial tools for satellite data feels this. The designer who came from a strong consumer product background and just joined a healthcare company feels this. The designer who has ten years of experience but just got promoted into a leadership role feels this.
The feeling of "I don't have enough foundation" is not a sign that you lack foundation. It's a sign that you're in a discipline that will always put you in front of problems you haven't solved before. That feeling is not a warning. It is the work.
The designers who grow fastest are not the ones who feel most certain. They're the ones who get comfortable with the uncertainty fastest — who learn to present their thinking clearly even when they don't have all the answers, who learn to say "here's what I know, here's what I don't know, and here's how I'm going to find out" with the same confidence that an architect stands in front of a critic.
Presentation is not separate from design. It is design. If you have great ideas but cannot communicate them, those ideas will never reach the people they could help. Someone else will name them. Someone else will get the credit. You will remain dependent on others to give your thinking a voice — and that is a much bigger professional risk than any gap in your software skills.
If You're Reading This and Recognising Yourself
Whether you came from architecture, engineering, journalism, teaching, finance, or anything else — if you are sitting in design rooms and doing the work of identifying problems, researching deeply, and communicating ideas clearly, you are not almost a designer.
You are a designer.
The panic you feel before a presentation isn't evidence that you don't belong. It's evidence that you care about doing the work well. Channel it. Use it to prepare more thoroughly, to know your reasoning more deeply, to anticipate the questions before they're asked.
And the next time someone asks you to justify your thinking in a room full of people who seem more certain than you — remember the whiteboard. Remember the three columns. Remember that the process you've been using your whole professional life, in whatever discipline you came from, is the same process. The medium changed. The thinking didn't.
You've been a designer your whole life. You just didn't know it yet.