Learning guide · prototype · Suggested 15–25 minutes
Capability Drift Detector
About this resource · How to use it · Learning engineering connections
What is this resource?
A guided activity for Capability Drift Detector. Explain how a design could help people Establish the performance outcome that has drifted and the time window over which the system changed, 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?
- Read Before you begin, then use Open the project to try the listed steps alongside this guide.
- 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 signals distinguish capability drift from equipment or process drift? 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 Establish the performance outcome that has drifted and the time window over which the system changed, and what evidence would justify another iteration.
A capability that was once adequate can degrade gradually as tools, staffing, procedures, or local workarounds change. Because there is no single launch event, organizations often notice the problem only after performance has already drifted.
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 maintenance organization has updated components and troubleshooting procedures over several years. The detector finds a growing cluster of escalations around one diagnostic step that veteran staff handle informally but newer staff cannot reconstruct.
Try this
- Read the representative use case. Identify who must do what and under which conditions.
- Sketch one small intervention for this use case. Compare it with a simpler alternative.
- Choose one assumption to test. Use the evidence prompts in the brief to define an outcome that could change your mind.
Keep this guide open while you explore.
Reflect
What threshold should trigger investigation rather than automatic retraining?
Observation → Explanation → Transfer → Next test
Pause & make sense
What are you taking away?
What threshold should trigger investigation rather than automatic retraining?
Help me make sense of this
- Separate what happened from why. Your observation is the result; your explanation is a claim that may need testing.
- Check another explanation. What else could account for the result? What comparison would distinguish them?
- Try without the support. Could you explain or perform the task in a new situation? Identify what evidence you would need.
- 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.
Choose another question on the map