WCC (NAWCCB) common mistakes
WCC · Understand the traps and how to avoid them.
Treating a project's triple constraints as fixed and answering that scope, schedule, and cost can all be held constant when a stakeholder adds requirements, instead of identifying which constraint must flex and documenting the change through the change-control process.
Candidates memorize the iron triangle as a definition but never practice applying it to a scenario stem, so they default to 'do it all' answers that ignore trade-offs and approval workflows.
What to do instead
For every scenario question, name the constraint being stressed, state the trade-off explicitly, and select the answer that routes the change through formal approval and baselining rather than informal accommodation.
Confusing project and program management roles, attributing program-level benefits realization, interdependency management, and governance to a single project manager, or assigning project execution to a PMO.
The terms sound interchangeable in everyday speech and candidates skim the stem for keywords like 'manager' without checking the scope described (single deliverable vs. coordinated benefits across projects).
What to do instead
Anchor each term to its defining output: project = a unique deliverable; program = related projects managed together for benefits; portfolio = prioritization across the organization; PMO = standards and support. Match the stem's scope to the definition before reading options.
Building a workforce plan from headcount targets alone, ignoring demand drivers such as attrition, retirement risk, span-of-control changes, and build-versus-buy-versus-borrow options, and failing to distinguish strategic workforce planning from vacancy filling.
Recruiting experience biases candidates toward requisition-based thinking, and exam stems often describe a business strategy without naming the workforce implication explicitly.
What to do instead
Convert the business scenario into a demand forecast, subtract projected supply (current staff minus expected attrition plus internal mobility), and identify the gap-closing strategy. Practice writing one-sentence gap statements before selecting an answer.
Selecting the fastest-sounding sourcing or selection method without weighing validity, adverse impact, and job-relatedness, for example endorsing unstructured interviews or personality tests as sole screeners, or skipping structured scoring rubrics.
Candidates optimize for speed and cost in scenario answers and underestimate how heavily selection validity and defensibility are tested.
What to do instead
Rank selection tools by predictive validity and structure (work samples and structured interviews high; unstructured interviews and single interviews low), and prefer answers that tie criteria to a job analysis and monitor adverse impact.
Treating total rewards as base salary only, overlooking pay mix, variable pay, benefits value, and non-monetary elements, or misapplying compa-ratio, range penetration, and market positioning concepts when asked to diagnose pay issues.
Candidates conflate 'compensation' with 'pay' and skip the arithmetic step, guessing at compa-ratio direction (below 1.0 means paid under midpoint) under time pressure.
What to do instead
Rehearse the core formulas until automatic: compa-ratio = salary / midpoint; range penetration = (salary - minimum) / (maximum - minimum). For every rewards question, list all reward elements in the stem before choosing, and check whether the question asks about internal equity or external competitiveness.
Answering employee-relations scenarios by choosing the most sympathetic or punitive response rather than the procedurally correct one, such as skipping documentation, investigating informally, or disciplining without progressive steps or consistency with past practice.
Real-world shortcuts and gut reactions feel intuitive, and candidates do not consistently map scenarios to just-cause, due-process, or progressive-discipline frameworks.
What to do instead
Apply a fixed checklist to every ER scenario: policy exists, investigation conducted, evidence documented, employee heard, consequence proportionate and consistent, appeal path available. Eliminate any option that skips a step, then choose among the procedurally sound remainder.
Confusing jurisdiction-specific employment law concepts, for example mixing exempt/non-exempt classification tests with independent-contractor tests, or applying a leave or accommodation rule from one legal regime to a scenario governed by another.
Statutes overlap and candidates study labels rather than decision criteria, so they match on keywords like 'overtime' or 'accommodation' without checking which test the stem invokes.
What to do instead
Build a comparison table for the tests you must know (duties plus salary basis for exemption; behavioral control, financial control, and relationship type for contractor status) and, for each practice question, write the governing test in one line before answering.
Choosing a training delivery method by novelty or cost rather than by learning objective, audience, and transfer conditions, and treating evaluation as an afterthought instead of designing Kirkpatrick levels or ROI measurement into the intervention.
Candidates equate modern formats (e-learning, microlearning) with effectiveness and rarely connect needs analysis to evaluation design.
What to do instead
Follow the chain explicitly: needs analysis determines objective, objective determines method and practice design, and evaluation level is chosen before launch. Prefer answers that include a needs analysis and a measurement plan over answers that only name a format.
Reporting HR metrics that are easy to produce rather than decision-relevant, presenting turnover as a single number without segmentation or cost, or confusing leading and lagging indicators and correlation with causation in analytics scenarios.
Candidates memorize metric definitions but not their use, and analytics stems reward reasoning about what a number can and cannot support.
What to do instead
For each metric, state the decision it informs and its leading/lagging status. When a stem presents data, ask what comparison or segmentation is missing (voluntary vs. involuntary, high performer vs. low, cohort vs. point-in-time) and prefer answers that add that context before concluding.
Treating an HRIS selection or implementation as a software purchase rather than a change and data-governance program, ignoring requirements definition, data migration and cleansing, integration, role-based access, and user adoption and training.
Technology questions read like IT questions, so candidates focus on features and vendor choice and overlook process design, data quality, and change management, which are usually the tested points.
What to do instead
For any HR technology scenario, run a standard sequence: define requirements from process and reporting needs, assess data quality and migration, plan integration and security/access, then plan change management and training. Eliminate options that skip requirements or data readiness.