Learning Capture and Reuse Cycle¶
Recurring practice — instantiates Compounding Leverage
Turns each cycle's hard-won lessons into reusable, traceable capability so the team starts every next cycle from a higher floor instead of relearning the same thing.
The gain a team most reliably leaks is what it learns. Each project teaches something — a trap to avoid, a shortcut that worked — but the lesson lives in one person's head and evaporates before the next project can use it. Learning Capture and Reuse Cycle is the recurring practice that closes that leak: at the end of each cycle of work it extracts the lesson, generalizes it into a reusable form, and feeds it into the next cycle so the team's effective capability rises each time instead of resetting. Its defining move is conversion with a trail — not merely recording what happened (that is a report) but turning it into something the next cycle actively reuses, tagged with where it came from. What compounds is the falling cost and rising quality of doing similar work again; the durable shelf that holds the results is a separate sibling, the Reusable Asset Library — this mechanism is the loop that keeps filling and refreshing it.
Example¶
A management-consulting practice runs dozens of similar diligence engagements a year. Historically each team rebuilt its models and interview guides from scratch, and the sharp trick one team found in March was reinvented — badly — by another in September. The practice institutes a Learning Capture and Reuse Cycle: at each engagement's close, a short session distills what actually moved the needle into a generalized artifact — a reusable model template, a redlined interview guide, a "gotchas" note — each tagged with the engagement it came from. The next team is expected to start from those artifacts, not a blank page. Setup to outcome: within a year the median engagement's setup week collapses, because the twentieth team inherits the compounded judgment of the previous nineteen, and any warning in the "gotchas" note can be traced to the client that taught it — so a lesson that has since gone stale can be found and retired rather than trusted forever.
How it works¶
- Harvest at the boundary. Capture is triggered by a cycle completing — an engagement, a sprint, an incident — not left to whenever someone has time; the lesson is freshest and most honest right at the close.
- Generalize, don't just record. The raw incident is abstracted to the reusable pattern: a war story becomes a checklist item, a one-off fix becomes a template. This conversion is the step that turns experience into capacity.
- Make reuse the default entry point. The next cycle is expected to start from the artifact; a lesson nobody reuses never compounded.
- Keep the lineage. Each artifact carries where it came from, so reuse is trusted and a lesson that expires can be traced back and pulled.
Tuning parameters¶
- Capture cadence — every cycle versus milestone-only. Frequent capture loses less but taxes the team; rare capture is cheap but forgets.
- Generalization altitude — how far to abstract a lesson. Too specific and it never matches the next case; too abstract and it decays into a platitude.
- Reuse enforcement — from "artifacts are available" to "starting from the artifact is required." Stronger enforcement compounds faster but can ossify practice around yesterday's lesson.
- Retirement aggressiveness — how quickly stale artifacts are pruned. Loose lets the base rot into misleading advice; tight keeps it trustworthy but risks discarding a still-good pattern.
When it helps, and when it misleads¶
Its strength is converting a workforce's episodic cleverness into a rising floor — the deliberate way to ride the experience curve, where cumulative practice keeps lowering the cost of the next unit of similar work rather than leaving that decline to chance.[n1] Its failure modes are quieter than they look: capture theatre, where documents are produced to satisfy the ritual but never reused (a write-only knowledge base that grows a maintenance cost and no benefit); over-generalized platitudes that survive review because no one can argue with them; and stale artifacts that mislead precisely because a lesson expired but its lineage was never checked. The classic misuse is running it to look diligent — a beautifully documented repository that signals rigor instead of being drawn on. The discipline that guards against this is to measure reuse, not capture: the health metric is how often the next cycle actually starts from a prior artifact, and every artifact carries a lineage and an expiry.
How it implements the components¶
Learning Capture and Reuse Cycle realizes the flow side of a knowledge-based loop — the machinery that generates and re-injects lessons, not the shelf that stores them:
repeatable_yield_cycle— each unit of work is a cycle whose yield includes a reusable lesson; capture is timed to that cycle's close.reinvestment_conversion_path— the generalize-and-reuse step is the conversion that turns a raw lesson into added capability the next cycle draws on.compounding_lineage_record— each captured lesson carries the trail of which cycle produced it, making reuse traceable and the loop testable.
It does not hold the lessons as a durable, searchable store — that base is the Reusable Asset Library; nor does it guard the retained gain against decay (Retention) or measure the loop's effective rate (Effective-Rate and Doubling-Time Dashboard).
Related¶
- Instantiates: Compounding Leverage — grows the team's know-how each cycle instead of letting it reset.
- Sibling mechanisms: Reusable Asset Library · Retention · Automation Capability Reinvestment · Compounding Loop Map · Referral or Participation Reinvestment Loop
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: The mechanism enacts a repeatable cycle that captures lessons, makes them traceable and reusable, and carries them into the next work cycle.
Nearest alternative: Communication, Facilitation & Learning — The cycle builds shared capability, but ordered capture-to-reuse enactment is primary.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Organizational learning developed recurring conversion of project lessons into reusable procedures and capability.
Related originating lineages:
- Library & Information Science — Knowledge curation supplied traceability, indexing, and retrieval for reuse.
Review resolution: Both independent reviews place the primary lineage in organizational_management. The queued differences (domain_reach_disagreement) concern secondary metadata rather than primary provenance. The final retains library_information_science only where a reviewer supplied a formative-lineage rationale; downstream application by itself is not treated as origin. origin_mode=cross_disciplinary_synthesis records the relationship among origin traditions, while domain_reach=universal records application breadth separately. encyclopedia_synthesis=true reflects whether either reviewer identified a corpus-specific synthesis, and confidence=high preserves the more cautious evidence assessment.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The cycle and the Reusable Asset Library are deliberately separate: the practice produces vetted, lineage-tagged lessons, and the library stores and serves them. Keeping them apart is what lets you diagnose a dead knowledge base — usually a reuse or curation problem in the cycle, not a defect in the shelf — without confusing the two.
[n1] The experience (or learning) curve — the empirical regularity that unit cost tends to fall by a roughly constant percentage each time cumulative output doubles (Wright's Law; brought into strategy by the Boston Consulting Group). Deliberately capturing and reusing lessons is a way to ride it on purpose rather than leave it to accident. ↩