Name the change you expected in the work
A platform can launch on time, pass its acceptance checks and attract regular users while leaving an important business problem unresolved. Before commissioning the next release, return to the reason the system was built. Which task should now be easier to complete, and for whom?
“The team uses the portal” describes activity. “The service team resolves requests with fewer return visits to the same problem” describes an outcome worth investigating. Pick one such outcome, name the business owner and agree what evidence would justify the next investment.
GOV.UK’s service-measurement guidance starts with a service’s purpose and recommends combining metrics with user research. For a business platform, that means checking both the records and the experience of the people doing the work. A usage chart alone cannot tell you whether a difficult step has disappeared or moved outside the system.
Keep four questions separate
| Question | Evidence to inspect | What it cannot establish alone |
|---|---|---|
| Are people using it? | The share of relevant work entering the new process, including work still handled elsewhere. | Whether the work ends in a useful result. |
| Does the work get finished? | A defined result linked to the original request, with unresolved cases retained. | Whether that result is correct or stays resolved. |
| Is the result good enough? | Reopened cases, corrections, missed commitments and a review of representative records. | How much effort the result required. |
| What does it take to operate? | Handling, checking, support and administration effort across the teams involved. | Cash savings or the cause of a change in performance. |
Make the comparison before and after launch credible
Use existing records to describe the earlier process, then apply the same definitions to the new one. Keep the request type, start point, end point and observation window consistent. Separate work that is materially different, such as routine requests and cases requiring an external approval. Note holidays, staffing changes, training and changes in demand.
GOV.UK’s completion-rate guidance distinguishes completing a digital transaction from the later success of an application. Apply the same care to your workflow: submitting a service request and resolving the customer’s problem are different events. Link the outcome back to the original case so delayed completions and unfinished work remain visible.
If reliable pre-launch records do not exist, say so. Start measuring now and use that period as a reference for the next change. Interviews and old spreadsheets may help reconstruct part of the picture, but label estimates and missing information. A precise percentage cannot repair an uncertain starting point.
A hypothetical review of a service portal
Imagine a service team reviewing a new portal. It takes 100 consecutive eligible requests from each of two agreed periods, one before launch and one after, using eligibility rules set before inspecting outcomes. Request types and staffing are comparable. It observes each request for ten working days from receipt. This window is chosen for the example; your review needs a period that fits the work and enough cases to support the decision.
The table classifies every request into one of three outcome groups. A request that was resolved and then reopened stays in the reopened group, even if the team resolves it again. The entry-channel row is a separate view of the same 100 requests in each period.
What the two groups of requests show
| Observation within the window | Before launch | After launch |
|---|---|---|
| Entered through the digital channel | 40 of 100 | 75 of 100 |
| Resolved, with no reopening recorded | 70 of 100 | 82 of 100 |
| Resolved and subsequently reopened | 12 of 100 | 8 of 100 |
| Not resolved within the window | 18 of 100 | 10 of 100 |
Use the result to choose the next investigation
Digital use increased, and 82 requests reached a resolution without a recorded reopening, compared with 70 before launch. Those are encouraging observations. They do not establish that the portal caused the difference or that future requests will behave the same way. The ten unfinished requests still need owners; the eight reopened requests need inspection.
Read several cases from each outcome group with the service team. Suppose missing attachments explain several unresolved requests. A focused next change might help customers provide the right attachment and give staff a clearer way to request it. Define what should change in those cases, then review the next comparable group.
The observation window also limits the claim: a case may reopen on day eleven, and one resolved late in the window has had less time to reopen. Continue following the cases, and use a consistent follow-up period after resolution if lasting resolution is the decision you need to assess. Do not silently remove slow cases to improve the headline.
End the review with a decision and an owner
Bring the business owner, someone who does the work and the development partner to a focused review. Use the case records to identify the next useful change. Treat the following as decision paths, not a scoring system that can hide a serious quality problem.
- Expand a tested scope when the observed outcome, quality and operating effort support it. Check whether the next team or request type introduces different conditions.
- Improve a specific step when the evidence points to a recurring obstacle. Name the change, owner and result to inspect next.
- Gather evidence when definitions, coverage or follow-up are too weak to judge. Assign the missing measurement and set a review date.
- Retire or replace a feature when its useful contribution does not justify its continuing burden. Plan how people will finish open work and access the records they still need.
Sources and further reading
Give the next release a measurable purpose.
Bring one live workflow, the outcome you expected to improve and the records you already have. We can help define a focused next change and the evidence for reviewing it.
Discuss your existing platform


