How to build a technology ROI measurement plan that survives go-live
The problem with most technology ROI frameworks is that they are built to win the business case, not to measure the outcome. By the time the project closes, the original baseline data is stale, the sponsors have moved on, and there is no mechanism to track whether the promised returns ever materialised.
A technology ROI measurement plan is not an addendum to the business case. It is a separate document that defines, before a line of code is written, exactly how you will know whether the investment worked.
Start with outcomes, not outputs
Most technology projects measure outputs: features delivered, systems integrated, training sessions completed. These are not ROI measures. They are delivery measures. ROI lives in what changed as a result of the delivery: processing time reduced, error rate dropped, revenue per customer increased, headcount released to higher-value work.
Every ROI claim in the business case needs a corresponding measurement in the plan. If you cannot specify how you will measure it, do not put it in the business case.
Define the baseline before you start
You cannot measure improvement without a baseline. This sounds obvious. It is consistently ignored. Common reasons: the data does not exist in a clean form, capturing it feels like extra work at the start of a project, or no one has explicit accountability for it.
The measurement plan must name the baseline metrics, who owns capturing them, in what system they will be recorded, and by what date before implementation begins. If the baseline cannot be established, the ROI claim cannot be made and should be removed from the business case rather than left as a number no one can verify.
Set measurement gates at 30, 90 and 180 days post-go-live
Technology ROI rarely materialises on go-live day. Adoption takes time. Process changes bed in. Training converts to habit. A single post-implementation review at project close almost never captures actual ROI.
Three measurement gates at 30, 90 and 180 days post go-live give a realistic picture of how value is accruing. The 30-day gate shows adoption health. The 90-day gate shows whether the process changes are holding. The 180-day gate is where meaningful ROI figures become available.
Name the accountable person
A measurement plan without a named accountable person is a list of intentions. The ROI measurement function needs to sit with someone in the business, typically the sponsor or the operational owner, not with the project team. The project team has delivered and moved on.
Feed back into the next investment decision
The most valuable use of a technology ROI measurement plan is not to validate the investment that has already been made. It is to improve the quality of the next investment decision. Organisations that close the loop between promised and delivered ROI consistently make better technology decisions over time. If the organisation has no record of whether its last five technology investments delivered their stated returns, it has no basis for confidence in the next one.
