OBA common mistakes
OBA · Understand the traps and how to avoid them.
Answering outcome-measurement questions by choosing the activity or output that sounds most impressive (e.g., 'hold a stakeholder workshop') instead of the indicator that would actually be tracked and compared against a baseline.
Candidates conflate 'what we will do' with 'how we will know it worked'; verbs like conduct, deliver, and train feel productive, so they get selected even when the stem asks for a measure, metric, or success criterion.
What to do instead
Before reading the options, rewrite the stem as a fill-in-the-blank: 'The best indicator/measure is ___.' Eliminate any option that is an action, a deliverable, or a resource. Keep only options that name a variable, its baseline, and its target or comparison.
Treating 'stakeholder' as a synonym for 'customer' or 'end user', and then selecting engagement or communication options that only address the external user group.
Everyday usage narrows the term, and options that mention customers feel concrete and safe. Candidates forget sponsors, regulators, delivery partners, and internal functions who can block or reshape the work.
What to do instead
For any stakeholder question, mentally list four categories (sponsor/decision-maker, doers, recipients, external authorities) and check whether the chosen option covers the category the stem's conflict actually involves. If the stem mentions approval, funding, or compliance, the relevant party is rarely the end user.
Choosing the most technically thorough analysis tool (full risk register, quantitative model, complete requirements traceability) when the stem describes a small, low-uncertainty, time-boxed situation.
Candidates equate sophistication with correctness and want to demonstrate knowledge of heavyweight techniques; they ignore the scale, cost, and proportionality cues embedded in the scenario.
What to do instead
Scan the stem for size, duration, uncertainty, and consequence-of-failure signals before evaluating options. Rank options by fit-to-context first, then by rigour. An option that is 'best practice in general' but oversized for the described context is a distractor.
Selecting the response that solves the immediate symptom (escalate, re-baseline, add resources) without first identifying or addressing the underlying cause described in the scenario.
Exam stems often end with a pressure phrase such as 'the deadline is at risk', which pulls attention to the deadline. Action-oriented options feel decisive, and analysis-oriented options feel passive.
What to do instead
Apply a sequence check: does the option gather information or diagnose before it acts? When two options both eventually solve the problem, prefer the one that precedes the other in a defensible order (understand, then decide, then act, then verify).
Confusing monitoring with control, and selecting 'collect data', 'produce a dashboard', or 'schedule a review' when the stem asks what to do about a detected deviation.
Both concepts live in the same performance domain, and reporting activities are highly visible and easy to describe, so they crowd out corrective-action options.
What to do instead
Anchor the distinction: monitoring observes and compares; control decides and acts on the comparison. If the stem already states that a variance is known, the correct answer must change something (corrective action, re-plan, escalation with a recommendation), not merely measure it again.
Handling ethical scenarios by picking the option that protects the project's schedule or the client relationship, rather than the option that discloses, escalates, or refuses the improper act.
Real workplaces reward delivery, and candidates import that reflex into the exam. Options that preserve harmony read as 'professional' and 'diplomatic'.
What to do instead
For any stem containing a legal, safety, conflict-of-interest, or truthfulness element, filter out every option that conceals, delays disclosure, or trades integrity for schedule. Then choose the most transparent option that also follows the proper channel and documents the action.
Misreading the question's subject: answering 'what should have been done earlier' when the stem asks 'what should be done next', or vice versa.
Stems are long, and the operative phrasing sits at the end after several sentences of context. Under time pressure, candidates pattern-match to the scenario topic and skip the actual ask.
What to do instead
Read the final sentence of the stem first, then read the scenario. Underline or mentally bold the tense and the subject (next, first, best, most likely, primary). Re-check the chosen option against that exact wording before moving on.
Building the plan, schedule, or budget in isolation from the people who will execute or be affected by it, then discovering late that the estimates or constraints were wrong.
Planning feels like an analytical, individual activity, and involving others looks like overhead. Candidates also assume the exam rewards speed of planning.
What to do instead
When a stem shows a plan failing on feasibility, adoption, or accuracy, prefer options that bring in the executing or affected parties early (participative estimating, review of assumptions, validation with the delivery team) over options that add documentation or tighten controls after the fact.
Assuming an approved baseline is immutable and rejecting any option that involves changing scope, schedule, or cost, even when the scenario clearly shows the original assumptions no longer hold.
Governance content emphasises baseline control, so candidates over-apply it and treat change as failure. They miss that controlled change through the proper authority is the correct professional response.
What to do instead
Distinguish unauthorised change (always wrong) from authorised change (often right). If the stem shows new information, a regulatory shift, or an infeasible constraint, the correct option usually routes the change through the change control process with impact analysis, rather than defending the baseline or quietly absorbing the change.
Picking an option that is merely plausible-sounding because it uses familiar terminology, without checking whether it is internally consistent with the constraints the stem already established.
Exam distractors are written to be fluent and jargon-rich. Candidates match on keywords rather than testing the option against the facts given, especially when running short on time.
What to do instead
Use a consistency test on the two finalists: does the option violate any stated constraint (budget, deadline, regulation, authority level)? Does it require information the stem says is unavailable? Eliminate on contradiction rather than selecting on familiarity, and reserve enough time to run this test on every scenario question.