When Learning Leads: Rethinking How Community Networks Measure Their Work

Over the years, I have had the privilege of working with large networks of development professionals and the organisations they build — people with deep, patient roots in the most marginalised communities. Their work is experimental yet community-driven; small in origin yet ambitious in scale. For them, participation is not a technique; it is the point. Many of these networks swim against the tide, largely invisible to international donors, domestic philanthropies and corporate funders. Learning is their engine. Making mistakes, and sharing the risk of those mistakes, is simply how they operate.

And yet, when it comes to measuring and reporting on their own work, something curious happens. They get caught between two worlds — the top-down system of monitoring they have inherited and the bottom-up, participatory learning they actually believe in. The intention is right, but the practice quietly drifts towards old habits: forms, formats, reporting cycles, quarterly targets and the anxious question, 'Are we on track?'

I have watched this drift happen in organisations led by some of the most imaginative people I know. It is not a failure of conviction; it is the pull of a very old gravity. The tools we use to measure development were designed for a different purpose — to reassure distant funders that money was spent as promised. They were never designed to help a team think. So we end up with organisations that talk about learning and practise reporting.

Here are a few thoughts on how that gravity can be resisted.

Treat monitoring as listening, not reporting

Most monitoring systems look backwards. They tell you, three months late, what you did. That has its uses, but it is not much help to someone trying to steer. Monitoring should be closer to listening — a continuous, live sense of what is happening right now. What is shifting? What is surprising us? What is emerging at the edges that nobody planned for? Who has quietly dropped out, and why? A good monitoring system does not just count; it notices.

Evaluation then does something different. It steps back, less often, and goes deeper into the harder questions — the ones you cannot answer from a dashboard. Is this actually changing anything? For whom? At what cost? Would this hold up somewhere else?

But here is the part most frameworks get wrong: learning does not fall out of monitoring and evaluation automatically. Data does not teach. People learn — but only if someone makes the space, calls the meeting, asks the awkward question, and writes down what was decided. Learning has to be designed for, staffed and protected, or it will always lose to the urgent.

A simple rhythm helps: notice what is happening; make sense of it together; decide something; change something; then watch again.

Retire the word "deviation"

When a programme moves away from its original plan, we call it a deviation — as if the plan were sacred and reality were misbehaving. In a fast-changing context, the plan is often the thing that is wrong. It was built on assumptions made a year ago, by people with less information than the team has today. Treating every change as a failure of discipline teaches staff to hide the changes, or worse, to keep marching in a direction they know is wrong because the log frame says so.

A better question than, 'Are we on track?' is: 'Is our understanding of this situation still correct, and what should we change now that we know more?' This one shift moves the centre of gravity from compliance to judgement. It makes adaptation the normal, expected behaviour of a competent team rather than an embarrassing exception to be explained in a footnote.

Make learning a shared act

Communities, frontline workers, young professionals, technical specialists, local government officials, contractors — each holds a different piece of the truth, and none holds all of it. The community knows what actually happened. The frontline worker knows why. The technical team knows what the numbers say. The official knows what is politically possible.

Learning happens when these pieces are deliberately brought into the same room and allowed to disagree. Not a consultation, where people are asked to comment on conclusions already drawn — but genuine co-production, where interpretation itself is shared.

This does not happen by goodwill alone. It requires investment: in the confidence of quieter participants to speak, in the skill to read evidence, in facilitation that stops the loudest voice from becoming the finding, and in the humility to let a community's reading of a situation overturn the organisation's.

Culture matters more than tools

Learning logs, review meetings, peer exchanges, reflection workshops, scorecards — all useful, none sufficient. Rituals matter; they create the occasion. But a system stands or falls on something less visible: whether people feel safe enough to say, "This isn't working."

If admitting a mistake costs someone their reputation, their next contract, or their standing in a meeting, no framework on Earth will produce honest learning. You will get beautifully documented success stories and no idea what is really going on.

Safety is demonstrated by leaders, not declared in policies. When the head of an organisation says openly, "I got this wrong, and here is what I now think," the whole system exhales. And let us be precise about what we are asking for. We do not celebrate failure — that is a slogan, and a slightly dishonest one. We create conditions where people can experiment honestly, admit what did not work, and find a better way, without fear.

Close the loop

After every reflection, ask five plain questions: What did we learn? What does it tell us about the assumptions we started with? What has changed in the world around us? What will we do differently, and who will do it? How will we know whether that change worked?

Without this, learning becomes a genre of writing rather than a practice. The real test is simple: what is different because we learned it? If nothing is, the learning did not happen.

Keep accountability — but keep it in its place

None of this is an argument against accountability. Funders deserve honest reporting on money and results. Communities deserve far more accountability than they usually get.

The danger is not accountability itself but accountability that creates an incentive to hide trouble. The fix is to hold two distinct spaces: one for stewardship and results, conducted rigorously; another for candour, where uncertainty and failure can be discussed without consequence. Quarterly reviews and annual cycles then become opportunities for genuine learning and adaptation, rather than mere compliance exercises.

When Learning Leads: Rethinking How Community Networks Measure Their Work

You may be interested to read

Dr. Anshuman Karol

PRIA

Dr. Rajesh Tandon