Summary
This is a case study of a strategic, enterprise-level IT project that was stalled due to organizational and cultural issues within company. By applying a few familiar research techniques and frameworks (and one unfamiliar modeling framework) towards understanding and solving organizational problems, the project team found its footing and was able to deliver a complex application that will position the company for success.
Key Insights
-
•
Project delays often arise from deep organizational and cultural issues rather than team incompetence.
-
•
Engaging stakeholders as co-creators in research recommendations boosts buy-in and eases persuasion.
-
•
Distinguishing immediate domain (project and industry) from extended domain (monitoring and success definitions) is critical to managing project scope.
-
•
Edgar Schein’s three levels of culture—artifacts, espoused beliefs, and unconscious assumptions—help reveal hidden organizational dynamics.
-
•
Cross-functional projects often fail due to siloed reporting and unconscious allegiance to functional areas over project teams.
-
•
Taking meeting minutes with named action items assigned to leaders reduced conflict and clarified accountability.
-
•
Pairing technical developers with subject matter experts enables translating complex domain knowledge into actionable design artifacts.
-
•
Soft systems methodology allows modeling of ‘soft’ organizational influences on project success, including norms and values.
-
•
Engagement challenges manifest at multiple levels: sponsors, project teams, and external stakeholders require targeted approaches.
-
•
Grassroots technical collaboration and integration efforts can succeed even when formal management engagement is lacking.
Notable Quotes
"When projects are late or delayed it’s often due to organizational and cultural issues rather than conduct of the project team."
"I like to engage my stakeholders as co-creators and co-discoverers so their ideas and concerns get reflected in recommendations."
"People on the project were reporting back to management in their silo, not talking to one another."
"I found the problem solver in the UI developer and identified the project’s sponsor who really felt the pain."
"Managers were asking for user stories but hadn’t done any analysis or design — they didn’t understand the scope."
"The difference between the way people talk about how things are done and how they are actually done reveals unconscious assumptions."
"Decision making here is basically forge trading — people argue and withhold support until they get what they want."
"Our technical leads started attending other teams’ meetings, helping break down integration barriers."
"At the turning point, the team realized they were in charge of their own process and got engaged."
"The biggest problem was to solve the engagement problem first with the sponsor, then the team, then external stakeholders."
Or choose a question:
More Videos
"Not everyone can become a great UX researcher, but a great UX researcher can come from anywhere."
Mackenzie GuinonM.C. Escher’s UX Research Career Ladder
March 9, 2022
"Disability isn’t a fixed group — aging, illness, injury can put anyone into a disabled state."
Gabriela BarnevaOperationalizing Inclusive Design in Service Design
November 20, 2025
"Observers interrupting sessions was a weird behavior we had to manage with clear rules."
Sarah RinkRemote User Research: Dos and Don'ts from the Virtual Field
June 11, 2020
"We’re not building to build, we’re building to learn."
Maria SkaadenContinuous Design: One eye on the horizon and the other on the next wave
November 8, 2018
"Cutting down on the analysis time was huge for us, speeding up speed to insight significantly."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"You need to review proposed changes before committing them to production, otherwise errors sneak in."
Jorge Arango[Demo] How to re-categorize content at scale using LLMs
June 5, 2024
"Make a case to hire people who are product agnostic to connect where products intersect in the rider journey."
Kristin TaylorBuilding Bridges Across Organizational Silos
November 18, 2022
"Don’t position yourself as the research expert; you are the expert in facilitating the quest for knowledge."
Anna Avrekh Dr. John Pagonis Klara Pelcl Sina SchreiberExpert Panel: Leading in and with Research
March 10, 2022
"Using AI to tighten the gap between design and engineering is essential to know how to use in our work right now."
Ryan Matthew Alex KurchevBridging Design and Code: AI-Powered Design System Integration
September 11, 2025
