Ideas

If you’re in the middle of implementation, learning isn’t something you wait for at the end — it’s how you make better decisions right now. This piece shows what learning actually looks like in the day-to-day work of teams, and the simple structures that help turn information into action.

The volume and pace of data coming at our organizations can feel overwhelming. Information arrives in fragments. We move quickly from one task to the next, with little time to absorb what we just learned — if we learned anything at all.

Maybe this sounds familiar …

Everyone joins the meeting — some in person, some on camera — chatting about the weather or a pet in the background. The meeting is about survey findings on a project now in its third round of data collection. The presenter jumps into the data: charts, graphs, key findings. They end on a slide with “main takeaways.” There’s a pause. A few thoughtful questions come up — about rigor, about community voice, about what can be shared externally.

Then the meeting ends. People move on to the next thing.

So, did we learn anything actionable? Maybe. But how might we shift “maybe” to “absolutely?”

Let’s replay that same meeting.

This time, after the greetings, the team lead names the purpose: We’re here to learn how to strengthen the implementation of this work together. Before the presentation starts, they ask: What do we know now that we didn’t know before?

As the data is shared, the conversation shifts:

• Which insights match what we’re seeing more broadly in the landscape — and which don’t? Why?
• What feels surprising? What feels evergreen?
• What feels useful for our work? What doesn’t?
• What do we want to try, change, or stop doing?
• Who else needs to hear this?

Now the meeting is doing something different. It’s not just sharing information — it’s creating knowledge.

What does learning look like during implementation?
Learning is not a separate step at the end of implementation. It happens in how people think, talk, and act while the work is unfolding. In practice, it looks like:

• Teams pausing to reflect in the middle of action;
• Testing ideas, adjusting quickly, and naming what they’re seeing;
• Connecting data to lived experience and professional judgment; and
• Surfacing assumptions — not simply sharing conclusions.

At its core, organizational learning culture helps people act on new knowledge. That requires space to reflect openly, consider consequences, and make sense of what’s happening together.

This is where conversation matters.

Drawing from work on knowledge creation, learning happens when we bring together:
• Tacit knowledge (experience-based insight); and
• Explicit knowledge (data-driven insight).

When those come together in real dialogue, something new can emerge.

What structures support strong feedback loops in organizations?
Good intentions aren’t enough. Learning needs structure. Feedback loops and continuous improvement cycles can exist at different levels — from quick team reflections to organization-wide learning systems. What matters is that they’re intentional, repeated, and connected to decisions.

Here are a few structures we see working in practice:

1. Structured team reflection practices à Build short reflection into regular team meetings:

• What stands out from what we’re seeing?
• What might this mean for our work?
• What should we try next?

These don’t need to be long — but they do need to be routine.

2. Decision-focused debriefs and processes à Move from insights to action with a few consistent prompts:

• What priority should we give these insights (low, medium, high)? Why?
• What values or assumptions are shaping our choices?
• What actions do we want to take — and what will they achieve?
• Who needs to be involved or informed?

This connects learning directly to decisions.

3. Cross-team learning collaboration à Create space to share learning across teams:

• Monthly learning huddles
• “What we’re trying / what we’re learning” updates
• Peer exchanges across programs

The goal is to share knowledge, not just store it.

4. Organizational learning systems à At the organization level, leaders help “weave” learning together:

• What are we learning across teams?
• What are we doing differently because of it?
• What do we still need to figure out?

This can show up in quarterly reviews, leadership meetings, or internal communications.

5. Documenting learning or the organizational memory loop à Strong feedback loops don’t happen in the moment — they build over time:

• Timelines that show how decisions evolved
• Visuals that map internal and external factors influencing choices
• Short memos that reveal key insights, decisions, and rationale

These approaches can be simple as long as they’re intentional.

This helps teams:

• Look back and understand why decisions were made;
• See patterns in what has (and hasn’t) worked; and
• Avoid repeating past missteps — or revisit ideas with new context.

Without it, learning is easily lost. With it, organizations build a shared memory that strengthens future decisions.

How do we know learning is actually happening?
You can feel it.
In organizations with strong learning cultures:

• People reference past lessons in current decisions;
• Teams adapt more quickly because they’re active attention;
• Mistakes are examined, not hidden;
• Knowledge moves across teams, not just within them; and
• Staff see how their work connects to the bigger picture.

In many organizations, this doesn’t happen on its own. There is often a role — formal or informal — that helps connect the dots.

This might be a team lead, evaluator, or someone in a strategy or learning role. They pay attention to what’s emerging across teams, use documentation to trace patterns, and help answer:

• What are we learning across the organization?
• What are we doing differently because of it?
• Where do we need to go deeper?

This “weaving” function is what turns individual team learning into organizational impact — both internally and in how the organization shows up externally.

Final thought: Continuous improvement mindset.
Learning during implementation isn’t about adding more meetings or more data. It’s about changing how we use the moments we already have.

When organizations create space to reflect, connect insights to action, and share learning across teams, implementation itself becomes a source of continuous improvement.

The question isn’t just: “Are we collecting good data?”
It’s still: “Are we learning yet?”

Community Science can help you design and implement feedback loops that facilitate learning. Please contact Amber Trout at atrout@communityscience.com.

References
1. Argyris, C., & Schön, D. A. (1996). Organizational learning II: Theory, method, and practice. Addison-Wesley.
2. Garvin, D. A. (1993). Building a learning organization. Harvard Business Review, 71(4), 78–91.
3. Grantmakers for Effective Organizations. (2016). Learning together: Actionable approaches for grantmakers. GEO.
4. Kikoski, J. F., & Kikoski, C. K. (2004). The inquiring organization: Tacit knowledge, conversation, and knowledge creation. Praeger.
5. Preskill, H., & Torres, R. T. (1999). Evaluative inquiry for learning in organizations. SAGE Publications.
6. Senge, P. M. (2006). The fifth discipline: The art and practice of the learning organization (Rev. ed.). Doubleday.
7. Center for Evaluation Innovation. (2021). Approaches to learning amid crises: Reflections from philanthropy. CEI.