I have sat in a lot of sprint meetings with a lot of design teams over the years.
And I have noticed a specific thing that happens in some of them. The designers are happy. Genuinely happy. They are laughing, engaged, moving quickly through the agenda. The energy is good. The velocity is high.
When I dig a little deeper into what is actually happening in those teams, I almost always find the same thing: these designers have stopped being designers. They have become the garnish.
The garnish is on every plate. It makes things look complete. It arrives after every decision has been made, about what goes on the plate, how it is prepared, what it costs. Nobody consults the garnish. It just shows up at the end and makes it presentable. These designers receive decisions, make those decisions look good, and ship them. The brief arrives. They execute. Everyone is pleased. Life is easy.
And here is the part that stays with me: when I tell them this, they are surprised. They were not being lazy. They were not cutting corners on purpose. They genuinely believed they were doing good work. Nobody told them they were not.
This blog is me telling you.
The gap between a mid-level designer and a senior designer is not years of experience. It is not the size of your portfolio or how deep your tool knowledge runs. It is five specific conversations, questions that senior designers ask themselves before they walk into any room, before they open Figma, before they accept any brief.
Mid-level designers do not have these conversations. Not because they are not smart enough. Because nobody showed them the questions exist.
Junior designers ask: what do I need to design?
Mid-level designers ask: how should I approach this problem?
Senior designers ask: should this problem exist at all?
(Source: UX Beginner, understanding design levels)
Conversation 1: "Is This Worth Solving, or Am I Just Making Someone Comfortable?"
This is the conversation that happens before every brief is accepted. Before the first sticky note. Before the first wireframe.
A mid-level designer receives a brief and starts designing. A senior designer receives a brief and interrogates it first. Not out of insubordination, out of professional obligation. Because the most expensive thing a design team can do is build the right solution to the wrong problem.
The questions that make up this conversation:
Is this a real problem or a comfort request? Someone powerful felt uncomfortable about something. The discomfort got turned into a brief. Now it is on your desk. Before you touch it: is there a user who has this problem? Is there data that says this matters? Or are you about to spend three weeks making a VP feel better about a feature that real users do not care about?
Am I on a business priority project? Or am I working on something that occupies design time without moving anything that matters? Senior designers know which projects are connected to the metrics the organisation actually tracks, and they fight to be on those projects, not the ones that look busy but do not move numbers.
Am I satisfying my own ego by following a process? This one is uncomfortable. It is the mad scientist question. There are designers who run twelve weeks of research for a decision that needed to be made in two. Not because the research was required, because research feels like good design. It is not good design if it is not connected to a decision the business is actually going to make. Process is a tool, not a virtue.
The garnish never asks any of these questions. It receives the brief and makes it look good. The designer who is actually doing senior work asks all three, before they open a single file.
The business language gap is the specific thing that keeps senior designers stuck: Senior Designer Still Treated Like a Delivery Person.
Conversation 2: "Where Is the Money, and Who Owns It?"
This is not a cynical question. It is an orientation question. And it is the question that separates designers who influence product direction from designers who receive it.
Every product decision is connected to a business bet. Someone has decided that this feature, this redesign, this research sprint is worth the organisation's resources. Who made that decision? What number were they trying to move? What does success look like, not in design terms, but in the terms your CFO or your VP of Growth would recognise?
Senior designers know the answers before the project starts. Not because they are business consultants, because you cannot make good design decisions without understanding the business context the design is operating inside.
Where is the money in this? Which metric does this project connect to? Retention? Activation? Revenue per user? Cost reduction? If you cannot answer this, you do not know what success looks like. Which means you do not know what you are designing for.
Who owns that metric? This is the person whose opinion about your work actually matters beyond aesthetics. They are the one who, when they say 'this does not feel right,' can stop the project. They are also the one who, when they say 'this is exactly what we needed,' can open every door. Senior designers find this person early and build the relationship before they need it.
Is this a priority, for whom? Something can be a priority for the design team and irrelevant to the business. Something can be a priority for the business and logistically impossible for technology. Something can be a priority for technology and a terrible experience for the customer. Senior designers understand the hierarchy of priorities across business, technology, organisational capability, and customer, and they know which one is actually driving this project right now.
LogRocket's research on senior vs mid-level designers confirms it directly: senior designers advocate for initiatives that can lead to significant business or user value. Mid-level designers are assigned tickets to work on, which are usually defined for them.
The difference is not talent. It is whether you know which question to ask first.
On getting into the rooms where these business decisions are made: How to Get a Seat at the Product Strategy Table.
Conversation 3: "How Much Proof Does This Decision Actually Need?"
This is the research maturity conversation. And it is the one that the mad scientist and the pure intuition believer both fail at, from opposite ends.
The mad scientist believes that more research is always better. More interviews, more usability tests, more data, more time. They use scientific rigour as a shield: if the research is not done properly, the findings are not valid, the decisions should not be made. This designer is often respected for their process and consistently behind on delivery. And here is the part nobody says directly: the research they run is frequently not connected to decisions the business was actually going to change. It is research for the sake of research.
The pure intuition believer goes the other way. They have done this before. They know what works. Their gut is good. They ship fast, they learn fast, they do not waste time on research that will just confirm what they already know. This designer moves quickly and has an impressive hit rate. They also occasionally catastrophically misread a context they thought was familiar.
The senior designer lives in the middle, but it is a specific, calibrated middle. The question they ask is not 'should I do research' but 'what is the cost of being wrong on this decision, and does that cost justify the time required to be more certain?'
- High cost of being wrong + reversible decision = lightweight validation before you commit
- High cost of being wrong + irreversible decision = proper research before you commit
- Low cost of being wrong + reversible decision = build it, measure it, iterate
- Low cost of being wrong + irreversible decision = rare, but worth a beat to think about
Do I need this research, or can I fairly assume and evaluate accuracy later? This is not a lazy question. It is a resource allocation question. Not every design decision warrants six weeks of discovery. Some decisions warrant two hours of assumption mapping. Senior designers know the difference and can articulate why.
Who can help me get answers I do not have? Senior designers do not put everything on the PM's desk and wait for the brief to get better. They identify who in the organisation knows things they need to know, customer success, data analytics, engineering, business development, and they go get those answers themselves. Research is not just a methodology. It is a mindset about where information lives and who has it.
How will I validate after? Not every assumption gets validated before shipping. But senior designers make their assumptions explicit, they write them down, they articulate what would prove them right or wrong, and they watch for the signal after launch. This is what turns delivery into learning. And it is what builds the track record that makes senior designers trusted.
The specific difference between designers who own outcomes and those who just deliver outputs: The Difference Between a ₹12L and ₹30L UX Designer.
Conversation 4: "Who Actually Matters in This Room, and What Do They Need From Me?"
Every design presentation, every stakeholder meeting, every sprint review is a political landscape. Not political in the pejorative sense, political in the accurate sense. There are people in those rooms with different mandates, different incentives, different fears, and different definitions of success.
Mid-level designers walk into these rooms with their work and hope the work speaks for itself. It does not. Work speaks to people who already believe in what you are trying to do. Everyone else hears a story they need to be persuaded by.
Senior designers map the room before they enter it.
Who is the real decision-maker? Not the most senior person, the person whose opinion will actually determine what happens next. Sometimes these are the same. Often they are not. The VP who attends the review may have strong opinions, but the engineering lead who has to build the thing is the one who can stop it. Senior designers know the difference.
Who is the customer's genuine ally, and who thinks they are but is not? Every room has someone who will advocate for the user when it is comfortable and fold when it is costly. Senior designers know which person is which. They build alliances with genuine allies and do not waste time trying to convert the performative ones.
How do I storyboard this so I do not sound like a designer? The question is not how to dumb things down. It is how to translate. The PM in the room cares about velocity. The engineering lead cares about feasibility and debt. The business head cares about margin and market position. The same design decision needs to be framed differently for each of them, not because you are being manipulative, but because the same outcome genuinely means different things to different people. Senior designers learn to speak all of these languages without losing their own.
How do I make my manager successful? This is the question that most designers never think to ask. Your manager is accountable for outcomes above your individual contribution. When you walk into a meeting, you are not just representing your work, you are representing your manager's bet on you. Senior designers understand this relationship and actively make their manager look good. Not through flattery. Through the quality of their thinking and the clarity of their communication in rooms their manager cares about.
The garnish is comfortable because it removes this conversation entirely. You never have to map the room if your job is just to make things look good after the decisions are already made. The cost is that you never get invited to the room where the decisions happen.
On what hiring managers are actually evaluating when they see how you present work: What Design Managers Look for When Hiring Senior UX Designers.
Conversation 5: "Am I Still Attached to This After It Ships?"
This is the ownership conversation. And it is the one that, once you start having it, makes being the garnish genuinely impossible.
Mid-level designers measure success at delivery. The thing shipped. It went through review. Stakeholders approved it. Job done. Next ticket.
Senior designers stay attached to what happens after. Not because they are anxious or controlling, because they understand that delivery is not impact. Delivery is the beginning of impact. What matters is whether the thing that shipped actually moved the thing it was supposed to move.
Did users understand the new flow? Did activation improve? Did the thing we hypothesised would happen, happen? Did it happen for the reasons we thought, or for different reasons that tell us something we need to know going forward?
If it did not work, do I know why? This is a harder question than it looks. Most designers do not follow up after launch because the information is uncomfortable. If the feature underperformed, there is a temptation to attribute it to implementation, or marketing, or timing, anything except the design. Senior designers follow up specifically because the discomfort is where the learning is.
What do I carry into the next conversation? Every project produces something beyond the deliverable, a better understanding of where users struggle, which stakeholder frames are most effective, what the organisation's real constraints are versus the stated ones. Senior designers extract this systematically and bring it back. Their next project starts richer because of what happened on the last one.
UX Beginner's research on design levels states it directly: senior designers can propose and advocate the need for research. They do not just execute it. They measure impact. They understand outcomes qualitatively and quantitatively.
This is the difference between a portfolio of pretty screens and a track record of decisions. The companion piece on what each level of the ladder actually demands: The UX Career Ladder Is Broken in India. Here's the Path That Actually Works.
The Question That Changes Everything
I started this blog with the designers in the sprint meetings. Happy. Moving fast. Being the garnish without knowing it.
I want to be clear about something: I do not blame them. The system rewards the garnish. It is easier to manage, easier to measure, easier to approve. It produces fewer uncomfortable conversations. If nobody in the room is asking the hard questions, the hard questions do not get asked, and everyone goes home on time.
But here is what is lost when design becomes decoration: the user. The actual human being whose experience was supposed to be the whole point. When designers stop interrogating briefs and start executing them without question, the user stops having a genuine advocate in the room. They just have someone who makes the decisions look good.
The five conversations I have described are not about being difficult. They are not about challenging for the sake of challenging. They are about doing the actual job, which is to make sure that what gets built is worth building, and that what gets shipped actually works for the people it was supposed to serve.
The designers who stay at mid-level are not less talented than the ones who move forward. They just have not started having these conversations yet. The moment you start asking them, you cannot go back to being the garnish. Not because it becomes harder, because it becomes impossible to unsee.
Start with one. The next time a brief lands on your desk, before you open Figma, before the first sketch, ask: is this worth solving? Or am I just making someone comfortable? That question alone will change how you show up.
Recognising Yourself in the Mid-Level Pattern?
At Xperience Wave, we work 1:1 with designers who are ready to stop executing and start influencing. Book a free 45-minute strategy call. We will tell you honestly where the gaps are and what to work on first.
Sources & References
- UX Beginner — Understanding design levels: Junior vs Mid-level vs Senior UX Designer. The progression of questions by seniority: juniors ask 'what', mid-level asks 'how', seniors ask 'why'. Senior designers seek holistic views, propose and advocate for research, and measure qualitative and quantitative outcomes.
- LogRocket (2025) — Why some designers stay stuck at mid-level. Mid-level designers are assigned tickets defined for them. Senior designers advocate for initiatives that drive significant business or user value.
- Xperience Wave — direct observation. The garnish pattern, sprint meeting dynamics, and the five conversations are drawn from 13+ years of working with design teams across India and internationally, and from mentoring 140+ designers through career transitions.
Read Next
- If you have the senior title but still feel like a delivery person: Senior Designer Still Treated Like a Delivery Person
- If the salary gap is what is bothering you: The Difference Between a ₹12L and ₹30L UX Designer
- If you are ready to get into the rooms where strategy gets made: How to Get a Seat at the Product Strategy Table
- Why the UX career ladder is broken in India: The UX Career Ladder Is Broken in India
- What hiring managers are actually looking for at senior level: What Design Managers Look for When Hiring Senior UX Designers
- Explore the programme built for this transition: Xperience Wave Current →
Murad is Co-founder and Head of Design at Xperience Wave, a UX mentorship and education company based in Bangalore. He has 13+ years of design leadership experience across India, Japan, Singapore, Dubai, Australia, and the US, and has worked directly with 3,000+ designers.
