Summary
In enterprise organizations, product development work, and therefore, design work, typically happens within a specific business unit or organization. Dedicated and embedded squads means there is a close and tight feedback loop between team members. But what happens when your company kicks off an initiative that spans across business units? How do you resource and run a design project with no dedicated designers? This case study will cover how we set out a vision, structured communications, built up an ad-hoc design team, shipped our first cross-organization product and all the lessons we learned along the way.
Key Insights
-
•
Unifying a sign-in experience across siloed business units requires cultural alignment more than just technical design.
-
•
An experience vision that is agnostic of technology helps align diverse stakeholders effectively.
-
•
Empowered small core teams can accelerate decision-making and maintain project momentum.
-
•
Embedding designers fractionally from different business units enables scalable design collaboration without a dedicated central team.
-
•
Rapid iterations and mixed usability testing approaches help identify issues early across modules and terminology.
-
•
Lack of prior trust among designers from different units hinders collaboration and slows progress.
-
•
Conflicting roadmaps and priorities between business units create complexity in resourcing shared projects.
-
•
Over-reliance on a single content strategist created a risky single point of failure for messaging consistency.
-
•
A formal kickoff meeting is crucial to align scope, roles, and expectations, even if delayed.
-
•
Service blueprints provide a valuable deeper view into backend systems and stakeholder responsibilities often overlooked in UI-focused maps.
Notable Quotes
"The complex problem we were solving was not really solution based at all. It was a cultural team alignment problem."
"The experience vision provided a tangible goal that everyone could work towards, focusing on the user's experience rather than the technology."
"Consistency over business unit efficiency meant choosing a unified interface over letting each business unit do their own thing."
"We formed a core task force empowered to make decisions quickly, avoiding weeks of delay waiting for formal approvals."
"I wish I’d spent more time cultivating relationships and trust with the designers embedded in other business units."
"Our content strategist was a single point of failure—when she left, we scrambled to pick up unfinished work."
"There was never an official kickoff meeting to align all stakeholders and set clear expectations."
"A service blueprint would have helped show the complex backend systems supporting what looks like a simple user interface."
"Investing time in people, relationships, and collaboration pays off in stronger teams and better user experiences."
"The work we do is fundamentally human, and humans are messy—sometimes things work, sometimes they don’t."
Or choose a question:
More Videos
"If you don't have good usability to begin with, being trauma-informed is not going to work out."
Carol Scott Melissa EgglestonAvoid Harming Your Team and Users: Promoting Care and Brand Reputation with Trauma-Informed UX Practices
February 5, 2025
"Regulations are design problems, not just technical ones, influencing how we create products and experiences."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"Mobile accessibility features are built in and ready to go without needing to install or configure anything extra."
Sam ProulxMobile Accessibility and You
June 9, 2022
"Remote work is totally different from working from home during a worldwide pandemic."
Ana FerreiraDesigning Distributed: Leading Doist’s Fully Remote Design Team in Six Countries
January 8, 2024
"I used GPT-4 to retag 1,200 blog posts, reducing an estimated 10–12 hours of tedious manual work to about a third of that time."
Jorge ArangoScale Smart: AI-Powered Content Organization Strategies
September 24, 2024
"No doctor wants to use an EHR; we’re often the least bad option in a field full of poor usability."
Chris MosesStretching the Definition of DesignOps with Product Development
November 7, 2018
"When you’re building a specific AI feature, you don’t want to make your user write their own prompt."
Trisha Causley[Demo] Complexity in disguise: Crafting experiences for generative AI features
June 5, 2024
"There’s a perception that generative AI is gonna change everything, but I think it’s gonna transform, not totally overhaul mine."
Clara Kliman-SilverUX Futures: The Role of Artificial Intelligence in Design
June 7, 2023
"An org chart is about formal reporting; a relationship map is about networking and collaboration across silos."
Michael PolivkaScaling Design through Relationship Maps
November 7, 2017
