BCT(B) common mistakes
BCT(B) · Understand the traps and how to avoid them.
When a scenario describes a business problem, the candidate jumps straight to proposing a software feature or tool instead of first clarifying the underlying business need and objectives.
The word 'solution' in the question stem triggers a tool-first reflex, and candidates conflate the BA role with a technical design role, skipping needs analysis.
What to do instead
Before answering, restate the problem in business terms: who is affected, what outcome is desired, and what constraints exist. Eliminate options that prescribe technology before the need and objectives are defined, and prefer the option that frames the problem and elicits requirements first.
The candidate treats a single stakeholder's stated want as the complete requirement set and selects the option that satisfies that one person.
Scenario stems often quote one vocal stakeholder, and candidates anchor on that quote rather than recognizing that requirements must be elicited from and validated with all relevant stakeholders.
What to do instead
Scan the stem for other affected parties and for signs of conflicting interests. Choose answers that gather input from multiple sources, reconcile conflicts, and confirm agreement rather than immediately accepting the loudest voice.
The candidate labels every requirement as functional and fails to distinguish non-functional requirements such as performance, security, availability, and usability.
Functional requirements are easier to spot in narrative text, so candidates under-detect quality attributes that are phrased as expectations or constraints.
What to do instead
For each stated need, ask whether it describes something the system does or a quality it must have. Practice classifying sentences containing words like 'within', 'must handle', 'secure', 'available', and 'easy to use' as non-functional, and select answers that capture both categories.
The candidate selects a future-state process design without first documenting and analyzing the current-state process.
Future-state diagrams look more impressive and candidates assume improvement means redesign immediately, underweighting the diagnostic value of as-is analysis.
What to do instead
Check whether the question asks for root cause, current-state understanding, or improvement opportunity. When the stem lacks evidence of a diagnosed problem, prefer options that map and measure the existing process before proposing redesign.
The candidate recommends removing a process step purely because it looks redundant, without checking downstream dependencies or control requirements.
Streamlining is a familiar improvement theme, and candidates equate step elimination with efficiency without considering risk, compliance, or rework effects.
What to do instead
Evaluate each proposed change against cycle time, quality, cost, and risk together. Reject options that remove a control or handoff without stating how the associated risk will be managed, and favor options that validate the change with data or a pilot.
The candidate confuses correlation with causation when interpreting a data trend described in a scenario and recommends action based on the association alone.
Stems present two variables moving together, and the narrative pressure implies a cause, which candidates accept without probing for confounders or alternative explanations.
What to do instead
Ask what else could explain the pattern and whether a controlled comparison or segmentation exists. Choose options that investigate alternative causes or gather more data before committing to a causal recommendation.
The candidate reports a metric or dashboard result without checking data quality, definitions, or the population it was drawn from.
Numbers in a stem feel authoritative, and candidates focus on interpreting the value rather than questioning how it was produced.
What to do instead
Before using any figure, verify the metric definition, time period, sample, and known data gaps. Prefer answers that state assumptions, reconcile conflicting sources, or flag data limitations alongside the finding.
The candidate evaluates a proposed solution only against how well it meets functional requirements and ignores feasibility, cost, risk, and organizational readiness.
Requirements coverage is the most visible criterion in the scenario, so candidates treat it as the sole decision basis and overlook trade-off analysis.
What to do instead
Build a mental evaluation matrix covering fit to needs, cost, risk, time to deliver, and organizational impact. Select the option that weighs multiple criteria or recommends a structured comparison rather than the option that simply satisfies the most features.
The candidate chooses to escalate an issue or seek approval from senior management as the first response to a routine stakeholder disagreement.
Escalation feels decisive and safe, and candidates assume authority resolves conflict faster than facilitation, so they skip the BA's own facilitation responsibilities.
What to do instead
Distinguish routine conflict from true blockers beyond the team's authority. For ordinary disagreements, prefer options that facilitate discussion, clarify interests, and document agreed decisions; reserve escalation for issues that genuinely exceed the group's mandate.
The candidate accepts a requested change directly into the current work without assessing its impact on scope, schedule, cost, and other requirements.
Change management fundamentals are often reduced to 'be flexible', so candidates equate responsiveness with immediately accommodating every request.
What to do instead
Route every change through an impact assessment and the agreed approval path. Choose options that analyze effects, document the decision, and update baselines only after authorization, and reject options that silently absorb scope.
The candidate discloses or uses confidential stakeholder information, or selects an option that sidesteps a conflict of interest, in order to resolve a scenario quickly.
Scenario pressure favors pragmatic-sounding answers, and candidates do not consistently screen options against professional conduct obligations.
What to do instead
Filter options through integrity, confidentiality, and conflict-of-interest standards before judging practicality. Eliminate any option that shares restricted information or proceeds without disclosing a personal interest, then choose among the remaining ethical options.