UX Career Development Paths

🐑 Business Language vs. UX Language. How to present design work, explain design decisions and get stakeholders on your side ↓ 🤔 Businesses rarely understand the impact of UX work. 🤔 UX language is overloaded with ambiguous terms/labels. 🤔 Business can’t support initiatives it doesn’t understand. ✅ Leave UX language and UX abbreviations at the door. ✅ Explain design work through the lens of business goals. 🚫 Avoid “consistency”, “empathy”, “simplicity”, “affordance”. 🚫 Avoid “design thinking”, “cognitive load”, “universal design”. 🚫 Avoid “lean UX”, “agile”, “archetypes”, “Jobs-To-Be-Done”. 🚫 Avoid “stakeholder management” and “design validation”. 🚫 Avoid abbreviations: WIP, POC, HMW, IxD, PDP, PLP, WCAG. ✅ Explain how you’ll measure success of your design work. ✅ Speak of business value, loyalty, abandonment, churn. ✅ Show risk management, compliance, governance, evidence. ✅ Refer to cost reduction, efficiency, growth, success, Design KPIs. ✅ Present inclusive design as an industry-wide way of working. As designers, we often use design terms, such as consistency, friction and empathy. Yet to many managers, these attributes don’t map to any business objectives at all, often leaving them baffled and utterly confused about the actual real-life impact of our UX work. One way out that changed everything for me is to leave UX vocabulary at the door when entering a business meeting. Instead, I try to explain design work through the lens of the business, often rehearsing and testing the script ahead of time. When presenting design work in a big meeting, I try to be very deliberate and strategic in the choice of words. I won’t be speaking about attracting “eye-balls” or getting users “hooked”. It’s just not me. But I won’t be speaking about reducing “friction” or improving “consistency” either. Instead, I tell a story. A story that visualizes how our work helps the business. How design team has translated business goals into specific design initiatives. How UX can reduce costs. Increase revenue. Grow business. Open new opportunities. New markets. Increase efficiency. Extend reach. Mitigate risk. Amplify word of mouth. And how we’ll measure all that huge impact of our work. Typically, it’s broken down into 8 sections: 🎯 Goals ← Business targets, KRs we aim to achieve. 💥 Translation ← Design initiatives, iterations, tests. 🕵️ Evidence ← Data from UX research, pain points. 🧠 Ideas ← Prioritized by an impact/effort-matrix. 🕹 Design work ← Flows, features, user journeys. 📈 Design KPIs ← How we’ll measure/report success. 🐑 Shepherding ← Risk management, governance. 🔮 Future ← What we believe are good next steps. Next time you walk in a meeting, pay attention to your words. Translate UX terms in a language that other departments understand. It might not take long until you’ll see support coming from everywhere — just because everyone can now clearly see how your work helps them do their work better. [continues in the comments]

Getting buy-in is one of the most underrated UX skills and ironically, it’s the one thing most juniors avoid because it feels like selling. But here’s the shift: Buy-in isn’t persuasion. It’s alignment. And you can do it without being pushy, political, or manipulative. Here’s the simple blueprint I teach my mentees (and use myself): 1️⃣ Start with their goal, not your idea Instead of leading with “I think we should redesign…” start with: “What’s the outcome we’re trying to drive?” When someone feels heard first, they’re far more open to the solution second. 2️⃣ Show the problem, not your preference Skip the “I like / I don’t like.” Lead with evidence: A user quote A friction point Data that signals a drop-off A pattern you observed in testing This shifts the conversation from opinion vs. opinion → shared problem vs. solution. 3️⃣ Present options not ultimatums People resist when they feel cornered. Try: “Here are two paths we can take. Want to walk through the trade-offs?” Giving choice = giving ownership. And ownership = buy-in. 4️⃣ Connect your idea to business impact The fastest way to lose buy-in is to stay in “design land.” Make it practical: “This reduces onboarding time.” “This lowers support tickets.” “This helps us hit the Q3 activation goal.” Speak their language and the conversation changes instantly. 5️⃣ Invite pushback early Nothing kills momentum like a surprise objection at the finish line. Instead: “Before we run with this, what concerns do you see?” This transforms critics into collaborators. 6️⃣ Close with clarity Always end with one crystal-clear next step: “Do we feel aligned on path A?” “Is this the direction you’d like me to move forward with?” “What’s the priority for this sprint?” Buy-in without a next step is just a nice conversation. This is how you get buy-in naturally not through pressure, but through partnership.

You know how Pixar grabs you in 10 seconds? A scene. A problem. A character with a goal. Then they pull you through a story arc you can’t ignore. Your UX portfolio should do the same. But most don’t. They open with “I’m a UX designer passionate about users…” Then show a bunch of pretty wireframes. No plot. No stakes. No transformation. You want to land your dream job? Tell a damn good story. → Start with the business or user problem. → Walk through your decisions — not just deliverables. → End with what changed because of your work. Hiring managers aren’t looking for portfolios. They’re looking for proof. Proof that you can think. Solve. Communicate. Own outcomes. That’s what the 7-step UXCP structure gives you: → A bold opener that hooks them. → Role-relevant proof of value. → Impact-based storytelling (not process play-by-plays). → A unique strength that sticks. → Referrals that speak volumes. → And a CTA that moves the convo forward. Sound familiar? It’s how Pixar tells stories. It’s how designers win trust. So here’s the question: Wireframes or story arc — which one makes you unforgettable?

Telling a compelling story with UX research has nothing to do with flair and everything to do with function, empathy, and influence. One of the most critical yet underappreciated lessons in UX and product work - beautifully articulated in It’s Our Research by Tomer Sharon - is that research doesn’t succeed just because it’s rigorous or well-designed. It succeeds when its insights are heard, understood, remembered, and acted upon. We need to stop treating communication as an afterthought. The way we present research is just as important as the research itself. Storytelling in UX is not decoration - it’s a core deliverable. If your goal is to shape decisions rather than just share findings, the first step is to design your communication with the same care you give your methods. That means understanding the mindset of your stakeholders: what they care about, how they process information, and what pressures they’re facing. Storytelling in this context isn’t about performance - it’s about empathy. The insight must also be portable. It needs to survive the room and be retold accurately across meetings, conversations, and documents. If your findings require lengthy explanations or rely too heavily on charts without clear conclusions, the message will fade. Use strong framing, clear takeaways, and repeatable phrases. Make it memorable. Avoid leading with your process. Stakeholders care far less about your methods than they do about the problems they’re trying to solve. Lead with the tension - what’s broken, what’s at risk, what’s creating friction. Only then show what you learned and what opportunities emerged. Research becomes powerful when it forecasts outcomes, not just reports behaviors. What will it cost the business to ignore this behavior? What might change if we take action? When we can answer these questions, research earns its place at the strategy table. Treat your report like a prototype. Will it be used? Will it help others make decisions? Does it resonate emotionally and strategically? If not, iterate. Use narrative elements, embed user moments, bring in supporting visuals, and structure it in a way that guides action. Finally, stop thinking of the share-out as a one-way street. Facilitate instead of presenting. Invite stakeholders to interpret, ask questions, and explore implications with you. When they co-create meaning, they take ownership-and that leads to real action. Research only creates value when it moves people. Insights are not enough on their own. What matters is the clarity and conviction with which they are communicated.

Focusing on screens kills design impact. Over the last few years, I’ve been in hundreds of design presentations and workshops. One thing is clear: when you lead with business outcomes, stakeholders pay attention. When you walk through a journey screen by screen, the design impact drops. People get stuck on details that don’t move their goals forward. You lose them. I was reminded of this this week when we fell into this trap… five minutes spent on the placement of a button without clarity on the intent. Here’s what to do instead. Start with the business goal. Pick two or three points in the flow where it either works or breaks. Show what users need in those moments, and how the design changes behavior. That’s where the impact is. Tools like Helio help bring that user data into the conversation with UX metrics. Show how the design solves actual user problems. That’s what holds attention. From there, show how the design supports those moments. Focus on the two or three areas where impact is strongest. You can always go deeper into the rest. But most people care more about what the work does than how each screen looks. When the conversation shifts to visuals too early, the story is gone. Here’s an example: Business goal: Increase trial-to-paid conversion  → Key point 1: Landing page Users need to quickly understand what they’re getting and if it’s worth their time.  We simplified the message and showed a clear outcome up front,  and as a result more people are considering the trial.  → Key point 2: Signup form Users don’t want friction or commitment too early. We reduced fields and removed the credit card requirement, and as a result more people were willing to sign up for the service.  → Key point 3: First-use experience Users need to see value fast or they drop. We guide them to one clear action that shows value in under a minute, so we simplified the message so more users stick with the trial signup. Here’s how to think about the story in each key moment: what the business needs → what users need → how the design closes the gap Design storytelling isn’t just about walking through screens, but rather showing what actually moves the business. That is design impact.

The biggest challenge in user experience isn’t research or execution — it’s proving impact on the business. Design doesn’t speak for itself. You have to connect the dots between user insight and business outcomes. Executive support doesn’t hinge on polished prototypes. It hinges on showing how your work moves the business forward. Here are 5 ways to bring UX and business into alignment — and turn design into a growth lever: 𝟭. 𝗠𝗮𝗽 𝘀𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿 𝗽𝘀𝘆𝗰𝗵𝗼𝗹𝗼𝗴𝘆 𝗯𝗲𝗳𝗼𝗿𝗲 𝘁𝗵𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝗸𝗶𝗰𝗸-𝗼𝗳𝗳 Want support? Know what they care about. Whether it’s speed, revenue, risk, or reputation, tailor your framing to their drivers and their biases. 🎯 Someone obsessed with sunk cost? Show long-term savings. 📊 Data-driven skeptic? Come with a prototype and a revenue forecast. 𝟮. 𝗕𝗿𝗶𝗻𝗴 𝘀𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿𝘀 𝗶𝗻𝘁𝗼 𝗱𝗶𝘀𝗰𝗼𝘃𝗲𝗿𝘆, 𝗲𝗮𝗿𝗹𝘆 𝗮𝗻𝗱 𝘃𝗶𝘀𝗶𝗯𝗹𝘆 Your best critics become co-owners when they’re part of the journey. Invite cross-functional stakeholders into problem-framing workshops. Co-create problem definitions. Align on what matters before the pixels move. 💬 Early involvement = fewer late-stage “surprises.” 𝟯. 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗲 𝗶𝗻𝘀𝗶𝗴𝗵𝘁𝘀 𝗶𝗻𝘁𝗼 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗺𝗲𝘁𝗿𝗶𝗰𝘀 Executives speak numbers. If your research can’t be tied to retention, revenue, or risk mitigation, it gets sidelined. 🧠 “Users were confused by the form” → “This friction costs us $XM/month in lost conversions.” 𝟰. 𝗣𝗮𝗰𝗸𝗮𝗴𝗲 𝗿𝗲𝘀𝗲𝗮𝗿𝗰𝗵 𝗳𝗼𝗿 𝗿𝗮𝗽𝗶𝗱 𝗰𝗼𝗻𝘀𝘂𝗺𝗽𝘁𝗶𝗼𝗻 Skip the 40-slide deck. Try an “impact brief.” Focus on the most powerful video clip. Use AI summaries. Give busy execs a frictionless way to get it. ⏱ Clarity wins trust. Brevity wins time. 𝟱. 𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗰𝗮𝗱𝗲𝗻𝗰𝗲 𝘁𝗵𝗮𝘁 𝘀𝗵𝗼𝘄𝘀 𝗺𝗼𝗺𝗲𝗻𝘁𝘂𝗺 Want executive buy-in? Don’t ask for a leap of faith. Pilot something small. Deliver a win. Share results. Then propose the next step. 📈 Stakeholders fund demonstrated momentum, not hypothetical potential. Bottom line: Great experience doesn’t just serve users. It drives strategy. But only when we meet the business where it is, and bring it with us. How are you aligning UX with business value in your work? I’d love to hear your thoughts.

A lot of designers approach presentation interviews by opening Canva or Figma and immediately trying to design the “perfect” deck. And then they wonder why it takes forever, feels chaotic, or never quite clicks. The solution is simple. Design the story before designing the slides. A strong presentation doesn’t start with visuals — it starts with structure. Here’s the outline I recommend to my clients for sharing any project: 1️⃣ Context & Company What does the company do, and who are their users and customers? What product are we talking about? What was your role? Give people enough background to understand the world you were operating in. 2️⃣ Problem What wasn’t working well? Why did this matter to the business and users? 3️⃣ Constraints Technical limitations, competing priorities, data gaps, cross-team dependencies — all the things that made the work challenging. 4️⃣ Process & Exploration How and what did you learn? What options did you consider? How did research and discovery shape your decisions? 5️⃣ Key Decisions Highlight a few moments where your judgment showed — the trade-offs, the “why this over that” thinking that hiring managers really need to hear. 6️⃣ Solution Give a demo of what you built. Walk through the final designs and explain the reasoning behind what you shipped. 7️⃣ Impact What changed in the business because of this? Talk about usage, adoption, revenue, clarity, speed, or reduced friction. 8️⃣ Learnings What you’d repeat, what you’d do differently, and what surprised you. Once this story feels clear, then build your slides. You’ll move faster, feel more confident, and spend far less time reworking the deck. A few additional tips that help almost everyone: ✅ Practice out loud early. Clarity comes from hearing yourself talk through it, not from polishing slides. ✅ Keep slides simple and visual. High-level bullets paired with clean visuals are plenty — slides should support your voice, not compete with it. ✅ Be conversational. A good presentation feels like walking a colleague through your work, not giving a performance. ✅ Focus on outcomes. Even small improvements or qualitative wins matter. If you get the story right, the rest becomes much easier — and your presentation becomes far more clear and memorable. Hope this helps! Let me know in the comments. #productdesign #uxdesign #designportfolio #uxcareers #designinterview #designhiring #designjobs

UX is a tightrope between business and user needs. If you want to be heard, you have to listen to both. Your designs exist within an ecosystem of competing priorities, ambiguous requirements, and conflicting feedback. It's up to you to navigate. And AI can't help you here — it's human connections that matter. People over process. What you shouldn't do: ❌ Rush into solutions before fully understanding stakeholder motivations ❌ Dismiss requirements and constraints as obstacles to good design ❌ Present only a single design direction, limiting stakeholder buy-in and participation What you should do: ✅ Design out loud and schedule regular touchpoints to gather feedback before formal presentations ✅ Document the design journey to maintain alignment and transparency ✅ Speak the language of business when presenting concepts to executives Great UX work happens through relationships you build. Make stakeholders your allies, and watch your influence grow naturally within the organization.

I used to wonder how to make my UX work more impactful. I saw designers getting astonishing results for their clients/stakeholders so I knew it was possible. I just didn’t know how to actually do it. I knew the standard processes and tools. So I thought I should hit my stakeholders over the head with how they’re doing it wrong and be the guy always fighting for users. That should do the trick, right? Wrong. Turns out I needed to: → Listen more → Follow my gut → Break the rules That’s when things started clicking. I pieced this together a long time ago in the tech world. Now I apply it to client projects. And it works... We’ve helped our clients: → 3.5x their conversion (eCommerce) → Oversubscribe their A round by 55% (health tech) → Rack up 8 awards for innovation (education) Here’s exactly how we did it: 1. Understand goals and constraints: - How is success measured? - What time pressure exists? - What have they already tried? - What are the biggest challenges? - Who are their customers or users? - What unique assets or data do they have? Literally everything depends on this. Asking the right questions upfront means better insights, better design recommendations, and better collaboration. 2. Audit the current product: - Review every screen, state, and flow - Gather screencaps and recordings - Identify opportunities, risks, problems Step 1 was the big picture. This is about details. Experience, intuition, and judgement matter here. 3. Make recommendations: - Prioritize by impact - Call attention to the top 3 issues - Present findings clearly. We use slides. Show what's happening with the current product—and how to transform it. 4. Agree on priorities, timelines, and process: - What’s the most important thing to do next? - How will we execute the work? Too many designers get caught up on "right" process. Right depends on context. There are lots of ways to succeed. 5. Execute the work: - Research, design, prototyping, testing - Every decision or finding gets tied to goals or risks AI is speeding this part up. It's a wild time. 6. Communicate & collaborate throughout: - Design is a team sport—we win together - The whole team knows what’s happening, and why - Nobody's left guessing Pro tip: Clarity is a gift designers are well positioned to give product teams. Capture roadmap, process, and status in a single visual to do this. Not sure how? DM me. 7. Ship product: “Everyone has a plan until they get punched in the face”—Mike Tyson. Things get real when they're put in front of users. Do that fast, but not so fast that you don’t get a good signal from the market. – I love helping clients succeed. Over time, I found these traits help: Teamwork Pragmatism Bias for action Lightheartedness Commitment to quality Find your own way. Break the rules when needed. Stay focused on impact. That’s what makes the work meaningful—and what makes for truly successful products (and design careers).

𝟑 𝐑𝐞𝐚𝐬𝐨𝐧𝐬 𝐖𝐡𝐲 𝐔𝐗 𝐃𝐞𝐬𝐢𝐠𝐧𝐬 𝐃𝐨𝐧’𝐭 𝐆𝐞𝐭 𝐁𝐮𝐢𝐥𝐭: “𝘎𝘳𝘦𝘢𝘵 𝘥𝘦𝘴𝘪𝘨𝘯! 𝘉𝘶𝘵… 𝘸𝘦 𝘥𝘰𝘯’𝘵 𝘩𝘢𝘷𝘦 𝘳𝘦𝘴𝘰𝘶𝘳𝘤𝘦 𝘵𝘰 𝘥𝘦𝘷𝘦𝘭𝘰𝘱 𝘪𝘵 𝘳𝘪𝘨𝘩𝘵 𝘯𝘰𝘸.”  “𝘜𝘴𝘦𝘳𝘴 𝘭𝘰𝘷𝘦 𝘪𝘵, 𝘣𝘶𝘵 𝘪𝘵’𝘴 𝘯𝘰𝘵 𝘪𝘯 𝘵𝘩𝘦 𝘳𝘰𝘢𝘥𝘮𝘢𝘱 𝘱𝘳𝘪𝘰𝘳𝘪𝘵𝘺.”  “𝘛𝘩𝘪𝘴 𝘤𝘢𝘯 𝘷𝘪𝘰𝘭𝘢𝘵𝘦 𝘍𝘋𝘈 𝘤𝘰𝘮𝘱𝘭𝘪𝘢𝘯𝘤𝘦 — 𝘵𝘰𝘰 𝘳𝘪𝘴𝘬𝘺.” “𝘛𝘩𝘪𝘴 𝘥𝘰𝘦𝘴𝘯'𝘵 𝘢𝘭𝘪𝘨𝘯 𝘸𝘪𝘵𝘩 𝘰𝘶𝘳 𝘣𝘳𝘢𝘯𝘥 𝘱𝘰𝘴𝘪𝘵𝘪𝘰𝘯𝘪𝘯𝘨." Sound familiar? I once spent weeks perfecting a redesign — only to hear, “It’s not in our Q2 roadmap,” because I didn’t sync with PMs early. Early in my career, I thought good design was about creating user-centered, visually pleasing designs. But I quickly learned: If your organization isn’t ready to back the design — it doesn’t matter how good it is. Here are 3 reasons UX designs often fail to launch — and how to fix them: ❌ User-first, but not business-aligned ✅ Great UX is important but isn’t enough. Can you articulate how it aligns with product strategy or differentiates from competitors? ❌ No talk of cost ✅ Stakeholders care about effort, resources, timelines. Use tools such as Impact vs. Effort matrix to help prioritize what’s feasible, now vs. later. ❌ Lack of cross-functional collaboration early on ✅ Bring PMs, devs, marketing, and compliance in early. Co-creation = more buy-in. 𝐁𝐞𝐟𝐨𝐫𝐞 𝐈 𝐩𝐫𝐞𝐬𝐞𝐧𝐭 𝐚𝐧𝐲 𝐝𝐞𝐬𝐢𝐠𝐧, 𝐈 𝐚𝐬𝐤: What business goal does this serve? Can we build it, and when? Why is now the right time? UX doesn’t stop in Figma. It’s also about bridging vision and reality, and getting your team on board to make it happen. What did I miss? Have you struggled with getting your designs implemented? I’d love to hear how you’ve navigated this. #uxdesign #productdesign #crossfunctional #designer #designstrategy #businessdesign #stakeholderalignment