The Tale of Two Companies: Building a Successful UX Practice in a Century-Old Enterprise
Summary
Key Insights
-
•
At Ford, shifting from protecting UX turf to a culture of sharing and collaboration was key to UX team growth and success.
-
•
Creating and sharing usability patterns internally can increase UX advocacy even among non-UX staff.
-
•
Establishing a UX Club and informal meetups helps build internal UX networks and culture.
-
•
Building a component library aligned with usability patterns paved the way for a design system before that term was widely used.
-
•
Filling unaddressed enterprise needs proactively can lead to new service areas and team spin-offs.
-
•
Letting go of tasks like front-end coding allowed CN’s UX team to focus on core design and strategy.
-
•
A clear UX vision must be sold internally and then demonstrated through results to gain broader organizational buy-in.
-
•
Managing up and across by building networks is crucial to identify UX opportunities beyond the team’s immediate scope.
-
•
User story mapping and journey workshops can transform waterfall requirements into agile backlogs and broaden UX impact.
-
•
Expanding leadership roles beyond UX (e.g., business analysis) can amplify the influence of UX in an enterprise.
Notable Quotes
"My job was to insulate my team from the pressures and not let anyone else do UX work. That was wrong."
"It was like publishing the family secret recipe, but sharing usability patterns was crucial for advocacy."
"We created a UX Club to talk shop, share struggles, and build ideas across teams."
"We didn’t know what a design system was, but by combining component libraries and usability patterns, we built one."
"Sometimes you have to fill a need even if there’s no formal name or structure for it yet."
"UX must operate beyond the pixel to have real impact in enterprise transformation."
"Be an expert but act as a collaborator. It’s a team sport."
"Managing up and across started with lots of coffees and questions to build a mental model of the organization."
"The team brought structure and clarity by mapping requirements into user journeys and stories."
"You owe it to your organization and your team to grow the practice while staying true to your vision."
Or choose a question:
More Videos
"We shifted from building each application type individually to creating a platform that planners can use to build their own."
Laura Smith Tom GaylerEmbedding Service Design and Agile Practice within UK Planning Teams to Create Services that Last
December 3, 2024
"People get stuck during the sessions when asked to describe their brand voice in just one or two words."
Trisha Causley[Demo] Complexity in disguise: Crafting experiences for generative AI features
June 5, 2024
"Not every recommendation from ChatGPT was feasible for the Nigerian context, so human collaboration was essential."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Developing team flow is a lot like dating—you have to nurture it, build instinct, and practice."
Ruzanna RozmanGetting in Flow with Your Team
January 8, 2024
"AI-powered enterprise tools sit on top of the classic IA infrastructure; without it, AI can’t scale effectively."
Karen McGrane Jeff EatonAI for Information Architects: Are the robots coming for our jobs?
November 21, 2024
"This method has a degree of reactivity; paying attention to something may alter or change behavior."
Amelia ColeData-Prompted Interviews
December 17, 2021
"Give non-researchers some applause when they run a test even if it's not perfect, then help them do it differently next time."
Trisha TerharEmpathizing with the Empowered: Non-Researcher Responses to Democratization
March 10, 2022
"Every spreadsheet is emotional. It’s a stage direction."
Jen van der MeerService design performs value
November 19, 2025
"I prefer techniques where individuals generate ideas quietly first, so their train of thought isn’t lost in group dynamics."
Steve Baty Richard Dalton Maria Giudice Harry MaxDiscussion
June 9, 2016
