Build capability through a live problem
Design development around work participants must actually do.
RedQuadrant practice note
Select a piece of work which participants have some ability to influence. It should be consequential enough to sustain attention and bounded enough to permit action during the programme. A hypothetical case can introduce a method; it cannot establish whether participants can use it in their own setting.
Agree the relationship between learning and delivery. Sponsors need to know what time, access, and decision authority participants require. Participants need room to discover that the original brief was incomplete or that the proposed solution was wrong.
Teach a method when it helps participants make a better observation, distinction, or decision. Ask them to explain what they used, what it allowed them to see, and what it left out. Competence includes recognising when a familiar method is a poor fit.
Build short cycles of application and review between sessions. Keep evidence of the work, including mistakes and changes of mind. Peer discussion becomes more useful when people bring a real choice and its consequences rather than an account designed to demonstrate progress.
At the end, review what participants can now do, the changes their work produced, and the conditions needed to sustain both. A certificate records completion. Continued capability depends on practice, support, and an organisation willing to use what people have learned.