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
"Legacy interconnected systems mean improving one area can create problems in another, and we don't always know those constraints upfront."
Alexandra SchmidtEnterprise UX Playbook
December 1, 2022
"Half-day Fridays is a way for us to give back to ourselves and promote work-life balance."
Jen Crim Jess Quittner Saritha Kattekola Alex Karr Gurbani PahwaCulture, DIBS & Recruiting
June 11, 2021
"Use your UX skills to design better working relationships by empathizing with colleagues like you do with users."
Christian CrumlishAMA with Christian Crumlish, author of Product Management for UX People
March 24, 2022
"We have to slow down hiring to be more thoughtful and deliberate about who we bring on the team."
Libby MaurerTreating Diversity & Inclusion in Hiring as a Design Problem
December 5, 2019
"When we engage people in the planning process, they take ownership of their city."
Ali Jeffery Sheri ChudowHow DesignOps Helped Enable Wall Street to Work Remotely
October 22, 2020
"Hugh Dubberly argues we should stop describing design as problem solving and instead see it as engaged conversation."
Daniel GloydDesigning From the Inside Out: How Method Acting Can Inspire Design Research
February 12, 2026
"When we tailor education to individual needs, everyone benefits."
Kristin SkinnerFive Years of DesignOps
September 29, 2021
"Design strategy focuses on providing a framework for developing design solutions that support a given product strategy, whereas product strategy addresses the business model, the roadmap, and prioritizing requirements - Frank Guo."
Johanna KollmannInsights-Driven Product Strategy: Get your Research to Count
December 6, 2022
"Human behavior is anything but linear, rational, or predictable."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
