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
"When adversity arises, showing your team aims at the same business target lowers chances of negative impact."
Bassel Deeb Will OsbornDo More With Less: Equip and Lead Design Orgs Through Adversity
October 2, 2023
"UX researchers are really good at applying their methods to people outside the business but terrible at applying them to the leaders they work with."
Sarah Alvarado Nalini P. Kotamraju Anne Mamaghani Peter MerholzHow to make UX research leadership more effective [Advancing Research Community Workshop Series]
October 26, 2023
"Designers adhere to standards not scientific ones, but design rigor tailored to dealing with complexity."
Yoel SumitroActions and Reflections: Bridging the Skills Gap among Researchers
March 9, 2022
"We’re trying to build a design operations role that balances top-down governance with bottom-up community building."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"Don’t send your recruiters to spam LinkedIn. That damages your brand and turns off potential candidates."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
"Bots is like a perfect on-ramp for UX for AI."
Greg NudelmanDesigning Conversational Interfaces
November 14, 2019
"When have you hired the last time someone over 50 or someone who is disruptive and not just culture fit? You need those complementary people."
Silke Bochat5 Antifragile Strategies for a DesignOps 2.0
September 23, 2024
"What screen readers allow us to do is to jump directly to bits of content that we are interested in to replicate the visual experience of skimming a web page."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
September 29, 2021
"Leadership is a mode, not a title, and anyone can be a leader."
Nalini P. KotamrajuTwo Jobs in One: Being a “Leader who is a Researcher” and a “Researcher who is a Leader"
March 10, 2021
