Solution Evaluation
Describes the tasks BAs perform to assess the performance and value delivered by a solution in use, identify limitations preventing it from realizing its full value, and recommend actions to increase value.
Measures how well a delivered solution actually delivers value, and decides what to do about it.
Most organisations declare victory at go-live. BABOK does not. Solution Evaluation closes the loop — value either showed up or it did not — and feeds the lessons back into every other knowledge area. It is small in exam weight (5%) but disproportionate in real-world impact.
In practice
The BA measures the solution's performance against the criteria set in Strategy Analysis, identifies limitations in the solution and in the wider enterprise that block value, and recommends actions: extend the solution, reduce constraints, replace components, or retire the change.
Relationships with other knowledge areas
- →Tests against the success criteria defined in Strategy Analysis.
- →Uses traceability from RLCM to know what should have been delivered.
- →Feeds lessons back to BAPM so the next initiative plans better.
- →Re-engages Elicitation when measurement contradicts what stakeholders said they wanted.
Where this lands on the exam
BACCM touchpoints
- Value. Value realisation is the central question of this KA.
- Solution. The solution is judged on outcomes, not features.
- Context. Enterprise constraints in the wider context often explain missing value.
Language to listen for in scenario stems
When a stem mentions post-implementation performance, KPIs, value not realised, or 'what should the BA do now that we are live' — it is Solution Evaluation.
Key concepts
The ideas that anchor everything else in this knowledge area.
Performance is what the solution does; value is the worth of that performance to stakeholders. They are not the same.
Limitations may live in the solution itself or in the enterprise around it (process, people, policy). Both are in scope.
Evaluation isn't a one-off post-launch report; value-realization is ongoing.
Common pitfalls
Patterns that frequently cost initiatives — and exam points.
- ⚠Reporting activity (usage) instead of outcomes (value).
- ⚠Blaming the solution for problems caused by surrounding processes or training.
- ⚠Recommending changes without evidence.
- ⚠Walking away after go-live; the value case is realized post-deployment.
Tasks
The 5 tasks that make up this knowledge area. Click any task to expand its inputs, outputs, techniques, and guidelines. Technique tags are clickable.