Paying for an Input Is Not the Same as Strengthening a Capability
An activity is something an organization does. A capability is an ability it can reliably bring to work: keeping accurate records, supervising staff, maintaining access or making decisions. An organization may deliver an activity once while lacking the continuity to repeat it. It may also spend on a system that never becomes usable.
Organizational strengthening therefore needs a reasoned connection between the proposed support and the operational problem. It does not require treating all administration as good or every technology purchase as progress.
Trace a Fictional Service Problem
An invented community-service organization has one administrator. When that person is absent, colleagues cannot find current supplier records. They recreate orders from messages, delaying preparation. The team proposes buying a new record application.
There are at least four plausible explanations for the difficulty: records are scattered; only one person knows the filing rules; access is restricted without backup; or the underlying procurement decisions are never recorded. Each implies a different response. A new application may address storage while leaving roles and missing decisions unchanged.
| Proposed Support | Plausible Mechanism | Evidence Needed Before Calling It Useful |
|---|---|---|
| A new shared system | Makes the authorized current record findable | Staff can locate the right record with the appropriate access; export/recovery and ownership are understood |
| Cover and practice time | Lets another staff member perform the task during absence | A trained colleague completes a realistic handover exercise without relying on the absent person |
| Clear purchasing roles | Reduces missing or disputed decisions | Staff know who records approval, receipt and payment; examples show the process being used |
| More activity funding only | Pays for another round of work | Resources genuinely cover the planned activity; it does not by itself resolve the continuity weakness |
These are hypotheses and example checks, not findings from a real organization. Do not use a successful rehearsal to claim reliable performance in every situation.
Build a More Credible Proposal
The fictional team chooses a small record-process redesign using its existing permitted tools, a backup role and protected practice time. Before buying new software, it checks whether the current tools can meet the need. The funder asks what will remain after support ends: who owns the process, who covers absence, how staff receive changes and how records can be recovered.
The proposal should distinguish an input such as training hours, an immediate capability demonstration such as retrieving a correct record, and a service consequence such as fewer preparation disruptions. Those are connected but separate claims. A test of retrieval does not establish why a future service improved; other conditions may change too.
Preserve Ownership and Practical Constraints
The organization doing the work needs a central role in defining the problem and deciding the feasible change. A funder's preferred system may be difficult to maintain, require unavailable connectivity or create inappropriate data access. The organization may reasonably prefer a simpler approach. That preference still needs a realistic explanation of the risk and how it will be managed.
If a key staff vacancy is the main problem, a short workshop may be insufficient. If the organization already has a usable process, funding a duplicate system may weaken it. Compare the proposed intervention with doing less, doing something different or improving the existing arrangement.
Explain What Is Known Afterward
Suppose the backup colleague successfully retrieves a current order in one practice exercise. Say exactly that, with conditions. Check later use and unresolved access or workload problems before claiming lasting capability. Do not transform expenditure on capacity into proof of community benefit.
Use the grant-form comparison to decide how the support might be structured, and the staff/project handover record to assign continuing ownership.
Source and Scope
INTRAC's OD approach, Our OD Approach, emphasizes context and organizational ownership. It is a provider's account, not proof that a particular intervention works. The causal reasoning, alternatives and fictional checks here are original teaching material.