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
"If you make an app that users only use once a year, don’t expect them to learn dozens of custom shortcuts."
Sam ProulxEverything You Ever Wanted to Know About Screen Readers
June 11, 2021
"You can access the digital swag bag by scanning the QR code or visiting fld.me/cd2022 for cool sponsor offers."
Bria AlexanderOpening Remarks
November 17, 2022
"You do not have to go publicly thank the employer who just laid you off. They’ll be fine without it."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"Shared language lets different roles venture out of their comfort zones and collaborate on changing the enterprise system."
Milan GuentherA Shared Language for Co-Creating Ambitious Endeavours
June 6, 2023
"Being involved early in product planning lets us bring the art and science of research to where it can be most helpful."
Erin May Roberta Dombrowski Laura Oxenfeld Brooke HintonDistributed, Democratized, Decentralized: Finding a Research Model to Support Your Org
March 10, 2022
"If you falsely think you are having the same experience as a native user, you become afraid of accessibility and say it's impossible."
Sam ProulxUnderstanding Screen Readers on Mobile: How And Why to Learn from Native Users
June 6, 2023
"For many of our tech clients, there’s a demand not just to use AI but to transparently show how and why, to respond to internal scrutiny."
Mujtaba HameedThe new horizon of ethnography: using AI to unlock the full potential of in-person research
March 11, 2026
"Technology generates as many new problems as new solutions."
Ilana LipsettAnticipating Risk, Regulating Tech: A Playbook for Ethical Technology Governance
December 10, 2021
"If we think disability as a mismatch between user and environment rather than a medical problem, it becomes easier to understand how accessibility benefits everyone."
Samuel ProulxFrom Standards to Innovation: Why Inclusive Design Wins
September 10, 2025