Business analysis does not end when development is complete.
Solution evaluation asks whether the implemented solution is actually delivering the intended outcome.
Evaluation cycle
- Define what success means.
- Identify useful performance measures.
- Collect evidence.
- Compare results with expectations.
- Identify defects or gaps.
- Decide whether further changes are needed.
What can be evaluated?
Depending on the solution:
- Business performance
- Customer behavior
- Adoption
- Defects
- Conversion
- Processing time
- Revenue
- Cost
- User satisfaction
- Operational performance
Acceptance vs. value
A solution can be accepted because it meets its defined criteria, but the broader business question can still be:
Did it create the expected value?
This is why acceptance and outcome evaluation should be treated as related but distinct activities.
Portfolio example
For an eCommerce project:
Requirement: Customers can subscribe to a product.
Acceptance: Subscription creation works according to defined scenarios.
Outcome: Measure whether subscriptions actually increase recurring revenue or retention.
This creates a clear chain from requirement to business outcome.