CBDA Use Results to Influence Business Decision Making is Domain 5 of the IIBA Certification in Business Data Analytics: 20% of 75 questions, so about 15 questions [1]. Section 2.5 of the Guide to Business Data Analytics has three tasks: recommend actions, develop an implementation plan and manage change [2]. The idea behind all three is simple. An analysis that nobody acts on has not produced value yet.
CBDA Use Results to Influence Business Decision Making at a glance
Domain 5 is where analytics results turn into a decision, a plan and a change in how people work. The facts:
| Item | Value |
|---|---|
| Domain | Use Results to Influence Business Decision Making (Domain 5) |
| Weight | 20% of the exam [1] |
| Exam format | 75 multiple-choice, scenario-based questions in 2 hours, online remote proctored only [1] |
| Guide section | 2.5: tasks 2.5.1 to 2.5.3, techniques (2.5.4) and a case study (2.5.5) [2] |
| Expected depth | 5 IIBA competencies: 3 at "General Awareness", 2 at "Practical Knowledge: Follows Rules" [3] |
| Exam fee | $324 (was $405), first year of IIBA membership included; sale runs October 29 to December 31, 2026 [4] |
Last verified: November 2026 (exam facts, fees and competencies on iiba.org).
The competency list and the guide do not line up one to one, and I think this is the most useful detail for the exam. The guide has three tasks [2]. The competency list has five items [3]:
| Competency | Level | Where it sits in the guide |
|---|---|---|
| 5.1 Determining if analytics results answer the research question | General Awareness | Start of 2.5.1 |
| 5.2 Assessing how well the analytics results are meeting the business need | General Awareness | Start of 2.5.1 |
| 5.3 Assessing proposed solution and recommending action | Practical Knowledge | 2.5.1 |
| 5.4 Developing an implementation plan | General Awareness | 2.5.2 |
| 5.5 Assessing organizational readiness and managing change | Practical Knowledge | 2.5.3 |
So the two places where the exam expects you to apply rules are recommending action and managing change [3]. The implementation plan is only "Understands". My take: spend your Domain 5 time on choosing between options and on change scenarios, not on plan formats.
The three tasks of Domain 5
The domain starts from one sentence in the guide: "Standalone reports and analytics results are useful only when some action is taken" [2]. Results can support a human decision or be built into workflows for real-time decisions, such as product recommendations in e-commerce, automated underwriting or fraud detection [2]. Any action based on them may change "people, process, offerings, or technology", and that change needs managing [2].
First step of 2.5.1: did the analysis answer the question?
The first step of Domain 5 is a check, not a recommendation. Before recommending anything, the analyst evaluates the analysis itself: did the outcome answer the research question, and how well did it address the business need [2]?
If the answer is no, and no feasible solution is found, the guide does not ask you to force a recommendation. The cycle repeats, "starting with the formation of a new research question" [2]. The six domains are iterative. This is a favourite exam move: a scenario where results are weak and one option pushes ahead anyway.
2.5.1 Recommend Actions
Recommend Actions turns validated results into solution options and a recommendation. If the analysis gave valuable insights, the work switches to conversations about how changes will be made. The guide calls these possibilities solution options, and they may include process, tool, resource or IT system changes [2].
What the analyst does:
- elicits the types of solution options the business might consider;
- rates and ranks the options;
- proposes a recommendation to the decision-makers, based on the analysis and insights [2].
The guide gives four criteria for a good solution: it aligns to the strategic direction, is valuable, provides a return for the investment and addresses stated KPIs [2]. It also says data professionals often need support to connect validated results back to the business, and business analysis professionals make results accessible and integrate them into deployable solutions [2].
One line is easy to miss. Changes from an analytics initiative "are prioritized, funded, and initiated like other change proposals" [2]. There is no fast track because the idea came from a model. Techniques named in the text: financial analysis for value, focus groups for feedback on options, and process, scope and organizational models [2].
The guide adds an e-commerce example that I would read twice. A retailer runs a proof of concept to detect pricing anomalies with a mix of models (Gaussian Naive Bayes, autoencoders, gradient boost and random forest), evaluated by F1 score, on static data [2]. The results are acceptable, but "Analytics results alone are not sufficient to deploy the solution" [2]. Before recommending it, the analyst asks four questions [2]:
| Question | Example from the guide |
|---|---|
| What is the financial return in production? | Live data streams, new architecture and changes to pricing algorithms versus savings from incorrect pricing |
| Are there alternative solutions? | A cheaper model, or a rule that flags prices some standard deviations away from the old price |
| What processes change? | Real-time blocking of purchases, when to run the model, whether to prioritize high-priced items |
| How will the deployed solution behave? | New data architecture and its fit with solutions such as product recommendations |
Key outputs: rated and ranked solution options and a recommendation the decision-makers can consume.
2.5.2 Develop Implementation Plan
An implementation plan outlines the strategy and a road map of the changes and tasks needed for a successful change [2]. The guide is direct: plans for analytics initiatives "are no different than implementation plans for other types of initiatives" [2].
The plan includes [2]:
- tasks and sub-tasks, resources, and a sequence with dependencies;
- high-level estimates provided by the stakeholders responsible for completing the tasks;
- constraints, assumptions, risks and dependencies.
To break down the work, analysts use functional decomposition, which "often takes the form of a work breakdown structure or story maps" [2]. Brainstorming and other elicitation techniques give the first list of tasks, and facilitation skills help to lead planning discussions [2].
Key output: the implementation plan. Exam angle: the estimates come from the people who will do the work, not from the analyst alone.
2.5.3 Manage Change
Manage Change is where the organization actually gets the value. In the guide's words, "Implementing change is the end goal" [2]. A change management team may run it with the analyst's support, or the analyst may be the change manager [2]. Business analysts suit this role because they keep continuity between the analytics work and the implementation [2].
What the analyst does [2]:
- makes sure stakeholders agree on what changes to make before implementing them;
- analyzes constraints, risks, assumptions, costs and the value proposition of each option;
- facilitates discussions, explains options and drives the decision;
- uses organization models, process models and sequence diagrams to show current and proposed ways of working;
- uses teaching skills to explain procedural changes.
Key output: implemented policies and procedures. Competency 5.5 adds "assessing organizational readiness" [3], a phrase the 2.5.3 text does not use. I read it as part of the stakeholder agreement and option analysis above.
Techniques for Domain 5
The 2.5.4 table lists ten BABOK Guide v3 techniques, and the guide says the list is not comprehensive [2]:
| Technique (BABOK v3) | Use in Domain 5 [2] |
|---|---|
| Acceptance and Evaluation Criteria (10.1) | Evaluate recommendations against agreed criteria and the business need |
| Balanced Scorecard (10.3) | Assess organizational impact of recommended actions or alternatives |
| Benchmarking and Market Analysis (10.4) | Evaluate competitor and market reactions to the recommendations |
| Decision Analysis (10.16) | Assess recommendations and their fit to the business problem; decision trees, multi-factor and sensitivity analysis |
| Financial Analysis (10.20) | Evaluate financial performance of recommended actions or alternatives |
| Lessons Learned (10.27) | Compile learnings on the approach, data resources and capabilities for future initiatives |
| Organizational Modelling (10.32) | Assist change management when the organizational model changes |
| Prioritization (10.33) | Prioritize recommendations or solution options |
| Process Analysis (10.34) | Understand the impact on future-state business processes |
| Risk Analysis and Management (10.38) | Assess risks, constraints and dependencies of the change |
Chapter 3 of the guide adds its own view. Decision Modelling and Analysis (3.8) "plays a significant role" here: the baseline decision model from Domain 1 is used to assess how insights affect decisions, and a decision tree can follow a decision to its logical impact (Guide, 3.8). Stakeholder List, Map, or Personas (3.16) says that after reporting "their work is not yet complete"; where insights are inconclusive, a consensus is needed on how to move forward (Guide, 3.16). Data Flow Diagrams (3.5) can show future-state data flows (Guide, 3.5). Concept Modelling (3.3), Data Dictionary (3.4) and Interface Analysis (3.13) are marked as having no significant role, with small supporting uses (Guide, 3.3, 3.4, 3.13).
The table explains why I like to link this domain to BABOK. Several of these techniques have their own articles here: Balanced Scorecard and Benchmarking and Market Analysis.
How it works in practice: the GiftRonline case
The guide's 2.5.5 case shows the domain on a real-looking problem [2]. GiftRonline, a UK online gift retailer, wants new customer segments instead of traditional demographic ones. It gives its data science team one year of transactional data. After comparing value-based segmentation, RFM and psychographic segmentation, and with the help of David Brown, a business analysis professional, the team groups products into baskets and clusters customers by their propensity to buy them [2].
The result: five product groupings and eleven customer clusters, and new customers can be classified with "almost (75%) accuracy" [2]. The executives are happy with the collaboration but confused. The segments are labelled cluster no.0, cluster no.1 and so on, and nobody knows how to operationalize them [2].
Mapped to the tasks:
| Step in the case | Domain 5 element |
|---|---|
| Executives ask "how do we operationalize results?" | Results answer the question, but are not yet consumable (5.1, 5.2) |
| A word cloud turns clusters into names such as "Holiday crafts" and "Jewelry & Luxury" | Making results accessible to stakeholders (2.5.1) |
| A spider chart compares segments by count (purchase visits), mean (average price paid per order) and sum (average spend per customer) | Shared understanding before a decision (2.5.1) |
| A feasibility study to integrate the findings with the CRM application, plus recommendations for the new segments | Recommend actions (2.5.1); in my reading, also the input for an implementation plan (2.5.2) |
The guide's takeaway is that insights can influence decisions, but they need to be communicated effectively, starting from "a shared understanding" of the results [2]. Note what the analyst did not do: he did not ask for a more accurate model.
A worked example: rating and ranking solution options
Ranking options is the step most exam scenarios hide inside. Here is the guide's pricing case pushed one step further. The weights and scores are mine and illustrative, not from the guide; the criteria are the guide's four [2].
| Criterion (weight) | A: real-time ML model, blocks purchases | B: rule, flag prices far from the old price | C: ML model in batch during pricing loads, high-priced items first |
|---|---|---|---|
| Strategic alignment (0.2) | 5 | 3 | 4 |
| Value (0.3) | 5 | 3 | 4 |
| Return on investment (0.3) | 2 | 5 | 4 |
| Addresses stated KPIs (0.2) | 4 | 3 | 4 |
| Weighted total | 3.9 | 3.6 | 4.0 |
The arithmetic: A = 1.0 + 1.5 + 0.6 + 0.8 = 3.9; B = 0.6 + 0.9 + 1.5 + 0.6 = 3.6; C = 0.8 + 1.2 + 1.2 + 0.8 = 4.0.
So the recommendation is option C, with A as a later step if C works. Then the other two tasks follow:
- Implementation plan (2.5.2): tasks such as the batch schedule, an alert queue for the pricing team and a CRM or catalogue integration, each estimated by the team that owns it, plus risks like a missed anomaly between loads.
- Manage change (2.5.3): agreement from pricing and customer service before go-live, a process model of the new review step, and short training for the people who will act on alerts.
A small detail from practice: a recommendation is stronger when it shows the options you rejected and why. One pair of BA trainers advises exactly that [5].
What practitioners and data say about the last mile
The data says that adoption, not modelling, is the usual bottleneck. In a 2023 survey of data scientists, "only 32% say that their models usually deploy" [6]. In McKinsey's 2026 survey of 1,719 participants, 37% report that AI has contributed positively to EBIT [7]. A 2026 benchmark of about 110 large companies reports that 93.2% of executives see cultural challenges and change management as the top barrier [8]. These are surveys about AI and data science, not about CBDA, but they describe the same gap Domain 5 is about.
Practitioners tell the same story in specific terms:
- The model took 6 weeks, the change took 8 months. A writer on industrial AI describes a predictive maintenance model that was ready in about six weeks. Changing technicians' behaviour took about eight more months: alerts as work orders in the maintenance system, thresholds agreed with technicians, a three-month shadow mode [9]. His line: "The changed behavior is the product." [9]
- Adoption beats accuracy. A practitioner writing about her AI projects saw a reporting launch where more than 90% of reports were still built in Excel. A basic recommendation model, rolled out in phases with shared KPIs and an owner, added more than €10M uplift within a year [10].
- The forecast was overridden. The head of a consulting firm's advanced analytics practice (2017) described planners or buyers who override the forecasting algorithm, so flannel ends up in Hawaii stores [11].
- "That's interesting" is not a decision. A data scientist recalls one of the first requests she received: stakeholders called the findings "interesting", and nothing changed [12].
- Results that contradict beliefs get ignored. A senior analyst on Reddit says an attribution model was ignored because it contradicted what the sales team believed: "data doesn't speak for itself" [13].
From a CBDA angle, candidates describe the exam as "scenario-based" [14] and warn that "many questions had two confusing answers" [15]. In Domain 5, those two answers are often "act on the results" and "check the results first".
Experts disagree on how far the analyst should go
Practitioners agree that results must be used, but not on who should push them.
1. The analyst recommends and stands behind it. Two CBAP trainers argue that the analyst should present what they believe is right for the organization, with the alternatives and why they were not chosen [5]. An analytics consultant goes further: analysts should stand by recommendations the way product managers do [16]. IIBA puts "recommending action" at Practical Knowledge [3].
2. The decision-maker owns the choice. Google's former chief decision scientist describes the advisor's job as helping decision-makers think in their own terms: "They're the actual decision maker." [17] An analyst in the same Reddit thread says that whether a recommendation is accepted, adjusted or rejected, "Those are all complete jobs for an analyst." [13]
3. Unused insight is the analyst's failure. One analytics product writer says insight "should be judged by its ability to drive behavior" [18].
4. Unused insight is a leadership and planning failure. A machine learning author points to under-planning and stakeholders who get cold feet before deployment [6].
5. Adoption needs its own role. A 2018 McKinsey article describes an analytics translator who "drives adoption among business users" [19]. The guide gives this role to the analyst or a change management team [2].
My view is close to the guide: recommend clearly, but treat "the decision-maker said no" as information, not as failure. For the exam, the guide's wording wins: the analyst proposes a recommendation and drives the decision-making process [2].
What the exam looks for in Domain 5
Domain 5 questions reward the answer that checks fit before acting. Typical scenarios and their correct reading:
| Scenario | Tempting answer | Guide reading |
|---|---|---|
| Results are inconclusive and no feasible solution appears | Recommend the cheapest option anyway | Repeat the cycle from a new research question [2] |
| A proof of concept scores well on static data | Deploy it | Assess production ROI, alternatives, process changes and solution behaviour first [2] |
| The sponsor wants the analytics change fast-tracked | Skip normal governance | Prioritize, fund and initiate it like other change proposals [2] |
| An implementation plan needs estimates | The analyst estimates alone | Stakeholders responsible for the tasks give high-level estimates [2] |
| Executives cannot use cluster labels | Ask for a more accurate model | Make results accessible: names, visuals, shared understanding [2] |
| The team wants to reuse what it learned | Write a final report | Lessons Learned on approach, data and capabilities [2] |
| Who manages the change? | Only a change management team | A change team with analyst support, or the analyst as change manager [2] |
How to prepare for the Domain 5 questions
- Learn the five competencies and the three tasks side by side (table above). Know which two are Practical Knowledge [3].
- Re-read the pricing anomaly box and the GiftRonline case. Both are about the gap between a working model and a working change [2].
- Review the ten BABOK techniques from 2.5.4, especially Decision Analysis, Financial Analysis, Prioritization and Risk Analysis.
- Revisit Domain 1, because Domain 5 closes the loop to the research question: see Identify the Research Questions. And Domain 4, where findings are framed: see Interpret and Report Results.
- Practice with scenario sets such as the CBDA decision-making quiz and full mocks in the CBDA exam simulator.
Check yourself: CBDA practice questions
1. An analytics team finds no clear pattern, and no feasible solution addresses the business need. What should the analyst do? A) Recommend the lowest-cost option. B) Repeat the cycle, starting with a new research question. C) Ask for a more complex model. D) Close the initiative with a final report.
Answer: B. The guide says the cycle is repeated, starting with the formation of a new research question [2]. A forces a recommendation without evidence.
2. After the analysis, the team wants to check how its insights affect business decisions. Which chapter 3 technique uses the baseline decision model from Domain 1 for this? A) Concept Modelling (3.3). B) Interface Analysis (3.13). C) Decision Modelling and Analysis (3.8). D) Data Flow Diagrams (3.5).
Answer: C. The guide says 3.8 "plays a significant role" in Domain 5 and reuses the baseline decision model (Guide, 3.8). A and B are marked as having no significant role.
3. Which technique compiles learnings on the analytics approach, data resources and capabilities for future initiatives? A) Balanced Scorecard. B) Lessons Learned. C) Process Analysis. D) Benchmarking and Market Analysis.
Answer: B. That is the 2.5.4 usage of Lessons Learned (BABOK 10.27) [2].
4. Who provides high-level estimates in the implementation plan? A) The analyst. B) The data science lead. C) The sponsor. D) The stakeholders responsible for completing the tasks.
Answer: D. Per 2.5.2 [2].
Key takeaways
- Domain 5 is 20% of the CBDA exam: three guide tasks, five competencies [1, 3].
- First check that results answer the research question; if not, loop back [2].
- Recommend Actions means eliciting, rating and ranking options against strategy, value, return and KPIs [2].
- Implementation plans for analytics are like any other plan; estimates come from task owners [2].
- Change is where value is realized, and the analyst may be the change manager [2].
FAQ
What is the Use Results to Influence Business Decision Making domain on the CBDA exam?
It is Domain 5 of the IIBA CBDA exam and weighs 20%, about 15 of 75 questions. It covers how analytics results become recommendations, an implementation plan and a managed change. The guide describes it in section 2.5.
How many tasks are in CBDA Domain 5?
The guide lists three tasks: Recommend Actions, Develop Implementation Plan and Manage Change. IIBA's competency list splits the domain into five items, adding two checks on whether results answer the research question and meet the business need.
What happens if the analysis does not answer the research question?
The guide treats business data analytics as iterative. If results do not deliver the needed insight and no feasible solution is found, the cycle repeats from a new research question instead of forcing a recommendation.
Which techniques matter most for CBDA Domain 5?
The guide lists ten BABOK techniques, including Decision Analysis, Financial Analysis, Prioritization, Risk Analysis and Management, and Lessons Learned. In chapter 3, Decision Modelling and Analysis (3.8) is the technique the guide says plays a significant role in this domain.
Does the analyst have to be the change manager?
No. Change may be run by a change management team that the analyst supports, or the analyst may hold the change manager role. The guide says business analysts suit the role because they keep continuity between analysis and implementation.
Sources
- IIBA: Certification in Business Data Analytics (CBDA)
- IIBA: Guide to Business Data Analytics, 2.5 Use Results to Influence Business Decision-Making
- IIBA: CBDA competencies
- IIBA: Certification fees
- BA Times: Oh no, you gave me what I asked for
- KDnuggets: Survey, machine learning projects still routinely fail to deploy (2024)
- McKinsey: The state of AI in 2026
- JD Supra: The state of AI, key insights from the 2026 executive benchmark
- DEV Community: Predictive maintenance, the hard part was not the ML model
- Towards AI: Adoption is where AI projects live or die (2025)
- Bain: The last mile of analytics (2017)
- Genevieve Hayes: "That's interesting" is not a compliment
- Reddit r/analytics: Seniors of this sub, what's one mistake you made
- Techcanvass: CBDA certification journey of Aniket (2024)
- Techcanvass: A CBDA candidate's certification journey (2024)
- Analytics Demystified: 7 tips for delivering better analytics recommendations
- DataCamp podcast: Making better decisions using data and AI (2023)
- Juice Analytics: From insight to impact
- McKinsey: Analytics translator, the new must-have role (2018)