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
"Keeping something cloud-based accessible is the most complicated because of hundreds of releases per day in continuous integration."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"Data tells you what happens; qualitative research tells you why it happens."
Prayag Narula Hannah HudsonEmpowering Designers to do Good Research
March 11, 2022
"Don't just flip the switch and say go talk to customers; you have to set guardrails and train people."
Janelle EstesUX Research Trends
January 28, 2021
"We often get designed into a corner by trying to fix words at the end instead of involving content designers earlier."
Craig Brookes Andreas Huebner Morgan Quinn"Just Make it Look Good" and Other Ways We're Misunderstood
June 11, 2021
"The community is an ongoing prototype; members have a strong, frequent voice in shaping what good looks like."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"Engagement and impact roles bring creativity and help maintain team morale in otherwise dry operations work."
Kate TowseyThe State of ResearchOps: More Than Just Theory
June 20, 2019
"Co-regulation means someone who is safe can help bring another out of a triggered state."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 9, 2022
"We have over 30 contracting teams spread across roughly 10 vendors all working on parts of the veteran experience landscape."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"I've thrived on being wrong and making mistakes, even when I wasn't actually wrong."
Tricia WangSCALE: Discussion
June 15, 2018
