Many government modernization efforts fall short because they treat the challenge as a technology problem, not an organizational one. New tools like digital platforms, shared services, AI, or enterprise risk management (ERM) frameworks are introduced to speed, streamline, and standardize work. But the organizational changes required to make those tools effective are often overlooked.

Two common patterns show up:

• Technology exposes existing organizational issues. For example, a new website project may reveal that content is siloed, production is uncoordinated, and teams don’t communicate across departments. The real barrier isn’t the content management system; it’s the underlying business model and spans of control.
• People resist changes to how work gets done. With ERM, staff may hesitate to identify risks because it could mean more work, expose weaknesses, or threaten their standing with supervisors. Standardizing risk practices across the enterprise can feel like a loss of local control, which creates resistance.

In short, technology solutions almost never address the organizational issues that are critical to success. When agencies don’t plan for behavior change, governance shifts, and new ways of working, even well-designed systems struggle to gain traction.

Any enterprise initiative will reshape how people work, communicate, and make decisions. That means organizational change needs to be built into the effort from the start, not treated as an add-on. A few practical steps help:

• Create a dedicated change plan. A project plan alone isn’t enough. Clearly describe the vision and goals, why the change is needed, and why it’s needed now. Commit to informing and engaging stakeholders throughout the process, not just at launch.
• Align the leadership team early. Begin at the leadership level and be candid. Leaders need to decide what they will change in their own behavior and how they will present a unified message—both in what they say and what they do.
• Recognize that change is non-linear. Many projects assume that once people see the value of a solution, they will automatically “buy in.” In practice, adoption is rarely clear-cut or linear. Expect pushback, questions, and the need to adjust along the way.

When agencies treat change as both a prerequisite to, and a consequence of, an enterprise solution, they are better positioned to reimagine processes and make the technology actually work in day-to-day operations.

Effective communication during modernization is less about having every answer and more about being clear, timely, and honest. Several practices help:

• Don’t wait for perfect clarity. Leaders often delay communication until every detail is decided. By then, messages can sound so high-level that employees still don’t know what’s happening. This can quickly erode confidence, especially where trust was already fragile.
• Test your messaging from the employee’s perspective. Put yourself on the receiving end. If you say automation will “free people up to be more strategic,” ask what that would mean to someone in a specific role. Will they understand how their day-to-day work might change? Adjust your language based on feedback.
• Acknowledge uncertainty directly. Any meaningful change involves uncertainty. Part of being a change leader is talking about what is known and what is not yet known. The role is to see uncertainty and proceed anyway—similar to merging into highway traffic: you move forward to find the opening, not the other way around.

Ultimately, enterprise solutions are as much about the people in the organization as the technology itself. Clear, candid communication about both change and uncertainty helps agencies rethink how they work and reduces the risk that modernization efforts will stall.