Leading Organizational Change for Government Work
Leading Organizational Change for Government Work: A Field Manual for the Frozen Middle
Stop me if you’ve heard this one: A new administration drops a priority initiative. The SES sends out a “call to action.” PowerPoints are built. Town halls are held. Six months later, nothing’s changed except everyone’s email signature now includes a new acronym they don’t understand.
I’ve spent twenty-five years in Air Force acquisition—watching transformation efforts crash against the rocks of organizational inertia. I’ve seen billion-dollar programs die because we couldn’t change how we wrote requirements. I’ve watched talented teams disintegrate because leadership confused activity with progress.
Here’s the hard truth: Government organizations don’t resist change. They resist bad change. And most change efforts in federal spaces fail not because of obstinate bureaucrats, but because leaders approach organizational development like a product delivery instead of a partnership cultivation. They treat culture like a system to be engineered rather than an ecosystem to be stewarded.
If you’re leading change in government—from implementing new procurement methodologies to shifting program office culture—you’re not just managing a project. You’re conducting maneuver warfare in a bureaucracy where the terrain is human capital, the enemy is complacency, and your only ammunition is trust built through consistency.
This is operational leadership. This is where strategy meets the immovable object of “that’s how we’ve always done it.”
Strategic Foundations: Think Before You Torque
Before you schedule that all-hands meeting or draft your communications plan, you need to understand that government organizations aren’t broken Silicon Valley startups waiting for your disruption. They’re complex adaptive systems with twenty-year memories, congressional oversight constraints, and mission-critical continuity requirements that don’t permit “move fast and break things.”
Conduct Cultural Archaeology
In acquisition, we conduct site surveys before we build. Do the same with your organization. Map the informal power structures—the COR who’s been there since the Clinton administration, the budget analyst who actually knows where the bodies are buried, the contracting shop that can kill your initiative with a misplaced FAR interpretation. These aren’t obstacles; they’re your coalition waiting to be built.
Understand the why behind current processes. That “outdated” review process you’re eager to streamline? It probably exists because someone got burned in an IG audit in 2008. That “bureaucratic” approval chain? It ensures statutory compliance with the National Defense Authorization Act. Innovation within constraints means respecting the guardrails while optimizing the path between them.
Identify the Real Decision Space
In government, authority is often diffuse. Your chain of command might support your change initiative, but if you haven’t mapped the stakeholders two levels up and across functional boundaries, you’re building on sand. I learned this in program management: the program manager owns the baseline, but the resource sponsor owns the money, and the user representative owns the requirements. Ignore any one of these, and your change effort becomes a hobby.
Strategic patience isn’t passive. It’s active preparation while waiting for the alignment of stars—budget cycles, leadership transitions, and mission tempo. Rush this phase, and you’ll spend the next eighteen months repairing relationships instead of advancing the mission.
Operational Leadership: Move the Middle
This is where most change efforts die—in the operational tier between executive vision and tactical execution. The “frozen middle”—those GS-12 to GS-14 supervisors and middle managers who’ve survived three reorganizations and four “transformation initiatives”—aren’t resistant to change. They’re resistant to fad surfing.
Build the Coalition Before You Need It
In Air Force acquisition, we don’t go to war alone. We build integrated product teams. Do the same with your change initiative. Identify your:
- Champions: Early adopters with credibility, not just enthusiasm
- Skeptics: The respected voices who ask hard questions (convert them, and you’ve won the organization)
- Blockers: Those with informal veto power who need to be neutralized or co-opted
Never announce change from the podium. By the time you make it public, the decision-makers should already be convinced. I learned this from a three-star who never called a meeting to make a decision—only to ratify decisions made in smaller rooms. Your change process should work the same way.
Translate Strategy into Shared Meaning
Government workers don’t resist change because they love inefficiency. They resist when they can’t connect the dots between the new initiative and the mission. If you’re implementing agile acquisition methods, don’t talk about “scrums” and “sprints.” Talk about getting capability to the warfighter faster while maintaining statutory compliance.
Values-based decisions are your anchor here. Government employees swore an oath—to the Constitution, to the mission, to the public trust. Frame your change effort through that lens. “This new contracting approach isn’t about making our lives easier; it’s about ensuring we steward taxpayer dollars with the same rigor we’d demand for our own families.”
Manage the Narrative
In the absence of information, government organizations fill the void with worst-case scenarios. Control the narrative through radical transparency about what you know, what you don’t, and what decisions are still pending. When I led organizational changes in program offices, we published a “decision log”—every question asked, every answer given, every concern recorded. It built trust through vulnerability.
Remember: partners, not products. Your change initiative isn’t a deliverable you hand off to the organization. It’s a collaborative construction project where the users are the builders. If they don’t feel ownership, you’ll be managing resistance instead of momentum.
Tactical Execution: Execute with Discipline
This is where leadership becomes craftsmanship. You have your strategy. You’ve built your coalition. Now you have to execute without breaking the operational mission.
Pilot Before You Scale
Government organizations can’t afford “big bang” transformations. Use spiral development concepts on your change management. Identify a pilot group—a single division, one contract vehicle, a specific functional area—where you can prove the concept with minimal risk to the broader mission. Capture lessons learned with rigor. Government culture respects evidence over enthusiasm.
When I implemented new source selection methodologies, we didn’t roll them out base-wide. We started with one $5 million requirement. We documented every friction point. We refined the process. Only then did we expand. Strategic patience means accepting that sustainable change moves at the speed of trust, not the speed of PowerPoint.
Create Feedback Architecture
Install mechanisms for frontline truth-telling. The field knows where your change initiative is breaking before headquarters does. I used “sensing sessions”—informal, off-the-record conversations with practitioners about what was actually happening versus what the metrics showed. If your change creates workarounds, you’ve failed, regardless of what the checklist says.
Measure what matters. Don’t track “training completion rates” as a proxy for change. Track “decision velocity” or “compliance error reduction” or “stakeholder satisfaction.” Metrics should reflect mission outcomes, not activity completion.
Institutionalize the New Normal
Change fails when it remains dependent on the leader who initiated it. Your job is to make the new way of operating the path of least resistance. Update the manuals. Modify the performance standards. Align the incentive structures. If you’re changing how requirements are written, but the performance reviews still reward requirements volume over quality, you’ve built a contradiction that will break your change effort.
Strategic Takeaways: The Hard Truths
1. Resistance is Data, Not Defiance When people push back on your change initiative, they’re telling you where the organizational antibodies are strongest. Listen. That resistance often protects institutional knowledge or mission-critical functions you’ve overlooked. Treat it as intelligence, not insubordination.
2. Authority is Borrowed, Not Owned In government, your positional authority is temporary and conditional. Real change leadership comes from moral authority—demonstrated competence, consistent integrity, and genuine concern for the workforce. You can’t mandate cultural change; you can only steward it.
3. Constraints are Features, Not Bugs The FAR, security requirements, and oversight mechanisms aren’t obstacles to change—they’re expressions of democratic accountability. Innovation within constraints means finding elegant solutions that enhance rather than erode public trust. If your change can’t survive congressional scrutiny or IG audit, it’s not ready for government work.
4. Change is Maintenance, Not Transformation The most successful organizational changes in government aren’t dramatic pivots; they’re evolutionary improvements that respect institutional memory. Think in terms of “continuous process improvement” rather than “disruption.” The former sustains; the latter exhausts.
5. Your Legacy is the Next Leader’s Baseline Change succeeds when it survives leadership transitions. Build systems, not momentum. Document rationale. Create decision frameworks. Your successor will thank you when they inherit an organization that evolved rather than one that requires revolution.
Leading organizational change in government is the ultimate test of operational leadership. It requires the strategic vision to see the end-state, the political acumen to navigate stakeholder minefields, and the tactical discipline to execute without breaking the mission.
Remember: you’re not fixing a broken machine. You’re stewarding a living institution entrusted with the nation’s security, welfare, or prosperity. Treat that stewardship with the gravity it deserves. Move with purpose. Build with patience. Execute with integrity.
The mission depends on your craftsmanship.
Dr. Jesse W. Johnson, DSL, MAOM Founder, Craftsman Leadership