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
"The linchpin of a good design space is a high top table for ad hoc gatherings without interruptions or formal scheduling."
Dave MaloufClosing Keynote: Amplify. Not Optimize.
October 24, 2019
"Requesting glossy portfolios up front risks excluding candidates with strong problem-solving skills who may not have had opportunities to showcase visual design."
Anna Avrekh Amy Jiménez Márquez Morgan C. Ramsey Catarina TsangDiversity In and For Design: Building Conscious Diversity in Design and Research
June 9, 2021
"Operations is the de-risking activity that creates scalable processes for better outcomes - Theresa."
Bria Alexander Patrizia Bertini Peter Boersma Jon Fukuda Dave Malouf Theresa Slate Changying (Z) ZhengCharting the future of DesignOps: A community workshop
April 18, 2024
"Design system adoption exploded when we focused on the needs of everyone who builds, extends, or uses it."
Luca RagerEmpowering Gaming at Scale: How Xbox Builds Powerful, Automated, and Distributed Design Systems with Sketch
September 30, 2021
"My job wasn’t to do good IA, it was figuring out how to be allowed to do good IA."
Sarah BarrettThe "How" of Enterprise Information Architecture
June 6, 2023
"Actors as standardized patients allow safe practice of healthcare scenarios when live environment testing is too risky."
Carol MassaDesigning Health: Integrating Service Design, Technology, and Strategy to Transform Patient and Clinician Experiences
December 3, 2024
"We don’t call anyone a product manager in our org, but as a product boss, I wear that hat and help designers grow into that ownership."
Wendy JohanssonBe a Product Boss!
December 6, 2022
"Carbon is just the starting point for what can be imagined. We're hired for our expertise to adapt, not just follow directions."
Mitchell BernsteinOrganizing Chaos: How IBM is Defining Design Systems with Sketch for an Ever-Changing AI Landscape
September 29, 2021
"A lot of design ops impact comes from influence, and influence comes from empathy and showing the benefit of what you are putting out."
Bria Alexander Laura Gatewood Corey Long Daniel Orbach Laine Prokay Deanna SmithThe Big Question about Resilience: A panel discussion
September 23, 2024
Latest Books All books
Dig deeper with the Rosenbot
What are the benefits and challenges of pairing engineers and designers in small, focused pods for product development?
In what ways does role fluidity impact collaboration, and how should expertise be respected across domains?
Why is the absence of self-governing professional institutions a challenge for the design field?