
The Uncomfortable Truth About Why Grant Operations Fail (and Why No One Wants to Say It Out Loud)
- Ann Marie, Principal Consultant
- Mar 18
- 3 min read

Let’s just say it.
Most grant management problems are not systems problems.
They’re not compliance problems.
They’re not even resource problems.
They’re behavior problems.
And that’s the part no one wants to touch.
We Don’t Have a Process Problem, We Have a Letting-Go Problem
In public administration, we love our processes. We build them, document them, defend them, and, if we’re being honest, hide behind them.
Processes make us feel safe.
Controls make us feel protected.
Systems make us feel like we’re “doing it right.”
But here’s the uncomfortable reality, many of the processes currently in place were designed for a different time, a different risk environment, and a different pace of work.
And yet, they persist.
Not because they still work.
But because changing them feels harder than tolerating them.
“We’ve always done it this way” Is Not a Strategy
If you’ve ever tried to introduce a more efficient way of managing grants, automation, AI-assisted workflows, streamlined reviews, you’ve probably heard some version of:
“That’s too many steps to implement.”
“We don’t have time to change this right now.”
“What we have works well enough.”
“What if something goes wrong?”
Let’s translate that:
We don’t want to relearn something
We’re afraid of short-term disruption
We’re more comfortable with known inefficiency than unknown improvement
We’re optimizing for perceived safety, not actual performance
This isn’t about logic. It’s about human behavior.
The Hidden Cost of Clinging to What’s “Worked”
What’s rarely acknowledged is that outdated processes don’t just slow things down, they actively introduce risk:
Manual workarounds create inconsistency
Over-layered reviews dilute accountability
Legacy controls miss modern threats
Staff burnout increases error rates
Ironically, the very systems designed to reduce risk often become the source of it.
But because those systems are familiar, they’re rarely questioned.
Control Does Not Equal Effectiveness
There’s a deeply ingrained belief in public sector environments that more control equals better outcomes.
More approvals.
More documentation.
More checkpoints.
But more is not always better, sometimes it is just more.
Effective operations are not about how many controls you have. They are about whether the right controls are applied in the right way, at the right time.
And here is where it gets uncomfortable, because once you accept that more control is not the answer, you are forced to ask what is.
That question usually leads somewhere people are not ready to go.
The Conversation Everyone Is Avoiding
Because if more layers, more manual reviews, and more oversight are not actually reducing risk, then what will?
This is where AI enters the conversation, whether people are ready for it or not.
Not the hype. Not the buzzwords. The actual operational reality.
AI has the potential to:
Reduce manual workload
Improve consistency
Surface risks earlier
Free up staff for higher-value work
And yet, adoption stalls.
Not because the technology is not capable.
Because people are not comfortable.
There is hesitation. Skepticism. Fear of getting it wrong. Fear of losing control. Fear of looking unprepared.
So instead, organizations stay where they are, over-relying on human-heavy processes that are already stretched thin.
The Real Work Is Not Technical, It Is Cultural
You can implement the best system in the world.
You can design the most efficient workflow imaginable.
But if the people using it do not believe in it, or worse, resist it, it will fail.
Operational transformation is not about tools.
It is about behavior change.
And behavior change is uncomfortable.
It requires:
Challenging long-held assumptions
Letting go of familiar, but ineffective, practices
Accepting short-term friction for long-term gain
Leading differently
That is the work most organizations avoid.
A Different Way Forward
Modernizing grant operations does not mean throwing everything out. It means being intentional about what stays, and what goes.
It means:
Re-evaluating processes through a risk-based lens
Designing workflows for how work actually happens today
Introducing AI responsibly to support, not replace, teams
Building systems people will actually use, not work around
And most importantly, it means addressing the behavioral barriers that keep organizations stuck.
If This Pissed You Off
Good.
That means it landed.
Now the only question is: What are you going to do about it?
If you are ready to move past outdated processes, rethink how your organization approaches risk, and explore how AI can be adopted responsibly to improve grant operations, we should talk.
Because the hardest part is not knowing what needs to change.
It is deciding that you are actually going to change it.





Comments