Overview
Solution Evaluation covers five tasks that judge value after something exists to evaluate, whether a prototype, a pilot, a release or a mature operational solution. You define and collect solution performance measures, analyze them against the desired value, assess limitations inside the solution, assess limitations in the enterprise around it, and recommend actions to increase solution value, which can include doing nothing or retiring the solution.
The knowledge area exists because delivering requirements does not guarantee delivering value. A solution can work exactly as specified and still miss its business objectives because of adoption, culture or process issues. Solution Evaluation closes the loop with Domain 4, using the objectives and potential value defined there, and with Domain 5, whose solution recommendation is now being tested in practice. Its recommendations often start new change requests in Domain 3.
How it's tested
Questions describe a solution that is live, piloted or prototyped and not producing the expected value. They ask which measure is BEST, what the analysis reveals, whether a limitation is in the solution or the enterprise, or which action to recommend. The reasoning compares actual results to the business objectives and locates the cause before proposing a remedy.
-
Choose the measure
A business objective is stated and you pick the performance measure that actually shows progress toward it, rather than one that is easy to collect.
-
Locate the limitation
A shortfall is described. You decide whether its cause lies in the solution's components or in the enterprise's culture, structure or operations.
-
Recommend the action
Analysis results are given and you pick the action that increases value, which may be organizational change, simplification or retirement rather than new features.
Six months after an online appointment tool launched, bookings through it remain low. Logs show the tool performs well, but front-desk staff still take phone bookings because their performance targets count calls handled. Options include adding features, retraining developers, retiring the tool, and addressing the incentive structure. The cause sits in the enterprise, not the solution, so the recommendation should target the organizational limitation.
Tasks 5
Official tasks from the IIBA outline, in outline order.
6.1 Measure Solution PerformanceBABOK Guide task 8.1: define, validate and collect measures of solution performance.
- What it means
- The business analyst defines performance measures that show whether the solution meets business goals and objectives, validates them with stakeholders, and collects them with attention to volume or sample size, frequency and timing, and currency. The output is solution performance measures.
- What to understand
- Measures may be quantitative or qualitative and should link to the objectives set in Strategy Analysis. If the organization has no suitable measures, the business analyst works with stakeholders to define them.
- How it shows up
- An objective is to reduce customer churn, and you choose a measure. Retention rate over a period fits better than system uptime.
- Common confusion
- Using technical metrics such as uptime or defects closed as proxies for business value. They may matter but rarely show whether the objective was met.
6.2 Analyze Performance MeasuresBABOK Guide task 8.2: interpret performance data against the desired value.
- What it means
- The business analyst analyzes measures to understand how the solution performs relative to the desired value, looking at risks, trends, accuracy and performance variances. The output is solution performance analysis.
- What to understand
- Short collection periods and small samples can mislead; trends over time and the accuracy of the data matter. A variance is a starting point for investigation, not a conclusion.
- How it shows up
- A single month of results shows a sharp drop in performance. The best answer checks whether the sample and timing are representative before recommending action.
- Common confusion
- Treating analysis as collecting more data. This task interprets data to identify gaps and their significance.
6.3 Assess Solution LimitationsBABOK Guide task 8.3: find factors within the solution that limit value realization.
- What it means
- The business analyst identifies internal solution component dependencies, investigates solution problems and assesses their impact on value. The output is solution limitation.
- What to understand
- Limitations can exist in software, processes, policies or interfaces that make up the solution. Problem investigation uses root cause analysis to separate symptoms from causes.
- How it shows up
- A pilot shows orders failing whenever an interface to the warehouse system times out. The limitation sits in a solution component dependency.
- Common confusion
- Labeling every shortfall a solution limitation. If the solution works but people do not use it as intended, the cause is likely an enterprise limitation.
6.4 Assess Enterprise LimitationsBABOK Guide task 8.4: find factors in the enterprise that limit value realization.
- What it means
- The business analyst assesses enterprise culture, analyzes stakeholder impact, examines organizational structure changes and performs an operational assessment to find what in the surrounding organization prevents value. The output is enterprise limitation.
- What to understand
- Culture, incentives, reporting lines, skills, policies and capacity can all block a working solution. Stakeholder impact analysis looks at functions, locations, tasks and concerns affected by the solution.
- How it shows up
- A solution performs well technically, but one region refuses to adopt it because of local practices. The limitation is in the enterprise.
- Common confusion
- Fixing enterprise problems with solution changes, such as adding features when the actual barrier is an incentive scheme or reporting structure.
6.5 Recommend Actions to Increase Solution ValueBABOK Guide task 8.5: recommend changes to the solution or enterprise to improve value.
- What it means
- The business analyst recommends actions based on the analysis, such as adjusting performance measures, doing nothing, organizational change, reducing complexity of interfaces, eliminating redundancy, avoiding waste, identifying additional capabilities or retiring the solution. The output is recommended actions.
- What to understand
- Recommendations should address the cause identified. Retirement decisions should consider ongoing costs, opportunity cost and necessary replacement, while ignoring sunk costs already spent.
- How it shows up
- An ageing solution costs more to maintain each year than the value it adds. Retirement or replacement is the value-based recommendation.
- Common confusion
- Assuming recommendations always add features. Simplifying, removing redundancy or doing nothing can increase value more.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Solution performance measures
Quantitative or qualitative measures that show whether a solution is contributing to business goals and objectives.
- Remember
- They should trace to the objectives from Strategy Analysis and be validated with stakeholders.
- Tested as
- Measure-selection questions test whether you pick a business outcome over a convenient technical metric.
- Trap
- Choosing system uptime or the share of test cases passed to show business value.
-
Solution limitation vs. enterprise limitation
A solution limitation lies within the solution's components; an enterprise limitation lies in the culture, structure, operations or stakeholders around the solution.
- Remember
- If the solution works as designed but value is not realized, look to the enterprise.
- Tested as
- One of the most frequently tested distinctions in this domain.
- Trap
- Adding features to overcome an incentive or culture problem.
-
Sunk cost
Money already spent on a solution that cannot be recovered.
- Remember
- Sunk costs should not drive retirement or continuation decisions; future costs and benefits should.
- Tested as
- Retirement scenarios often mention a large past investment as a distractor.
- Trap
- Keeping a failing solution because so much has been invested.
-
Opportunity cost
The value of the best alternative forgone by continuing with the current solution.
- Remember
- It is part of the case for retiring or replacing a solution.
- Tested as
- Appears with ongoing cost and replacement in retirement questions.
- Trap
- Comparing only current maintenance cost against zero.
-
Performance variance
The difference between expected and actual performance of the solution.
- Remember
- A variance prompts investigation into causes; it does not by itself identify the cause.
- Tested as
- Analysis questions ask what to do after a variance is found.
- Trap
- Recommending action from a variance without checking data accuracy and trends.
-
Sample size, frequency and currency
Collection considerations: enough data points, collected at suitable intervals, recent enough to reflect current performance.
- Remember
- Small or outdated samples can make a healthy solution look poor or a poor one look healthy.
- Tested as
- Stems with one month of data or a single site test this.
- Trap
- Drawing firm conclusions from a short pilot period.
-
Stakeholder impact analysis
Part of Assess Enterprise Limitations that examines how the solution affects stakeholders' functions, locations and concerns.
- Remember
- It explains resistance and adoption gaps by showing who loses or gains from the change.
- Tested as
- Adoption-problem scenarios point to it.
- Trap
- Assuming resistance is irrational rather than investigating its impact.
-
Recommended action types
The BABOK lists options including do nothing, organizational change, reduce complexity of interfaces, eliminate redundancy, avoid waste, identify additional capabilities and retire the solution.
- Remember
- The best action targets the identified cause and the greatest value gain.
- Tested as
- Recommendation questions offer several of these as options.
- Trap
- Defaulting to additional capabilities.
-
Evaluating partial solutions
Solution Evaluation can be applied to prototypes, pilots, proofs of concept and releases, not only to complete solutions.
- Remember
- Early evaluation reduces the risk of scaling something that does not deliver value.
- Tested as
- Pilot scenarios test whether you know evaluation applies before full rollout.
- Trap
- Waiting for full implementation before measuring value.
-
Operational assessment
Examination of whether the enterprise can operate and sustain the solution, including policies, processes, tools, skills and capacity.
- Remember
- It belongs to Assess Enterprise Limitations.
- Tested as
- Scenarios about support teams overwhelmed or missing skills point here.
- Trap
- Treating operational gaps as defects in the solution.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Assess Solution Limitations vs. Assess Enterprise Limitations
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Assess Solution Limitations | Find factors within solution components that limit value | Looks inside the solution: components, dependencies, problems | Blaming the solution when adoption is the real issue |
| Assess Enterprise Limitations | Find factors in the organization that limit value | Looks outside the solution: culture, structure, operations, stakeholders | Proposing technical fixes for incentive or structural problems |
Solution performance measures vs. test metrics
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Solution performance measures | Measures of contribution to business goals and objectives | Show business value over time | Choosing whatever is easiest to collect |
| Test and technical metrics | Measures of whether the solution functions correctly, such as defects or uptime | Show quality and operation, not value realization | Using them as proof that objectives were achieved |
Recommend more capability vs. simplify vs. retire
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Identify additional capabilities | Add capabilities that offer extra value | Right when evidence shows unmet needs the solution could address | Using it by default for every shortfall |
| Reduce complexity, eliminate redundancy, avoid waste | Remove interfaces, duplication or non-value activity | Increase value by subtraction | Overlooking simplification because it adds no visible features |
| Retire the solution | Replace or remove a solution whose ongoing cost exceeds its value | Considers ongoing cost, opportunity cost and replacement, not sunk cost | Keeping it because of past investment |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Technical metric as value
- What candidates pick
- System availability as the measure of success for an objective to grow online sales.
- Why it looks right
- Availability is easy to measure and clearly related to the solution.
- Why it's wrong
- Solution performance measures must show progress toward business objectives, such as online sales growth or conversion rate.
Clue to watch for When the stem states a business objective, pick the measure that tracks that objective.
-
Feature fix for a people problem
- What candidates pick
- Adding automation to a solution staff are not using.
- Why it looks right
- Making the solution better seems to encourage use.
- Why it's wrong
- If the solution works but incentives, culture or structure block adoption, the limitation is in the enterprise and needs organizational change.
Clue to watch for Phrases like works as designed, passed testing, or staff prefer the old way.
-
Sunk cost reasoning
- What candidates pick
- Continuing to invest because millions were already spent.
- Why it looks right
- Walking away feels like wasting the investment.
- Why it's wrong
- Past spending cannot be recovered; decisions should weigh future costs, benefits and opportunity cost.
Clue to watch for Mentions of large past investment alongside rising ongoing costs.
-
Acting on thin data
- What candidates pick
- Recommending retirement after one poor month of a pilot.
- Why it looks right
- The data shows a clear shortfall.
- Why it's wrong
- Analyze Performance Measures considers sample size, timing, trends and accuracy before conclusions are drawn.
Clue to watch for Short periods, a single site or seasonal timing in the stem.
-
Waiting for full rollout
- What candidates pick
- Postponing evaluation until the complete solution is deployed.
- Why it looks right
- Evaluating an incomplete solution seems unfair.
- Why it's wrong
- Solution Evaluation applies to prototypes, pilots and releases, and early evaluation reduces the risk of scaling a poor solution.
Clue to watch for The stem describes a pilot or a first release.
-
More features by default
- What candidates pick
- Identifying additional capabilities as the recommendation.
- Why it looks right
- New capabilities look like progress.
- Why it's wrong
- Value may rise more by reducing complexity, eliminating redundancy, avoiding waste, organizational change or doing nothing.
Clue to watch for Analysis showing duplication, complex interfaces or low use of existing features.
Answer framework
Use these steps when a scenario asks whether a solution is delivering value and what to do about it.
- Restate the business objective the solution was meant to achieve, and confirm that the chosen measures actually track it rather than technical health.
- Check the data for sample size, timing, currency and accuracy, and look at trends over time before trusting any single performance variance.
- Decide whether the cause lies within the solution's components or in the surrounding enterprise's culture, structure, operations or incentives.
- Match the recommendation to that cause, considering simplification, organizational change, doing nothing or retirement as well as new capabilities.
- Base any continue-or-retire choice on future costs, benefits and opportunity cost, setting sunk costs aside completely when comparing the options.
Practice question
Want more like this? The CBAP practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Study the five tasks as a cycle: measure, analyze, look inside the solution, look at the enterprise, then recommend. Begin by reviewing business objectives and potential value from Domain 4, because every measure here should trace to them.
The high-priority concepts are business-value measures versus technical metrics, the solution versus enterprise limitation distinction, and the full range of recommended actions including retirement and doing nothing. Candidates commonly underestimate Assess Enterprise Limitations because they expect problems to be technical, and they underestimate the measurement considerations in Measure Solution Performance and Analyze Performance Measures, which produce clean questions about thin or outdated data.
After reading, practice with scenarios describing a live solution that underdelivers and force yourself to name the location of the cause before picking a remedy. Then work questions on retirement decisions until you automatically discard sunk cost. Finally, mix in Domain 4 and Domain 3 questions, since recommendations from Solution Evaluation often lead to new strategy work or change requests.
FAQ
How much of the CBAP exam is Solution Evaluation?
IIBA weights it at 14%, about 17 of 120 questions as a planning estimate.
Does Solution Evaluation only apply after full implementation?
No. It applies to prototypes, proofs of concept, pilots and releases as well as mature solutions, which lets organizations learn before scaling.
What is the difference between a solution limitation and an enterprise limitation?
A solution limitation is inside the solution, such as a faulty component or dependency. An enterprise limitation is in the organization around it, such as culture, incentives, structure or operational capacity.
Can the recommendation be to do nothing?
Yes. The BABOK lists doing nothing as an option when the value of change does not justify the effort, along with organizational change, simplification and retirement.
How should sunk cost be treated?
It should be ignored when deciding whether to continue or retire a solution. Decisions should rest on future costs, expected benefits and opportunity cost.
How does this domain connect to Strategy Analysis?
Strategy Analysis defines business objectives and potential value; Solution Evaluation measures whether the solution is achieving them and recommends how to increase value.
How much study time does Solution Evaluation need?
As a planning estimate, about 20 to 30 hours within a 180-hour plan, focused on scenario practice about live or piloted solutions.
Other Business Analysis certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 6 knowledge
You have seen how to measure and analyze solution performance, locate limitations in the solution or the enterprise, and recommend value-increasing actions. Practice questions will test whether you find the real cause before choosing a fix.