The period that follows.
WHAT HAPPENS IMMEDIATELY AFTER
Productivity falls, as people learn.
WHAT TO EXPECT
Questions in volume Errors from unfamiliarity Processes discovered to be missing Resistance surfacing
WHAT NOT TO INTERPRET AS FAILURE
Any of that, within reason.
WHAT TO PROVIDE
Accessible support Rapid resolution of blocking problems Visible acknowledgement of difficulties
WHAT TO TRACK
Issues raised, by area Time to resolution Recurring problems
WHAT RECURRING PROBLEMS INDICATE
Configuration or training gaps.
WHAT TO PRIORITISE
Anything preventing work Anything producing wrong data
WHY WRONG DATA FIRST
It compounds, and correction becomes harder.
WHAT TO RESIST
Adding features during stabilisation.
WHY
Attention is needed on making the current scope work.
WHEN TO DECLARE STABILITY
When issues fall to a manageable level and processes run without intervention.
WHAT TO DO THEN
Review what was deferred, and plan the next phase.
WHAT TO CAPTURE
Lessons, while they are fresh.
WHAT TO HAND OVER
Ownership, from the project to the business.
