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."
Dig deeper—ask the Rosenbot:
More Videos
"Reflection in action involves noticing surprise, questioning assumptions, experimenting, and reflecting on the move."
Yoel SumitroActions and Reflections: Bridging the Skills Gap among Researchers
March 9, 2022
"If you are silent about your pain, they will kill you and say you enjoyed it."
Zariah CameronReDesigning Wellbeing for Equitable Care in the Workplace
September 23, 2024
"We make the invisible visible and turn abstract strategy into something people can see, touch, and act on."
Doug PowellDesignOps and the Next Frontier: Leading Through Unpredictable Change
September 11, 2025
"If you’re generating buy-in, don’t forget what it will mean for your difficult stakeholders—they may have external pressures you don’t know about."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Safe money has solid returns, so fiscally responsible companies demand higher returns from new investments especially with inflation."
Mike OrenWhy Pharmaceutical's Research Model Should Replace Design Thinking
March 28, 2023
"Design Ops is fundamentally a servant leadership role—guts, no glory, always supporting."
Jacqui FreyScale is Social Work
March 19, 2020
"Trust takes time, hard work, and consistency to build, especially in times of change when time is a luxury we don't have."
Kim Holt Emma Wylds Pearl Koppenhaver Maisee XiongA Salesforce Panel Discussion on Values-Driven DesignOps
September 8, 2022
"When we design for the edges, we get the middle for free."
Samuel ProulxFrom Standards to Innovation: Why Inclusive Design Wins
September 10, 2025
"This is not a checklist or promotion tool; you don’t have to excel in everything to grow."
Laine Riley ProkayHow DesignOps can Drive Inclusive Career Ladders for All
September 30, 2021
