This is part 5 of Adaptive Learning Capacity, a five-part series on how organizations learn while the work is happening. New to the series? Start with part 1.
This is the last post in a series following Linden Pathways, a composite workforce program, through what it takes to learn while the work is happening. In the last post, Linden acted on what it had learned. They launched an evening track, made Denise’s Saturday check-ins an official part of the program, dropped the readiness assessment that had been screening out the people they most wanted to serve, and had an honest conversation with their funder about what all of that might do to their completion numbers.
The first cohort went well. Shift workers on the evening track stayed at noticeably higher rates than the Thursday group, and referrals from the family shelter started to pick back up. Overall completion dipped a few points, as expected, and the workforce board took it in stride.
Then spring arrived.
Marisol went on family leave for six weeks. The annual grant report came due the same month as the site visit. A new cohort started, bigger than any before it. The eight-week check-in on the evening track, the one they’d written down so carefully, got pushed once and then again. The Saturday calls, now officially part of the program, slid back to being something Denise did when she could find the time.
Nobody decided to let any of it go. Nothing was holding it in place, and the busy season did what busy seasons do.
If you’ve ever made a good change and watched it fade a few months later, you know this feeling. I see it constantly, and it’s rarely about commitment. Linden’s team cared a great deal about what they’d learned. What they didn’t have yet was a way for that learning to survive a hard month.
Good intentions need somewhere to live
In the learning cycle I use with organizations, this is the final piece, embedding: making learning part of how the work gets done, so it doesn’t depend on one person’s energy or one good meeting. Over the last three posts, we followed Linden through noticing, making meaning, and responding. Embedding is what lets an organization keep doing all three, in a busy month and a slow one, with a full staff or a short one. In the first post, I described adaptive learning capacity as whether an organization lets people use their skills when it counts. This is how that capacity gets built.
When people hear “learning culture,” they often picture a mindset: curiosity, openness, humility. Those qualities matter a lot. Culture also lives in the ordinary structures of work, though. It shows up in the meetings you already hold, the questions that appear on agendas, and the moments when decisions actually get made. That’s where learning either finds a home or drifts away.
Attach learning to what already happens
When organizations want to learn more, they often add something new: a learning meeting, a lessons learned document, a reflection retreat. Each of those can help, and each is also one more thing to remember in a week that’s already full. When things get busy, the new thing is usually the first to go.
A sturdier approach is to ask where learning could live inside something you already have to do. When Linden regrouped after that spring, that’s what they looked for.
The monthly staff meeting already existed, so they set aside 10 minutes at the start for case managers to share what they were hearing from participants. Supervision already happened every other week, so the program director started asking in each session what participants were saying that wasn’t show up anywhere else. The board already got a quarterly program update, so they added a short section on what the team was learning and what it might mean for strategy. And new staff onboarding now included the story of the readiness assessment, so nobody new would bring it back as a quick fix.
Each of those changes supported on of the three moves. The 10 minutes at the staff meeting and the supervision question gave noticing a regular place to happen. The board section made room for making meaning at the level where strategy gets set. And the onboarding story kept an old response from coming back.
Your existing rhythms will look different. At a foundation, they might be docket review, grantee site visits, or the annual strategy retreat. In a coalition, the steering committee agenda or the partner newsletter. On a small team, the weekly check-in and the end-of-year report. The question to ask about each one is the same: what could this already-scheduled moment do for our learning, if we asked one more question in it?
Infrastructure doesn’t have to be technology
When I use the word infrastructure, people sometimes picture software. Software can help, but most of what made a difference at Linden was much simpler: a recurring agenda item, a clear path for a case manager’s observation to reach the program director, and a one-page decision log.
The decision log mattered more than anyone expected. Each entry recorded what they decided, what evidence it was based on, and when they planned to come back to it. That meant the eight-week check-in on the evening track lived someone besides one person’s memory. It also means that two years from now, when completion numbers are under pressure and someone suggests a screening step at intake, there will be a record of why Linden stopped doing that.
Most organizations have shared drives full of reports that hold a great deal of knowledge nobody can find when they need it. What made Linden’s log useful was that it sat close to the decisions it informed. So when you’re deciding how to capture something you’ve learned, it helps to ask how it will find its way back into a future decision, and who will be there to see it.
Put learning where decisions get made
Linden’s biggest decisions came once a year, when they built the program plan for the workforce board in January. In past years, they had held a reflection session each spring, after the plan was already submitted. It was always a good conversation, and it had almost no chance of changing anything until the following year.
So they moved it. The team now holds a learning review in November, built around the same question from the second post: What will it take for participants with the most barriers to stay through completion? It’s the same people and the same amount of effort, but now the conversation happens six weeks before the decisions it’s meant to inform.
Many organizations have plenty of learning going on and plenty of deciding going on, in completely separate places. Connecting the two is often a matter of timing.
What leaders do counts as infrastructure too
Some of the most important structures at Linden weren’t written down anywhere. It lived in what the executive director did.
At that first November review, she told the story of the meeting where she’d offered the “more barriers” explanation and everybody had nodded. “I was partly right,” she said, “but I was also wrong in a way that mattered, and I’m really glad Marisol and Denise spoke up.” It took about 30 seconds, and it told everyone in the room that disagreeing with her was welcome, more clearly than any policy could.
What leaders ask about tells people what deserves attention. How they respond to uncomfortable news tells people whether it’s safe to bring it again. You can put “What are you noticing?” on every agenda, but if people have learned that the right answer is “everything’s on track,” the question turns into a ritual.
Watch for routines that stop working
Learning infrastructure can go stale like anything else. The staff meeting question that sparks a real conversation this year can become a box everyone checks next year. The board update section can fill up with the same three bullet points every quarter. Eventually a routine like that becomes what Linden’s quarterly report was at the start of the story: something that keeps running without showing anyone what’s changing.
So build in a small moment, maybe once a year, to ask of each routine whether it’s still telling you anything. If it isn’t, change it or let it go. Your learning infrastructure deserves the same curiosity as everything else.
Start with your weak link
You don’t need to build all of this at once, and I’d genuinely suggest you don’t try. A comprehensive “learning system” can quickly become its own layer of bureaucracy, which helps no one.
At Linden, the weak link was the path between what Denise saw and what the program director knew. For your organization, it might be somewhere else. These questions can help you find where learning most often gets stuck:
Noticing: Do people know what’s worth paying attention to? Is there somewhere for what they notice to go?
Making meaning: Do they get to make sense of it with people who see the work differently?
Responding: Can that understanding reach the people with authority to act? Can a decision actually change? Does anyone pay attention to what happens afterward?
Embedding: Does what you learned this time show up the next time you face a similar question?
Wherever the answer is shakiest is probably the best place to start. Build one thing there.
How you’d know it’s working
As an evaluator, I can’t end a series like this without asking how you’d know whether any of this is making a difference.
One of the simplest indications of progress I know is time: how long it takes for something one person notices to reach the people who can act on it, and for them to decide what to do. At the start of the story, Linden’s early signals took the better part of a year to turn into a decision, and even then only becaues of a chance conversation.
About 18 months later, something new came up. Two evening track participants mentioned to Denise that the city was cutting a bus route that ran past the training site at 8pm. She raised it at the next staff meeting, in the 10 minutes set aside for exactly that. It reached the program director within a week. Within a month, Linden had worked out a transportation arrangement with one of its hospital partners, before the route change took effect.
In the space of a month, Linden noticed something, made sense of it together, and responded, and none of it depended on one person carrying it alone. Nothing about that was dramatic. It was just fast, and nobody had to get lucky for it to happen.
You can start tracking this without building anything new. The next time someone raises something that seems worth attention, write down the date. Then note when it first reaches the people who could act on it, and when a decision gets made, even if the decision is to wait and watch. After three or four of these, you’ll have a rough sense of how long learning takes to travel in your organization and where it tends to stall. That stalling point is often your weak link.
Where this leaves us
At the start of this series, I asked how Linden found out that the people it was built to serve were slipping away. The honest answer was by chance. The program director happened to stop by a desk, and Marisol happened to mention what she’d been seeing.
What Linden built over the following year wasn’t elaborate: a few questions in meetings that they already held, a decision log, a review moved to a better month, and a leader willing to say she’d been wrong. Each piece made it a little easier to notice what was changing, make sense of it together, and respond. Together, they meant that the next time something shifted, finding out didn’t depend on chance. That’s what I mean by adaptive learning capacity: an organization that can keep learning its way forward, especially when it doesn’t yet know what to do.
A few places to start
If you’d like a starting point, here are some deliberate small moves, each one attached to something you probably already do:
In the next month, add one recurring question to a meeting that already happens, such as What are you noticing that you don’t know what to make of yet?
In the next month or two, try a short debrief after an upcoming event: What did we expect, what actually happened, and why might those be different?
Within two months, get clear on who can make the call on one kind of change that comes up often.
Within three months, add a question about what you’re learning to a report or update you already produce.
Thank you for following Linden’s story with me. If one of these ideas stayed with you, I’d love to hear which one.
The Adaptive Learning Capacity series:
Building the Habits that Make Leaning Last (you are here)
