Sabina's hackathons becoming mandatory quarterly events is a good outcome, but the tutorial ends there without asking what happens when she moves on. A lesson on sustaining change would address what happens after the deal is closed:
- how to embed the change in formal policy rather than informal norm so it survives personnel turnover
- how to build redundancy by distributing stewardship across multiple people so no single departure kills the initiative
- how to connect your change to recurring organizational rhythms (budget cycles, annual reviews, onboarding processes) so it does not have to be re-justified from scratch each year
- how to create written institutional memory so that five years later someone can answer "why do we do it this way?"
Sabina's hackathons becoming mandatory quarterly events is a good outcome, but the tutorial ends there without asking what happens when she moves on. A lesson on sustaining change would address what happens after the deal is closed: