A successful software launch can produce a peculiar moment: the project team celebrates while the operational team begins discovering what daily use actually involves.
MBIE released a stocktake of its active technology initiatives and a review of their governance on 21 September. The stocktake covered 70 initiatives active as at 21 July, ranging from routine technology work to larger programmes. The review identified improvements to oversight; the existence of 70 initiatives should not be confused with 70 failed projects.
Define the result before buying the system
The lesson for other organisations is to connect technology decisions to a specific operating problem. A proposal should explain what will improve, who will experience the improvement and how the business will tell whether it happened.
Replacing an ageing system may be necessary, but even then the intended outcome should be clear. Reliability, simpler administration and better information are different goals and may require different choices.
A named business owner is important because technical delivery and commercial benefit are not identical. A system can meet its specification while leaving an awkward process largely untouched.
Budget for adoption
Training, data preparation and changes to working practices belong in the investment decision. Leaving them until the end can make a reasonably priced system expensive to use well.
It also helps to decide what will stop. If staff must maintain the new system and every old workaround indefinitely, the expected saving may never materialise.
After launch, a short review should compare the result with the original case. That review is more useful when it can identify something to change, rather than simply record that the project has closed.
Public-sector technology operates at a different scale from many private businesses, but the management questions are familiar. Clear responsibility, realistic adoption costs and visible benefits make a digital investment easier to judge before, during and after delivery.
