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
"Business leaders are super busy, data-driven, competitive, and have a finely tuned bullshit meter."
Doug PowellClosing Keynote: Design at Scale
November 8, 2018
"Matching researchers by language and culture makes children more comfortable and improves consent."
Mila Kuznetsova Lucy DentonHow Lessons Learned from Our Youngest Users Can Help Us Evolve our Practices
March 9, 2022
"Artifacts of the future help us envision and grasp the change that we’re hoping to have—it’s not just bullet points or vision statements."
Sarah GallimoreInspire Progress with Artifacts from the Future
November 18, 2022
"Field usability testing showed stakeholders immediately how much value UX can add by catching issues before deployment."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Who deals with chaos, ambiguity, and disruption best? It’s us, design operations humans."
Alnie FigueroaThe Future of Design Operations: Transforming Our Craft
September 10, 2025
"Mixed methods research, combining qualitative and quantitative, gives the fullest understanding of customer experience."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"When you encounter an obstacle, how do you respond? Maybe it’s an invitation to grow."
Emily EagleCan't Rewind: Radio and Retail
June 3, 2019
"No two re-platforming journeys are exactly the same, and there isn't one single formula that works every time."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Designers are often seen as bottlenecks because our work is harder to estimate and track than engineering’s."
Asia HoePartnering with Product: A Journey from Junior to Senior Design
November 29, 2023
Latest Books All books
Dig deeper with the Rosenbot
How can organizations democratize accessibility knowledge among designers, developers, and researchers?
How do champions at different organizational levels impact the success of service design initiatives?
Who are the multiple user types involved in designing services for public sector innovation portfolios?