From challenge to capability

Approach

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

What is this resource?

A working approach to developing capability: a definition, a seven-step cycle and questions that make each step useful. Refinement continues throughout rather than waiting for a final stage.

How should I use it?

  1. Start with the capability definition, then follow the pipeline from a challenge through Evaluate and back to Understand. Read the text explanation if the diagram is difficult to view.
  2. Use each step’s decision cue and question on a problem you know. Follow the worked-case or simulation link when you want to examine an example or test a decision.

How does this connect to LENS and learning engineering?

Learning engineering connects human flourishing, learning sciences and systems engineering through evidence-informed iteration. In LENS, this means examining what people can do together with the tools, authority and opportunities that enable action. The cycle makes those assumptions and evidence needs explicit; completing its steps alone does not demonstrate learning or impact.

Bring human flourishing, learning sciences and systems engineering to the same challenge. Understand the work, change the conditions for action, and use evidence to revise decisions. The pipeline offers seven steps with 8. Refine throughout.

A working definition

What we mean by capability

The capacity of a person, team, or human-system arrangement to accomplish valued work under stated conditions, with usable opportunities to act.

We examine output quality, capability, learning, and impact as distinct claims. Each needs evidence that fits the work, its conditions, and the decision being made. A good output alone does not establish that someone learned, can perform independently, or can act in another setting.

William Gray-Roncal & James Diamond · Working definition for community discussion, developed in Capability Matters.

Three foundations, one shared purpose

The human, the science and the system must succeed together.

Develop capability that serves people, rests on credible learning evidence, and works in the conditions where it matters.

HumanHuman flourishing
People have a say, find purpose, and can act with dignity and security. Examine who benefits and who carries the cost.
Does this help people live and act well?
ScienceLearning sciences
Use research about learning, practice and transfer. Choose measures and comparisons that can test the explanation, including evidence that could challenge it.
What supports the claim that learning occurred?
SystemSystems engineering
Connect people, tools, tasks, authority and feedback. Test the complete arrangement, including its limits, maintenance and recovery.
Can this work reliably in the intended setting?

Our synthesis connects these fields. OECD’s Education for Human Flourishing (2025) informs the human-purpose component. Its Learning Compass also connects agency with individual and collective well-being.

The capability pipeline

Start with a challenge. Follow Understand → Map → Design → Build → Instrument → Experiment → Evaluate, then return directly to Understand. Refine any step when evidence changes an assumption; the numbered sequence is a guide to decisions, not a rule to delay feedback.

On a narrow screen, scroll the diagram horizontally. The numbered explanations below provide the same sequence in text.

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
Challenge → cycle → capability → deployment → challenge. Deployment puts the capability to work through adoption and effective use. Results and evidence return us to the challenge; Refine stays at the center throughout.

What each step asks of us

  1. Understand

    Frame the capability gap before choosing a solution. A sponsor’s target can reward activity while leaving the actual problem unchanged.

    Decision cue: Distinguish what people need to do from what is easy to count.

    Ask: Whose task, access conditions or definition of success have you not checked?

  2. Map

    Map capabilities and conditions. People, tools, authority, incentives and support jointly shape what is possible. A skills diagnosis alone can miss a system constraint.

    Decision cue: Connect human and system requirements, dependencies and competing explanations.

    Ask: What observation would distinguish a knowledge gap from an access, workload or tool problem?

  3. Design

    Compare interventions and their tradeoffs. A useful intervention acts on a plausible mechanism within your authority; adding features does not resolve an invalid assumption.

    Decision cue: Compare a simpler alternative, name who keeps control and identify a stop condition.

    Ask: What does this choice exclude, and who carries the burden if it fails?

  4. Build

    Make the smallest useful candidate real. Construction reveals integration, staffing and recovery requirements that a plan can hide.

    Decision cue: Exercise a representative task and its failure path before expanding scope.

    Ask: Which dependency, fallback or correction path must actually work?

  5. Instrument

    Choose evidence that can change a decision. A convenient metric can improve while the capability you care about stays unchanged.

    Decision cue: Choose the outcome, comparison, missing-data checks and decision rule before reading results.

    Ask: Could these measures reveal that your preferred approach failed, or exclude an important group?

  6. Experiment

    Test the instrumented intervention under representative conditions. A bounded experiment can reveal how access, staffing and support affect the result before wider use.

    Decision cue: Specify the comparison, permissions, support and stopping rule for the test.

    Ask: What evidence would justify changing the intervention or moving toward deployment?

  7. Evaluate

    Interpret evidence within its limits. A favorable trend can reflect chance, selection, exposure or another change; a null can reflect an ineffective intervention or limited evidence.

    Decision cue: Separate observed change from causal explanation and unmeasured outcomes.

    Ask: What claim is supported, for whom, over what period, and what remains unknown?

The LENS approach across settings

These cases show how different kinds of work call for different evidence.

Rwanda RapidSMS

Map a referral from the community health worker to the facility. Compare whether a message was received with whether the family received care.

Latin American Learning Analytics

Use local inquiry to design an advising tool. In a pilot, observe whether advisers can act on a flag and whether students can challenge a mistake.

Read why LENS uses a casebook.

Explore the approach in practice

Worked narratives and a fictional simulation offer different ways to examine these decisions. Each has its own instructions, evidence limits and controls.

Explore five worked cases

Study a narrative, find the turning point, or predict before revealing the explanation. Compare how different system constraints change the decision.

Try the branching simulation

Make decisions in a fictional scenario, inspect outcomes, and compare revised branches. Its probabilities are teaching assumptions, not forecasts.

Why it matters

A decision to make

Ask yourself