Illuminate LLC

Category: Evaluation + Learning Systems

Evaluation methods, feedback loops, and learning practices that help organizations make better decisions.

  • What Today’s Senior Evaluation Roles Reveal About the Field’s Expanding Competencies

    What Today’s Senior Evaluation Roles Reveal About the Field’s Expanding Competencies

    Part of the Next Chapter of Evaluation Leadership Series

    Why outcomes expertise increasingly needs to be paired with delivery fluency, AI literacy, governance, and cross-functional leadership

    Across international development, senior evaluation roles are beginning to ask for a different combination of capabilities. One recent position description made that shift especially visible.

    Much of the profile would be familiar to experienced leaders in evaluation, development effectiveness, and organizational learning. It called for deep knowledge of outcomes, performance systems, institutional reform, target management, implementation monitoring, and government delivery. Many professionals in our field could read those qualifications and recognize work they have been doing for years.

    Then the description went further. The successful candidate would also need to understand AI-enabled analytics, large language models, predictive tools, and real-time intelligence. This person would need to work comfortably with senior government leaders, multilateral institutions, implementation teams, researchers, and data scientists.

    The role treated outcomes, delivery, technology, learning, institutional reform, and leadership as parts of the same job.

    One position alone does not establish a field-wide trend. But senior roles often reveal the problems institutions are preparing to solve and the capabilities they believe they will need next. In this case, the signal was hard to miss.

    Outcomes expertise still matters deeply. Increasingly, it may not be enough on its own.

    Evidence Is Moving Closer to Delivery

    Evaluation professionals have long helped institutions answer essential questions: what changed, for whom, why, and what should be learned?

    Those questions remain central to responsible practice. They bring discipline to claims of success and help institutions distinguish meaningful progress from activity.

    Organizations are now asking evidence to do something more: inform decisions while implementation is still underway, so leaders can catch a stalling rollout or a failing assumption while there is still time to respond.

    None of this is new to anyone who has worked closely with program teams. Political conditions shift. Partners change. Staffing gaps appear. Resources tighten. Communities respond in ways that challenge the original design.

    What has changed is the expectation that evidence systems should help institutions navigate these conditions as part of delivery, not only explain them afterward.

    That changes what senior evaluation leaders are expected to contribute.

    The Role Is Becoming More Integrated

    Evaluation functions still carry real responsibility for measurement, accountability, and learning, and some questions genuinely need time. Long-term outcomes cannot be rushed, and credible conclusions about impact, sustainability, and contribution still require careful design.

    The trouble starts when evaluation sits too far from where decisions actually get made.

    A strong report arrives after a program has already changed course. Monitoring data gets collected but rarely reaches the meetings where decisions happen. A dashboard shows performance slipping without telling anyone why or what to do about it.

    The problem in these cases is rarely the evidence itself. It is the system around it: evidence is produced in one part of the organization, interpreted in another, and expected to shape decisions somewhere else entirely.

    Adaptive management, developmental evaluation, rapid-cycle learning, and Collaborating, Learning, and Adapting (CLA) have all grown out of this same gap. Each tries to close the distance between what organizations are learning and what they are doing.

    Senior evaluation leaders are increasingly the ones asked to close it.

    AI Fluency Is Entering the Leadership Brief

    Development institutions hold decades of evaluations, project documents, monitoring reports, and learning briefs. Much of that knowledge exists but stays out of reach in practice. A team may know that a useful lesson is buried somewhere in the archive and still spend weeks looking for it.

    AI-supported systems can help teams search that material, identify recurring themes, and retrieve relevant evidence far faster than before. Generative AI can support early synthesis as well, provided that sources remain visible and a person still checks the work.

    That value comes with new questions.

    A polished summary can still be incomplete. A pattern can be easy to detect and hard to interpret. A predictive model can look precise while drawing on weak or poorly governed data.

    Faster analysis does not remove the need for judgment. It raises the stakes for leaders who can ask how an output was produced, what it rests on, and what might be missing.

    The Leadership Profile Is Expanding

    Methodological expertise remains the anchor. Senior evaluation leaders still need a strong grounding in research design, theories of change, qualitative and quantitative evidence, causal reasoning, and the limits of inference.

    Around that foundation, several capabilities are becoming harder to do without.

    Leaders need enough AI and data fluency to question an output rather than simply accept it. They should understand how it was produced, what informed it, where bias might enter, and what needs expert review before it shapes a decision.

    Most evaluation leaders will not need to build models or write code. They do need enough understanding to guide responsible use and work well with the specialists who build the tools.

    They also need a stronger grasp of implementation and delivery. It is difficult to design a useful evidence system without knowing how decisions actually get made, where work stalls, and what pressures program teams are under.

    Relational skill matters just as much because evidence does not move through an institution on its own. Someone has to interpret it, debate what it means, and decide what happens next.

    Governance now belongs on this list too. Privacy, bias, consent, data sovereignty, transparency, and human accountability cannot sit entirely with the technical team.

    The emerging evaluation leader works across these boundaries. They connect program teams with technical specialists, translate evidence into terms executives can act on, and help institutions decide not only what can be measured, but what should matter.

    Evaluation Leaders Are Well Positioned for This Moment

    This shift can feel unsettling for people who have spent years building deep technical expertise. But evaluation leaders are not starting from behind.

    Evaluation leaders already understand that more information does not automatically create more insight. They know that methods shape findings, missing information matters, and patterns only become meaningful when interpreted in context.

    An indicator can be technically sound and still miss what a community actually values. Evidence is also shaped by power, incentives, language, and organizational culture long before anyone begins analyzing it.

    These are exactly the instincts responsible AI use requires.

    The opportunity is to carry evaluation’s strongest traditions into this wider arena. That means keeping rigor and independent judgment intact while building technological fluency and working more closely with delivery teams.

    A Field in Motion

    The profession has evolved before, expanding from measurement into learning, participation, systems thinking, and adaptive management. Each shift has asked practitioners to add new capabilities without giving up the discipline that makes the field credible in the first place.

    AI and real-time decision support are part of the next evolution. They are not the whole story.

    The larger shift is toward evidence that does more than explain what already happened. It is increasingly expected to help institutions steer while there is still time to change course.

    Outcomes expertise remains essential to that work. What has changed is the environment in which it now has to operate.

    For evaluation leaders, the real question is no longer only whether we understand outcomes and impact. It is whether we can connect that understanding to delivery, technology, learning, governance, and better decisions.

    That is what the next chapter of evaluation leadership will ask of us.

    Next in the series: The Evaluation Leader as Integrator will explore what it takes to connect program teams, technical specialists, senior decision-makers, and communities without losing rigor, context, or accountability.

  • The Hardest Part of Improvement

    The Hardest Part of Improvement

    There is no shortage of ideas for organizational improvement.

    Strategic planning processes identify priorities. Employee surveys surface recurring concerns. Customers explain where services fall short. Audits uncover risks. After-action reviews capture hard-won lessons while they are still fresh. Board retreats end with pages of flip charts covered in commitments and next steps. Evaluations add their own layer of recommendations to the pile. By the time those conversations are over, most teams have a fairly clear picture of what could be better.

    The harder question is what happens next.

    Why do some recommendations become everyday practice while others quietly disappear?

    Over the years, we have noticed that organizations are often better at identifying opportunities for improvement than they are at embedding those improvements into the way they actually work.

    That isn’t because people don’t care. Quite the opposite. Most teams genuinely want to improve. They spend time discussing findings, prioritizing recommendations, and developing action plans. There is often real energy in the room, and people leave believing the conversation mattered.

    Then everyone returns to their day jobs.

    Projects continue moving. New requests arrive. Vacancies need to be filled. Budgets shift. Leadership priorities change. The urgency of today’s work gradually overtakes the importance of yesterday’s reflection.

    Six months later, some recommendations have taken hold. Others remain exactly where they started: in a report, a meeting summary, or a strategic plan that everyone remembers but few have revisited.

    And people begin to realize that making improvement part of everyday work is harder than expected.

    Improvement Is a Different Kind of Work

    Perhaps one of the assumptions organizations make, without realizing it, is that once people understand what needs to change, change naturally follows.

    Experience suggests otherwise.

    Knowing what needs to change and making that change stick are two very different kinds of work. The first depends on insight. The second depends on systems.

    The first recommendations to move forward are often the easiest ones. They show that the process mattered and that the organization is taking action.

    The more difficult recommendations, however, are necessarily more difficult to address. They may require coordination across teams, changes to existing processes, additional resources, or sustained leadership attention. Those are much easier to postpone, even when everyone agrees they are important.

    And so, six months later, organizations are often in an uncomfortable position, having acted on some of what they learned, but definitely not all of it.

    It’s not that leaders are ignoring what they need to do.

    It is simply that harder changes are hard to implement, especially in light of all the other things that need to happen.

    The Real Work

    Organizations may not need more recommendations as much as they need stronger ways of carrying good recommendations forward.

    Knowing what needs to change is an important milestone. Designing an organization that can consistently act on what it learns is something else entirely.

    That may be the hardest part of improvement.

    Questions for Reflection

    Think back to a time that your organization was successful in driving improvements to a program or process. What did that look like? What enabled success? Does your organization know how to implement change successfully and on a regular basis?

    If so, then there is probably some combination of the following in place at the systems level:

    1. A Clear Review Process: A consistent mechanism for evaluating progress and identifying course corrections.
    2. Resource Realism: Structural clarity on the exact time, funding, and headcount required to implement changes.
    3. Executive Sponsorship: Sustained leadership buy-in and a willingness to fiercely protect the resources committed to the effort.
    4. Explicit Accountability: Defined roles, clear ownership, and transparent responsibilities for execution.
    5. Continuous Learning Loops: Simple, repeatable checkpoints to reflect on what is working and what isn’t.
    6. Cultural Reinforcement: Deliberate celebration of success and structural reinforcement of existing strengths.

    How does this compare with how your organization is structured today?

    If you could use a partner to help put these systems and habits in place, let’s connect. Whether you need a strategic diagnostic of your current operational processes or hands-on facilitation to design stronger learning loops, we are here to help you turn insight into sustained impact.

  • Why Monitoring and Evaluation Belongs in Every Project Manager’s Toolkit

    Why Monitoring and Evaluation Belongs in Every Project Manager’s Toolkit

    Monitoring and evaluation for project managers is not about turning project leads into full-time evaluators. It is about strengthening the judgment, adaptation, and results focus that good project managers already bring to their work. Project managers already do many of the things that make monitoring and evaluation valuable.

    They read situations. They notice when a project is starting to drift. They make decisions with incomplete information. They adjust course before anyone hands them a report telling them to.

    That instinct, the steady question of “Is this actually working?”, sits at the heart of monitoring and evaluation (M&E). Many project managers are asking it every day. They may simply not be calling it M&E.

    This instinct is becoming a more visible and expected part of the role. For a long time, M&E often sat with someone else: the M&E officer, the evaluation consultant, or the team that arrived at the midline or endline, collected data, and wrote a report after teams had already made many important decisions. In that model, M&E happened around the project rather than inside it.

    That model is becoming harder to sustain. For project managers, this shift does not have to feel like one more responsibility on an already full plate. It can be an opportunity to make the judgment they already use more systematic, more visible, and more useful.

    The Role Is Shifting, Whether the Org Chart Says So or Not

    Several forces are bringing M&E closer to the project manager’s day-to-day work:

    • Funders and clients want better evidence of progress. Many donors, clients, and organizational leaders no longer want to wait until the end of a project to understand what happened. They want to know whether the work is on track, what teams are learning, and how teams are adjusting along the way. That requires evidence to reach the people making decisions while there is still time to act.
    • Teams are often leaner than the work requires. Many projects do not have a dedicated M&E specialist, or they share one across several projects. When that support is limited, the need to understand progress does not disappear. Project managers are often well positioned to notice what information is missing and what evidence would help the team decide well.
    • Adaptive management depends on timely information. More organizations are asking teams to learn and adapt as they implement. If leaders expect a project to adjust based on real-time information, the people managing the work need information that helps them see what is changing and why.
    • Technology has made some data easier to access. Dashboards, mobile data collection, and simple analytics tools now help project managers see patterns without waiting for a formal study. These tools do not replace evaluation expertise, but they make it easier for teams to use information regularly and thoughtfully.

    Together, these shifts are narrowing the distance between project management and M&E. The work may still be formally assigned to a specialist, and that expertise remains valuable. However, project managers are increasingly part of the evidence conversation because they are closest to implementation, decisions, and day-to-day learning.

    Why This Matters for Project Managers

    Even when M&E does not appear in a job description or performance review, it supports the work project managers are already trying to do.

    • It strengthens the early-warning instinct project managers already use. Good project managers often sense when something is off. Monitoring makes those signals clearer by showing where participation is dropping, where timelines are slipping, where quality concerns are emerging, or where an assumption is not holding. With better information, managers can respond earlier and with more confidence.
    • It turns professional judgment into a stronger evidence base. Project managers make many decisions based on experience, context, and practical judgment. M&E strengthens that judgment rather than replacing it. When a manager needs to justify a pivot, defend a resource request, or explain why an approach needs to change, data can show the reasoning behind the decision.
    • It makes good management more visible. Some of the most important work project managers do is hard to see: the risks they identify early, the quiet adjustments that keep things on track, and the small course corrections that prevent larger problems later. Good monitoring documents those decisions and shows how the team used evidence to keep the project moving in the right direction.
    • It helps project managers tell a stronger results story. Activity reporting rarely tells the whole story. A manager who can explain the actions the team took, what changed, what the team learned, and how the team adapted its approach, communicates value more clearly to clients, funders, leadership, partners, and the team itself.
    • It connects management to meaning. Most people do not come to project work only to complete tasks. They want the work to matter. M&E helps project managers look beyond whether activities happened on time and within budget and ask whether the work is making a difference and how it can be strengthened.

    What Monitoring and Evaluation for Project Managers Looks Like in Practice

    Caring about M&E does not mean becoming a full-time evaluator. It means building a few practical habits into everyday project management.

    • Focus on the indicators that matter most. You do not need to track everything. Instead, understand the project’s logic well enough to identify the few measures that show whether the work is moving in the right direction.
    • Ask “How will we know?” early. This question does its best work during design, before activities begin. It helps teams clarify what success looks like, what information they will need, and how they will use it once they have it.
    • Use monitoring data as a management tool, not only a report. Ask what the data suggest, what may need to change, and what additional information would help the team move forward.
    • Work with the M&E support available to you. When a specialist or evaluation team is involved, share the decisions you are facing and the questions you need answered. That keeps M&E useful for implementation, not only for external requirements.
    • Tell the results story, not just the activity story. When reporting up or out, go beyond what the project delivered. Describe what changed, what the team learned, what adjustments were made, and why they mattered.

    An Example in Practice: Consider a training project manager who tracks only attendance. That manager can report how many people participated, which is useful but incomplete.

    If the team also gathers feedback on whether participants are learning the intended skills, where they need more support, and how they are applying the learning in their roles, the project gains information it can act on right away. That information can help the team improve future sessions, adjust materials, support participants more effectively, and tell a more credible story about the training’s value.

    In that case, M&E is not extra paperwork. It is part of improving the work while the work is still happening.

    None of this requires taking over the evaluator’s role. It simply means recognizing that the question “Is this actually working?” belongs close to the people managing the work.

    The Bottom Line

    Project managers do not need to become evaluation specialists to benefit from M&E. They need practical ways to use evidence as part of everyday management.

    The person responsible for delivering a project is often the one best positioned to notice what is changing, what questions need answering, and what the team should do next. M&E makes that judgment stronger, helping project managers lead with greater clarity, adapt with greater confidence, and tell a more credible story about the value of their work.

    Managing delivery and understanding results are increasingly connected. For project managers, that connection is not a burden. It is an opportunity to make good work even stronger.

    For readers who want to explore evaluation concepts further, resources such as BetterEvaluation and the OECD DAC evaluation criteria offer useful starting points.