GAQM CPD common mistakes
GAQM CPD · Understand the traps and how to avoid them.
Treating the exam as a single-subject PMP-style test and studying only schedule, cost, and risk, while skipping the portfolio, programme, and organisational-governance material that the GAQM portfolio certification actually covers.
Candidates assume any 'project management' certification follows the PMBOK knowledge-area structure, so they reuse familiar study material and never check the published syllabus or exam blueprint for the actual domain weighting.
What to do instead
Download the official exam syllabus and build a coverage matrix mapping each listed topic to a study source. Allocate study hours in proportion to the published weighting, and explicitly schedule sessions for the governance, portfolio-selection, and benefits-realisation topics that generic PM prep skips.
Memorising definitions of portfolio, programme, and project without being able to classify a described scenario into the correct level or distinguish the role of portfolio manager, programme manager, and project manager.
Definitions are easy to flashcard, so candidates stop at recall. Exam items typically present a short situational description and ask which management level, role, or document applies, which requires application rather than recall.
What to do instead
For each concept, write three one-sentence scenarios of your own and practise assigning the correct level, role, and artefact. Drill the distinguishing criteria (scope, duration, benefit coupling, governance authority) rather than the wording of definitions.
Answering situational questions from personal workplace habit ('this is how my company does it') instead of from the standard, documented process the exam expects.
Experienced practitioners rely on intuition built in one organisation, and that intuition often conflicts with generic good-practice guidance, especially around change control, escalation, and stage-gate approval.
What to do instead
Before answering any scenario, identify which process step the question is testing, then choose the option that follows the documented sequence. Review every practice question you miss and write down the standard process step you substituted with a habit.
Confusing the project charter with the project management plan, or the business case with the benefits realisation plan, and selecting the wrong document in 'which artefact should be produced or reviewed next' items.
The documents overlap in content and are often produced close together in time, so candidates remember the names but not the authorisation and content boundaries between them.
What to do instead
Build a one-page comparison table for each document pair: purpose, who authors it, who approves it, what it authorises, and which process creates it. Test yourself by covering the columns and reconstructing them from memory.
Misreading negatively phrased or 'EXCEPT' questions and selecting the true statement when the question asked for the exception.
Under time pressure, candidates scan for keywords and pattern-match to the first familiar-sounding option, and the qualifier at the end of a long stem gets lost.
What to do instead
Circle or mentally flag every EXCEPT, NOT, LEAST, and FIRST in the stem before reading the options. For exception items, evaluate each option as true or false and then select the odd one out, rather than picking the first plausible statement.
Choosing the most decisive-sounding option (escalate to the sponsor, terminate the project, renegotiate the contract) on conflict and issue-resolution scenarios instead of the collaborative, process-first option.
Action bias feels like strong management, and real workplaces sometimes reward escalation, so candidates pick the dramatic answer over the correct 'assess, document, discuss with the team, then escalate if unresolved' sequence.
What to do instead
Learn the standard escalation ladder and apply it: gather facts, consult the team or stakeholder, attempt resolution within the project manager's authority, document, then escalate. When two options both seem reasonable, prefer the one that keeps the decision at the lowest competent level.
Ignoring earned value and other quantitative formulas until the week before the exam, then applying the wrong formula or misinterpreting a CPI or SPI above or below 1.0.
Quantitative items are a minority of the paper, so candidates deprioritise them, and formula recall decays quickly without spaced repetition and worked examples.
What to do instead
Write a single formula sheet (PV, EV, AC, CV, SV, CPI, SPI, EAC variants, TCPI) and do five worked numerical items per study session from the first week. For each result, state in words what the number means for cost and schedule before moving on.
Spending disproportionate time on a handful of hard scenario items and running out of time, leaving later questions unanswered or guessed without reading.
Scenario items are long and candidates over-invest in them because they feel high-stakes, and many candidates never rehearse under a timed, full-length condition.
What to do instead
Take at least two full-length timed mock exams. Set a per-question time budget from the total item count, mark and move on after the budget is exceeded, and reserve the final minutes for flagged items and a check that no question is blank.
Treating governance, stakeholder engagement, and benefits management as soft topics and skipping them, when they carry a substantial share of scenario items about decision rights and benefit tracking.
These topics feel less technical and less testable than schedule or cost, so candidates under-prepare, yet scenario items about who approves a stage gate or how benefits are measured are common.
What to do instead
Study governance structures, stage-gate and toll-gate decision rights, benefits registers, and benefits realisation reviews with the same rigour as cost and schedule. Practise explaining, in two sentences each, who decides what at each gate and how benefit realisation is measured after handover.
Reviewing only the correct answers on practice tests and never analysing why the distractors were wrong, so the same misconceptions recur on the real exam.
Reviewing answers feels productive but is passive; candidates confirm what they already knew and skip the diagnostic work of identifying the faulty reasoning behind each wrong option.
What to do instead
Keep an error log with four columns: question topic, chosen option, correct option, and the specific misconception that caused the error. Re-test yourself on logged misconceptions weekly, and retire an entry only after you can explain why every distractor in that item is wrong.