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 originate from organizational and cultural issues rather than team capabilities.
-
•
Engaging stakeholders as co-creators improves buy-in and eases persuasion.
-
•
Understanding both immediate and extended domains helps clarify project boundaries and success criteria.
-
•
Unstated cultural assumptions drive unconscious behaviors that impede project progress.
-
•
Cross-functional projects often fail when participants prioritize their silo over the project team.
-
•
Taking meeting notes and assigning action items with responsible managers reduces conflict and clarifies accountability.
-
•
Pairing technical and domain experts to create detailed process flows enables better user story creation and shared understanding.
-
•
Facilitating after-action reviews and empowering teams to lead meetings fosters ownership and engagement.
-
•
Assigning team members to participate in related projects’ meetings improves cross-team integration and collaboration.
-
•
Soft Systems Methodology can visualize intangible organizational and cultural influences that affect project outcomes.
Notable Quotes
"Project delays are frequently due to organizational and cultural issues rather than actions of the project team."
"I like to engage my stakeholders as co-creators and co-discoverers because that makes persuasion so much easier."
"A cross-functional project in name only means people report back to their management silos, not to the project team."
"In many organizations, people believe the team from their functional area is their real team, not the cross-functional project team."
"Taking meeting minutes and assigning action items with director names reduced arguing and helped move things forward."
"We converted process boxes directly into user stories to create a common language for the team."
"The project team gradually realized they were in charge of their own process and could get work done."
"We assigned people to attend other teams’ meetings to help with integration and started being seen as leaders."
"Hardest to uncover are the unconscious assumptions people make about how things should be done."
"Sometimes you just have to do what you can and come back to it later when analyzing culture versus delivery demands."
Or choose a question:
More Videos
"Sometimes you’re the leader, sometimes you’re at the end, sometimes you’re trying to get other folks to come in."
Jennifer KanyamibwaCreating the Blueprint: Growing and Building Design Teams
November 8, 2018
"Having a repo isn’t the same as having a strategy for socializing and evangelizing the research."
Brigette Metzler Dana ChrisfieldResearch Repositories: A global project by the ResearchOps Community (Videoconference)
August 27, 2020
"We assigned people to attend other teams’ meetings to help with integration and started being seen as leaders."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Design will never be able to stay static; it is how you show up responding to probing the system daily."
John Mortimer Milan Guenther Lucy Ellis Patrick QuattlebaumPanel Discussion
December 3, 2024
"Fifty percent of our designers were already active in coaching or mentoring, yet there was a call for a different mentorship flavor."
Dante GuintuHow to Crush the Talent Crunch
September 8, 2022
"Fourth order design is about understanding the system structure and how we intervene to create new pathways of experience."
Richard BuchananCreativity and Principles in the Flourishing Enterprise
June 15, 2018
"Shemus Bern is going to talk about how you drop into a client site and grok what’s going on without losing why they hired you."
Dan WillisTheme 3: Intro
January 8, 2024
"Failure is only the beginning."
Dan WardFailure Friday #1 with Dan Ward
February 7, 2025
"We don't just need to do a better job of articulating our value. We need to become more valuable."
Chris GeisonTheme Two Intro
March 28, 2023