Sign in with LinkedInWhy Too Many Government Modernization Efforts Fail
This article explains why so many government modernization efforts fail and discusses what steps to implement to drive change within government organizations. Please contact DALY to learn how to drive change within government agencies.
Frequently Asked Questions
Why do so many government modernization projects fall short?
Many government modernization efforts fall short because they treat the work as a **technology project**, not an **organizational change effort**.
On paper, solutions like digital modernization, PMO stand-ups, enterprise risk management (ERM), shared services, AI, and CX look like they will **speed, streamline, standardize, and modernize** operations. In practice, they often overlook how much the organization itself needs to change for these solutions to work.
For example:
Most projects assume that once people see how “obvious” or “smart” a solution is, they will quickly get on board. But change is rarely linear or clean. The moment you plan an **enterprise solution**, you are triggering a process that affects **everything and everyone** across the organization.
In short, modernization fails when agencies:
Successful modernization requires treating **organizational change as both a prerequisite and a consequence** of any enterprise solution—and leading both with equal discipline.
On paper, solutions like digital modernization, PMO stand-ups, enterprise risk management (ERM), shared services, AI, and CX look like they will **speed, streamline, standardize, and modernize** operations. In practice, they often overlook how much the organization itself needs to change for these solutions to work.
For example:
- A new website project may reveal deeper issues: siloed content, uncoordinated production, and limited cross-department communication. The real problem isn’t the website; it’s the **underlying business model and organizational structure**.
- An ERM initiative may stall because staff are reluctant to identify risks that could expose team weaknesses, create more work, or affect their standing with supervisors. In this case, **resistance to change becomes a risk in itself**.
Most projects assume that once people see how “obvious” or “smart” a solution is, they will quickly get on board. But change is rarely linear or clean. The moment you plan an **enterprise solution**, you are triggering a process that affects **everything and everyone** across the organization.
In short, modernization fails when agencies:
- Focus on tools instead of behaviors, incentives, and culture.
- Underestimate resistance to change and fear of loss of control.
- Skip structured change management and communication.
Successful modernization requires treating **organizational change as both a prerequisite and a consequence** of any enterprise solution—and leading both with equal discipline.
How should agencies build change management into modernization from day one?
To make modernization stick, agencies need to design **organizational change** into the initiative from the beginning, not bolt it on at the end. A few practical steps:
1. Create a dedicated change plan (not just a project plan)
2. Start with the leadership team—and be direct
3. Don’t wait for perfect clarity before communicating
4. Test your messaging from the employee’s point of view
5. Acknowledge uncertainty and lead through it
When agencies treat enterprise solutions as being **about people as much as technology**, they can reimagine how work gets done and reduce the risk that modernization efforts stall or fail.
1. Create a dedicated change plan (not just a project plan)
- Clearly describe the **vision and goals** of the change.
- Explain **why the change is needed** and **why it’s needed now**.
- Commit to **informing and engaging stakeholders** throughout the process, not just at launch or go-live.
2. Start with the leadership team—and be direct
- Align leaders on what they personally will need to **change in their own behavior**, not just in their talking points.
- Ensure leaders present **consistent verbal and behavioral messages** about the initiative.
- Avoid vague, lofty language that leaves people unsure what is actually happening.
3. Don’t wait for perfect clarity before communicating
- Leaders often delay communication until every detail is decided. By then, trust may already be eroding.
- Share what you know, when you know it, and be transparent about what is still being worked out.
4. Test your messaging from the employee’s point of view
- Put yourself “on the receiving end.” If you say automation will “free people up to be more strategic,” spell out what that means for **day-to-day work**.
- Ask: Would this message make sense to me if I were in their role? What questions or worries would I have?
5. Acknowledge uncertainty and lead through it
- Any meaningful change involves **uncertainty**. Your role as a change leader is to talk about what is known and what is unknown.
- Progress often looks like merging into traffic: you have to keep moving to find the opening. Standing still doesn’t create clarity.
When agencies treat enterprise solutions as being **about people as much as technology**, they can reimagine how work gets done and reduce the risk that modernization efforts stall or fail.
What role should leaders play in successful government modernization?
Leaders are central to whether modernization efforts succeed or stall. Their role goes far beyond funding and tool selection. They are responsible for **owning and modeling the change** the organization needs to make.
Key responsibilities include:
1. Co-owning the change, not delegating it
2. Communicating early, clearly, and honestly
3. Building and sustaining trust
4. Normalizing discussion of risk and resistance
5. Framing modernization as an enterprise journey
When leaders actively embrace these responsibilities, modernization efforts can **reshape how the organization works**, rather than simply layering new technology on top of old ways of operating.
Key responsibilities include:
1. Co-owning the change, not delegating it
- Leaders must agree on what they will **personally change**—in decisions, priorities, and behaviors—to support the initiative.
- If leaders stay anchored to their existing “spans of control,” enterprise efforts like unified taxonomies, shared services, or ERM will struggle.
2. Communicating early, clearly, and honestly
- Talk about the change **before every detail is finalized**.
- Avoid overly general or aspirational language that leaves staff guessing what will actually change.
- Explain both the **benefits** and the **impacts** on how people work.
3. Building and sustaining trust
- When information is delayed or vague, **confidence in leadership erodes**, especially where trust was already fragile.
- Leaders should be transparent about trade-offs, risks, and unknowns to maintain credibility.
4. Normalizing discussion of risk and resistance
- In areas like ERM, leaders need to make it safe to **surface risks** without fear of punishment.
- They should treat resistance as **data** about concerns and incentives, not as disloyalty.
5. Framing modernization as an enterprise journey
- Leaders should consistently reinforce that enterprise solutions affect **the entire organization**, not just a single system or team.
- They need to help staff see how changes connect to the agency’s mission and to better service for the public.
When leaders actively embrace these responsibilities, modernization efforts can **reshape how the organization works**, rather than simply layering new technology on top of old ways of operating.
