Introduction

We report results more than ever. Yet we learn too slowly how to improve them.

The limitations of results-based measurement and management have been visible for decades. They date back to New Public Management in the early 1990s and its predecessor, Peter Drucker’s management by objectives, introduced thirty years earlier.

“Management by results—like driving a car by looking in a rear-view mirror.” — W. Edwards Deming (1942)

This article offers a response to that unease, and introduces an approach I call Thoughtful Monitoring™.

It is not a new layer. Not a MEL framework. Not a method, a better dashboard or another taxonomy of indicators.

Instead, it is rigorously relational. Thoughtful Monitoring creates space for managers, field teams and client beneficiaries to bring their knowledge together. It enables them to have real conversations, learn lessons and take action.

Participatory approaches have rightly renewed attention to the voices of those intended to benefit from support. However, the continuing silence of frontline staff still stifles innovation and adaptation.

Thoughtful Monitoring also learns from history. It builds on Dennis Rondinelli’s pioneering work in the late 1980s: decentralised decision-making, continuous adjustment based on implementation feedback, and systems that learn while an intervention is underway. In this approach, monitoring evidence actively shapes decisions instead of merely reporting them.

Introduction to Thoughtful Monitoring

Thoughtful Monitoring has five defining features:

1. It focuses on decisions and users. It begins with the needs of managers, implementers and client beneficiaries. Its task is not to identify information needs and retrofit them into a framework. Instead, it surfaces decision uncertainties at the time and in the context in which they matter.
2. It integrates monitoring into management and delivery. Monitoring is embedded within existing functions, processes, responsibilities and workflows. This prevents standalone activities from drifting away from operational, financial and decision-making realities.
3. It adapts to context and uncertainty. Accepting that “success always starts with failure,” it uses rapid feedback loops to identify problems and opportunities early. This helps teams navigate unknowns, adapt the change process and reduce implementation risk and wasted resources.
4. It promotes learning and practical insight. It tests assumptions and draws on frontline experience and indigenous knowledge systems, including through storytelling, to inform continuing improvement.
5. It strengthens accountability and relevance. It balances donor requirements with responsiveness to the people programmes serve. It values lived experience and supports priorities around results, learning and risk management without relying on overly prescriptive systems.

What this actually means

The proposition is simple: monitoring should help people decide, not merely report what has already happened. Doing this requires more discipline than asking, “What information do you need?” or “Which questions should monitoring answer?”

“A performance measurement system needs to tell you whether the decisions you’re making now are going to help you in the coming months.” — Likierman (2009)

Just as importantly, better monitoring does not require more complexity or sophistication. On the contrary, it often requires less.

Keep it simple. Resist the reflex to add complexity.

The problem with many monitoring systems is not only that they contain too many indicators. It is that too many indicators are disconnected from decisions, thresholds and consequences.

Better monitoring is not more elaborate monitoring, nor is it simply the addition of another method. It is more focused, selective and honest about what people need in order to act.

Decision-driven monitoring starts somewhere different

Most monitoring systems begin with a familiar question: What should we measure? The answer is typically presented as an array of indicators within a framework.

Thoughtful Monitoring begins somewhere else entirely: with decisions.

• Who needs to decide what—today?
• What do they not understand well enough to decide with confidence?
• What information would change their understanding, decision or action?

This is not a methodological refinement. It is a reversal of logic.

Decision-driven monitoring is designed backwards from real decisions made in real time. Information is not collected simply because it appears in a framework. It is collected because it is useful—and usefulness is judged by whether it improves a decision.

This approach does not add layers. It removes them. It strips monitoring systems down until only what is relevant to decisions remains.

Six practical convictions

Thoughtful Monitoring converges around six practical convictions:

1. Decisions come first. Monitoring exists to inform action, not to justify it after the fact.
2. Uncertainty is normal. It is not a design flaw but the starting condition of any meaningful decision.
3. Knowledge is distributed. Client beneficiaries, frontline teams and managers each hold partial truths; none is sufficient alone.
4. Timeliness matters more than volume. Information that arrives too late is often indistinguishable from no information at all.
5. Usefulness is the real standard. If data changes neither understanding nor action, it is noise.
6. Simplicity is a discipline. Improvement comes not from accumulating indicators and frameworks, but from refusing unnecessary complexity and sophistication.

Not another system to install

Thoughtful Monitoring is not adopted as a system. It builds on what already exists and is delivered through three fundable components. These can be contracted together or separately, allowing monitoring itself to evolve with the context.

1. Diagnostic

The Diagnostic is not an indicator review or a framework refresh. It uses a bespoke interview guide and structured process to identify why monitoring fails to inform decisions across different groups—and how to fix it.

2. System design

System design involves co-designing or refining monitoring so that it becomes part of core management routines, job descriptions and delivery processes. This enables communities and frontline staff to share and act on what they observe and experience, rather than waiting for management approval at every turn.

3. Embedded support

Embedded support provides accompaniment to managers and teams. It helps Thoughtful Monitoring become part of how people manage and work, rather than a contrived external addition.

This flexible, à la carte design allows organisations to adopt the five features selectively. It is not a rigid, all-or-nothing framework.

What changes in practice?

When monitoring is built in this way, the roles of those involved begin to change.

1. Client beneficiaries are no longer treated as data points. They become active participants in shaping understanding and reflecting on what support they need, why it matters and how it should be delivered.
2. Managers must confront their real uncertainties: what they do not understand and where decisions rely on assumptions that have never been properly tested.
3. Field teams are no longer reduced to data collectors. They are recognised as essential sources of lived experience, able to reveal what is working, what is not and why.

This is not monitoring as extraction. It is more than data. It is monitoring as part of the exchange through which interventions are delivered and change is stimulated—the inspiration for Developmental Evaluation (personal communication with Michael Quinn Patton).

Thoughtful Monitoring does not reject results. Instead, it makes results more achievable by improving how programmes and organisations respond during implementation. Consequently, people are more likely to receive timely, relevant and effective support.

For example, within weeks, a team can see more than the fact that uptake is low in District X or Ministry Y. It can identify which implementers are struggling, which assumptions are failing and whether the problem lies in demand, delivery capacity or policy interpretation.

Because the approach is anchored in decision points rather than reporting requirements, monitoring becomes faster, more relevant and more adaptive:

• Data arrives in time to matter.
• Frontline knowledge becomes actionable rather than anecdotal.
• Programmes adjust before failure becomes inevitable.

Monitoring therefore shifts:

• From retrospective to real-time;
• From extractive to embedded; and
• From indicator-driven to decision-driven.

It moves from describing change after the fact to shaping it while change is still possible.

An invitation to work differently

Thoughtful Monitoring is not a framework to implement or a system to install. It is a way of starting differently:

• Start with the decisions that matter.
• Ask what is not understood.
• Identify what would genuinely change action.
• Design for that—and only that.

From there, the practice develops through use: conversation, adjustment and shared learning among those closest to the work.

This is an invitation to treat monitoring not as an administrative requirement or retrospective justification, but as a living tool for navigating uncertainty and improving decisions as they are made.

“Cross the river by feeling for stones.” — Attributed to Deng Xiaoping

Thoughtful Monitoring shifts monitoring from a reporting obligation into a strategic asset. In doing so, it strengthens effectiveness, accountability and responsiveness to the real world.

I am working with a select group of organisations to put Thoughtful Monitoring into practice: diagnosing what is not working, redesigning monitoring around real decisions, and supporting teams in the field and the office.

If you are interested, send us a message.