How to Drive a Design Project When you Don’t Have a Design Team
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
"Accessibility defects are bugs. If it’s a P1 blocking bug for an accessibility issue, treat it like any other P1 bug."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"The best products come from marrying analytics with human stories."
Prayag Narula Hannah HudsonEmpowering Designers to do Good Research
March 11, 2022
"Being open and flexible to what's most helpful for the team at that moment is key."
Janelle EstesUX Research Trends
January 28, 2021
"We often get designed into a corner by trying to fix words at the end instead of involving content designers earlier."
Craig Brookes Andreas Huebner Morgan Quinn"Just Make it Look Good" and Other Ways We're Misunderstood
June 11, 2021
"If you don’t feel connected and you’re standing alone, the challenge looks much bigger."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"Designing the service so the team can be efficient and impactful is essential — otherwise you just move the inefficiency around."
Kate TowseyThe State of ResearchOps: More Than Just Theory
June 20, 2019
"Psychological safety is the number one factor determining team effectiveness and performance."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 9, 2022
"The collaboration cycle requires following standards for accessibility, content, design system usage, and IA or you don’t launch your product."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"Being comfortable with discomfort is key — if someone tells me I'm wrong, I'm okay with that."
Tricia WangSCALE: Discussion
June 15, 2018
Latest Books All books
Dig deeper with the Rosenbot
What is continuous feedback in product and CX research, and how do tools support it?
Who are natural allies for healthcare UX professionals inside complex healthcare systems, and how do you engage them?
Why is prior authorization such a persistent problem and how can patient-centered solutions be designed around it?