From Designer to Consultant: What Changes and What Doesn't
When I made the shift from in-house UX designer to commercial consultant, I expected the tools to change. I didn't expect the mindset shift to be so complete.
For seven years, I was a UX designer. Good at it. Respected for it. The kind of designer who got invited into meetings. The kind whose work shipped with minimal revisions.
But I was frustrated in a way I couldn't fully articulate. I'd deliver work I was proud of, and nothing would change. Not dramatically. The product would improve, incrementally, but the fundamental problems the business faced — growth, conversion, retention — felt completely disconnected from my work.
I thought the problem was the companies I worked at. Or the stakeholders. Or the way design is structured in most organizations.
Eventually, I realized the problem was how I was thinking about my own work.
The Shift That Matters
When I moved into commercial consulting, the change I anticipated was tactical. I'd work with more clients. I'd run audits. I'd have more variety.
The change that actually happened was deeper.
As an in-house designer, my primary orientation was: what does this design communicate? As a consultant, it became: what behavior does this design produce, and what does that behavior cost or generate?
That's not a small difference. It changes every design decision you make. It changes the questions you ask in kickoffs. It changes how you present your work. It changes what "done" means.
What Changed: How I Define the Problem
In-house, problems were handed to me. "We need to improve the onboarding flow." "The dashboard is confusing." "Users are dropping off at checkout."
These feel like design problems. They're not. They're symptoms. The real problem is always one level higher: retention is below the cohort target, LTV is lower than CAC, the conversion rate from trial to paid is 4% when it should be 12%.
As a consultant, my job starts with finding the real problem. Not the one the client presents. The one that's actually costing them money.
This requires a different kind of conversation. Not "tell me about your users." More like "walk me through your P&L and show me where the growth is breaking."
What Changed: How I Present
In-house designers present design. Wireframes, mockups, prototypes. "Here's what we're proposing and why."
Consultants present business cases. "Here's the problem we identified, here's the cost of that problem, here's what we're proposing, and here's what it would mean for revenue if we're right."
This sounds obvious. But most designers I coach have never written a business case in their life. They've presented work. They've explained decisions. But they've never named the revenue number associated with the design change they're proposing.
When you start doing that, stakeholder conversations change completely. You're not defending aesthetic choices. You're discussing risk and return.
What Changed: How I Measure Success
In-house: success was a shipped product. Stakeholders happy. Timeline met. Design approved.
Consulting: success is the metric moving. Conversion rate improved. Churn reduced. Trial-to-paid increased. If the number doesn't move, the design didn't work, regardless of how good it looked.
This is harder. It requires humility. Sometimes your design doesn't work, and you have to own that and iterate. But it's also more honest. And it's how you build actual credibility with clients, not the kind based on beautiful deliverables, but the kind based on results.
What Didn't Change: The Core Skills
Here's what I want to be honest about: the UX skills I built in-house are the foundation of everything I do as a consultant.
The ability to read an interface as a user would. To see where attention goes. To find where the mental model breaks. To understand what information a user needs at each step. These skills are irreplaceable.
What changed is how I contextualize them. I no longer use UX language to explain them. I use business language. "This step loses users because they don't know why they're doing it" becomes "this step has a 68% drop-off rate because the goal isn't clear, which is costing you $X in lost trials."
Same insight. Different frame. And the different frame is what makes it actionable for the people who need to approve and fund the fix.
What Didn't Change: The Work Itself
I still do research. I still synthesize. I still design. I still prototype. The workflow isn't dramatically different.
What's different is the context I hold throughout. Every decision is filtered through: does this make the business case stronger? Does this make it clearer what to do and why? Does this move the number I was hired to move?
That filter sounds constraining. In practice, it's liberating. It gives every design decision a clear test. And when you pass the test — when the design change moves the metric — it feels different from anything I experienced in-house.
For Designers Who Want to Make This Shift
You don't have to become a consultant to apply this thinking. Most of the value comes from changing how you orient to your current work.
Start by asking, for every project: what metric am I trying to move? If you can't name one, find it. Talk to your PM, your CFO, your head of growth. Find the number.
Then frame every design presentation around that number. "This change is intended to improve activation by reducing the time it takes a new user to complete their first meaningful action. Our current median time is 14 minutes; the benchmark for companies with similar products is 6 minutes. Here's what we're proposing and why we think it closes that gap."
That's not a different type of design. It's the same design, with a different frame. And it changes everything about how your work lands.
If you're a designer looking to make this shift — into consulting, into a more strategic in-house role, or just into influencing your organization more effectively — that's exactly what UX coaching focuses on. Find out more about coaching here →