Lesson Capture vs. Operationalization: Why Identified Findings Still Need Operating Change

Two leaders study a layered operating structure where a pale diagnostic plane is held above a darker sustainment frame, with one marked weak joint showing where change can decay.

Captured findings still have to become operating change

Today’s Executive Briefing: Lesson Conversion Failure

Von Zedtwitz’s survey of R&D managers found that roughly one in five projects receives a post-project review (Von Zedtwitz, R&D Management, 2002). The number is over two decades old. The pattern underneath it has not changed.

The problem was never the absence of review. Most organizations, when pressed, produce findings. The post-mortem runs. The debrief circulates. Participants nod in recognition. The findings are accurate. The architecture that produced the original failure stays untouched.

Sandia National Laboratories drew the distinction most organizations skip. An observation is a data point. A lesson identified is an observation that has been analyzed and assigned a recommendation. A lesson learned is a verified change in behavior or institutional process that resulted from the lesson identified, confirmed through a closed-loop process with a named owner and a governance board (Sandia National Laboratories, Considerations for Implementing an Organizational Lessons Learned Process, 2013).

Most organizations live permanently at the second tier. Lessons get identified. Recommendations get written. The organization treats the act of identifying the lesson as having learned it.

The review exists. The findings land. The language of accountability is present. And no structure underneath converts any of it into changed ownership, changed process, or attached consequence. The posture looks right. The installation never happens.

The person who built the review process did the right work. The question is whether anyone built what comes after. An owner who checks six months later whether the condition returned. A gate that catches the same pattern before it produces the same cost. The difference between managing what you already know and acting on what you already know is the difference between reviewing a finding and changing the structure that produced it.

Tool: The Lesson Conversion Check

Five questions. Ten to fifteen minutes. One page.

Pick the last structural finding your leadership team formally agreed on, something documented, discussed, and acknowledged as a real gap.

  1. What did the review identify?
  2. Who owns changing the structure that produced it?
  3. What process, gate, cadence, or authority line changed afterward?
  4. Where will the organization check whether the condition returned?
  5. What consequence now exists if the same pattern appears again?

If question one has a clear answer and questions two through five do not, the lesson was captured. It was not converted. The organization is carrying an identified lesson as if it were a learned one. The gap is not knowledge. The gap is installation.

© 2026 Lauren Carter. This instrument is proprietary. For individual diagnostic use only. Reproduction, adaptation, or redistribution in any form requires prior written permission from Lauren Carter.

What has your organization already learned that still has no owner, no changed path, and no consequence attached to it?

If this names the condition underneath what looks like the problem, there is more here. Subscribe for the next Briefing.

— Lauren

Clicking tells us you meant to answer. Hitting submit sends us the actual response. Without submit, we can’t see your choice.

If this is the conversation someone in your network has been needing, forward it. They'll know.

Lauren Carter

A twice-weekly diagnostic on the structural conditions underneath how organizations actually perform. Each issue names a mechanism most strategy conversations skip, then gives you a tool to test it in your own operation. Built for executives, founders, and operators who already suspect the problem is architectural.