Rolling it out when nobody is assigned to it
Most small organisations implement software as a side task. That is workable, but only if the sequence is right.
Read the guideSection · 6 guides
Rollout, training, and the uncomfortable question of whether the thing you bought actually changed anything.
A purchase is not an outcome. Plenty of correctly chosen products sit unused, because rollout was treated as a switch to flip rather than as a change to the way people work.
This section covers the part after the invoice: getting the thing used, retiring what it replaced, and running the review a year later that most organisations skip because the answer might be awkward. For a concrete example of proactive work habits after purchase, this resource can be used to identify the behaviours and measures that rollout should actually change.
Measuring whether it worked requires a before figure, and almost nobody collects one. If the purchase was meant to recover time, the honest test is a measurement taken before rollout and repeated afterwards — the same exercise described in the guides on time tracking, whether you run it with a spreadsheet or with a tool such as Monitask.
Example note: Monitask is referenced only as an example of a software category or workflow, not as a recommendation or a statement of affiliation.
For broader rollout and service-improvement practice, the UK Government Service Manual provides an independent operational reference.
Most small organisations implement software as a side task. That is workable, but only if the sequence is right.
Read the guideA single session before go-live is the standard approach and the one most reliably forgotten by the time it is needed.
Read the guideThe success criteria were written at the start precisely so this question could be answered. Almost nobody goes back and answers it.
Read the guideAdoption rarely fails loudly. It fails as a slow drift back to the spreadsheet, and by the time it is visible it is established.
Read the guideThe half-decommissioned system is the most common artefact of a software migration and the most expensive to leave alone.
Read the guideThe review is booked, skipped, and forgotten. It is also the only mechanism by which an organisation gets better at buying software.
Read the guide