FMP common mistakes
FMP · Understand the traps and how to avoid them.
Treating every 'first action' or 'next step' stem as if it asked for the best long-term solution, so the candidate picks the most thorough option instead of the immediate procedural step.
Stems use verbs like 'first', 'immediately', and 'next' interchangeably with 'best', and candidates default to choosing the most complete-sounding answer. Underline the operative verb and match the option to that time horizon; the correct option is usually the smallest complete action that unblocks the situation (verify, isolate, notify, then correct).
What to do instead
Before reading options, circle the time-word in the stem and write 'now' or 'eventually' beside it. Eliminate options that belong to the other horizon. Practice with paired stems that differ only by that word.
Skipping the scope/authority check and choosing a technically correct fix that the candidate has no authority to perform.
Technical training rewards the right repair; exams reward the right repair by the right person. Options are written so one is technically ideal but requires a work order, vendor, or engineering approval the role lacks.
What to do instead
For any action question, run a two-question filter: 'Am I allowed to do this?' then 'Is this the right fix?' Reject technically ideal options that require escalation the stem has not authorized, and prefer the option that documents, escalates, or obtains approval.
Reading the schedule network as a list of activities and adding durations, rather than tracing the longest path through dependencies.
Candidates who have not internalized critical path method treat 'total duration' as a sum, and distractors are built from exactly that arithmetic. Float and near-critical paths are ignored.
What to do instead
Redraw the network on scratch paper with earliest start/finish forward pass and latest start/finish backward pass. Identify zero-float activities explicitly, then answer. Any question about delay impact must be traced to the path, not the individual task.
Answering risk questions with a response (mitigate, avoid, transfer) when the stem asks about the process step (identify, analyze, plan response, monitor).
Risk terminology overlaps and candidates collapse the process into a single bucket, so they pick a plausible tactic for a question about sequencing or documentation.
What to do instead
Classify the stem first: is it asking 'what category of response', 'which step comes next', or 'who owns it'? Keep a one-line definition of each response type and each process step on a memory sheet, and match the stem to the definition before scanning options.
Confusing cash flow with profit, or contribution margin with gross margin, when evaluating a proposal.
Everyday language treats 'making money' and 'having money' as the same, and the exam deliberately offers a profitable-but-cash-negative option as a distractor.
What to do instead
For any financial evaluation, write the three lines separately: revenue, cash timing, and margin. Ask whether the question is about liquidity, profitability, or return. Compute contribution margin as price minus variable cost per unit, and never substitute it for net income.
Ignoring the time value of money and comparing undiscounted totals across options with different cash timing.
Candidates without finance depth add up cash flows across years as if they were equivalent, and the exam includes a higher nominal total that is worth less when discounted.
What to do instead
Whenever cash flows span more than one period, discount each to present value before comparing. Memorize that a dollar later is worth less and that payback period ignores cash flows after the cutoff; flag any option relying on payback alone as incomplete.
Choosing the answer that solves the immediate technical problem while ignoring the people or communication step the scenario is actually testing.
Operations-trained candidates read scenarios as equipment problems, but many stems embed a stakeholder, safety-culture, or team-morale issue that is the real decision point.
What to do instead
Read the last sentence of the scenario twice and ask 'who is affected and what do they need to know?' If a person or team appears in the stem, check whether the correct option includes communication, coaching, or escalation before the technical fix.
Defaulting to a directive or autocratic response whenever the stem mentions urgency, safety, or a deadline.
Urgency feels like a license to command, so candidates pick the fastest-sounding option even when the scenario rewards a brief consult or a clear delegation.
What to do instead
Match leadership style to the situational variables in the stem: time pressure, team competence, and consequence of error. High urgency plus low competence favors directive; high competence plus adequate time favors consultative or delegative. State the variable that drove your choice.
Treating 'all of the above' or the longest, most comprehensive option as safe, and not eliminating options that contain an absolute word.
Test-taking habit substitutes length for correctness, and exam writers insert absolutes ('always', 'never', 'only') into otherwise attractive distractors.
What to do instead
Eliminate absolutes unless the stem states a rule with no exceptions. Judge each option on its own merits before considering combination options, and prefer specific, bounded actions over sweeping ones.
Answering from memory of a similar-sounding standard or regulation instead of the facts stated in the stem.
Candidates import assumptions from their own site or from a different standard, then select an option that is true in general but wrong for the scenario given.
What to do instead
Highlight the stated facts and constraints in the stem and reject any option that depends on information not present. If two options are both true, the tiebreaker is which one the stated constraints permit; mark the question for review rather than guessing on an unstated assumption.