Michelle Sutter, a director on the Board of the Senior Executives Association, explains why the practitioner needs to be front and center.
There are a lot of conversations happening right now about government modernization and reform. Panels. White papers. Initiatives. Task forces. Bold ideas about how to fix what is broken.
That is a good thing. We need those conversations.
But what is missing too often is the practitioner perspective. The voice of people who have actually operated inside federal agencies. The people who understand how policies turn into processes, how systems interact, and how work actually gets done on the ground.
Without that perspective, we risk repeating a familiar pattern. Well-intentioned reforms that look promising on paper struggle when it comes time to implement them.
If we are serious about modernization, the first question we need to answer is not what policy should change. It is, ‘What outcome are we trying to achieve?’
Until those questions are clearly answered, the impact of reforms will continue to be diluted.
We can change legislation. We can issue new guidance. We can launch initiatives. But if the purpose and desired end state are not clearly defined, it becomes extremely difficult to build something that is implementable, sustainable and effective.
Modernization is not just about speed or efficiency. It is about coherence.
Shared services offer a clear example.
Across the federal government, agencies often operate multiple systems that perform the same basic function. Financial management systems are a common case, but there are many others. In numerous instances, a single agency may rely on more than one system that performs the same or similar function. Across government, the number of variations increases even more.
A practitioner question is simple: Why?
What problem are we solving by maintaining multiple systems?
Is that complexity delivering value, or is it creating cost, risk and fragmentation?
Modernization could mean consolidating systems where it makes sense, standardizing platforms and reducing unnecessary variation. Not because consolidation sounds appealing in theory, but because it improves usability, oversight, security and long-term sustainability.
These questions cannot be answered without practitioners at the table. The people who do the work every day, who understand how systems function in practice rather than theory, how transitions ripple across operations, and what failure looks like when implementation goes wrong.
Practitioners have not consistently been included because modernization efforts tend to elevate strategic vision and policy design over operational execution. The focus is often on what should happen, rather than how change is implemented, sustained and experienced in real operational environments.
Closing that gap requires bringing practitioner perspectives into modernization efforts early, not after implementation challenges emerge.
The hiring process is another example.
Federal hiring is complex, with multiple steps and handoffs. In many cases, an HR specialist is responsible for qualifying candidates based on specialized experience described in a position description.
Here is the practitioner reality. That HR specialist may never have worked in the role they are qualifying. They are doing their best, but they are interpreting technical qualifications through a document rather than through lived experience.
Meanwhile, the hiring manager, whether an engineer, special agent, financial analyst, cybersecurity professional or other technical expert, is often better positioned to assess whether a candidate can actually perform the work.
Modernization does not mean removing HR from the process In practice, this has meant embedding technical subject-matter experts closer to mission and operational teams, while HR establishes clear policy, compliance and equity guardrails. In agencies I’ve worked in, this shift reduced bottlenecks, improved adoption, and allowed HR to focus on system integrity and workforce outcomes rather than transactional approvals.
That is an operating model question, not just a policy one.
Security clearances present a similar challenge. Clearance levels vary. Processes vary. Timelines can stretch for months or longer. Agencies often rely on different formats, workflows and handoffs even when requirements are comparable.
A practitioner looks at that landscape and asks clear, practical questions.
These are not abstract questions. They directly affect mission delivery, hiring timelines, workforce planning and national security readiness.
The common thread across all of these examples is this: Modernization falters when we focus on changing rules without redesigning how work actually flows.
Successful reform requires alignment across three elements.
We are in a moment of real opportunity. The changes of the past year have created space to rethink how government works. That opportunity should not be wasted on reforms that are elegant in concept but fragile in execution.
If we want a federal government that is effective, sustainable, and capable of meeting future demands, we must design it intentionally. Not only at the policy level, but at the operational level.
That starts with the outcome.
It requires designing for implementation.
And it depends on bringing practitioners into the conversation early, not after the fact.
Modernization is not about doing more.
It is about doing what makes sense, in a way that actually works.
Michelle Sutter is a former military and civil service leader and a federal practitioner with experience in executive operations, workforce strategy and organizational modernization. Her work focuses on translating policy intent into practical, implementable outcomes, with an emphasis on execution, governance and sustainability across complex federal environments.
Copyright © 2026 Federal News Network. All rights reserved. This website is not intended for users located within the European Economic Area.