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
-
•
Establishing an experience vision can align diverse teams towards a common goal.
-
•
Building a core task force enhances efficiency and decision-making in complex projects.
-
•
Embedded designers can help bridge gaps between different business units.
-
•
Iterative testing and feedback improve the design process and final product.
-
•
Trust is essential; fostering relationships can facilitate better collaboration.
-
•
Content strategy should not depend on a single individual to prevent project risks.
-
•
Kickoff meetings are critical for aligning expectations and responsibilities among stakeholders.
-
•
Service blueprints can provide clarity on complex backend processes and enhance stakeholder understanding.
-
•
Collaboration takes time but is ultimately beneficial for project success and user experience.
-
•
Reflection and retrospectives are vital for continuous improvement and learning.
Notable Quotes
"We learned quite a bit and we're here today to share that with you."
"The project was led by technology and the catalyst being an overhaul of the entire back-end infrastructure."
"The complex problem we were solving was not really solution-based at all; it was a cultural team alignment problem."
"An experience vision is a really powerful tool because it provides a tangible goal that everyone can work towards."
"When I asked for some work to be done, there was often crickets or, mm-hmm. Okay. Sure."
"The work that we do is fundamentally human, and the truth is, humans are messy."
"Retrospectives and reflections are a really big part of the culture within our design organization."
"Investing in people and relationships pays off in the long run."
"Without understanding the problem to be solved, we're left scrambling."
"What we are providing are experiences for fellow humans."
More Videos
"Job security in design is high because the work is complex."
John MaedaMaking Sense of Enterprise UX
June 9, 2016
"Instead of doing it by feature, what if we did it by thinking style?"
Indi YoungThinking styles: Mend hidden cracks in your market
January 8, 2025
"Measuring the wrong success indicators can stifle progress and growth."
Chris ChapoData Science and Design: A Tale of Two Tribes
May 13, 2015
"Time management in collaboration is more than just meeting deadlines."
Elizabeth ChurchillExploring Cadence: You, Your Team, and Your Enterprise
June 8, 2017
"We have to make sure that we are being mindful and inclusive."
Rusha SopariwalaRemote, Together: Craft and Collaboration Across Disciplines, Borders, Time Zones, and a Design Org of 170+
June 9, 2022
"The most common way people give up their power is by thinking they don't have any."
George AyeThat Quiet Little Voice: When Design and Ethics Collide
November 16, 2022
"We need to normalize video off for our meetings when people need a break from being on camera all day."
Ariba JahanTeam Resiliency Through a Pandemic
January 8, 2024
"Design thinking is a set of behaviors, not just a toolbox of methods."
Julie Gitlin Esther RaiceDesign as an Agent of Digital Transformation at JPMC
June 9, 2021
"The greater part of progress is the desire to progress again."
Matteo GrattonCan Data and Ethics Live Together?
October 1, 2021
