monival.org

02 · Evaluation approaches

Utilization-Focused Evaluation

Utilization-Focused Evaluation (UFE) is Michael Quinn Patton's approach built on a single premise: an evaluation should be judged by its usefulness to the specific people who will act on it. Every design decision — questions, methods, analysis, reporting — is negotiated with named primary intended users, for explicitly agreed intended uses, from the first day of the engagement.

Last updated · Reviewed against 4 cited sources

The founding premise

Most evaluation approaches start from a question about the programme. Utilization-Focused Evaluation starts from a question about the evaluation: who will use this, and for what? Patton’s premise is that an evaluation’s worth is measured by what happens because of it — the decisions informed, the improvements made, the understanding changed — not by its methodological elegance or the weight of its report [1]. That premise is not a soft one. It imposes discipline that many conventionally commissioned evaluations never face: before a single method is chosen, the evaluator must establish that specific people intend to do specific things with the findings, and design backwards from that.

The approach is deliberately agnostic about methods. A utilization-focused evaluation can contain a randomised trial, a contribution analysis, or a set of focus groups; the approach dictates how the design is chosen and by whom, not what it is [1]. That makes UFE compatible with every design in the methods cluster — and it makes “we did UFE” an empty claim unless the user-and-use negotiation actually happened.

Primary intended users: named people, not “stakeholders”

The load-bearing concept is the primary intended user. UFE rejects the abstraction of “stakeholders” — everyone touched by a programme, which in practice means no one in particular — in favour of identifiable individuals who have a genuine stake in the findings, the authority or influence to act on them, and the willingness to engage with the process while it runs [1][2].

Identifying them is an act of organisational analysis, not list-making. The test questions are concrete:

  • Who faces a real decision this evaluation could inform, on a timetable the evaluation can meet?
  • Who has the standing to act — budget authority, design authority, board influence?
  • Who will still be in post when the findings land?

The last question matters more than commissioners expect. Personnel turnover is the most consistently observed threat to use: an evaluation designed around a champion who departs mid-stream loses its user, and usually its use [2]. The practical mitigations are to recruit more than one primary intended user, to secure institutional as well as personal commitment, and to re-run the user identification step whenever the cast changes.

Intended uses drive everything downstream

With users identified, the next negotiation fixes the intended uses. The classic menu — judging overall merit for accountability or continuation decisions, improving the programme, generating knowledge for the field — leads to very different evaluations, and mixing them without deciding an order of priority is how evaluations end up doing several jobs badly [1]. The commitment device is explicitness: intended uses are written down, agreed, and used as the standard against which every subsequent design choice is checked. Should the sample prioritise breadth or the sites where the decision is contested? Should the report be a document at all, or a working session with the users? UFE answers every such question the same way: whichever serves the agreed use.

This is also where UFE connects to the Utility standards of the Program Evaluation Standards, which make attention to users and use a formal quality criterion for the profession, not merely one approach’s preference.

Utilization-Focused Evaluation pipeline with feedback loop and use leaks

Five boxes in a row: identify primary intended users; negotiate intended uses; design for use; analyse with users; facilitate use. Arrows join them left to right, and a return arrow runs from the last box back to the first, labelled next evaluation cycle. Beneath the pipeline, dashed arrows exit between stages, labelled user turnover, decision delayed, and report shelved — the points where intended use is lost.

next evaluation cycle: re-identify users firstIdentify primaryintended usersNegotiateintended usesDesignfor useAnalysewith usersFacilitateuseuser turnoverdecision delayedreport shelveduse leaks: where evaluations lose their users between stages
Figure 1. The UFE engagement as a use pipeline. Every stage is negotiated with the primary intended users; the dashed exits underneath are the characteristic points where use leaks away.Stage sequence follows Patton's U-FE Checklist (2013).

Process use

UFE names something most commissioning frameworks ignore: organisations change by doing evaluation, independently of any finding. Staff who help frame evaluation questions get clearer about their own programme logic; teams that sit in on analysis sessions learn to interrogate their data year-round. Patton calls this process use, and in UFE it is planned deliberately — sessions are designed so that the users’ engagement builds evaluative capacity, not just sign-off [1][4]. Process use is also the honest answer to a common commissioning complaint (“the findings told us what we already knew”): if the process forced the organisation to make its implicit knowledge explicit and act on it, the evaluation worked.

Working the checklist

Patton’s own U-FE Checklist turns the philosophy into an operational sequence: assess organisational and evaluator readiness; identify and engage primary intended users; negotiate intended uses; frame questions the users care about; make design and methods decisions with the users; keep them involved through data collection and interpretation; and actively facilitate use after findings exist, rather than declaring the job done at report submission [2]. The Western Michigan University checklist repository, where the evaluation-checklist tradition is curated, holds the wider family of tools that pair with it [3].

Two features of the sequence deserve emphasis. First, readiness assessment comes before user identification — if the organisation has no live decisions and no appetite for learning, the correct UFE outcome may be not to evaluate yet [2]. Second, facilitation of use is a budgeted phase, with the evaluator’s engagement continuing past the report into the meetings where findings meet decisions. An evaluation plan whose timeline ends on the report delivery date is, by UFE’s standard, unfinished — the concern picked up on use and management response.

Where UFE goes wrong

The approach’s honest account of itself includes its failure modes, and they are worth stating as bluntly as Patton does:

  • User turnover. The engagement is built on relationships with named people; when they leave, the evaluation must re-negotiate or it drifts. Treat every staffing change among primary intended users as a design event.
  • Capture. Designing around users means the loudest or most senior user can bend the evaluation toward questions that flatter their position. The corrective is a genuinely plural user group and an evaluator willing to hold the negotiated agreement against later pressure [1].
  • Use versus misuse. Findings can be used selectively, quoted out of context, or suppressed. UFE’s answer is not neutrality but vigilance: the evaluator attends to how findings are used, and the negotiated intended uses give a public benchmark against which misuse is visible.
  • Compliance gravity. In donor-funded settings the accountability report often reasserts itself as the real product. Naming intended uses in the terms of reference, and distinguishing them from reporting obligations, is the available defence.

UFE’s user-by-user, decision-by-decision logic assumes there is a reasonably stable programme to make decisions about. Where the programme itself is still being invented — where the thing to be used is rapid feedback rather than settled findings — the use-driven logic leads to developmental evaluation, which Patton built on exactly this foundation [4].

Sources

  1. Utilisation-Focused Evaluation (approach page) — BetterEvaluation (Global Evaluation Initiative), n.d..Living overview of Patton's approach, its rationale and step sequence. Accessed 18 August 2026.
  2. Utilization-Focused Evaluation (U-FE) Checklist — Michael Quinn Patton, hosted by BetterEvaluation, 2013.Patton's own operational checklist for running a UFE, updating his 2002 version. The closest thing to a canonical step sequence.
  3. Evaluation Checklists — The Evaluation Center, Western Michigan University, n.d..The checklist repository in which the UFE checklist tradition sits, alongside meta-evaluation and design checklists. Accessed 18 August 2026.
  4. Developmental Evaluation: Applying Complexity Concepts to Enhance Innovation and Use — Guilford Press, 2010.Patton's account of where UFE's use-driven logic leads when the programme itself is still developing — the sibling approach.