A transformation project should not be evaluated only by whether the planned activities were completed.
A company may have:
However, these outputs do not automatically demonstrate that the business has improved.
The more important questions are:
A post-implementation review provides a structured answer to these questions.
For an EDGE-related project, the review also helps the company maintain a clear connection between the original business problem, the project activities and the actual outcomes achieved.
A post-implementation review is a formal assessment conducted after a project has been implemented and has had sufficient time to operate in a real business environment.
It evaluates:
The review should not be treated as a fault-finding exercise. Its purpose is to establish what worked, what did not work, what evidence exists and what management should do next.
The review should take place after the new system, process or capability has been operating long enough to generate meaningful evidence.
The appropriate timing depends on the project.
An initial review may take place shortly after implementation to assess:
A stabilisation review may take place after several weeks or months, once employees have had time to use the new process consistently.
This review can assess:
A benefits review should take place when sufficient operational data is available to evaluate whether the original business outcomes have been achieved.
Depending on the project, this may require several months of measurement.
A project should not be declared unsuccessful simply because benefits cannot be measured immediately. However, the company should define when the benefits will be reviewed and who is responsible for collecting the evidence.
Project closure usually focuses on whether implementation activities are complete.
Benefits realisation focuses on whether the business has achieved meaningful value.
Project Closure
Benefits Realisation
Deliverables are completed
Business outcomes are measured
Contract milestones are reviewed
Operational performance is assessed
System or process is launched
Employees consistently use the capability
Project documentation is finalised
Business procedures are updated
Project team is released
Permanent ownership is established
Budget and timeline are reviewed
Productivity, quality or growth outcomes are evaluated
A project can be closed administratively while benefits are still being realised.
This is why businesses should distinguish between:
The first step in a post-implementation review is to return to the original project objectives.
The review should ask:
For example, if the project was designed to reduce manual order processing, the review should not focus only on whether the software was installed.
It should assess:
The original objectives provide the reference point for evaluating performance.
The review should first establish what was actually delivered.
This may include:
The review should compare the actual deliverables against the approved scope.
Important questions include:
This establishes whether the project delivered what it promised before assessing whether those outputs created value.
A new capability cannot create value if employees do not use it.
Adoption should therefore be reviewed separately from implementation.
Possible adoption indicators include:
Low adoption may indicate:
The review should distinguish between unwillingness to adopt and legitimate operational barriers. Employees may be avoiding a system because it is difficult to use, creates duplicate work or does not reflect how the business actually operates.
The next step is to determine whether the redesigned process is working better in practice.
Operational measures may include:
The review should compare:
For example, a reduction in processing time may be caused partly by lower transaction volume rather than by the new system. Similarly, an increase in productivity may be influenced by additional hiring, seasonal changes or other operational improvements.
A credible review should consider the wider business context rather than attributing every change to the project automatically.
Operational improvements matter because they should contribute to broader business outcomes.
Depending on the project, these may include:
The review should identify which outcomes have been:
This classification is more useful than declaring the entire project a success or failure.
A post-implementation review should also assess whether the project’s financial and resource assumptions remain valid.
This may include:
A project may deliver operational value but require higher ongoing support costs than expected.
Alternatively, the initial investment may be higher than planned while the long-term benefits are stronger.
The review should therefore assess both:
Management should understand what it will cost to maintain the new capability and whether the expected benefits justify those costs.
Transformation projects often introduce new reporting structures, dashboards or data-driven decision processes.
The post-implementation review should assess whether the information being used is reliable.
Questions include:
A new dashboard is not necessarily a reliable management tool.
If the underlying data is incomplete or inconsistent, the business may make decisions with greater speed but not greater accuracy.
A transformation project should strengthen the business’s ability to operate and improve.
The review should therefore assess whether internal employees can:
If the business remains dependent on one external provider for basic operational tasks, the project may not have fully achieved its capability-building objective.
The review should identify knowledge gaps and establish a plan for addressing them.
A post-implementation review should confirm that the new capability has a permanent owner.
This includes checking whether:
Ownership should continue after the project team is dissolved.
Without permanent accountability, the capability may deteriorate as attention shifts to other priorities.
The review should examine how employees experienced the transformation.
This can be assessed through:
Useful questions include:
Employee feedback is particularly important because operational problems may not appear in formal project reports.
A review conducted immediately after go-live may measure implementation activity rather than sustained performance.
Employees may log into a system without using it correctly or consistently.
Without a baseline, management cannot determine whether performance has improved.
Business performance may be affected by market conditions, staffing changes, customer demand or other initiatives.
Small unresolved problems can become permanent workarounds if they are not assigned owners and deadlines.
Capability development, resilience, data quality and management visibility may also be important outcomes.
If lessons are not captured, the business may repeat the same mistakes in future transformation projects.
A practical review report can follow this structure:
Provide a concise overview of:
Restate the original business objectives, targets and baseline measures.
Compare planned and actual deliverables, timelines, costs and scope changes.
Summarise usage, training, employee feedback and process compliance.
Compare baseline, target and actual results.
Assess productivity, cost, quality, service, revenue or capability improvements.
Identify unresolved risks, defects, dependencies and operational concerns.
Confirm internal ownership, knowledge transfer and ongoing support arrangements.
Identify what should be repeated, changed or avoided in future projects.
Set out the next actions, owners, priorities and timelines.
The review should not end with a report that is filed and forgotten.
Each material finding should lead to a decision or action.
Possible actions include:
Actions should include:
This turns the post-implementation review into an improvement mechanism rather than a retrospective document.
Transformation value is rarely visible in a single moment.
Some benefits appear quickly, such as reduced manual work or faster reporting. Others require more time, such as improved customer retention, stronger internal capability or better management decision-making.
A mature business therefore treats post-implementation review as an ongoing discipline.
It asks:
This approach helps ensure that EDGE-supported transformation contributes to long-term enterprise development rather than becoming a one-time implementation exercise.
Before formally closing the transformation programme, management should confirm:
The original business objectives have been restated.
Planned and actual deliverables have been compared.
Scope changes have been documented.
Adoption and usage have been measured.
Operational performance has been compared with the baseline.
Business outcomes have been assessed.
Financial and ongoing operating costs have been reviewed.
Data quality and reporting reliability have been checked.
Internal knowledge transfer has been completed.
Permanent ownership has been assigned.
Employee feedback has been collected.
Outstanding risks and issues have named owners.
Lessons learned have been documented.
Improvement actions have deadlines and accountable owners.
A future review date has been established.
If your Singapore business has completed or is preparing to complete an EDGE-supported transformation project, Grant Consulting can help you assess implementation outcomes, measure benefits, identify capability gaps and develop a practical improvement roadmap.
Call us now to discuss your post-implementation review and next-stage transformation priorities:
WhatsApp us
```