Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Surviving Your UX Career in Enterprise Design
Summary
If you’re just getting started in your UX career and find yourself in an enterprise environment, how can you face some of the unique challenges of practicing UX design? What if I'm not a domain expert in my new field? What happens if my team asks me to deliver something they want, but come up with something I think they really need? What if my organization doesn't have a good process for UX work? We'll discuss how to deliver professional work without all the resources at your disposal. Learn strategies to tap into your company’s people, processes, and data to shore up the quality of your UX practice.
Key Insights
-
•
Enterprise UX designers often work outside their domain expertise and must quickly build knowledge through internal experts and customer-facing roles like support and sales.
-
•
Maintaining a glossary of domain-specific jargon helps validate assumptions and align project terminology with user expectations.
-
•
Delivering exactly what is asked, such as a simple checkbox, builds trust and respects team deadlines, even if you see opportunities for bigger improvements.
-
•
Proposing larger redesigns as separate future ideas enables creative expression without jeopardizing immediate deliverables.
-
•
Documenting UX processes and templates in a shared Wiki increases transparency and accelerates onboarding for new team members.
-
•
Setting clear milestones with project plans and demonstrating past project timelines helps manage stakeholder expectations around delivery speed.
-
•
Early and frequent solicitation of candid negative feedback prevents shipping subpar designs and reduces costly fixes later.
-
•
UX designers act as connective tissue in enterprise teams by educating stakeholders, facilitating collaboration, and bridging knowledge gaps.
-
•
Explaining the rationale behind design decisions (the why) fosters understanding and reduces defensiveness among stakeholders.
-
•
Measuring success in enterprise UX includes customer satisfaction, usage metrics, and tracking complaints to prioritize impactful fixes.
Notable Quotes
"Start knocking on doors immediately. There are people at your company who are domain experts and it’s your job to find them."
"Your fresh eyes are actually an asset. Question why things are done a certain way and what jargon means."
"If someone asks you for a cup of coffee, here’s the cup of coffee. You did it. But always have proposals on the side for more."
"Bad news does not improve with age. As soon as you get a whiff that something isn’t right, jump and fix it."
"Give a why of why you’ve made this design decision. It helps your team understand and reduces defensiveness."
"You are a contractor for your team. They want to know when the thing is done and that you delivered thoroughly."
"Designing in enterprise means facilitating conversations and educating your teams because many stakeholders don’t speak design."
"Tracking complaints and fixing things immediately, even if it’s just one person, is a mark of good UX impact."
"Create a UX brief with meetings and milestones so your PM knows where they need to be involved and where they don’t."
"Leading your path through ambiguity as a designer sometimes means teaching younger PMs how to work with you."
Or choose a question:
More Videos
"We have a responsibility to help heal communities and build trust so we can do design with intention."
Samuel MartinCo-Design vs Faux-Design: Navigating the Complexities of Sharing Power in Co-Design
March 27, 2026
"Being a manager is really hard, and just because you’re a great individual contributor doesn’t mean you’ll enjoy it."
Kayla Farrell Chelsey Glasson Sean Fitzell Jared LeClercWhat It's Like To Be a User Researcher at Compass
March 12, 2021
"You can’t really advocate for UX or move an organization forward without interacting with your team and business colleagues."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Pilot studies are a must; I always run a pilot session the day before full launch to refine my discussion guide."
Lily Aduana Savannah Hobbs Brittany Rutherford5 Reasons to Bring Your Recruiting in-House (and How To Do It)
March 12, 2021
"Serendipity happens when you explore across different journeys, personas, and contexts in the knowledge repository."
Tony TurnerCapturing Deep Insights
September 30, 2021
"Prioritization came from engaging all stakeholders cross-functionally through an intake process."
Marjorie Stainback Molly Fargotstein Stephanie MarshWhat Research Ops Professionals Have Learned from COVID-19
July 16, 2020
"We want participants to feel like they are an extended member of our team, part of a trusted inner circle."
Theresa MarwahHow Atlassian is Operationalizing Respect in Research
February 27, 2020
"You can change the time zone via a pull-down menu on the program page, and all session times will adjust accordingly."
Louis RosenfeldWelcome / Housekeeping
June 7, 2023
"Helen will bridge AI/ML towards engaging with data scientists to augment humanity with complex data."
Uday GajendarTheme Four Intro
June 6, 2023
