The Trouble with Time in Evaluation

Evaluation tends to assume that time will eventually do the work for us, that if a project is given sufficient duration and enough reporting cycles, the outcomes we care about will rise to the surface in a form that can be recognized, named, and assessed, an assumption that feels reasonable precisely because it aligns so neatly with how institutions already understand patience, responsibility, and progress.

The problem is that time does not simply pass, and anyone who has spent years inside organizations working on equity, systems change, or long-horizon initiatives knows this in a way that is difficult to explain but impossible to forget, because the most important things rarely arrive on schedule, while other things, often less meaningful, appear quickly and with a confidence that far exceeds their substance. Trust, for instance, does not behave like a deliverable. Alignment never accumulates evenly, and learning often shows up not at the end of a process but in the middle of one that has already looped back on itself several times, carrying with it the residue of earlier attempts that were necessary even though they did not “work” in any conventional sense.

Evaluation, however, often treats time as a neutral container in which these processes unfold, as if duration itself were a guarantee of clarity, and as if the calendar could be relied upon to sort signal from noise, meaning from effort, and progress from motion. This is where the discomfort begins, though it is usually felt long before it is named.

You know the feeling. People seem to endlessly repeat themselves in meetings, and this might be less because they lack understanding, and much more because the conditions for common understanding are still forming. Think of programs; they pause and they adjust, sometimes because they are drifting of course, but mostly because the terrain keeps shifting beneath them. Reports too, often arrive filled with confident language that everyone recognizes as slightly premature, even when it is technically accurate. Most often, then, nothing feels stalled. But nothing feels resolved either.

What is happening instead is that evaluation is asking questions that belong to a different theory of time, one in which change advances steadily, outcomes appear in sequence, and patience consists of waiting calmly for the future to arrive. In practice, however, time behaves less like a straight line and more like a force that bends, compresses, and redistributes pressure, rewarding presence in some places while demanding endurance in others, and remembering very clearly who was required to wait, who was allowed to move quickly, and whose labour remained invisible in the process.

One of the most consequential ways this shows up in evaluation is through the future, which often functions as a kind of alibi, allowing present strain to be justified by promised outcomes that hover just far enough ahead to remain intact, stabilizing institutional timelines and making extraction feel temporary, even when the same patterns repeat year after year. The future, in this sense, reaches backward into the present, shaping how effort is distributed, how urgency is framed, and how disappointment is managed, until evaluation becomes less a practice of understanding than a mechanism for maintaining optimism under pressure. This is why so many people working in this space recognize the feeling of writing reports that sound convincing while leaving something important unsaid, of translating relational labour into outcomes language that never quite fits, and of sensing that the most meaningful changes are taking place somewhere adjacent to what evaluation is expected to see.

The issue here is that the temporal assumptions governing judgment no longer match the conditions under which change is actually taking place today. When evaluation begins to pay attention to time itself, rather than waiting for time to deliver answers, something subtle but important shifts. Then, repetition starts to read as information rather than delay, preparation registers as movement rather than waiting, and uncertainty begins to look like a sign of proximity to reality rather than a failure of clarity. Judgment slows, though not in a way that feels indulgent or evasive, but in a way that allows proportion to return, aligning claims with what can responsibly be known and decisions with what the work is actually asking for next.

Time, in other words, stops being the thing that evaluation is waiting on and becomes the thing evaluation learns from. This matters now because we are living in a moment that demands rapid response while carrying deep and unfinished histories, a moment in which institutions are asked to move quickly and repair carefully at the same time, producing a tension that everyone feels and few frameworks acknowledge.

Evaluation sits squarely in the middle of this tension, deciding what counts, what gets carried forward, and what disappears quietly between reporting cycles, which means that thinking seriously about time is no longer a philosophical indulgence but a practical necessity.

Why does this matter now? Because we’re living in a moment where institutions are asked to move fast and heal deeply—at the same time. Evaluation sits right in the middle of that paradox. It decides what gets remembered and what gets buried. So thinking seriously about time is urgent.