Overview
Strategy Analysis covers four tasks that connect a business need to a change worth making. You analyze the current state to understand the need and the context behind it, define a future state with business objectives and the potential value of change, assess risks that could reduce that value, and define a change strategy that sets solution scope, closes the gap between the two states and plans transition states and releases.
The knowledge area exists so that solutions are chosen to solve the right problem rather than to satisfy whoever asked first. Strategy Analysis can happen before an initiative is approved, during it when conditions change, or afterward. Its outputs drive Domain 5, where business objectives and solution scope bound requirements and design options, and Domain 6, where the expected value set here becomes the yardstick for measuring the solution.
How it's tested
Questions are scenario-based and often longer case studies describing an organization's problem, goals and constraints. They ask what to do FIRST, which analysis BEST reveals the cause, or which change strategy is MOST appropriate. The winning reasoning separates the need from proposed solutions, ties choices to stated business objectives and respects the organization's risk tolerance and readiness.
-
Need before solution
A stakeholder asks for a specific system or feature. You choose to analyze the current state and the business need before defining requirements.
-
Choose the analysis
Symptoms are given, such as falling retention or rising costs. You pick the technique, such as root cause analysis, SWOT or benchmarking, that fits the question being asked.
-
Select the path
Several change strategies are described. You choose the one that best balances value, risk tolerance, enterprise readiness and constraints.
A hospital's chief operating officer says a new scheduling system is needed because clinics run late. Options include eliciting system requirements, comparing scheduling vendors, defining transition states, and analyzing the current state to find why clinics run late. The request names a solution, not a need. Root causes such as staffing patterns or check-in processes may make a system unnecessary, so analyzing the current state comes first.
Tasks 4
Official tasks from the IIBA outline, in outline order.
4.1 Analyze Current StateBABOK Guide task 6.1: understand the business need and how the enterprise works today.
- What it means
- The business analyst examines the business need and the current context: organizational structure and culture, capabilities and processes, technology and infrastructure, policies, business architecture, internal assets and external influencers such as competitors, customers, suppliers and regulation. The outputs are the current state description and business requirements.
- What to understand
- The business need is the problem or opportunity driving the change; it should be stated without presupposing a solution. Understanding current capabilities and constraints is what makes the later gap analysis meaningful.
- How it shows up
- A sponsor requests a particular technology, and you are asked what to do FIRST. The answer analyzes the need and root causes before accepting the solution.
- Common confusion
- Writing the business need as a solution, such as 'we need a new CRM', instead of the problem it solves, such as rising customer churn.
4.2 Define Future StateBABOK Guide task 6.2: set business objectives, define the future state and its potential value.
- What it means
- The business analyst defines measurable business goals and objectives, the scope of the solution space, constraints, the future organizational, process, technology and policy context, assumptions, and the potential value of reaching that state. Outputs include business objectives, the future state description and potential value.
- What to understand
- Business objectives should be specific and measurable, often expressed with SMART criteria, so value can be measured later. Potential value must account for costs and negative effects, not only benefits.
- How it shows up
- A stem gives a vague goal like 'improve service' and asks for the best objective. The correct answer is measurable and time-bound.
- Common confusion
- Confusing goals with objectives. Goals are broader, longer-term statements; objectives are measurable targets that show progress toward a goal.
4.3 Assess RisksBABOK Guide task 6.3: analyze uncertainties that could affect the value of the change.
- What it means
- The business analyst identifies risks from unknowns, constraints, assumptions and dependencies, assesses their likelihood and impact on value, considers the stakeholders' risk tolerance and recommends a course of action. The output is risk analysis results.
- What to understand
- Risk tolerance shapes the recommendation: risk-averse stakeholders accept less uncertainty for lower reward, risk-seeking stakeholders accept more for potential gain, and risk-neutral stakeholders weigh them evenly. Sometimes the recommendation is not to proceed.
- How it shows up
- A change carries a high-impact uncertainty and the sponsor is described as conservative. The best answer reflects that tolerance, such as phasing the change or gathering more information.
- Common confusion
- Treating this task as project risk management. Assess Risks looks at risks to achieving the value of the change, not schedule or budget risks of the project.
4.4 Define Change StrategyBABOK Guide task 6.4: define solution scope, analyze gaps, assess readiness and plan the transition.
- What it means
- The business analyst performs gap analysis between current and future states, assesses enterprise readiness, defines the solution scope, evaluates alternative change strategies and plans transition states and release planning. The outputs are the change strategy and solution scope.
- What to understand
- Several strategies can close a gap. They are compared on value, cost, risk, timelines and opportunity cost, and enterprise readiness, meaning culture, capacity and willingness to change, can rule out an otherwise attractive option.
- How it shows up
- Two strategies deliver similar value but the organization has just absorbed a major reorganization. Readiness points to a phased change with transition states.
- Common confusion
- Treating gap analysis as the change strategy. The gap analysis shows what must change; the change strategy chooses how and in what sequence to make it.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Business need
The problem or opportunity of strategic or tactical importance that drives a change, described independently of any particular solution.
- Remember
- A request for a system is a proposed solution; the need is the business problem it is meant to fix.
- Tested as
- Many FIRST questions test whether you identify the need before working on requirements.
- Trap
- Accepting the stakeholder's solution as the need.
-
Business requirement
A statement of goals, objectives and outcomes describing why a change has been initiated, produced as an output of Analyze Current State.
- Remember
- It sits at the top of the requirements classification above stakeholder, solution and transition requirements.
- Tested as
- Classification questions ask which type a statement such as 'reduce returns by 10%' represents.
- Trap
- Classifying it as a stakeholder requirement because a stakeholder said it.
-
SMART objectives
Business objectives written to be Specific, Measurable, Achievable, Relevant and Time-bounded.
- Remember
- Measurability here is what makes value measurable in Solution Evaluation later.
- Tested as
- Stems ask you to pick the best-written objective from several options.
- Trap
- Choosing an inspiring but unmeasurable statement such as 'become customer-centric'.
-
Root cause analysis
Structured examination of a problem to find its underlying cause, using techniques such as the five whys and fishbone (Ishikawa) diagrams.
- Remember
- Treating symptoms produces solutions that do not satisfy the need.
- Tested as
- Recurring-problem scenarios point to it as the best analysis technique.
- Trap
- Selecting a new system to fix a problem whose cause is a process or policy.
-
SWOT analysis
A framework that analyzes internal strengths and weaknesses and external opportunities and threats.
- Remember
- Strengths and weaknesses are internal; opportunities and threats are external.
- Tested as
- Used in current-state and strategy questions about competitive position.
- Trap
- Placing a competitor's new product under weaknesses instead of threats.
-
Gap analysis
Comparison of current and future states to identify the capabilities, processes, technology and other elements that must change.
- Remember
- It feeds the change strategy but does not choose the path.
- Tested as
- Appears when a stem asks how to determine what needs to change.
- Trap
- Selecting it when the question asks how to choose among alternative approaches.
-
Enterprise readiness assessment
Evaluation of the organization's cultural readiness, operational capacity and ability to absorb and sustain the change.
- Remember
- Low readiness can make a high-value strategy fail, so it influences the strategy and transition states.
- Tested as
- Stems about change fatigue, recent reorganizations or resistance point here.
- Trap
- Choosing the highest-value option without considering whether the enterprise can absorb it.
-
Transition states
Intermediate states between current and future, often realized through planned releases, that deliver value incrementally.
- Remember
- They reduce risk and allow learning, and they may require transition requirements.
- Tested as
- Phased-rollout scenarios test whether you plan intermediate states.
- Trap
- Assuming the change must jump directly to the future state.
-
Risk tolerance
How much uncertainty stakeholders will accept: risk-averse, risk-neutral or risk-seeking.
- Remember
- The recommended response depends on the stated tolerance, not on a universal rule.
- Tested as
- Risk questions often describe the sponsor's attitude as the deciding clue.
- Trap
- Always recommending the lowest-risk option even when the sponsor is risk-seeking.
-
Solution scope
The set of capabilities a solution must deliver to meet the business need, defined in the change strategy.
- Remember
- It is distinct from project scope, which is the work to deliver the solution.
- Tested as
- Scope questions test whether you know which scope the business analyst defines.
- Trap
- Confusing solution scope with the project scope statement.
-
Potential value
The value that could be realized by implementing the future state, considering benefits, costs and possible negative outcomes.
- Remember
- It becomes the baseline against which solution value is later measured.
- Tested as
- Links Strategy Analysis to Solution Evaluation and to Analyze Potential Value and Recommend Solution.
- Trap
- Counting only benefits and ignoring costs or negative effects.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Business need vs. business requirement vs. business objective
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Business need | The problem or opportunity driving change | Why change is needed, stated without a solution | Writing it as a request for a system |
| Business requirement | Goals, objectives and outcomes describing why the change is initiated | Top level of the requirements classification | Labeling it a stakeholder requirement |
| Business objective | Measurable target used to assess progress toward a goal | Specific and measurable, enabling value measurement | Accepting a vague aspiration as an objective |
Gap analysis vs. change strategy vs. transition states
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Gap analysis | Identifies differences between current and future states | Shows what must change | Treating it as the chosen path |
| Change strategy | The chosen approach to move the enterprise from current to future state | Decides how the change will be made, compared against alternatives | Ignoring readiness and opportunity cost when choosing |
| Transition states | Intermediate states delivered through releases | Breaks the strategy into manageable, value-delivering steps | Planning a single big-bang change for a low-readiness organization |
Solution scope vs. project scope
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Solution scope | Capabilities the solution must deliver to meet the need | Defined by the business analyst in the change strategy | Expanding it to include project management work |
| Project scope | Work required to deliver a product, service or result | Owned by project management | Assuming the business analyst owns the project scope statement |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Starting with the requested solution
- What candidates pick
- Eliciting requirements for the system the executive asked for.
- Why it looks right
- The executive has authority and the request is specific.
- Why it's wrong
- Strategy Analysis first establishes the business need; the requested system may not address the root cause.
Clue to watch for A stem that names a solution but not a measurable problem signals Analyze Current State.
-
Fixing the symptom
- What candidates pick
- Adding staff or tools to clear a recurring backlog.
- Why it looks right
- It addresses the visible pain quickly.
- Why it's wrong
- Without root cause analysis the backlog returns; the cause may be a policy, handoff or data quality issue.
Clue to watch for Words like recurring, persistent or 'keeps happening' point to root cause analysis.
-
Ignoring readiness
- What candidates pick
- The change strategy with the highest projected value.
- Why it looks right
- Value is the stated goal of business analysis.
- Why it's wrong
- An enterprise that cannot absorb the change will not realize the value; readiness is part of choosing a strategy.
Clue to watch for Mentions of change fatigue, a recent merger or staff resistance.
-
One-size risk response
- What candidates pick
- Always the most cautious option.
- Why it looks right
- Caution feels professionally safe.
- Why it's wrong
- The BABOK ties recommendations to stakeholders' risk tolerance; a risk-seeking sponsor may rationally accept more uncertainty for higher value.
Clue to watch for Adjectives describing the sponsor's appetite, such as aggressive or conservative.
-
Vague objectives
- What candidates pick
- 'Improve customer satisfaction' as the business objective.
- Why it looks right
- It sounds strategic and widely agreed.
- Why it's wrong
- Without a measure and timeframe, value cannot be confirmed later in Solution Evaluation.
Clue to watch for When asked for the BEST objective, pick the one with a number and a date.
-
Project risk instead of value risk
- What candidates pick
- A schedule contingency plan when asked to assess risks of the change.
- Why it looks right
- Risk management is familiar from project work.
- Why it's wrong
- Assess Risks focuses on risks to the value of the change, such as adoption, assumptions and dependencies.
Clue to watch for The stem talks about benefits, adoption or business outcomes, not deadlines.
Answer framework
Use these steps when a scenario asks how to frame, justify or plan a change.
- Separate the stated business need from any solution a stakeholder has already proposed, and rewrite the need as a problem or opportunity.
- Analyze the current state and root causes, including culture, capabilities, processes, technology, policies and external influencers such as regulation.
- Define measurable business objectives and the future state, and estimate potential value including costs and negative effects.
- Assess risks to that value against the stakeholders' stated risk tolerance and the assumptions, constraints and dependencies involved.
- Choose a change strategy using gap analysis, enterprise readiness and alternative comparison, and plan transition states and releases where delivering everything at once is too risky.
Practice question
Want more like this? The CBAP practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Study the four tasks in order, because each output feeds the next: the current state and business need, then the future state and objectives, then risks to value, and finally the change strategy. Keep the business need visible throughout, since most traps here involve losing it.
The high-priority concepts are the need-before-solution principle, measurable objectives, risk tolerance and the difference between gap analysis and the change strategy. Candidates commonly underestimate external influencers in the current state and enterprise readiness in the change strategy, because both feel soft compared to process analysis. They also miss that Strategy Analysis can recommend not proceeding at all.
After reading, practice with longer case-study questions in which a stakeholder proposes a solution in the first sentence; train yourself to look for the underlying problem. Then work through questions linking this domain to Domain 5's Analyze Potential Value and Recommend Solution, and to Domain 6's performance measures, because the objectives set here are reused there. Review every missed question by asking whether you confused the need with a proposed solution.
FAQ
How much of the CBAP exam is Strategy Analysis?
IIBA weights it at 15%, about 18 of 120 questions as a planning estimate.
Does Strategy Analysis only happen before a project starts?
No. It can be performed before an initiative, during it when the need or context changes, and after it to identify further improvements.
What is the difference between a business need and a business requirement?
The need is the problem or opportunity behind the change. The business requirement states the goals, objectives and outcomes that describe why the change is being made.
Is gap analysis the same as the change strategy?
No. Gap analysis identifies what differs between the current and future states. The change strategy chooses how to close that gap, compares alternatives and plans transition states.
How does risk tolerance affect answers?
The best recommendation depends on whether stakeholders are risk-averse, risk-neutral or risk-seeking. Read the stem for clues about the sponsor's appetite before choosing.
How does this domain link to Solution Evaluation?
The business objectives and potential value defined here become the measures Domain 6 uses to judge whether the solution is delivering value.
How much study time does Strategy Analysis need?
As a planning estimate, about 25 to 30 hours within a 180-hour plan, with an emphasis on case-study practice.
Other Business Analysis certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 4 knowledge
You have worked through defining the need, the current and future states, risks to value and the change strategy. Practice questions will test whether you resist the requested solution and start from the real problem.