Building the Capacity to Use Evidence

An organization can commission strong research, build sophisticated dashboards, and train staff in analytical tools without becoming meaningfully evidence-informed. Capacity is demonstrated not by the volume of information produced, but by whether evidence routinely shapes questions, choices, implementation, and learning.

Reports often arrive at the end of a project and compete with established priorities, limited time, unclear authority, and operational pressure. Training can increase individual knowledge without changing how teams make decisions. Technology can improve access to information while leaving interpretation fragmented. These are not simply communication problems. They are signs that evidence use has not yet been built into the organization's operating system.

The 2024 CDC Program Evaluation Framework treats learning from and using insights as a cross-cutting action and acting on findings as a core evaluation step. The GAO's 2026 training and development guide emphasizes alignment with mission priorities, integrated learning approaches, stakeholder involvement, and continuing evaluation. The Federal Data Strategy likewise frames learning, leadership, and accountability as connected organizational responsibilities.

Evidence use is not a final stage after research is complete. It is a capability designed into how an organization identifies questions, develops people, makes decisions, and learns from action.

1. Establish a shared agenda for learning.

Evidence capacity begins with agreement about which questions matter most. Without priorities, analytical teams respond to isolated requests, measures multiply without purpose, and research resources scatter across topics that may be interesting but not consequential.

A learning agenda provides a practical structure. It identifies strategic and operational questions, explains why they matter, and clarifies what evidence already exists and what still needs to be developed. The agenda should connect to mission, planning, budgeting, program improvement, and accountability rather than sit beside them as a separate research document.

Priority questions should be specific enough to guide inquiry but durable enough to support learning over time. They also need owners, decision points, and an expected use. “Understand program effectiveness” is too broad. “Determine which implementation conditions are associated with sustained participation before the next funding decision” creates a clearer path from evidence to action.

2. Clarify ownership across the evidence cycle.

Evidence work crosses organizational boundaries. Program teams understand operations and context. Data stewards know the strengths and limitations of information systems. Researchers and evaluators design credible inquiry. Technology teams maintain tools and access. Leaders allocate resources and retain authority for decisions.

Capacity grows when these responsibilities are explicit. Teams should know who frames the question, approves the design, protects the data, reviews the analysis, interprets the result, decides what action follows, and monitors what happens afterward.

Clear ownership does not mean that one office controls the entire process. It means collaboration has a structure. Defined roles reduce the risk that evidence is produced without an intended user, that decisions are made without appropriate review, or that everyone assumes someone else is responsible for follow-through.

3. Create recurring routines for interpretation and action.

Evidence is more likely to influence decisions when teams encounter it through regular operating routines rather than exceptional presentations. Those routines might include monthly performance conversations, quarterly learning reviews, structured after-action discussions, decision memos, implementation checkpoints, or planned interpretation sessions during an evaluation.

The routine should do more than display results. It should require participants to distinguish among:

what the evidence directly establishes;
what remains uncertain or contested;
which assumptions have changed;
what options and trade-offs are available;
who has authority to act; and
what will be measured after action is taken.

The CDC's guidance on acting on findings emphasizes planning for use, preparing findings for use, and facilitating insights into action. These activities should begin before the final report. Interim discussions can build shared understanding, surface interpretation problems, and prepare decision-makers for findings that challenge expectations.

4. Build skills around real work.

Evidence capacity requires technical competence, but one-time training rarely changes practice on its own. People need opportunities to apply new skills to authentic decisions, receive feedback, work with experienced colleagues, and revisit concepts as responsibilities evolve.

A strategic development approach begins with the capabilities the mission requires. Different roles may need different depths of skill:

leaders need to ask good questions, interpret uncertainty, and recognize overstatement;
program staff need to define measures, understand data-generation processes, and connect findings to implementation;
analysts need technical methods, documentation practices, and the ability to communicate across disciplines;
data and technology teams need stewardship, privacy, security, interoperability, and user-centered design; and
facilitators need to help groups interpret evidence, navigate disagreement, and convert learning into feasible action.

The current GAO training guide describes planning, design and development, implementation, and evaluation as an integrated cycle. That cycle is useful beyond formal training programs: learning investments should align with organizational priorities and be assessed by whether they improve performance, not simply by attendance or satisfaction.

5. Close the loop between action and new evidence.

An evidence-informed decision is still a hypothesis about what will work in practice. After action is taken, the organization needs to observe implementation, track intended and unintended effects, and decide whether to continue, adapt, expand, or stop.

Closing the loop requires an explicit measurement plan. What would progress look like? Which early indicators would suggest the approach is off track? What feedback will be gathered from the people implementing or experiencing the change? When will the decision be revisited, and who will participate?

This feedback should update the learning agenda, improve data and tools, and shape future development priorities. In a mature learning system, evidence does not terminate in a decision. It informs action, action produces new information, and that information improves the next decision.

A concise capacity test

Leaders assessing their organization's ability to use evidence should be able to answer five questions:

Priorities: Do we share a small set of consequential learning questions connected to mission and decisions?
Ownership: Are responsibilities clear from question formation through action and monitoring?
Routines: Where and when do teams interpret evidence, examine uncertainty, and decide what follows?
Capability: Do people have the skills, tools, time, and support needed for their roles?
Learning: Does implementation generate feedback that changes future decisions and evidence-building priorities?

A gap in any one area can limit the value of otherwise strong research. The purpose of the test is to identify where evidence use breaks down and where a focused investment could strengthen the entire system.

Capacity is visible in ordinary decisions.

An evidence-informed organization is not one in which every decision requires a formal study. It is one in which people routinely ask what is known, how it is known, what remains uncertain, who may be affected, and how the organization will learn from what it does next.

That capacity is built through aligned questions, accountable roles, recurring routines, applied development, and disciplined feedback. Over time, these practices make evidence less of a special product and more of a normal feature of responsible management.

Building the capacity to use evidence.