> Markdown version of [/videos/2109-software-rollouts-are-a-people-problem-meet-the-nine-change-management-monsters](https://www.wearedevelopers.com/videos/2109-software-rollouts-are-a-people-problem-meet-the-nine-change-management-monsters). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Software Rollouts Are a People Problem: Meet the Nine Change Management Monsters

Software rollouts don't fail over code; they fail because of communication debt and human chaos. Learn to defeat the nine change management monsters sabotaging your next big deployment.

- **Speakers:** [Nina Malakhova](https://www.wearedevelopers.com/@nina-malakhova)
- **Event:** World Congress 2026 Europe - Virtual Stage
- **Published:** July 3, 2026
- **Duration:** 28:06
- **URL:** https://www.wearedevelopers.com/videos/2109-software-rollouts-are-a-people-problem-meet-the-nine-change-management-monsters

## Summary

Software rollouts inevitably transform from objective technical deployments into subjective, chaotic human challenges. To navigate this volatility, rollouts must account for three vulnerability classes—communication, enablement, and technology—metaphorically termed "change management monsters." These project roadblocks, such as the stakeholder "disengager" or the outdated "legacy gremlin," feed on underlying communication debts that accumulate when teams prioritize implementing the "what" over explaining the "why." Because software expects a stable state while organizations are inherently organic, lasting adoption relies on targeted behavioral guidance rather than simply deploying new tools or increasing email announcements.

Combating these rollout bottlenecks requires applying specific governance frameworks to align stakeholders and maintain momentum. For instance, utilizing DACI or RAPID distinctly defines who owns, approves, or advises on decisions, neutralizing the "indecisive sludge" of unassigned responsibility. To secure stakeholder buy-in, the ADKAR model steps users through awareness and desire before rushing into "how-to" technical training. Meanwhile, controlling the "scope hydra" is streamlined by the MoSCoW matrix, where transparently communicating what *won't* be built is just as vital as detailing the MVP. When replacing beloved but outdated tools, the "strangler fig" strategy allows teams to slice away legacy systems piecemeal, reducing user friction significantly.

Underpinning these mitigation strategies is the proactive management of decision, ownership, narrative, and structural debts. Leaders must establish a rigorous single source of truth for Architecture Decision Records to avoid "Chesterton's Fence" scenarios—where new teams blindly destroy vital past processes because the rationale wasn't documented. Additionally, narrative debt is countered by persistently retelling the product's core story across multiple channels, recognizing that adults typically must encounter a message seven times to retain it. Ultimately, the objective of managing these factors isn't to operate with zero friction—which can stall shipping pipelines entirely—but to cultivate a launch culture characterized by explicit accountability, documented rationale, and zero organizational surprises.

**Keywords:** software rollout adoption, enterprise change management, organizational communication debt, decision governance frameworks, daci decision matrix, rapid governance model, adkar adoption model, directly responsible individual, chesterton's fence principle, architecture decision records, moscow priority matrix, strangler fig migration, gartner time framework, legacy software phase-out, single source of truth, narrative alignment strategy, technology scope creep, stakeholder resistance management

## Chapters

1. **Differences between software development and enterprise software rollouts** (00:00) — Adapting to human unpredictability is necessary because organizational change operates differently than standardized software development.
1. **Fixing stakeholder disengagement using the DACI role framework** (03:06) — Re-engaging ghosting stakeholders requires aligning the product narrative and explicitly defining project decision roles.
1. **Preventing meeting bloat through single source of truth documentation** (05:25) — Repeated alignment meetings can be eliminated by enforcing a searchable and written source of truth.
1. **Breaking organizational indecision loops using the RAPID framework** (06:25) — Clarifying decision-making roles accelerates project progress in organizational cultures that hesitate to commit.
1. **Mitigating single points of failure in software project teams** (07:36) — Rotating tasks and documenting processes prevents project stalls when key individuals are suddenly unavailable.
1. **Overcoming user resistance to change through the ADKAR model** (09:06) — Building user awareness and desire before teaching new functionality increases overall software adoption success.
1. **Empowering local champions for effective organizational software training** (10:28) — Leveraging respected peers for localized enablement yields substantially better training outcomes than formal sessions alone.
1. **Controlling project scope creep using the MoSCoW prioritization matrix** (11:20) — Communicating precise boundaries on what will not be built prevents unmanageable project feature requests.
1. **Phasing out legacy software via the strangler fig approach** (12:29) — Slicing away functionality piece by piece significantly reduces the friction of abandoning familiar legacy systems.
1. **Eliminating overlapping software toolsets with the TIME framework** (13:37) — Categorizing tool redundancies into tolerate, invest, migrate, or eliminate clarifies the organizational technology stack.
1. **Documenting project reasoning to avoid architectural decision debt** (14:29) — Recording the rationale behind previous choices prevents future teams from blindly accepting or completely breaking systems.
1. **Resolving diffuse responsibility to prevent project ownership debt** (17:41) — Assigning directly responsible individuals guarantees that critical decisions and complex workflows are actively managed.
1. **Standardizing project narratives to reduce stakeholder misunderstanding** (20:08) — Retelling a consistent core message across multiple channels cements strategic alignment throughout the organization.
1. **Restructuring communication flows to prevent institutional knowledge loss** (23:27) — Designing intentional asynchronous information repositories stops valuable context from leaking out of suboptimal chat threads.
1. **Strategic acceptance and management of enterprise communication debt** (24:55) — Recognizing when to tactically defer alignment allows teams to balance thorough documentation with shipping velocity.

## Related Moments

- [Overcoming developer resistance to accelerate software deployments](https://www.wearedevelopers.com/videos/1069-100-times-more-frequent-deployments-how-did-we-create-a-high-performance-team) (from "100 times more frequent deployments: How did we create a high performance team?")
- [Recognizing the social realities of technical migrations](https://www.wearedevelopers.com/videos/100164-the-migration-cookbook) (from "The Migration Cookbook")
- [Communicating purpose during organizational software transformations](https://www.wearedevelopers.com/videos/1701-how-visionary-leaders-drive-transformation) (from "How Visionary Leaders Drive Transformation")
- [Key takeaways for navigating software evolution and technical debt](https://www.wearedevelopers.com/videos/100006-you-will-migrate-eventually-a-developer-approach-to-technology-adoption) (from "You Will Migrate Eventually: A developer approach to technology adoption")
- [Using failed adoption to drive necessary architectural improvements](https://www.wearedevelopers.com/videos/100233-when-human-meets-canary) (from "When human meets canary")
- [Identifying core challenges in modern software development](https://www.wearedevelopers.com/videos/1023-from-zero-to-hero-launch-manage-your-cloud-apps-with-free-openshift-red-hat-developer-hub) (from "From Zero to Hero: Launch & Manage Your Cloud Apps with Free OpenShift & Red Hat Developer Hub")

## Related Articles

- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [Events like RSAC Get You CISOs. Developers Decide What Actually Gets Deployed.](https://www.wearedevelopers.com/magazine/693-events-like-rsac-get-you-cisos-developers-decide-what-actually-gets-deployed)
- [Ignore the Hype: How to Avoid Being Deceived by Technological Trends](https://www.wearedevelopers.com/magazine/528-ignore-the-hype-how-to-avoid-being-deceived-by-technological-trends)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Staff Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1470125-staff-software-engineer-database-infrastructure) at **GitHub**
- [Principal Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1465908-principal-software-engineer-database-infrastructure) at **GitHub**
- [Release Manager](https://www.wearedevelopers.com/jobs/ext/1631545-release-manager) at **BWI GmbH**