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
"In Western modernity, if something is not an object, it is not real research or real knowledge."
Victor UdoewaBeyond Methods and Diversity: The Roots of Inclusion
March 26, 2024
"Every few years consultants come in and tidy up our mess, but as soon as they leave, we mess it all up again."
Peter MorvilleThe Architecture of Understanding
May 13, 2015
"You have to be careful not to be too weird; mental models differ internationally."
Sam LadnerHow Research Can Drive Strategic Foresight
March 9, 2022
"The feedback culture in our company means there’s transparent discussion if conclusions aren’t clear or agreed upon."
Michelle Bejian Lotia Anne-Marie MorellRolling Out a Repository: How Zapier Centralizes Insights from Across their Organization
March 28, 2023
"Empathy walls emerged at DTA because teams needed a visceral way to bring stories back from the field."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"Backcast from preferred or risky futures to start thinking about what we need to do today to get there or avoid that outcome."
Sarah GallimoreInspire Progress with Artifacts from the Future
November 18, 2022
"This is real serious analysis, not pre-prepared or fake data."
Joerg Beringer Thomas GeisScaling User Research with AI: Continuous Discovery of User Needs in Minutes
September 10, 2025
"Organize your product managers, designers, and engineers around customers, not features or code repositories."
Peter MerholzCustomer-Centered Design Organizations
June 8, 2017
"We have been focused for so long on getting that seat that we haven’t realized that a lot of us are actually already there."
Dalia El-ShimySo You've Got a Seat at the Table. Now What?
March 31, 2020