Shortlist

Section · 6 guides

Adoption

Rollout, training, and the uncomfortable question of whether the thing you bought actually changed anything.

Home/Adoption

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.

Adoption7 min read

Reviewing the decision a year on

The review is booked, skipped, and forgotten. It is also the only mechanism by which an organisation gets better at buying software.

Read the guide