Business Problems and Opportunities

Business Problems and Opportunities

Quick Answer: Before sourcing data or choosing techniques, CBDA practitioners identify and frame the business situation: the problem or opportunity the organization wants to address, expressed as a business need (not a tool request). A solid frame states context, decision makers, uncertainty, and value at stake so research questions can be written without jumping to solutions.

Identify the Research Questions is the first CBDA knowledge area and carries roughly 20% of exam weight. Competency 1.1 — Identify and frame the business situation is the foundation for everything that follows: current-state analysis, future-state outcomes, gap analysis, KPIs, scope, assumptions, and eventually the research questions themselves. On scenario questions, the highest-scoring path is almost always to slow down, reframe the ask, and confirm the business need before any analytical work begins.

What "Frame the Business Situation" Means

Framing is deliberate discovery, not passive note-taking. When a sponsor says "our churn is bad" or "we need predictive analytics," the practitioner does not accept that sentence as the problem definition. Framing answers:

1. What is happening (or could happen) in the business? Context, process, market, customer, or operational reality.
2. Why does leadership care now? Trigger events, competitive pressure, cost, risk, or growth targets.
3. Who owns the decision? Named roles or committees that will act on analytics results.
4. What is uncertain? The knowledge gap that data work could reduce.
5. What would "better" look like? Direction of improvement without prescribing a specific tool.

Until those elements are clear enough to support a research question, the analytics effort is solution hunting, not business data analytics.

Problems vs Opportunities

IIBA language for CBDA treats problems and opportunities as two valid starting points for analytics research. Both must still be framed as business situations.

Exam tip: Do not assume "problem" is always negative and "opportunity" is always positive fluff. A delayed claims backlog is a problem; discovering that 18% of high-value customers never receive a retention offer is an opportunity. Both can justify analytics. The CBDA focus is whether the situation is defined as a business need rather than as a deliverable request.

Business Need vs Stakeholder Want

A stakeholder want is a preferred solution, feature, or artifact. A business need is the underlying requirement for change, decision support, or understanding that creates value.

Wants are useful clues—they reveal pain and preferred language—but they are not the situation. If you accept a want as the situation, you skip needs analysis and often produce expensive unused deliverables.

Avoid Solution-Jumping

Solution-jumping is selecting a technique, tool, or architecture before the research question exists. Classic CBDA traps include:

• Treating a tool request ("build a dashboard") as the business situation.
• Starting with available data and asking "what stories can we tell?" instead of "what decision must this inform?"
• Assuming the first stakeholder's stated problem is complete without cross-checking adjacent decision makers.
• Jumping to predictive models when the real gap is definitional (everyone uses different "active customer" rules).

The disciplined sequence for Domain 1 is: situation → business need → current state → future state / gaps / success metrics → scope & assumptions → research questions → approach. Later chapters cover scope, approach, and question formulation; this section locks the first gate.

Scenario Walkthroughs: Vague Ask → Framed Situation

Retail: Cart Abandonment

Vague executive ask: "Online conversion is soft. Build something with our web analytics so we can fix it."

Discovery questions a CBDA practitioner asks: Which segment, channel, and product family? Over what period did conversion change? Is the decision about pricing, UX, fulfillment speed, inventory accuracy, or promotion targeting? Who can change which lever?

Framed business situation (problem): Online conversion for mobile new customers in three priority categories fell 2.1 points year over year while desktop held flat. Merchandising and digital product share ownership of checkout UX and promo rules. Leadership needs to know which abandonment stages and customer cohorts drive the most recoverable revenue so they can prioritize one or two interventions before peak season—not a general "web data exploration."

Why this frame works: It names the gap, owners, time pressure, and the decision (prioritize interventions), without prescribing a dashboard or model type.

Finance: Credit Line Utilization

Vague executive ask: "Risk wants AI on credit lines."

Framed business situation (problem + opportunity mix): Revolving credit customers with high utilization and thin payment history are generating a rising share of late-stage delinquencies, while a subset of low-risk customers never receive limit increases and attrite to competitors. Credit risk and product management must decide whether to tighten underwriting on high-risk utilization patterns and expand proactive limit offers for low-risk segments, using evidence that separates risk of loss from opportunity of profitable growth.

Trap called out: "AI on credit lines" is a technique want. The business need is decision support for underwriting and limit strategy under capital and loss constraints.

Healthcare: Readmissions

Vague executive ask: "CMS penalties are painful—give us a predictive model for readmissions."

Framed business situation (problem): Thirty-day unplanned readmissions for heart failure exceed the peer benchmark, driving quality penalties and bed capacity pressure. Care management can deploy finite post-discharge nursing capacity. Clinical and quality leaders need to know which discharge characteristics and care-gap factors most strongly associate with preventable readmission, so scarce outreach is directed where it changes outcomes—not simply "who scores high on a model" without an action pathway.

Business need vs want: The want is a predictive model. The need is prioritized, actionable risk insight tied to interventions the organization can actually staff.

A Practical Framing Checklist

Use this checklist in interviews and on exam scenarios:

1. Restate the situation in business language (revenue, cost, risk, customer, compliance, capacity)—not IT language.
2. Classify problem vs opportunity (or both) and name the value at stake.
3. Separate want from need by asking "If we delivered X perfectly, what decision would still be hard?"
4. Identify decision makers and decision timing (who acts, by when).
5. List what is already believed vs. what is unknown (hypotheses vs. open questions).
6. Refuse tool-as-situation statements until the decision gap is explicit.
7. Confirm the framed situation with stakeholders before deep current-state data work.

Exam Traps to Watch

• Trap: Tool request as situation. If the stem says "leadership asked for a dashboard," the best next step is usually clarify the decision/need—not wireframes or SQL.
• Trap: Accepting symptoms as root. "Call center wait times are high" may be staffing, volume mix, process design, or product defects. Framing keeps the situation open enough for discovery.
• Trap: Single-stakeholder tunnel vision. Executives may want growth metrics while operations wants reliability; alignment sessions surface the shared need or an explicit multi-objective situation.
• Trap: Analysis without a decision owner. If no one will act on the answer, you do not yet have a framed analytics situation—you have a curiosity project.

Framing is a professional skill, not bureaucracy. On the CBDA exam and on the job, the practitioners who create business value are those who convert vague asks into decision-ready business situations before a single query runs.