What we look at
- Who actually uses it, and what they still do in email.
- Whether status is visible without a meeting.
- Whether the named constraint moved.
- What people invented around the system in the first weeks.
Why this step
A go-live followed by silence is how the old stitching comes back. We review against the live week. We adjust what people will not use. We close the file when the process carries the work, and the manager is no longer the integration layer.
What we do
- Schedule reviews against the live process.
- Change what the week refuses.
- Leave when the named constraint is carried by the process.
What we do not do
- A handover that assumes the process will adopt itself.
- A warranty in place of sitting with the people who use it.
- Closing the file because the build tasks are done.
Related problems
The other steps
How a file actually runs
Discovery, a scoped build, then scheduled reviews. That is the calendar of the file.
Describe the process as it runs. A specification is optional.