Over the past two weeks, we’ve examined how “evidence-based” standards shape nonprofit work, and how they can sometimes function as gatekeepers. But even when access isn’t the issue, another challenge often emerges: Implementation.

Nonprofit teams are asked to deliver evidence-based programs without the infrastructure to fully support them. The research may be strong and model may be sound, but staffing can be lean, funding is restricted, training is uneven, reporting requirements are heavy, and community needs are evolving.

When expectations outpace infrastructure, the strain doesn’t show up in research articles. It shows up in burnout, adaptation, and quiet improvisation.

This exercise helps you make visible what often goes unnamed: The gap between research and real-world capacity (and what teams lose in the process.)

Objective:

To identify where implementation expectations exceed infrastructure and determine what support teams require to close the gap.

This activity is ideal for:

• Nonprofit staff and leadership teams responsible for implementing research-informed programs
• Program directors and managers navigating the day-to-day realities of delivery
• Evaluation and learning staff trying to align rigor with feasibility
• Executive leaders assessing whether expectations match capacity

(Funders can benefit from the insights generated, but this exercise centers the experience of the teams doing the work.)

What you’ll need:

• A whiteboard, flip chart, or shared virtual document
• Sticky notes or a digital commenting tool
• A copy of the evidence-based model or framework your team must use to guide your program or service
• 45–60 minutes of uninterrupted time

The steps:

Step 1: Name the Evidence

Think about a program or service that you’re currently implementing. Identify the model, framework, or standards guiding this program or service.

Write down:

• What the model, framework, or standard requires
• The conditions it assumes
• The outcomes it promises

Keep this descriptive, not evaluative. Simply describe the expectations and assumptions as they are, without debating whether they’re realistic, fair, or effective.

Step 2: Map Your Infrastructure

Now shift focus inward.

List:

• Current staffing levels and roles
• Funding structure and restrictions
• Available training and expertise
• Reporting and compliance demands
• Community needs and contextual realities

You may start noticing some tension here.

Step 3: Identify the Implementation Gaps

Place the two lists side by side.

Ask:

• Where do expectations exceed infrastructure?
• Where does the model assume resources you don’t have?
• Where are staff already adapting the model to make it workable?

These points of friction are not failures. They are signals.

Often, this is the moment staff realize the strain they’ve been carrying is about alignment, not competence.

Step 4: Determine What Support You Need

For each gap, discuss:

• What additional infrastructure would support implementation?
• Which gaps require resource changes versus expectation changes?
• Who has authority to adjust timelines, scope, or reporting?

This reframes the conversation from “Why aren’t we meeting the standard?” to “What would make this realistic?”

Let’s process

During the exercise, you may notice:

• Your team is already doing significant adaptive labor to bridge gaps.
• Some expectations assume infrastructure that doesn’t exist.
• Burnout often stems from misalignment, and not from lack of commitment.

To reflect further, ask:

• Where have we been compensating for missing infrastructure?
• Which assumptions about capacity should we challenge?
• What conversations does this exercise make possible with leadership or funders?

Key takeaway

Evidence can guide strong programs but it can’t implement itself. When funders or institutions ask nonprofit teams to deliver research-informed work without the infrastructure to support it, the gap doesn’t disappear. Staff absorb it.

Mapping that gap makes the invisible visible. It validates the experiences of teams navigating lean staffing, restricted funding, and evolving community needs while leaders and funders hold them to rigorous standards.

Naming the strain strengthens alignment. And alignment—not pressure—is what makes evidence sustainable in practice.

Raise Your Voice: Where does implementation strain show up most in your work—and what support would make it more sustainable? Share in the comments section below.

Was this useful? Subscribe to the Raise Your Voice newsletter, and explore my consulting services.