BS common mistakes
BS · Understand the traps and how to avoid them.
Answering from workplace habit: reading a scenario and selecting the option that matches how their own organisation actually does it, rather than the option that reflects the generally accepted, definitional approach described in the exam's foundational material.
Years of local practice create a strong 'this is how it's done' reflex, and local practice is often a simplified or non-standard variant of the reference model. The candidate recognises a familiar situation and stops evaluating the options against stated principles.
What to do instead
Before choosing, ask 'is this the definitional/generally accepted answer, or just my employer's shortcut?' Flag any option that only makes sense if you assume a specific internal process, policy name, or org chart, and eliminate it unless the stem supplies those details.
Treating near-synonyms as interchangeable - using output, outcome, benefit and deliverable as if they mean the same thing, or risk versus issue, assumption versus constraint, scope versus requirement - and therefore picking an option that uses the right-sounding word in the wrong sense.
Everyday business language blurs these pairs, so the distinction feels cosmetic. Exam items are usually built precisely on the boundary between two adjacent terms, and the distractor is designed to be defensible under the loose colloquial reading.
What to do instead
Build a two-column glossary with only the terms that have a near-twin. For each, write the exam definition plus one boundary test and one counter-example (e.g. 'internal to the team = output; change experienced by the user = outcome'). Before answering, check whether the stem hinges on one of those pairs.
Memorising framework names and their component lists but not being able to say what problem each framework solves or what situation should trigger its use, so scenario questions that never name a framework go unrecognised and get answered from intuition.
Frameworks are easy to revise as labelled diagrams, and revision feels productive. Recall of a label is much easier than the conditional judgement 'this situation calls for this approach', so the gap stays invisible until an unlabelled scenario appears.
What to do instead
For each framework write a single line in the form 'Use when … / Do not use when …' plus a short trigger phrase (the words in a stem that should make you reach for it). Practise by covering the framework names in sample stems and naming the approach from the situation alone.
Skipping ahead in the process: choosing the option that starts doing the work (build it, schedule it, sign it off) when the stem shows the necessary basis has not yet been established, or accepting a step that is correct in general but out of sequence for the stage described.
Action options feel competent and decisive, and most candidates have more real experience of doing than of the upstream analysis. The 'first' or 'next' requirement is easy to read past when the later action is genuinely good practice.
What to do instead
Label the stage of the scenario in one or two words before looking at the options, then reject any option that belongs to a later stage. For sequence items, ask 'what must be true before this option is even possible?' and treat any unresolved prerequisite as a reason to eliminate it.
Defaulting to escalation: selecting 'refer to the sponsor/manager' or 'raise it with governance' for routine variances that sit inside delegated tolerance, and conversely choosing to handle locally a matter that exceeds the role's authority or involves a conflict.
Escalation is taught as the safe answer and carries no apparent downside, so it becomes a blanket choice. Distinguishing routine from exceptional requires reading the tolerance, threshold or authority detail that the stem deliberately includes.
What to do instead
Apply a two-branch rule: within tolerance, within role authority and no ethical dimension → the role acts and reports; outside tolerance, beyond authority, or ethical/legal exposure → escalate to the named owner. Scan the stem for numbers, thresholds and role titles before choosing.
Choosing the option that protects delivery when an ethics, compliance or safety option is present, and treating 'not illegal' or 'not prohibited in the policy I know' as equivalent to acceptable conduct.
Delivery pressure is the dominant frame in most operational experience, and ethical reasoning is slower than schedule reasoning. Candidates also reason from a narrow legal test because it feels objective and defensible.
What to do instead
If the stem mentions law, regulation, safety, confidentiality, gifts, or a personal interest, eliminate the delivery-friendly option first, before weighing anything else. Select the option that surfaces and discloses the issue to the right owner rather than the one that quietly resolves it.
Choosing a technique because its name is familiar or because it sounds sophisticated, without checking whether the data, sample size or input it requires is actually available in the scenario, and without checking whether the question asks for explanation or prediction.
Technique names are learned as a list, and revision rewards recognition. The constraint that a method needs certain inputs is rarely tested until it appears inside a scenario that supplies different inputs.
What to do instead
Before selecting a technique, state out loud what data it needs and confirm each input exists in the stem. Then ask whether the question wants to explain a past result, forecast a future one, or generate options - different families of technique answer each. Eliminate any option that requires data you would have to invent.
Accepting a quantitative option without a sanity check: not noticing unit mismatches (per month versus per year, percentages versus percentage points), dropping a zero, or choosing a figure that ignores a stated base rate or denominator.
Under time pressure the candidate locates the right formula, computes once, and matches to the first numeric option that looks similar. Calculation errors and deliberate near-miss distractors survive because nothing tests the result against an expected size.
What to do instead
Estimate the answer to one significant figure before computing, and compare the two. Write units next to every number as you use it, and convert everything to a single time base and a single currency or unit before calculating. If the option set contains a plausible-looking value within about 10% of your estimate, re-derive rather than guess.
Ignoring the qualifier in the stem - 'first', 'most appropriate', 'primary', 'best' - and picking a generally sound action that is not the first, not the most appropriate, or addressed to the wrong audience; for example broadcasting to all stakeholders when the stem singles out one group with a specific concern.
The qualifier is a single short word inside a long stem and the options often all describe legitimate actions, so the choice collapses into 'which of these is good?' rather than 'which of these satisfies the qualifier?'.
What to do instead
Underline or mentally circle the qualifier before reading the options, then re-read it after selecting and ask whether your choice still holds. For stakeholder items, map the stakeholder named in the stem to their interest and preferred channel, and eliminate any option aimed at a different audience.
Treating monitoring and review as a reporting activity: choosing 'produce a status report' or 'record the deviation' rather than the option that compares actual against the baseline, decides on corrective action, and updates the plan or the approach.
In many workplaces the visible artefact of monitoring is the report, so the observable output gets mistaken for the purpose. Options that stop at documentation feel complete and low-risk.
What to do instead
Require every monitoring or review answer to contain both a comparison against a stated baseline and a decision or action that follows from it. Reject any option that ends at recording, circulating or archiving, and look for the option that closes the loop into the plan or the next cycle.