A digital project can produce its agreed deliverable without yet showing whether the business should spend more. An Albany business may have a configured form, a report or a working prototype, while the effect on actual operating work still needs examination.
Measuring results means connecting the project purpose, evidence and next decision. It does not require a complicated dashboard. It requires clear definitions and enough context to distinguish completed work, useful capability and assumptions about future benefits.
The next spending decision gives measurement a purpose
Identify what the business is considering: extending a workflow, adding functions or commissioning a further stage. Explain which question must be answered before that commitment makes sense. A measure is useful when it informs that question.
Government goal-setting guidance connects measurable aims with actions, resources and review. Apply that connection before collecting figures. A large report can still leave the next decision unclear if no one has defined what the project was meant to establish.
A deliverable and an operating result are different
A supplier may complete configuration while staff still need practice or an agreed rule. A form may save a request correctly while the receiving person lacks enough context to respond. These observations concern different parts of the project.
Keep technical completion separate from operational acceptance. Identify the person authorised to assess the business task, including its receiving step. A general completion label should not make unresolved preparation or an important exception disappear from the record.
A baseline needs definitions and conditions
Describe how the relevant task works before the change, where suitable evidence is available. Define the measure and its source. Task time, corrections and customer understanding answer different questions and should not be casually combined.
Business.gov.au’s productivity guidance includes task time, customer experience and rework among possible measures. Select those appropriate to the actual project. Keep the period, staffing and request types with the baseline so the later comparison remains interpretable. If the recording method changes, mark that difference explicitly. A new system may make previously invisible correction work easier to count, so an increased total can require investigation rather than being read automatically as worse performance.
Evidence is stronger when the whole task is visible
A shorter first action may leave another person with more checking or correction. Follow the task through handover and a useful next step. Include the staff member receiving the result, not only the person using the new screen.
Record relevant exceptions and any assistance needed. An ordinary request, an amendment and an incomplete case can reveal different limitations. Use safe examples where possible and avoid creating unintended live commitments merely to obtain a result for the project report.
A bounded test supports bounded conclusions
A prototype or small pilot can clarify understanding under stated conditions. It does not establish every future workload, access need or commercial result. Retain the actual role, version and configuration that were examined.
The DTA’s research guidance, written for government, considers task-based testing and documenting what has been tested. Use those methods as prompts while keeping the private business context and the limits of its own activity clear.
Observed change is distinct from a claimed cause
Requests, staff capacity or the offer itself may change during the project. A difference in the measured result does not by itself prove the digital intervention caused it. Note relevant changes and consider plausible alternative explanations.
Separate the finding, the explanation and the action being proposed. If evidence is missing, identify what would help. A useful review can support further investigation rather than producing an invented precise saving to justify the next package.
- The project purpose and next spending question.
- The deliverable, operating task and acceptance owner.
- The baseline, definitions and relevant conditions.
- The observed result, limitations and competing explanations.
- The proportionate next action and retained work.
Full effort remains part of the result
Include preparation, staff practice, source checking, support and continuing administration alongside supplier charges. A technical improvement may still require internal work. That can be reasonable, but it should remain visible in the comparison.
Distinguish forecast savings from observed effort. If a proposed next stage assumes a staff role or source record the business cannot provide, resolve that dependency before treating the budget as complete. An expected benefit should not quietly become a confirmed resource.
The review should produce an owned decision
Record whether to retain the present scope, correct a limitation, gather more evidence or prepare another bounded stage. Name who will act and what would be examined next. Keep significant unanswered questions and their evidence requirements with the dated decision.
A useful measurement record leaves the business able to explain why further spending is or is not justified. It connects evidence with the actual work rather than treating a finished project file as proof that every intended benefit has arrived.