You Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
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
"We can use mental model skylines with thinking styles to find support gaps we didn’t see before."
Indi YoungThinking styles: Mend hidden cracks in your market
January 8, 2025
"I feel like probably the luckiest person here. And I have COVID."
Chris GeisonTheme 1 Intro
March 9, 2022
"Math models don’t just provide numerical precision, they can be inspirational for thinking about UX spread."
Scott PlewesWhy Isn't Your UX Approach Going Viral?: A Mathematical Model
March 28, 2023
"Building on AI and generative AI means giving up control."
Katie JohnsonDisrupting generative AI products with just-in-time consumer insights
June 4, 2024
"Shared outcomes and shared goals are critical to any measurement initiative."
Kristin Skinner Kamdyn Moore8 Types of Measures in Design Operations
April 16, 2020
"Everybody involved in product making should have empathy for each other, not just for the customer."
Monty HammontreeThe Future of UX Research
December 3, 2020
"We are designing data services for developers, not final clinician-facing experiences."
Lais de Almeida Maria IzquierdoDesigning Data Services
December 4, 2024
"Clarity and cruelty are different things; you want directness without belittling."
Joshua GravesWe Need To Talk: Addressing Unmet Expectations (Part 2 of 3)
April 28, 2025
"Psychological safety is far and away the key ingredient for teams being effective."
Brenna FallonLearning Over Outcomes
October 24, 2019
