1. Purpose
Programmes often repeat the mistakes of earlier ones, not for lack of reviews but because what was learned never changed anything. This procedure treats a lesson as complete only when it has changed a checklist, template, rule, guide or plan that the next programme will actually use.
It also keeps reviews blameless. The aim is to understand how the system of plans, tools, interfaces and rules allowed something to happen, so that people speak openly and the fixes go to the right place.
How a programme reviews what happened after a gate or at the end, turns observations into lessons, and makes sure the next project actually uses them. A lesson counts only when it changes something: a checklist, a template, a rule, a training item or a plan. The review is blameless and looks at the system, not at individuals.
10 more sections for registered members.