Business Analysis 101: Solution Evaluation - Recommending Actions to Increase Value, Retire, Replace, Enhance

What This Is

Recommending actions to increase value is the BA’s systematic way of deciding whether an existing solution should be retired, replaced, or enhanced (or left as?is). It appears after the solution?assessment phase and feeds into the Solution Evaluation and Requirements Management & Communication knowledge areas.

Real?world example: A financial services firm has a legacy Customer Relationship Management (CRM) system that is costly to maintain. The BA evaluates usage data, stakeholder pain points, and market alternatives, then recommends either retiring the system, swapping it for a cloud?based CRM, or adding new analytics modules to increase business value.

Key Terms & Techniques

• Retire – Decision to discontinue a solution because it no longer delivers sufficient value or aligns with strategy. (Solution Evaluation; Deliverable: Recommendation Document)
• Replace – Decision to swap the current solution for a new one that better meets functional or non?functional needs. (Solution Evaluation; Deliverable: Replacement Business Case)
• Enhance – Decision to add new capabilities or improve performance of the existing solution. (Solution Evaluation; Deliverable: Enhancement Requirements Specification)
• Cost?Benefit Analysis (CBA) – Quantitative technique that compares the total expected costs of a change against its benefits. (Strategy Analysis; Deliverable: CBA Worksheet)
• Value?Added Matrix – A visual tool that plots potential actions against expected value and effort, helping prioritize retire/replace/enhance options. (Solution Evaluation; Deliverable: Value?Added Matrix)
• Fit?Gap Analysis – Compares current solution capabilities (fit) with future business needs (gap) to identify where enhancements or replacements are required. (Requirements Analysis & Design Definition; Deliverable: Fit?Gap Report)
• Risk?Benefit Matrix – Plots risk level against benefit level for each recommended action, supporting governance decisions. (Solution Evaluation; Deliverable: Risk?Benefit Assessment)
• Stakeholder Impact Assessment – Evaluates how each recommendation will affect stakeholder groups (e.g., users, support staff, customers). (Stakeholder Analysis; Deliverable: Impact Assessment Matrix)
• Business Case – A structured argument that justifies investment in a recommended action, including ROI, NPV, and payback period. (Strategy Analysis; Deliverable: Business Case Document)
• Transition Planning – Outlines the steps, resources, and timeline needed to move from the current state to the recommended future state. (Transition Planning; Deliverable: Transition Plan)
• Change Control Process – Formal governance mechanism that reviews, approves, and tracks recommended actions. (Requirements Management & Communication; Deliverable: Change Request Log)
• Benefit Realization Review – Post?implementation assessment that measures whether the expected value was actually delivered. (Solution Evaluation; Deliverable: Benefit Realization Report)

Step?by?Step Process Flow

1. Collect Baseline Data – Gather performance metrics, cost data, user complaints, and strategic objectives for the existing solution.
2. Perform Fit?Gap & Cost?Benefit Analyses – Use Fit?Gap to spot functional gaps; run CBA for each possible action (retire, replace, enhance).
3. Develop Value?Added & Risk?Benefit Matrices – Plot each option against expected value, effort, and risk to visualize trade?offs.
4. Engage Stakeholders in a Decision Workshop – Present the matrices, discuss impacts, and capture preferences using voting or MoSCoW prioritization.
5. Draft Recommendation Document – Summarize analysis, justify the chosen action, and attach supporting artifacts (business case, transition plan).
6. Obtain Governance Approval & Initiate Transition Planning – Submit the recommendation through the Change Control Process; once approved, work with the project team to create a detailed transition plan.

Common Mistakes

• Mistake: Jumping straight to “replace” because the solution feels outdated.
  Correction: Conduct a full Fit?Gap and Cost?Benefit analysis first; sometimes a small enhancement yields higher ROI than a full replacement.

• Mistake: Treating “retire” as a cost?only decision.
  Correction: Include de?commissioning costs, data migration risks, and stakeholder impact; retire only when total cost of ownership (TCO) exceeds the value of keeping the solution.

• Mistake: Skipping stakeholder impact assessment and assuming users will accept any change.
  Correction: Use the Stakeholder Impact Assessment to surface resistance, training needs, and change?management activities before finalizing the recommendation.

• Mistake: Documenting only the chosen action and discarding the analysis of alternatives.
  Correction: BABOK requires that the Recommendation Document retain the rationale and evaluation of all alternatives for auditability and future reference.

• Mistake: Confusing “enhance” with “fix bugs.”
  Correction: Enhancements add new capabilities or improve performance; bug fixes are part of maintenance and should not drive a retire/replace decision unless they indicate deeper quality issues.

Certification Exam Tips

• ECBA: Remember that retire/replace/enhance belongs to the Solution Evaluation knowledge area; the exam often asks which activity follows “Assess solution performance.”
• CCBA: Watch for questions that mix Fit?Gap (Requirements Analysis) with Cost?Benefit (Strategy Analysis). The correct answer will reference the Solution Evaluation step where the recommendation is made.
• CBAP: Expect scenario?based items that require you to select the best technique (e.g., Value?Added Matrix) for comparing multiple actions. The key is to match the technique to the output (Recommendation Document) not the input (raw metrics).
• Trap: “The BA should decide to retire a solution alone.” – The BA recommends; final decision rests with governance (Change Control).

Quick Check Questions

1. Scenario: After analyzing a legacy billing system, the BA finds that fixing recurring performance bugs would cost $200k annually, while a cloud?based replacement would cost $1.2M with a 3?year ROI of 150%. Which recommendation is most defensible?
   Answer: Replace – the cost?benefit analysis shows a higher ROI and lower long?term cost than continual enhancements.

2. Scenario: Stakeholders are split: the finance team wants to retire the current inventory module, while operations wants to enhance it. Which technique helps the BA surface the best overall action?
   Answer: Value?Added Matrix – it visualizes value vs. effort for each option, allowing an objective comparison that includes both groups’ concerns.

3. Scenario: The BA has completed a Fit?Gap report showing three major gaps. The next step is to decide whether to enhance the existing system or replace it. What is the primary artifact the BA should produce next?
   Answer: Recommendation Document – it consolidates analysis, presents alternatives, and recommends the preferred action.

Last?Minute Cram Sheet (10 One?Liners)

1. Solution Evaluation is the BABOK knowledge area where retire/replace/enhance decisions are made.
2. Fit?Gap Analysis-output: Fit?Gap Report (identifies gaps, not the final decision).
3. Cost?Benefit Analysis-output: CBA Worksheet (quantifies ROI for each alternative).
4. Value?Added Matrix plots expected value vs. effort for retire, replace, enhance options.
5. Risk?Benefit Matrix helps governance weigh risk against benefit before approval.
6. Stakeholder Impact Assessment-output: Impact Assessment Matrix (shows who is affected and how).
7. Business Case is required when the recommendation involves replace or enhance (not for retire?only).
8. Change Control Process-output: Change Request Log (records the BA’s recommendation and decision).
9. Transition Planning follows an approved recommendation; it produces a Transition Plan with timelines and resources.
10. Benefit Realization Review is the post?implementation check that confirms the recommended action actually delivered value.