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
"You need to believe what you’re doing is the right approach. You need to believe in your own skills and your team’s skills."
Megan KiersteadYou Are a Badass at UX: Overcoming Imposter Syndrome
March 10, 2021
"Machine intelligence can elevate experiences by easing frictions and amplifying human judgment and agency."
Josh Clark Veronika KindredSentient Design, AI, and the Radically Adaptive Experience (1st of 3 seminars)
January 15, 2025
"The average user doesn’t exist."
Samuel ProulxDesigning beyond caricatures: Embracing real, diverse user needs
December 4, 2024
"You have to present UX value from the stakeholder’s perspective: what will John the developer get from doing this?"
Kit Unger Jackie Ho Veevi Rosenstein Vasileios XanthopoulosTheme 2: Discussion
January 8, 2024
"It’s not enough to build a repository and expect people to come; you need a distribution strategy to put research where users are."
Ben Davies Matt Duignan Andrew Michael Dr. Emily DiLeoExpert Panel: The Principles of Research Repository Design
March 11, 2022
"Tracking users without their understanding breaks the trust we need to build ethical products."
Matteo GrattonCan Data and Ethics Live Together?
October 1, 2021
"It’s often large B2B enterprise products that really warrant the most from some robust design ops practices."
Ryan Matthew Alex KurchevDesignOps without Boundaries: Building More with What You Have
September 10, 2025
"Co-creation is the single best way to get people to really buy into the ideas and use the design system properly."
Dave Malouf Amy ThibodeauPanel: Design Systems and Documentation
November 7, 2017
"Psychological safety comes from having hard conversations upfront and requires demonstration from leadership."
Christopher Taylor Edwards Valerie RoskeDesign as a Team Practice, A Practical Guide to Cross-functional Collaboration
September 30, 2021
Latest Books All books
Dig deeper with the Rosenbot
Who within healthcare organizations are natural allies for UX practitioners and how can these relationships be leveraged?
How can AI-assisted daily analysis sessions with clients enhance stakeholder engagement?
What is the evolving role of researchers of one in organizations practicing democratized research?