I was working on a hot air balloon pilot booking app a few years ago. We'd finished the research phase, built the flows, validated with users. The network data was clear: pilots in certain regions had three times the booking density during monsoon season cos tourists wanted the post-rain landscape shots. The entire booking flow, pricing model, and availability calendar needed to account for this seasonal pattern.
I walked into a review with the CEO. Showed the data. Explained how the booking architecture needed to reflect regional demand patterns. His response: "Just make it look clean and make sure the button works."
That was it. Weeks of research, real behavioral data, a structural recommendation that would have affected revenue. Reduced to "make the button work."
If you've reported to a non-design manager, you know this moment. You've been in this room. You brought substance and got asked for surface.
The Reality Most Designers Live In
There's a popular idea that design teams should report to design leaders. Makes sense on paper. A design VP understands what research means, knows why a structural recommendation isn't the same as a color preference, can evaluate your growth based on the actual craft.
The reality looks different.
InVision surveyed thousands of companies about design maturity. Only 5% reached the highest level, where design is integrated into business strategy and has genuine executive representation. 41% were still at the lowest tier, where design is treated as visual production [1]. Pave analysed compensation and reporting structures across 900+ companies and found that design leaders overwhelmingly report to non-design executives: Heads of Product, CTOs, CEOs. Almost none report to a dedicated design executive [2]. NNGroup surveyed 557 design practitioners and found no single best practice for where design sits in the org chart [3].
The vast majority of designers report to someone who doesn't come from design. That's the baseline, not a dysfunction or an outlier in the data.
Which means the career conversation you're trying to have, the one about your growth, your trajectory, your next move, is happening with someone who may not understand what good looks like in your discipline. And that gap between how you think about your work and how they evaluate it is where careers stall.
Why Career Conversations Break Down
This isn't a bad-manager problem. Most non-design managers aren't hostile to design. They just don't have the vocabulary for it.
A design manager watches you run a research synthesis and recognizes the strategic thinking behind how you framed the insights. A non-design manager sees that you "talked to some users" and wonders when the screens will be ready.
A design manager understands that the decision to simplify a flow from seven steps to three involved information architecture, edge case analysis, and multiple rounds of validation. A non-design manager sees a simpler screen and assumes it was simpler to make.
The evaluation gap shows up in three places.
Goals that don't map to design work. Your manager sets OKRs around feature delivery speed, ticket completion, or stakeholder satisfaction scores. None of these measure design quality, research depth, or the strategic impact of your decisions. You hit every goal and still feel like your actual contribution is invisible.
Feedback based on likeability, not craft.Gallup tracked nearly 15,000 employees and found that only 16% said their last conversation with their manager was "extremely meaningful" [4]. When managers don't understand the work, feedback defaults to personality: "great team player," "easy to work with," "always positive in meetings." That's not career development. That's a character reference.
Promotion criteria borrowed from other functions.Engineering has clear ladders: junior writes code under supervision, senior designs systems independently, staff shapes technical direction across teams. Product has them too. Design? Your manager might be using the engineering ladder cos that's what they know. So you get measured on output volume and technical complexity instead of research quality, systems thinking, or the business impact of your design decisions.
The Translation Problem
The real issue isn't that your manager doesn't value design. The issue is that you're speaking different languages about the same work.
You say: "I conducted contextual inquiry across three user segments and identified a critical mental model mismatch in the onboarding flow."
They hear: "She talked to some people and thinks the onboarding needs changes."
You say: "The information architecture needs restructuring cos users are creating workarounds that increase support ticket volume."
They hear: "He wants to redesign something that's already shipped."
Neither person is wrong. But one person controls your performance review, your promotion timeline, and your project assignments. And that person is working with an incomplete picture of what you actually do.
The fix isn't waiting for your manager to learn design. Some will, most won't have time to. The fix is translating your work into the language they already operate in: business outcomes, risk reduction, measurable impact.
Six Moves for a Career Conversation That Actually Lands
These aren't abstract tips. Each one comes with a sentence you can actually say.
1. Set goals in their language, not yours
Before your next goal-setting conversation, take every design goal and translate it into a business outcome your manager already cares about.
Don't say: "I want to improve the research maturity of our team."
Say: "I want to reduce the number of post-launch fixes we ship by running structured research before development starts. Last quarter we had 14 post-launch patches. I want to cut that by half."
Your manager understands fewer patches. They understand reduced engineering rework. They might not understand research maturity, and they don't need to. The outcome is the same.
2. Make your decision-making visible
Design decisions happen in your head, in your Figma files, in conversations with users. Your manager sees the output, not the 40 decisions that shaped it. So they assume the work was straightforward.
Before your 1:1, pick one decision from the past week and explain it in two sentences.
Say: "The checkout flow has three steps instead of five. We tested both versions and the shorter flow reduced drop-off by 23%, but I kept the address confirmation as a separate step cos our support data showed 18% of delivery errors come from auto-filled addresses."
You're not asking for praise. You're showing that design involves tradeoffs that affect business metrics. Over time, this changes how your manager categorizes your work.
3. Bring a career roadmap they can evaluate
Most designers walk into career conversations with vague aspirations: "I want to grow into a senior role," "I want to lead a team someday." Your manager can't do anything with that.
Build a one-page roadmap. Three columns: where you are now (with specific evidence), where you want to be in 12 months (with specific capabilities), and what you need to get there (projects, exposure, learning).
Say: "Right now I'm handling execution on two product areas. In 12 months, I want to be leading the design direction for one full product vertical. To get there, I need to run at least two end-to-end projects where I own the research-to-ship pipeline, and I need exposure to the quarterly business review so I understand how leadership evaluates product success."
This gives your manager something concrete to support.
4. Track your work in metrics they report on
Find out what numbers your manager presents in their own reviews. Revenue? NPS? Feature adoption? Support tickets? Churn? Then start connecting your work to those numbers.
Keep a running doc. Every two weeks, add one line: what you did, what it affected, what moved. You don't need a full analytics setup. You need one connection between your work and a metric that matters upstream.
Say: "The onboarding redesign went live three weeks ago. First-week activation is up 11% compared to last cohort. I want to talk about what I learned from this project and how it shapes what I take on next."
Your manager now has something to repeat when their boss asks what the design team accomplished this quarter.
5. Train them (without calling it training)
Your manager won't sign up for "Design Thinking 101." But they'll absorb the principles if you share them as context for decisions.
When you present work, spend 30 seconds on why you made a choice, not what the choice was. "I tested this with five users cos research shows that five users surface 85% of usability issues. More than that has diminishing returns for this type of evaluative study." You're not lecturing. You're giving them a reason to trust the process, and over time, they start internalizing the reasoning.
When they push back on something you know is wrong, don't say "that's not how design works." Say: "I hear you. I tested that approach in the first round and here's what happened." Evidence wins where authority can't.
6. Learn their language back
This is the part most designers skip. You want your manager to understand design. Fair. But have you tried to understand what keeps them up at night?
Sit in on a product review. Read the quarterly business update. Ask your manager directly: "What are the three things your boss is measuring you on this quarter?" Then figure out how your work connects to those things.
Say: "I know the team is being measured on time-to-market for the payments feature. I can cut two weeks off the design phase if I run a modified research sprint instead of the full discovery process. The tradeoff is we'll have less confidence on edge cases, but I'll flag those and we can patch in v2. Want me to scope that?"
You're now speaking their language. And you're demonstrating the exact kind of strategic judgment that earns promotions.
The Two-Way Model
Career conversations with a non-design manager work best when you accept two responsibilities at the same time.
Teach them what design actually involves.Not through a formal workshop or a slide deck, but in small moments every week. Show them a before-and-after of a flow you simplified. Explain why you chose to research before designing. Share a user quote that changed the direction of a feature. Over months, their mental model of design shifts from "makes things look nice" to "makes decisions that affect whether this product works."
Learn what they actually need from you.They're managing a team, reporting upward, balancing competing priorities. If you can understand their constraints, you can frame your growth in terms they can sponsor. "I want to grow" is an ask. "I want to take ownership of the research phase for Project X, which will free up your bandwidth and give us better data before the dev sprint starts" is a partnership.
The designer who figures out how to do both, teach and learn simultaneously, stops being someone who needs to be managed and starts being someone who co-manages the relationship.
The Hot Air Balloon Problem, Revisited
That CEO who told me to "make the button work"? I went back to him a week later with a different approach. Instead of showing the research data, I showed him revenue. "Pilots in these three regions have 3x the booking density during post-monsoon season. If we build the availability calendar around seasonal demand instead of flat availability, the projected booking increase is 40% in Q3. The design work for this is a restructured booking flow that takes regional data into account."
He approved it in the meeting.
The design work was identical. The research was the same. What changed was the language. I stopped explaining design and started explaining business impact. He didn't need to understand information architecture. He needed to understand that this recommendation would make the product more money.
Your career conversation works the same way. You're not dumbing down your work. You're translating it so the person who controls your trajectory can actually see it.
Free Resource: Career Conversation Cheatsheet
We built a one-page cheatsheet with all six moves, including the exact sentences, goal translation examples (design language to business language), and a 1:1 agenda template you can bring to your next career conversation.
Print it and bring it to your next 1:1.
Career Conversation Cheatsheet
All six moves with the exact sentences, goal translation examples from design language to business language, and a 1:1 agenda template for your next career conversation.
No spam. Just the cheatsheet.
Sources & References
- [1] InVision. "The New Design Frontier: Design Maturity Model." Survey of thousands of companies finding only 5% at highest design maturity level. invisionapp.com
- [2] Pave. Compensation and reporting structure analysis across 900+ companies. Design leaders overwhelmingly report to non-design executives.
- [3] Nielsen Norman Group. Survey of 557 design practitioners on reporting structures. Found no single best practice for where design sits in an org chart.
- [4] Gallup. "The #1 Great Manager Habit." Study of nearly 15,000 employees. Only 16% reported their last conversation with their manager was extremely meaningful. gallup.com
Further Reading on Xperience Wave
- Design Strategy Sounds Like a Buzzword Until You Actually Build One
- Why Product Managers Get Credit for Your Design Work (And What You Can Do About It)
- She Shipped Three Times While He Was Still Researching. They're Both Right. That's the Problem.
- The UX Job Market in India (Sep 2026): What's Actually Hiring, What's Shrinking, and What's Winning
About the Author
Shaik Murad is Co-founder and Head of Product & Design at Xperience Wave, a UX design studio based in Bangalore, working across designer mentorship, UX services for businesses, and a design community of 1,370+ designers.
- Murad, Co-founder & Head of Product & Design, Xperience Wave
