When the technology you use becomes your biggest operational problem
There’s a moment when you stop seeing it. You’ve been living with it for so long that it no longer registers as a problem — it’s just part of the landscape. A form here, a spreadsheet there, a plugin that never quite works properly. Your organization keeps moving, but it’s pushing an invisible weight.
We call this a Frankenstein system: a collection of digital tools that grew by accumulation, without strategy, without any coherent vision. Each piece has its own internal logic, but the end result is a monster that consumes time, money, and energy in ways that almost never appear in any budget.
How do you recognize one?
The clearest signal isn’t technical — it’s human: the people using the system seem to be fighting it. Every simple task requires several steps that make no sense. Nobody knows exactly what state all the tools are in. The same data has to be entered in three different places.
A particularly common case: WordPress sites with a dozen stacked plugins. When something breaks, diagnosing the problem becomes an archaeological expedition. And when someone new joins the team, learning to use the site becomes an initiation ritual no one should have to go through.
If your organization can’t answer at a glance the question “what digital tools do we use and how do they relate to each other?”, you already have your answer.
How does it happen?
Almost always the same way: solving problems without a strategy. An urgent need arises, someone is hired to fix it, they deliver what’s asked of them, and nobody asks the harder questions: does this fit with what we already have? With what we’ll need in two years?
The “you ask, I deliver” model is comfortable for the vendor and disastrous for the organization. Because what’s requested is rarely what’s needed. What’s requested is the symptom; what’s needed is understanding the cause.
Mission-driven organizations — NGOs and SMEs included — tend to operate with tight budgets. That means every technology decision gets made with urgency as the criterion, not strategy. And so, layer by layer, the Frankenstein is built.
The cost nobody is measuring
The most visible cost is financial: licenses, maintenance, patch development. But the real cost lives somewhere else.
It’s in the time these systems swallow simply by existing. The time spent entering the same data twice. The time spent finding the right information across four different tools. The time waiting for a website to load when it should take two seconds.
It’s in the manual work accepted as inevitable. Tasks that should be automated but that someone does by hand every Monday because “that’s how it’s always been done.”
And above all, it’s in the missed opportunities: the donation that wasn’t completed because the payment gateway didn’t inspire confidence. The visually impaired user who left the website because it didn’t meet accessibility standards. The potential partner who couldn’t find what they were looking for because the information architecture was a maze.
Those costs don’t appear on any invoice. But they’re there.
Why doesn’t anyone act?
Two forces hold change back: fear and resignation.
Fear is understandable. Touching an organization’s digital infrastructure feels risky. What if something stops working? What if we lose data? What if it costs more than we think? Legitimate questions that, without proper guidance, become paralysis.
Resignation is quieter and more dangerous. It’s accepting that a certain level of technological friction is normal. That it’s like this for everyone. That there’s no time to fix it because there’s already enough to do with the main mission.
What it means to do it right
Resolving a Frankenstein system isn’t just “fixing the website” or “migrating to a better tool.” It means first understanding what the organization truly needs, how the team works, what its levers of impact are — and from there, building a digital infrastructure that serves the mission instead of hindering it.
The good news is that the moment to act has never been better. Recent advances in technology and artificial intelligence make it possible to cover far more needs with tighter budgets than just a few years ago. The size of your organization is no longer an excuse for not having digital tools that actually work.
The question isn’t whether you can afford to improve your digital infrastructure. The question is how much it’s costing you not to.
Do you recognize any of these symptoms in your organization? We’d be glad to hear from you.