Capacity Building Without Ownership

The problem is not with training itself. The problem is with what training is asked to substitute for: ownership. In many institutions, capacity building is treated as an end state. Staff are trained. Certificates are issued. Photos are taken. The assumption is that once people have been taught, systems will sustain themselves.

This assumption is false.

Training transfers knowledge. Ownership assigns responsibility. Without the latter, the former decays quickly.

Consider what typically happens after a capacity-building exercise. Staff return to roles that have not changed. Incentives remain the same. There is no explicit accountability for system health — no budget authority, no mandate to enforce standards. When problems arise, responsibility diffuses.

The trained staff member knows how the system should work. They do not have the authority to make it work.

Over time, this produces a familiar failure mode. The trained individual becomes a local hero — called in emergencies, relied upon informally, blamed quietly when things go wrong. The institution itself never changes. When that individual transfers, retires, or burns out, the system collapses. The failure is then attributed to "loss of capacity."

Ownership means someone is explicitly responsible for outcomes, not just effort. It means budgets align with responsibility. It means authority to enforce usage, retire broken processes, and say no to unsafe shortcuts. It also means consequences when systems are neglected.

Capacity building without ownership creates what looks like competence without power. It teaches people to see problems they are structurally unable to fix.

This dynamic is reinforced by how many programs are designed. Donors and implementers prefer training because it is measurable, time-bound, and politically safe. Ownership is messy. It raises questions about governance, incentives, and accountability — questions that persist long after the project ends and the report is filed.

So training proliferates. Systems do not. This is why institutions can host repeated workshops on the same tools every few years. The knowledge keeps being replenished because the conditions that cause its loss are never addressed.

Where ownership exists, capacity compounds. Where ownership is absent, capacity evaporates.

Effective systems invert the order. They establish ownership first: clear roles, authority, budget, and accountability for system performance. Training then supports those roles. Skills are refreshed because they are exercised. Knowledge sticks because it is used.

This distinction matters most in resource-constrained environments, where redundancy is low and failure is expensive. When no one owns the system, everyone improvises. Improvisation becomes normal. Normalized improvisation eventually replaces the system itself.

Capacity building was never meant to carry this weight. It cannot substitute for governance. It cannot compensate for the absence of responsibility. It can only amplify structures that already exist.

Until that question is answered, workshops will continue, systems will continue to decay, and the cycle will repeat — well-documented, well-intentioned, and ineffective.

Walter Kwami writes from over 30 years in IT, with particular interest in how technology must be engineered — not merely adopted — in resource-limited contexts.