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
"You have to prepare research to withstand scrutiny by anyone so your team can go forward confidently."
Anna Avrekh Dr. John Pagonis Klara Pelcl Sina SchreiberExpert Panel: Leading in and with Research
March 10, 2022
"Impact of research is not always immediate or linear; it can be a long-term, complex process to measure."
Taylor KlassmanShaping the Next Era of UX Research: Collaborative Forum
March 11, 2025
"Organizations are racialized and systematically exclude qualified researchers of color."
Dr. Jamika D. Burge Steve Portigal Alba Villamil Sam LadnerThe Future of Research: Bridging the Gaps
July 29, 2021
"No surprises. Tell participants everything they’ll be experiencing from who will be in the room to if the session will be recorded."
Marisa BernsteinIt Takes GRIT: Lessons from the Small, but Mighty World of Civic Usability Testing
December 9, 2021
"You have to know what the development roadmap is to ensure design system changes are properly integrated and prioritized."
Dan Mall“Ask Me Anything” with Dan Mall, Author of Upcoming Rosenfeld Title, Design that Scales
October 2, 2023
"The researchers I know aspire to do lofty work, but we have a long way to go to get there."
Chris GeisonTheme 1 Intro
March 9, 2022
"It’s worth explaining your new communication approach to stakeholders to save their time and foster discussion."
Bruce GillespieLearning from journalism: Balancing impactful communication with compassionate storytelling
March 13, 2025
"If you put garbage in, garbage comes out – AI reflects the biases in its training data."
Nancy DouyonWe'll Figure That Out in the Next Launch: Enterprise Tech's Nobility Complex
June 15, 2018
"Will you become an advocate for the world’s most vulnerable voices muffled and unheard in complex systems?"
Liz EbengoThe Burden on Children: The Cost of Insufficient Post-Conflict Services and Pathways Forward
December 4, 2024
