CTMA common mistakes
CTMA · Understand the traps and how to avoid them.
Choosing an answer that names a specific tool or system (an ERP module, a CAD package, a particular maintenance technique) without first checking whether the question is asking about the process, the deliverable, or the organisational capability that tool supports.
Candidates with hands-on technical backgrounds anchor on the technology they use daily and treat any question mentioning a tool as a tool-selection question, even when the stem describes a planning or governance problem the tool cannot solve by itself.
What to do instead
Before answering, restate the stem in one sentence and label it as process, output, or capability. Eliminate any option that answers a different label, even if the option is factually true about the tool.
Treating technology roadmaps as fixed multi-year schedules and selecting the option that commits to a single technology at a single date, rather than the option that builds in review gates and decision points.
Roadmap artefacts seen in vendor decks look like Gantt charts, so candidates equate roadmapping with scheduling and overlook the uncertainty-management purpose of the exercise.
What to do instead
When a stem mentions roadmap, portfolio, or technology plan, prefer answers containing staged investment, decision gates, or trigger conditions over answers containing fixed dates or single-platform commitments.
Answering technology-insertion questions by picking the most advanced option instead of the option that matches the organisation's absorptive capacity and integration effort.
Candidates equate newer technology with better management judgement, and exam stems that describe a modest-capability organisation are read as generic best-practice prompts.
What to do instead
Scan the stem for signals about skills, training, existing infrastructure, and change load. If those signals are weak, eliminate the most advanced option and choose the one that sequences adoption or pilots first.
Confusing capacity with throughput or utilisation, and computing capacity from demand figures rather than from available time minus planned losses.
Everyday usage treats capacity as 'how much we can do', so candidates plug demand into the capacity slot and then answer a utilisation question as if it were a capacity question.
What to do instead
Write the formula down before calculating: capacity comes from available hours and effective rates; utilisation divides actual output by capacity; throughput is observed output per period. Label the unknown first, then compute.
Mixing up push and pull logic, or applying lean tools (kanban, takt time, value-stream mapping) to a context where demand is too unstable or setup times too long for them to apply.
Lean vocabulary is over-learned and candidates pattern-match any stem containing waste or inventory to a pull answer without checking demand variability, batch constraints, or buffer requirements.
What to do instead
Check the stem for demand stability, setup time, and variability. If those conditions are unfavourable, look for the answer that uses buffering, decoupling, or hybrid logic rather than the pure pull answer.
Reading a quality or process-control scenario and jumping to the corrective action before identifying whether the question asks about detection, containment, root cause, or prevention.
Candidates conflate corrective and preventive action, and treat any defect mention as a call for a control chart or an inspection step, when the stem may be asking about the systemic fix.
What to do instead
Classify the question as detection, containment, root cause, or prevention before reading the options. Then eliminate options that operate at the wrong level, even when they are technically valid quality tools.
Using a single-point estimate for a cost, tolerance, or schedule comparison when the stem supplies ranges, variability, or uncertainty, and then selecting the option that reflects the midpoint.
Candidates want a clean number and mentally collapse a range into its average, discarding the information the stem deliberately provided to test whether uncertainty is handled.
What to do instead
When a stem contains a range, a standard deviation, or a worst-case figure, treat that as the intended decision input. Prefer options that use the range, add margin, or state a probability over options built on a single average.
Applying a formula with the wrong unit basis, such as mixing watts and kilowatts, gauge and absolute pressure, or per-hour and per-year cost rates, and then choosing the numerically closest option.
Calculation pressure plus unit labels embedded in the middle of a stem cause candidates to skip unit reconciliation, and distractor options are frequently built from exactly these unit errors.
What to do instead
Convert every given quantity to a single consistent unit set before substituting into the formula, and write the units next to each intermediate result. If two options are close, recheck the unit conversions rather than the arithmetic.
Answering motivation and team questions by selecting the option that sounds most supportive or most democratic, regardless of what the situation calls for.
Leadership content is read as a values test, so candidates default to consensus-building answers even in stems describing urgent, low-competence, or safety-critical situations where directive action is correct.
What to do instead
Identify situational variables first: urgency, team competence, task ambiguity, and consequence of error. Choose the style that fits those variables, and reject the supportive option when the stem signals a crisis or a compliance requirement.
Treating change management and stakeholder engagement as a single announcement step, and choosing the option that communicates the decision rather than the option that builds commitment or addresses resistance.
Candidates reduce change to communication because that is the visible artefact, and underestimate the sequencing of sponsorship, involvement, and reinforcement that the exam tests.
What to do instead
When a stem involves a change initiative, prefer answers that sequence diagnosis, stakeholder involvement, and reinforcement over answers that centre on a single communication event, and check who owns the change before selecting.