Course 2
Operating an Outcome
What keeping an outcome actually involves, from the upkeep to the off-switch.
A named outcome is not a kept outcome. Something has to remain true, something comes round again, something is in the way, somebody has to answer for it, and at some point it has to be declared finished or let go. This course is the operator's view. It is about the maintenance of a state, which is quieter work than reaching one and is where most of the effort actually goes.
5 lessons
Lessons in this course
- 2.1 What has to stay trueReaching an outcome is one moment. Keeping it is the rest of the time.
- 2.2 What recursRenewal cycles, filings, reviews and intervals: the clockwork inside an outcome.
- 2.3 What it is blocked onA blocker named precisely is usually half solved. A blocker named vaguely never is.
- 2.4 Who is answerableA mandate, a delegate and the difference between helping and owning.
- 2.5 Knowing when it is doneA definition of done that another person could check, and knowing when to stop entirely.