When the Workaround Becomes the Strategy: Digital Infrastructure for NGOs and Decentralised Organisations

The workaround as a permanent solution

Somewhere in Germany, an NGO is coordinating its work through a WhatsApp group, three different cloud services, a homemade form tool, and a spreadsheet that only one person truly understands. This is not an exception. For many organisations, it is simply reality. And they all have good reasons for how things got this way.

Digital infrastructure in NGOs and decentralised organisations rarely emerges from deliberate planning. It grows from workarounds. A tool gets introduced because it was free in a project budget. A database expands because no one had time to implement a CRM. A process runs through a personal email account because it was faster than navigating the official system. Over the years, a patchwork takes shape that somehow works – until it doesn’t.

The balance that keeps tipping

When it comes to what makes decentralised organisations particularly challenging to run digitally, three difficulties come up in practice again and again.

The balance between central control and local autonomy 
Decentralised organisations work because their local units can make independent decisions. Digital systems need to support that autonomy without sacrificing the coherence of the whole. This is a genuine tension – both technically and organisationally.

Data protection
Many NGOs work with particularly sensitive data: counselling records, health data, data relating to vulnerable individuals. GDPR compliance here is not a matter of box-ticking – it is an ethical baseline. And it is often harder to guarantee with off-the-shelf tools than with purpose-built solutions.

The competence gap
Many NGOs have no dedicated IT department. The people responsible for introducing and maintaining digital systems are often generalists with full calendars and a primary role that has nothing to do with technology. This limits what is realistically implementable and sustainable – regardless of what is technically possible.

What regularly fails

Tool sprawl instead of platform thinking
When every department or every local unit chooses its own tools, the result is an infrastructure that no one can fully oversee. Data sits in silos. Knowledge and documents are lost when individuals leave. Processes cannot be coordinated. Reports require manual consolidation. This is not a sign of decentralised strength. It is a sign of missing strategy.

Project funding without operating costs
A classic pattern: a new digital platform is funded within a project. It gets introduced, the final report gets written – and then the platform somehow keeps running, because no one budgeted for ongoing operations. Digital infrastructure gets treated as a one-off project. It is a continuous investment.

Insufficient internal IT expertise
Digital transformation projects that are entirely externally driven rarely end well. Not because external partners are poor, but because knowledge of the system must reside within the organisation itself in order to sustain it over time. If the only person who understands the CMS is the agency – and not the internal team – the dependency has already taken hold.

What successful organizations do differently

Platform thinking: one infrastructure, many use cases
The most effective digital projects in decentralised organisations start with a single question: what is the smallest common set of requirements shared by all units? A platform is built on that foundation – with clear governance, defined roles, and a logic that allows for growth.

Open source as a structural decision
Open-source platforms offer a specific advantage for NGOs and decentralised organisations: they create no new proprietary dependencies. An organisation that has built its infrastructure on an open-source platform retains its freedom of action – regardless of how any individual vendor chooses to structure its licensing.

Shared infrastructure: the principle behind Joci OS
Another approach that works in practice: shared infrastructure for similar organisations. Rather than each NGO building, maintaining, and financing its own platform, organisations with comparable requirements share a common infrastructure – and configure it for their specific needs. This lowers the entry cost, distributes the maintenance burden, and gives smaller organisations access to a professional digital foundation.

This is the principle behind Joci OS: a digital infrastructure for NGOs and decentralised organisations that operates as a shared platform across multiple deployments. What was originally built for TelefonSeelsorge can – with the right adaptations – serve the next organisation too.

Technology follows the mission

The question of which digital infrastructure an NGO or decentralised organisation needs cannot be answered without first answering a prior question: what is the mission, and how should technology contribute to fulfilling it? Technology is never the starting point. It is the answer to a question that must be asked first.

But that answer has to be given at some point. And the first step is usually not a new tool – it is an honest look at what is already there.

Three practical entry points

Take stock before investing.
Before evaluating a new platform, it is worth understanding why the existing ones are not working. Is it the software? The governance? A lack of internal competence? The answer determines the solution.

Define concrete questions. One, not ten.
What is the single digital weak point that costs the organisation the most energy – in coordination, in documentation, in communication? Addressing that one point yields visible improvement faster than launching a full-scale digitalisation project.

Don’t try to solve it alone.
Decentralised organisations that have successfully built digital infrastructure have almost never done so in isolation. The question is not whether external support is needed, but at which point in the process – and from whom.

Where is your digital infrastructure holding back your organisation’s impact most today – and what would be the first concrete step?