Learning guide · prototype · Suggested 15–25 minutes

Capability Requirements Builder

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

What is this resource?

A guided activity for Capability Requirements Builder. Explain how a design could help people Start from the system impact and failure modes, and what evidence would justify another iteration. Begin with the use case below. Keep the proposed design separate from what the current exercise actually implements.

How should I use it?

  1. Read Before you begin, then use Open the project to try the listed steps alongside this guide.
  2. Record an observation, explanation, transfer question and next test in the reflection panel. Saving is optional; Print one-page guide produces a paper copy.

How does this connect to LENS and learning engineering?

This activity connects a capability question to observable work and a possible next decision. What must a person actually do, under what conditions, to satisfy the system requirement? Design brief only. There is no working prototype to try yet. Use the reflection to distinguish what you observed from what still needs evidence.

Explain how a design could help people Start from the system impact and failure modes, and what evidence would justify another iteration.

Many systems specify technology, staffing, and process requirements in detail while leaving the human capability requirement vague: 'trained,' 'experienced,' or 'qualified.' If the capability is not defined at observable task grain, it cannot be designed, developed, or verified well.

Before you begin

Begin with the use case below. Keep the proposed design separate from what the current exercise actually implements.

A use case to work with

A new operations center needs analysts who can recognize when an automated alert is misleading. The prototype converts that need into observable decisions, evidence requirements, escalation actions, and representative test scenarios.

Try this

  1. Read the representative use case. Identify who must do what and under which conditions.
  2. Sketch one small intervention for this use case. Compare it with a simpler alternative.
  3. Choose one assumption to test. Use the evidence prompts in the brief to define an outcome that could change your mind.
Open the design brief (opens in a new tab)

Keep this guide open while you explore.

Pause & make sense

What are you taking away?

What evidence would make the requirement verifiable?

Optional. Notes are not sent to a server or scored. Browser storage is specific to this device and can be cleared; download a copy to keep it. Avoid sensitive information on shared devices.

Open my notebook

Notes stay on this page unless you choose to save or download them.

Help me make sense of this
  1. Separate what happened from why. Your observation is the result; your explanation is a claim that may need testing.
  2. Check another explanation. What else could account for the result? What comparison would distinguish them?
  3. Try without the support. Could you explain or perform the task in a new situation? Identify what evidence you would need.
  4. Choose one next move. Return to the concept, compare another example, or test one changed assumption.

Choose your next move

Return to the process, or examine how evidence could change a design.

The Capability Pipeline →Evidence-to-Impact Mapper →
Choose another question on the map