If processes, communications, training, leadership expectations, and the people doing
the work do not change with the technology, the gaps do not disappear. Employees are
left to close them.
A new system launches on schedule.
Three weeks later, one team is working entirely in it. Another is entering information into the new system while maintaining the spreadsheet it was supposed to replace. Supervisors are giving different instructions about which process to follow. Employees have started building workarounds for the steps that no longer quite fit.
The technology works.
The organization has not fully changed with it.
At TMA, this is one of the connections we pay close attention to in modernization work: the space between implementing a technical capability and changing how an organization actually operates.
Modernization may be managed as separate technical, operational, communications, and training workstreams. The people performing the mission do not experience it that way. They experience one change.
When those pieces do not connect, employees are left to close the gaps.
And that is often where a technically successful implementation begins to lose operational value.
Communication Is Part of Implementation
A new capability only creates value if it improves how the organization operates.
The real measure is not simply whether the system works; it is whether the work works better because of it.
Did a handoff become clearer? Did a duplicate process disappear? Can leaders see something they could not see before? Can employees accomplish the work more effectively?
If the new system launches and the old workaround survives beside it, the organization has added technology without removing the friction it was meant to address.
This is where communication becomes part of the implementation itself.
Organizations communicate change in more ways than they sometimes realize. Employees receive the official announcement, but they also receive signals through supervisor instructions, training, documentation, policies, system permissions, leadership behavior, and the processes they encounter when they actually try to do the work.
Those signals need to tell the same story.
Suppose employees are told the new platform is now the authoritative source, but leadership still asks for the legacy spreadsheet at the weekly status meeting.
The official message says: use the new system.
Leadership behavior says: maintain both.
Employees will respond accordingly.
Now the modernization effort has created duplicate work, competing sources of information, and uncertainty about which process actually counts.
Communication is how a technical change becomes an organizational change.
Leaders need to understand the outcome they are expected to reinforce. Managers need to know how workflows and responsibilities are changing. Users need clear guidance about what will be different in their work and where they can get help.
Training has to reinforce that same operating model.
Teaching someone which button approves a request is system training. Preparing them for the changed work means explaining when approval is required, what information must be present, who owns the next action, and what happens when the request falls outside the standard process.
When people understand the technology but not the operating model around it, the old workflow has a way of rebuilding itself around the new system.
Communication also has to move in both directions.
The organization needs ways to hear where users are confused, where guidance conflicts with reality, and where the new process is creating problems no one anticipated.
Those signals tell you where the connections still need work.
Workarounds Are Signals
After deployment, pay attention to what employees do when the new process does not work as expected.
If the unofficial spreadsheet comes back, ask why.
If support requests repeatedly cluster around the same step, look at the process surrounding it.
If two teams interpret the same workflow differently, find out whether their work genuinely requires different approaches or whether they received conflicting guidance.
These behaviors are easy to label as resistance. Sometimes they are.
But sometimes a workaround reveals something the implementation missed: an exception no one planned for, information users still cannot access, or a handoff whose ownership was never resolved.
That makes feedback from the people doing the work valuable operational information.
The goal is not to force compliance with a new process simply because it is new. The goal is to understand whether the new way of working is producing the improvement that justified the change in the first place.
Deployment tells you whether the capability is available.
The workarounds tell you where the organization still has not caught up.
What We Have Seen in Practice
Through TMA’s work supporting federal and defense organizations, we have seen how closely technology, operations, communications, workforce needs, and data are connected.
To the people performing the mission, a new system, revised process, updated guidance, training, and changing expectations are not separate functional areas.
They are one change.
That perspective shapes how we approach modernization.
Technical capability matters. So does the environment in which that capability will operate.
The process being configured should be the process employees are taught. The expectations leaders reinforce should match the guidance employees receive. Communications should create understanding while also giving users a way to surface what is not working. And what happens after deployment should inform what happens next.
The stronger those connections are, the less reconciliation is left to the people trying to perform the mission.
You cannot modernize the system and leave the organization behind.
Modernization succeeds when a new capability does more than work as designed. It improves how the mission gets done.
At TMA, we approach modernization with that full operating environment in mind, connecting technology, people, processes, communication, and mission outcomes so organizations can move from implementation to sustained operational use.
Explore TMA’s capabilities →
