Community-serving organizations and collaboratives rarely lack commitment, expertise, or information about how their work could be stronger.
Across organizations and collaboratives, people hold different pieces of the picture. Staff see where people are getting stuck. Participants and community members know where programs, services, and initiatives fit their lives and where they do not. Partners see connections, gaps, and duplication across a system. Leaders understand the broader pressures shaping difficult decisions.
The challenge is often finding enough space to bring those perspectives together, make sense of them collectively, and decide what they mean for the work.
And that is becoming increasingly difficult. As demand grows, programs fill, wait-lists increase, staff stretch to meet ongoing commitments, and funding and accountability pressures intensify, so stepping back can feel difficult to justify. The ethical and operational pressure is to keep delivering: support the next participant, deliver the next program, meet the next target, complete the next report, and respond to the next immediate need or opportunity.
These pressures shape how organizations and collaboratives are able to approach program design, evaluation, and service review. Design may be compressed into the work required to secure funding and launch a program or initiative quickly. Evaluation may become organized around required indicators and reporting cycles. Service review may arise when efficiency, restructuring, or difficult resource decisions become urgent.
These are real pressures. Organizations, collaboratives, funders, and other partners are responsible for accounting for resources, understanding results, and making responsible choices. The difficulty is that the learning value of design, evaluation, and review can become crowded out by their most immediate requirements.
Under those conditions, learning can begin to feel separate from the real work.
We think learning has to be part of the real work.
Programs, Services, and Initiatives Evolve, Whether or Not There is Time to Redesign Them
Few long-standing programs, services, collaborative initiatives, or service networks look exactly as someone would design them today.
Organizations and collaboratives are constantly adapting. Community needs and interests change, participation patterns shift, funding priorities evolve, new partnerships emerge, policy environments change, and staff find practical ways to respond to challenges as they arise. Most of these adaptations are thoughtful responses to real circumstances, made with the best information and resources available at the time.
They also tend to happen gradually, one decision at a time. A new activity is added to meet an emerging need or opportunity. Staff develop a workaround to keep a program accessible or running smoothly. A reporting requirement leads to a new process or data system. Partners divide responsibilities according to the capacity available at that moment.
Over time, the work evolves while the shared understanding of it may stay much the same. The systems for learning, coordination, and reflection may not develop at the same pace as the programs, services, and initiatives themselves.
Intentional learning creates an opportunity to reconnect what is happening now with the needs, opportunities, purpose, values, and outcomes that guide the work.
- Are we still responding to the right needs and opportunities?
- Are people experiencing the program, service, or initiative as intended?
- What have staff, participants, partners, and community members learned that has not yet shaped the model?
- Which parts of the work are helping, and which are creating friction?
- What could continue, change, connect differently, or conclude?
These are learning questions. They are central to quality, mission fulfilment, and impact.
It's possible to have information without having useful learning
Sometimes important information is missing. Just as often, useful knowledge already exists across program and service data, participant, member, and audience experience, community feedback, frontline insight, partner perspectives, and years of professional practice.
Across an organization, partnership, or collaborative, different people see different parts of the work and the structures available to bring those perspectives together may be limited.
Data can remain in dashboards and reports. Participant stories may support communications without shaping program decisions. Staff may repeatedly identify the same operational problem without having a place to explore its wider causes. Partners may understand gaps in a service pathway or network differently based on where they sit within it.
Gathering more information will not necessarily resolve that. What may be missing is an opportunity to interpret what is already known, identify patterns and tensions, and decide what the learning calls for.
Reports can capture learning, but they do not create it. The greater value lies in bringing people with different experiences and perspectives together to interpret what they are seeing.
Shared sensemaking moves an organization or collaborative from individual observations and disconnected information toward a fuller understanding of what is happening, why it may be happening, and what could happen next.
Program design can create shared clarity
Program design often begins with the practical requirements of launching a program, service, or collaborative initiative: developing a proposal, identifying activities, preparing a workplan, and describing intended outcomes. These foundations help communicate an idea, secure resources, and coordinate implementation.
Funding timelines and immediate community needs can create pressure to move quickly from identifying a problem to deciding what the program will do. Assumptions about participant needs, pathways to impact, partner roles, and the conditions required for success may remain implicit because there has been limited opportunity to examine them together.
Design can create space to make those assumptions visible.
It can bring staff, partners, participants, people the work is intended to reach, community knowledge, research, and other forms of information into a conversation about the need or opportunity being addressed, the changes the work seeks to support, and the role it can realistically play within a broader system.
This shared picture can reveal where people understand the work differently before those differences become operational problems. It can clarify how activities, relationships, resources, and external conditions are expected to contribute to outcomes. It also creates a clearer basis for recognizing what the organization or collaborative needs to learn once implementation begins.
The questions include: What are we trying to do? Why do we believe this approach will make a difference? What conditions need to be present? What will help us recognize when the model needs to evolve?
Alongside a plan, program design can create the shared clarity that helps organizations and collaboratives implement, learn, and adapt with greater confidence.
Evaluation can be reclaimed as a learning practice
Evaluation has become closely associated with reporting, performance targets, and demonstrating that resources were used as promised.
Those purposes matter. Organizations, collaboratives, and funders have responsibilities to communities, participants, and the public. All need credible information about the outcomes of their work and investments.
When accountability becomes the dominant frame, useful learning can be crowded out. Funding agreements may emphasize volumes, outputs, contractual obligations, and short reporting cycles. Organizations and collaboratives understandably organize their data systems around the information they are required to provide. Questions that would help understand the work more fully may receive less attention because they sit outside the formal reporting structure.
An organization or collaborative may be able to report how many people it reached while knowing much less about:
- who was not reached;
- how people experienced the program, service, or initiative;
- whether it met the need or opportunity that brought people there;
- why outcomes differed among participants;
- what staff and partners had to do behind the scenes to make the work possible;
- whether the current model remains the best use of limited capacity.
Externally required information and internally useful learning can reinforce one another. Too often, they develop as separate systems, and the immediate reporting obligation wins.
This can narrow evaluation into an exercise in proving and reporting. It can also make evaluation feel burdensome to staff and participants, particularly when information is collected without a clear line of sight to how it will be interpreted or used.
We need to reclaim evaluation as a learning practice.
Evaluation can help an organization or collaborative reduce uncertainty. It can test assumptions, explore what is contributing to results, notice unintended effects, and create a stronger basis for decisions. That learning can improve programs, services, initiatives, and resource choices internally, while giving communities, funders, partners, and advocates a clearer account of what the work is accomplishing and what it is teaching us.
Evaluation can ask: What can we credibly demonstrate? What are we learning? What will we do with that learning?
Over time, this can build a clearer and more grounded understanding of what the work needs.
Service review can widen the field of view
Service reviews often arise during periods of change. Funding may be uncertain, demand or participation may have shifted, partners may be reconsidering their roles, or leaders may need to make difficult decisions about priorities and resources.
Efficiency and sustainability are real considerations. A service review creates an opportunity to place them within a broader picture of community need and interest, participant experience, service quality, coordination, outcomes, operations, relationships, and organizational or collaborative purpose.
That wider view can surface important distinctions. A service may appear efficient on paper while creating barriers for participants. Two programs may appear to overlap while serving different needs or groups. Staff may have developed workarounds that keep a service functioning but consume significant capacity. Community needs, participation patterns, referral pathways, or partner relationships may have changed in ways the current model no longer fully reflects.
A review can bring together the people, experience, operational information, service data, community trends, and strategic considerations needed to understand the whole picture.
It helps an organization or collaborative understand how the service or service network is functioning now, whether it remains relevant and accessible, how it fits within a broader system, and what would be required for it to evolve.
The central question becomes: Is this still the right service, initiative, or service network, structured and delivered in the right way, for the people and communities we hope to serve?
Service review can create the perspective needed to make consequential choices about what may continue, change, connect differently, expand, be redesigned, or conclude.
A Connected Practice of Learning
Program design, evaluation, and service review support learning at different moments.
Design can make intentions and assumptions visible before and during implementation. Evaluation can help organizations and collaboratives learn from what happens in practice. Service review can widen the lens and support choices about the future of a service, service network, or collaborative initiative.
They do not always occur in sequence. A review may reveal the need for a clearer program theory. An evaluation may surface a design assumption that needs to be reconsidered. A new program or initiative may adapt as people learn what works in practice. A collaborative may need to revisit both its shared outcomes and how partners contribute to them.
Together, these practices support a recurring cycle of clarity, action, learning, and adjustment.
Making learning part of the work
Creating opportunities to learn does not require putting programs, services, or initiatives on hold for an elaborate study. The approach can be proportionate to the questions being asked, the decisions to be made, and the capacity available.
Sometimes that involves a formal evaluation or service review. Sometimes it begins with revisiting a program or initiative design, making better use of existing information, or creating space for people who see the work differently to think together.
What matters is whether the learning helps people make better choices. Learning may lead to a clearer program model, a more useful set of measures, a redesigned service pathway, stronger partner roles, or a decision to simplify, expand, connect, or conclude part of the work. It may reveal an internal process that consumes staff capacity without strengthening accountability or quality. It may help an organization or collaborative communicate more credibly about its results, its learning, and the investments still required.
Do/able can help organizations and collaboratives create the conditions for useful learning. We can help frame the questions that matter, involve the people closest to the work, bring different forms of knowledge together, facilitate shared sensemaking, and translate what is learned into practical direction.
Organizations and collaboratives already hold deep knowledge about their communities and their work. A thoughtful process can help that knowledge become more visible, connected, and usable.
Community-serving organizations and collaboratives will continue to work in uncertain, interconnected, and changing environments. Making room to learn is one of the ways they can protect quality, make thoughtful choices, and remain responsive to the communities they serve and engage.
Let’s Keep the Conversation Going
If you’re thinking about these concepts and interested in talking through how your organization integrates learning we’d love to have that conversation.
