top of page

Nobody Told Me This When I Started in Design

  • 8 hours ago
  • 6 min read

Nobody sits you down at the start of a design career and gives you the honest version. You get the technical stuff, the software tutorials, the design principles, the portfolio advice. What you don't get is someone pulling you aside and saying, look, here's what this actually feels like, and here's what to do about it.


So consider this that conversation.


I'm writing this for two groups of people. Those just starting out, finding their feet in their first studio or agency role, wondering quietly whether they're good enough to be there. And those a few years in, who've hit a wall they can't quite name, feeling frustrated or stuck or somehow invisible in rooms they've been sitting in for years. Both groups have more in common than they realise.


The Thing Nobody Admits Out Loud

Let's start with imposter syndrome, because almost everyone in design has it and almost nobody talks about it properly.


It's that persistent, low-level anxiety that you've somehow blagged your way into the room and someone is about to notice. That your ideas aren't as good as everyone else's. That you're the weak link. That the person next to you has it figured out and you're the only one holding a map upside down.


Here's what I can tell you from experience: you are almost certainly not the only one feeling it. The design industry is full of talented people who spend a significant amount of energy convincing themselves they don't belong. Some of them are very senior. Some of them have won awards. I'll be straight with you, after twenty years in this industry, I still feel it from time to time. It doesn't discriminate, and it doesn't necessarily go away on its own.


It's worth noting that for some designers, this feeling runs deeper than a confidence wobble. Neurodivergent designers in particular, and there are a lot of us in this industry, often carry an additional layer of it. A sense of operating slightly differently to everyone else, without always knowing why. But that's a thread for another article. The point here is that whether it stems from inexperience, background, or simply how your brain works, the feeling is common, it's valid, and it is not an accurate measure of your ability.


Staying Quiet Feels Safe. It Isn't.

Early in my career I stayed quiet a lot. In client meetings, in crits, in conversations with senior colleagues. I didn't ask questions I needed to ask, because I was afraid of looking like I didn't know something. I didn't push back on briefs that didn't make sense, because who was I to question someone more experienced? I sat on frustrations rather than voicing them, because raising something felt riskier than absorbing it.


What I didn't understand then is that staying quiet has its own costs, and they compound.


Isolation is the first one. When you don't speak up, you don't connect. You become someone who nods and delivers rather than someone who contributes and belongs. That's a lonely place to work from, and it's self-reinforcing. The longer you stay quiet, the harder it becomes to find your voice.


Self-doubt is the second. Silence gives your anxieties room to grow unchecked. Every unanswered question becomes evidence that you don't know enough. Every frustration you absorb becomes proof that something is wrong, either with the project or with you. Neither of those conclusions is usually accurate, but without communication to reality-check them, they solidify.


Frustration is the third. And this one tends to be the one that eventually breaks things, either the project, the relationship, or your enthusiasm for the job altogether.

The antidote to all three is the same thing: open communication. Which sounds obvious when you write it down, and is genuinely hard to do when you're sat in a room feeling like the least qualified person at the table.


The Client That Proved It

After years of gradually building confidence, finding my voice in rooms, and developing a way of working that felt honest, it was one particular project that showed me just how much that approach could change an outcome.


Working with the London Stock Exchange, on the Refinitiv engagement, the stakes were high and the expectations weren't always clear. By that point in my career I had enough belief in my approach to bring the client and key stakeholders into the process properly. Not just at review stages, but throughout. Building a genuine rapport, checking in regularly, asking questions, and being honest about where things were going well and where they weren't.


I was even honest about previous failings on our side. Not in a self-flagellating way, but in the way you'd talk to someone you trusted. Here's what went wrong before, here's what we're doing differently, here's where I need your input.


We had a real problem on our hands, and there was a genuine risk this relationship wasn't going to survive it. What turned it around wasn't a slick presentation or a redesigned proposal. It was choosing to be honest, working through it together, and actually listening to what the client needed rather than assuming we already knew.


And that last part matters more than most designers give it credit for. Not just hearing, but genuinely listening. Active, focused, unhurried listening. It's what builds trust in a room. It's what surfaces the things a client hasn't quite found the words for yet. It's what turns a brief from a document into a conversation, and a conversation into the kind of working relationship where good work actually gets made. The questions worth asking almost always come from listening properly first.


The result was one of the most successful projects I've worked on, professionally and personally. A business relationship that was destined to fail became one of the strongest I've had. Not because the work was perfect, but because the relationship was built on something real. Trust, earned through honesty rather than performance.


That project confirmed something I'd been learning slowly for years: confidence doesn't mean having all the answers. It means being honest about what you know, what you don't, and what you need. Clients and stakeholders respond to that far better than polished certainty that falls apart under scrutiny.


Questions Are Not a Weakness

One of the most damaging myths in design, and in professional life generally, is that asking questions signals a lack of knowledge. It doesn't. It signals engagement, intellectual honesty, and the self-awareness to know that understanding something properly is worth more than appearing to already know it.


The designers I've seen struggle most over time are not the ones who asked too many questions early on. They're the ones who didn't ask enough, made assumptions, and built on shaky foundations for years.


Ask the obvious question. Ask the one you think you should already know the answer to. Ask it in the client meeting, in the team standup, in the crit. Nine times out of ten, someone else in the room wanted to ask the same thing and didn't.


And when someone shoots you down for asking, which occasionally does happen, that tells you something useful about the environment you're working in, not something true about you.


Questioning Up is Part of the Job

This one takes longer to learn, and it matters enormously.


Questioning your manager, your creative director, or your client is not insubordination. It is, done well, one of the most valuable things you can do. Briefs are often wrong, or incomplete, or based on assumptions that nobody has stress-tested. Senior people make bad calls. Clients sometimes ask for things that will not serve their users, or their own goals, and part of your job is to say so.


The key is how you do it. Not combatively, not as a challenge to authority, but as a genuine question in service of the work. "I want to make sure I understand the reasoning here" goes a long way. "I have a concern about this approach" said early is almost always better than silently delivering something you knew wasn't right.


The designers and design directors I respect most are not the ones who agree with everything. They're the ones who push back thoughtfully, explain their reasoning, and make everyone around them sharper for it. That's not arrogance. That's professional confidence, and it's something you can build deliberately, one conversation at a time.


On Finding Your Voice

None of this is immediate. Finding your voice in a room, particularly a room full of people who seem more confident or more experienced, takes time and repetition. You will have conversations that don't go the way you hoped. You will ask questions that land awkwardly, push back at the wrong moment, or say something in a meeting that you replay on the way home and cringe at.


That's the process. It's not a sign you're bad at this. It's a sign you're learning it.

What I'd tell my earlier self, the one sitting quietly in meetings absorbing frustrations and mistaking silence for professionalism, is this: your perspective has value precisely because it's yours. The observation you're holding back because you're not sure it's worth saying is very often the one the room needed to hear. And the question you're not asking because you're afraid of looking inexperienced is, almost without exception, a perfectly reasonable question.


Speak up. Ask the thing. Push back when it matters. Build the relationships that let you be honest, with clients, with colleagues, with yourself.


The work will be better for it. And honestly, so will you.

bottom of page