Most agencies don’t resist modernization because they don’t see the problems. This resistance appears because the path forward feels riskier than staying where they are.
TL;DR;
If you’re responsible for a nutrition program and your current system feels dated, rigid, or overly manual, but it’s also too critical to touch – well, it just means you’re human. And you’re not alone.
“We know it’s not ideal… but it works… enough…”
This is the not-always-quiet tension many agencies just keep living with.
The system takes more clicks than it should. Reports require workarounds. Manual steps creep in because the software can’t quite keep up with policy or process changes. Staff feel the friction every day.
And yet, change feels Heavy – Hard – and Scary.
Modernization isn’t just a technical decision. It’s an emotional one. It introduces uncertainty into programs that must run flawlessly, every day, for the people who depend on them.
When the stakes are high, doing nothing can feel like the safest option.
There are a few very human forces at play when organizations feel stuck.
Even a known pain can feel safer than an unknown future. Legacy systems may be frustrating, but they’re familiar. Teams know where the cracks are. A new system introduces ambiguity, and ambiguity is uncomfortable.
Change is often framed around what you might gain. But people instinctively focus on what they could lose: hard-earned expertise, trusted workflows, or control during transition. Those perceived losses often outweigh promised benefits.
When teams are already stretched thin, modernization can feel like just one more overwhelming decision in a long list. The energy required to evaluate options, plan transitions, and manage change can feel unavailable, even when the need is obvious.
For many staff, mastery of the current system is part of their professional identity. Change can feel like starting over, or worse - like invalidating or losing years of experience.
None of this is irrational. In fact, it explains why so many agencies live in a state of functional discomfort, aware of the problems, but really hesitant to move.
Here’s the paradox: Even when the status quo is painful, it often wins, because the change path feels riskier.
The pain of today is known. The relief of tomorrow is theoretical.
Modernization discussions often jump straight to features, timelines, and platforms. But until the emotional math shifts, until change feels safer than staying put, momentum stalls.
This isn’t an inevitable failure of leadership – but it is a signal that the approach needs to change.
We often pose “what will I lose if I risk this change,” and framing it that way almost always sets the question up as:
Possible Losses in Reputation + Finances + Productivity > Desire to Change
This isn’t wrong. And you do need to consider these factors in your evaluation, but it is a naturally biased perspective that gives an illusion of safety.
But what if you asked yourself, “Is it bad for me if I don’t prepare for change?” Framing it this way forces you to look at the other side of the coin, and be more strategic instead of reactive.
I often find that as you go higher in the org-chart, the focus moves from daily operations to strategy and forecasting. I learned to go into my meetings with my executives with “We’ve identified where our system is holding us back – here are options to address that or ways to build resilience.”
Now that frames the question as
Desire to Change > Perceived Safety in Reputation + Finances + Productivity
By planning ahead, this change can be incremental, adaptable, and designed around the realities of how your teams actually work – not change for change’s sake.
If you feel stuck, it means you probably haven’t examined the change equation from both sides yet.
Sometimes the first step isn’t a decision. It’s a conversation, one that explores options, tradeoffs, and readiness without pressure to commit.
No timelines. No promises. Just clarity.
Sometimes, changing the math starts with simply understanding it.