Study guide
7.5 Recommend Actions to Increase Solution Value
CBAP Certified Business Analysis Professional Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & BACCM Framework
1.1 CBAP Exam Structure, Eligibility & Study Plan 1.2 The Business Analysis Core Concept Model (BACCM) 1.3 Key Concepts, Terms & Requirements Classification 1.4 Business Analysis Governance & Stakeholder Engagement Principles
2 Chapter 2: Business Analysis Planning and Monitoring
2.1 Plan Business Analysis Approach 2.2 Plan Stakeholder Engagement 2.3 Plan Business Analysis Governance 2.4 Plan Business Analysis Information Management 2.5 Identify Business Analysis Performance Improvements
3 Chapter 3: Elicitation and Collaboration
3.1 Prepare for Elicitation 3.2 Conduct Elicitation 3.3 Confirm Elicitation Results 3.4 Communicate Business Analysis Information 3.5 Manage Stakeholder Collaboration
4 Chapter 4: Requirements Life Cycle Management
4.1 Trace Requirements 4.2 Maintain Requirements 4.3 Prioritize Requirements 4.4 Assess Requirements Changes 4.5 Approve Requirements
5 Chapter 5: Strategy Analysis
5.1 Analyze Current State 5.2 Define Future State 5.3 Assess Risks 5.4 Define Change Strategy 5.5 Business Case Development & Financial Analysis
6 Chapter 6: Requirements Analysis and Design Definition
6.1 Specify and Model Requirements 6.2 Verify Requirements 6.3 Validate Requirements 6.4 Define Requirements Architecture 6.5 Define Design Options 6.6 Analyze Potential Value and Recommend Solution 6.7 Data Modeling & Process Modeling Techniques 6.8 Use Cases, User Stories & Acceptance Criteria Definition 6.9 Non-Functional Requirements & Solution Constraints
7 Chapter 7: Solution Evaluation
7.1 Measure Solution Performance 7.2 Analyze Performance Measures 7.3 Assess Solution Limitations 7.4 Assess Enterprise Limitations 7.5 Recommend Actions to Increase Solution Value
8 Chapter 8: Underlying Competencies, Techniques & Perspectives
8.1 Analytical Thinking, Problem Solving & Business Knowledge 8.2 Behavioral Characteristics & Interaction Skills 8.3 Core BABOK Techniques Master Review 8.4 Business Analysis Perspectives
7.5 Recommend Actions to Increase Solution Value
Key Takeaways Explain This Topic AI
Task 30 (Recommend Actions to Increase Solution Value) synthesizes evaluation findings to propose actionable course corrections for enterprise leadership.
Core recommendation strategies include Do Nothing (Maintain Status Quo), Enhance Solution (Technical Modifications), Modify Business Process (Enterprise Interventions), and Retire/Decommission Solution.
Every recommendation must be justified using rigorous financial metrics (ROI, NPV, Payback Period) and strategic trade-off analyses.
Senior business analysts must avoid the Sunk Cost Fallacy: past unrecoverable expenditures must never justify maintaining an underperforming legacy solution.
The BA acts as an objective strategic advisor, balancing solution capabilities against enterprise readiness to maximize net value realization.
Last updated: August 2026
- 7.5 Recommend Actions to Increase Solution Value
- Purpose of Task 30
The primary objective of Task 30: Recommend Actions to Increase Solution Value is to define and justify specific action plans to eliminate performance gaps, resolve solution and enterprise limitations, and maximize realized business value. Task 30 represents the synthesis task of Solution Evaluation. It translates diagnostic insights from Tasks 26 through 29 into formal, strategic recommendations for business sponsors and executive decision-makers.
Business analysts must evaluate the financial cost, risk, and operational impact of potential recommendations to provide objective trade-off analyses rather than superficial suggestions.
Inputs, Outputs, and BACCM Relationships
Recommending actions requires synthesizing solution limitations, enterprise limitations, and original business objectives.
BABOK Component Element Name Description & Strategic Context
Inputs Enterprise Limitation Documented organizational, cultural, and operational barriers (Task 29).
Inputs Solution Limitation Documented technical defects, usability issues, and architectural flaws (Task 28).
Outputs Recommended Actions Formulated recommendations detailing cost-benefit trade-offs, risk assessments, and implementation roadmaps.
Guidelines & Tools Business Objectives, Solution Scope Strategic targets and change governance framework guiding recommendation feasibility.
Mapping to the Business Analysis Core Concept Model (BACCM)
Context: Ensures recommendations are achievable within current regulatory, competitive, and economic conditions.
Need: Directly targets closing the performance gap between actual solution results and original business needs.
Solution: Specifies technical enhancements, architectural updates, or replacement strategies for the solution artifact.
Stakeholder: Formulates change management, re-training, and organizational restructuring plans for affected stakeholders.
Value: Maximizes net business value realization through positive cost-benefit balance.
Change: Outlines the operational transformation roadmap needed to execute the recommended course of action.
Recommendation Strategy Taxonomy
BABOK Guide v3 categorizes recommended actions into four core strategies: RECOMMENDED ACTIONS STRATEGY TAXONOMY
- ┌───────────────────────────┬───────────────────────────┬───────────────────────────┐
- │ DO NOTHING │ ENHANCE SOLUTION │ MODIFY BUSINESS PROCESS │
- ├───────────────────────────┼───────────────────────────┼───────────────────────────┤
- │ • Accept Status Quo │ • Software Refactoring │ • Process Re-engineering │
- │ • Cost of Change > Value │ • Architectural Upgrades │ • Re-training Programs │
- │ • End-of-Life Horizon │ • Feature Expansion │ • Incentive Alignment │
- └───────────────────────────┴───────────────────────────┴───────────────────────────┘
- ┌───────────────────────────────────────────────────────────────────────────────────┐
- │ RETIRE / DECOMMISSION │
- ├───────────────────────────────────────────────────────────────────────────────────┤
- │ • Solution Sunset & Legacy Migration │
- │ • Complete Replacement by New Technology │
- │ • Total Cost of Ownership (TCO) Exceeds Realized Business Value │
- └───────────────────────────────────────────────────────────────────────────────────┘
- 1. Do Nothing (Maintain Status Quo)
Recommended when performance gaps are minimal, or when the financial cost, risk, and operational disruption of taking corrective action exceed the potential incremental value gained.
Strategic Rationale: The solution is near its planned end-of-life horizon, or financial Return on Investment (ROI) for fixes is negative.
2. Enhance Solution (Technical Modification)
Recommended when performance gaps stem primarily from internal solution limitations (Task 28).
Actions: Refactoring software code, upgrading hardware capacity, adding missing functionality, optimizing database indexing, or redesigning user interfaces.
3. Modify Business Process / Enterprise Capabilities
Recommended when performance gaps stem primarily from enterprise limitations (Task 29).
Actions: Re-engineering operational workflows, updating Standard Operating Procedures (SOPs), realigning performance incentive structures, conducting targeted re-training, or adjusting organizational reporting lines.
4. Retire / Decommission Solution
Recommended when the solution no longer delivers sufficient business value, technical debt makes maintenance cost-prohibitive, or superior alternative solutions exist.
Actions: Developing sunset strategies, executing data retention and migration plans, and transitioning operations to modern platforms.
Financial Evaluation and Decision Frameworks
Senior BAs must justify every recommendation using rigorous financial and strategic evaluation metrics:
Financial / Decision Metric Conceptual Formula / Definition Analytical Application in Task 30
Cost-Benefit Analysis (CBA) Total Expected Benefits minus Total Implementation & Operating Costs. Evaluating net value generated by each candidate recommendation option.
Return on Investment (ROI) (Net Incremental Benefit / Total Implementation Cost) * 100 . Comparing financial efficiency across competing recommendation options.
Payback Period Time required for net incremental benefits to equal initial investment cost. Assessing liquidity risk and time-horizon feasibility.
Sunk Cost Fallacy Avoidance Disregarding past unrecoverable expenditures when evaluating future options. Preventing organizations from throwing good money after bad legacy solutions.
Opportunity Cost Value forgone by selecting one recommendation alternative over another. Evaluating strategic trade-offs of resource allocation.
Practical Example: Recommending Value Optimization Strategy for an Enterprise Logistics Platform
An enterprise logistics company evaluated its 10-year-old legacy dispatch system.
Evaluation Findings: System latency was high (Task 28 limitation), and dispatchers maintained paper logs (Task 29 limitation). Annual legacy maintenance cost was $1.2M, while actual realized annual benefit was only $400K.
Options Evaluated:
Option A (Do Nothing): Retain system; lose $800K net annually.
Option B (Enhance Legacy): Refactor codebase for $2.5M; annual maintenance drops to $800K. ROI payback = 6.2 years.
Option C (Modify Process + SaaS Replacement / Retire Legacy): Decommission legacy system ($300K migration cost), adopt cloud SaaS solution ($400K/yr sub), and retrain dispatchers ($100K). Annual net benefit = $900K. Payback = 0.8 years.
Formulated Recommendation: The BA recommended Option C: Retire Legacy Solution and Modify Business Process , backed by a Cost-Benefit Analysis demonstrating net 3-year savings of $2.1M and a 10-month payback period.
CBAP Exam Strategy & Comprehensive Chapter Synthesis
Sunk Cost Trap: The CBAP exam frequently tests whether candidates fall for the sunk cost fallacy. Previous capital spent on a solution MUST NEVER justify maintaining an underperforming legacy solution.
Align Cause with Recommendation: Ensure solution limitations trigger technical enhancement options, while enterprise limitations trigger process/training/policy modification options.
The "Do Nothing" Option: Never eliminate "Do Nothing" automatically. If the cost of change exceeds the performance gap value, "Do Nothing" is the BABOK-correct choice.