Moving to Outcomes: Transforming Social Systems Through Results-Based Accountability: Summary & Key Insights

When I began working with public systems, I realized that most of our measurement frameworks were fundamentally misaligned with our goals. We were tracking procedures and budgets rather than the actual effects on people’s lives. Every day, staff were busy producing reports, writing grant proposals, and complying with process requirements. These activities, though important, didn’t guarantee success. They only proved effort. In Results-Based Accountability, we start by distinguishing between activity-based measures and outcome-based measures.

Traditional approaches ask, 'What did we do?' RBA asks, 'Is anyone better off?' This simple shift in language changes everything. It compels us to define success in terms of real-world improvement — children ready for school, people with jobs, families in stable housing, communities where citizens feel safe. Once we identify those outcomes, we can align our activities to serve them. RBA begins with results at the population level: the broad, community outcomes that reflect public well-being. From there, we cascade down to performance accountability, where the focus is on programs and agencies.

Understanding this two-part structure is crucial. Population accountability concerns entire communities, asking how all children, adults, or families fare within a jurisdiction. Performance accountability focuses on how well a specific program or agency contributes to those population results. By keeping these levels distinct yet connected, RBA ensures clarity and coordination. It prevents agencies from confusing isolated program metrics with community outcomes, and instead encourages collaboration to achieve shared goals.

To make this shift practical, RBA introduces clear definitions: results express the condition of well-being we seek; indicators track progress toward those results; performance measures assess how effectively programs achieve their specific objectives. Each measure flows logically from the fundamental principle that accountability must answer both how much we did, how well we did it, and whether anyone is better off.

Take, for example, a youth employment program. A traditional report might emphasize how many workshops were held or how many participants enrolled. RBA asks deeper questions: how many participants gained employment, sustained it for six months, or increased their income? Those are measures of real impact. Once you adopt this logic, your reporting stops being a routine exercise — it becomes a mirror that reflects the actual effectiveness of your work.

Through many years of implementation, I’ve seen that this clarity reshapes organizational culture. Staff begin to see data not as a compliance burden, but as a tool for storytelling and learning. Managers stop asking 'Did we meet our quota?' and start asking 'Did we change lives?' This shift, subtle yet profound, transforms accountability from a system of punishment into a system of progress.

In other words, Results-Based Accountability doesn’t reject performance measurement — it redeems it. It gives measurement meaning by reconnecting it with purpose.

One of the most practical and transformative components of RBA is what I call 'Turn the Curve thinking.' This process gives organizations and communities the ability to move from data observation to data-driven action. When we talk about turning the curve, we mean improving performance over time against a baseline. Every indicator and measure has a trend — a curve — that shows whether things are getting better, worse, or staying the same. The purpose of accountability is to turn that curve upward in the direction of improved well-being.

Let me walk you through the logic. First, we identify the baseline data for a given indicator — say, high school graduation rates or homelessness figures. Then, we engage stakeholders to understand what lies behind those numbers. Data is not cold; it carries stories. Turning the curve means digging into those stories, finding leverage points, and applying practical actions that can bend the trendline toward better outcomes.

The process is collaborative by nature. No single agency can turn a population-level curve alone. Change emerges when partners across education, health, housing, and community sectors come together around shared results. In workshops I’ve led, one of the most powerful experiences comes when teams see the baseline graph, point to the line that represents reality, and declare: 'We’re going to turn that curve.' That declaration creates hope, but also responsibility. It anchors ambition in measurable action.

The method follows common sense steps. Review the baseline, diagnose contributing factors, brainstorm what works elsewhere, and choose specific, doable actions that can accelerate progress. Importantly, the process doesn’t demand perfect data or massive resources; it thrives on clarity and focus. Participants leave with a plan built around evidence and commitment.

Consider one example from child welfare services. A department noticed its rate of repeat maltreatment cases was not declining despite extensive training and compliance programs. Using Turn the Curve sessions, staff examined the drivers — case load pressures, inconsistencies in follow-up, communication gaps between agencies. They looked at data from other jurisdictions with better curves and discovered that joint case reviews between agencies dramatically cut recurrence rates. They instituted that change, tracked progress, and within a year the curve genuinely turned downward. This wasn’t magic; it was disciplined accountability applied through partnership.

What makes the Turn the Curve process powerful is not its technical sophistication but its accessibility. Anyone in any community can use it. It democratizes data. It moves accountability out of administrative reports and into collective conversation where people can see, discuss, and act upon the evidence together. When you turn the curve, you’re not just changing numbers — you’re changing lives.