Working draft.

Approach: capability, cycle and step explanations

The iteration cycle, worked through five real cases

The Capability Pipeline

About this resource · How to use it · Learning engineering connections

What is this resource?

Five worked narratives apply a seven-step capability cycle with continuous refinement across healthcare, government services, aviation, education and autonomous vehicles. Teaching interpretations accompany the source narratives; historical claims have not been independently rechecked here.

How should I use it?

  1. Pick a case and begin in Study mode to inspect the seven numbered steps and the continuing refinement reflection. Use the central Refine prompt to revisit any earlier assumption.
  2. Try Find the turn or Predict first before revealing the decision-specific explanation. Compare your reason with the presented evidence.
  3. Compare two cases and use the coupled-loops diagram to identify how a change to work conditions could change learner performance.

How does this connect to LENS and learning engineering?

Comparing contrasting cases supports conditional judgment: the same process can turn on different constraints. In LENS terms, map both the human capability and system conditions, then ask which measurement would reveal a failure. Locating a turning point in a worked case does not establish transfer to a new system.

Seven steps, one loop: understand → map → design → build → instrument → experiment → evaluate → understand. Refine sits at the center: use evidence to improve any part of the work throughout the cycle. Start with a challenge; develop a capability that acts on the problem. Explore the seven steps and a continuing refinement question across a hospital screening workflow, a federal insurance marketplace, an airliner, a math-tutoring program at scale, and a self-driving car. What changes case to case isn't the shape of the loop — it's which single step the story actually turns on.

The cycle in use

A challenge enters Understand through the dotted arrow. Follow Steps 1–7, then return from Evaluate to Understand. Refine throughout. Deployment connects the resulting capability back to the challenge through adoption and effective use.

The Capability Pipeline: seven steps, continuous refinement A challenge enters Step 1, Understand, through a dotted arrow. The numbered cycle continues through 2 Map, 3 Design, 4 Build, 5 Instrument, 6 Experiment and 7 Evaluate, then returns directly to Understand. 8 Refine is at the center and informs every step. The cycle produces a capability. A return arrow labeled Deployment connects Capability back to Challenge. Challenge 8. Refinethroughout 1Understand 2Map 3Design 4Build 5Instrument 6Experiment 7Evaluate produces Capability Deployment
Evaluate (7) → Understand (1)Evidence returns us to the challenge. Refine is a continuing practice at the center of all seven steps.Challenge → cycle → capability → deployment → challengeAdoption, effective use and results inform how we understand the challenge in the next cycle.

Why it matters

A decision to make

Ask yourself

The step that decides the story is rarely evaluate. It's usually earlier — design, build, or instrument — because those steps determine what evaluate is even able to see. A system instrumented to track only its own headline metric cannot evaluate a cost that metric doesn't measure.

Below, five cases — one apiece from government services, aviation, healthcare, education, and autonomous vehicles — are walked through all seven steps, with a continuing refinement reflection. Each carries one clearly marked point where a different upstream decision would plausibly have produced a different downstream result.

Learning guide. Open a step for why it matters, a decision cue and a question to apply to this case. Teaching commentary is an interpretation of the presented narrative, not new historical evidence. In Find the turn and Predict first, the decision-specific explanation appears only after your guess or reveal.

Pick a case

Same seven steps and continuous refinement, five different systems. Each card names the domain, the real frame, and how the case actually turned out. Three ways to work a case are below the picker — study it worked out, find where it turns yourself, or commit to a call before you're shown what happened.

Mode

Integrative Practice

Learners and systems develop together

The seven steps, with continuous refinement, support linked cycles of learner development and system evolution. Joint practice couples them at every step: people influence the system, and experience with the system shapes learning.

Development, contributions and evidence Feedback and revision
Learner development and system evolution coupled through joint practice A shared challenge guides two parallel loops. Learner development creates learning conditions, implements teaching and practice, and investigates knowledge, skill and agency. System evolution creates requirements and designs, implements deployment and operation, and investigates performance. Each loop revises its creation step. Both contribute continuously to joint practice, which couples their work during creation, implementation and investigation. Joint-practice findings revise learning and systems. Evidence of collective capability, effective use and learner flourishing feeds back to shared goals, resources and conditions.
Read down the solid arrows for contributions and evidence, and follow the dashed arrows back for revision. Joint practice is continuous throughout both loops. Its position below them shows their connection; it does not add a later step.

Integrative Practice keeps the loops coherent. Connect each choice to its rationale, evidence needs and subsequent revisions. Use findings from authentic practice to revisit goals, resources, roles and learning conditions.

This is a conceptual view of how the seven-step cycle and continuous refinement fit together. Learner development, system evolution and collective capability each need their own evidence.