CTC (NAR) common mistakes
CTC · Understand the traps and how to avoid them.
Treating mentoring and coaching as interchangeable labels, so scenario answers recommend 'coaching' for a struggling performer who actually needs structured skill transfer from a more experienced mentor, or recommend 'mentoring' when the goal is short-term, question-driven performance improvement.
The two terms overlap in everyday speech, and candidates rely on the colloquial sense ('coaching someone up') rather than the exam's distinction: coaching is typically non-directive, goal-focused and performance-oriented, while mentoring is developmental, experience-based and often longer-term.
What to do instead
Before answering, classify the need on three axes: time horizon (short vs long), direction of expertise (peer/supervisor vs senior role model), and whether the goal is a specific performance gap or broader career development. Build a one-line decision rule and apply it to every scenario stem before reading the options.
Recommending a formal, escalated conflict-resolution process (HR referral, mediation, written warning) for an early-stage interpersonal disagreement that could be handled by a direct conversation between the parties.
Candidates associate 'conflict management' with procedure and want to appear thorough, and exam stems often describe emotionally charged situations that feel serious even when the substantive issue is small.
What to do instead
Apply a severity and stage screen: is there a policy violation, safety issue, or repeated pattern? If not, the correct first step is almost always a private, direct, fact-based conversation using a structured format (observation, impact, request). Reserve escalation for documented, repeated, or rights-based conflicts.
Jumping to the first workable solution in creative problem-solving items instead of diverging first, then converging, and failing to separate problem definition from solution generation.
Under time pressure, candidates default to solution mode, and many options look plausible because they address a symptom rather than the root problem. The exam rewards process discipline, not cleverness.
What to do instead
For each scenario, explicitly restate the problem in one sentence and check whether the proposed action addresses cause or symptom. Prefer answers that generate multiple options before selecting, use structured tools (brainstorming rules, mind mapping, reverse brainstorming, weighted criteria), and only then converge.
Mislabeling DISC profiles by stereotyping: calling a high-D colleague 'a leader' and a high-S colleague 'unmotivated', or confusing high-I sociability with high-D assertiveness, and then prescribing a communication approach that clashes with the actual style.
DISC dimensions are behavioral tendencies, not competence or motivation measures, and the I/D and S/C pairs share surface features (both I and D can be talkative; both S and C can be quiet) that trip up candidates who learned only the four labels.
What to do instead
Learn each dimension as a pair of observable behaviors: pace (fast vs steady) and focus (task vs people). Diagnose from described behavior in the stem, not from job title. Then match the recommendation to the style: give high-D brevity and options, high-I interaction and recognition, high-S time and reassurance, high-C data and accuracy.
Confusing emotional intelligence components, for example recommending 'empathy' when the scenario calls for self-regulation, or treating self-awareness as equivalent to self-management, leading to a mismatched intervention.
The four-branch model (self-awareness, self-management, social awareness, relationship management) is easy to memorize as a list but hard to discriminate in scenarios, because a single incident can involve several branches at once.
What to do instead
Ask two questions about the stem: whose internal state is the focus (self vs others) and whether the task is recognizing or regulating. That yields a 2x2 that maps directly onto the four branches. Choose the option that addresses the branch the scenario actually names, not the one that sounds most compassionate.
Treating negotiation as a fixed-pie contest: choosing options that claim value aggressively (anchoring low, withholding all information) rather than options that expand the pie through interests, tradeables, and objective criteria.
Candidates import assumptions from competitive bargaining and from pop-culture negotiation advice, and distributive-sounding options often read as 'strong' or 'decisive'.
What to do instead
For each negotiation item, identify the parties' underlying interests and whether multiple issues exist (price, timing, scope, payment terms). If more than one issue exists, prefer integrative moves: log-rolling across issues, contingent agreements, and objective standards. Reserve distributive tactics for genuine single-issue, one-off situations.
Designing presentations that lead with background and methodology and bury the recommendation, or answering 'add more slides' when the scenario describes an audience that is disengaged or a decision that was not made.
Candidates mirror the academic or technical writing they know, where context precedes conclusion, and they equate thoroughness with slide volume rather than with the audience's decision.
What to do instead
Structure answers around audience and purpose: state the ask or recommendation up front, support it with a small number of evidence points, and specify the action requested. When the stem describes disengagement, prefer options that change framing, channel, or interaction over options that add content.
Confusing cash flow with profit, or evaluating a project on revenue or payback alone, when the scenario hinges on working capital, timing of receipts, or the cost of capital.
Non-financial managers habitually equate a sale with money earned and a budget with cash, and exam stems deliberately describe profitable-but-illiquid situations that look healthy on an income statement.
What to do instead
For every finance scenario, name the statement or metric in play: profit and loss, cash flow, or balance sheet. If timing of cash is mentioned, analyze receivables, payables, and inventory before recommending growth spending. For investment choices, compare on a discounted basis (NPV, IRR) rather than payback or gross revenue.
Answering project management scenarios by choosing to 'work harder' or 'escalate to the sponsor' rather than applying the control process: baseline, monitor, analyze variance, take corrective action, and manage change through a formal request.
Candidates without delivery experience treat schedule slips as effort problems, and escalation feels like decisive leadership. The exam rewards process control and stakeholder communication over heroics.
What to do instead
Map each stem to a phase (initiating, planning, executing, monitoring/controlling, closing) and ask which process artifact is missing. When a change is requested, prefer impact assessment and change control over silent acceptance; when a risk is identified, prefer documented risk response over reactive firefighting.
Treating team building as a social event: recommending a team outing, icebreaker, or morale boost when the scenario describes unclear roles, unstated norms, or unresolved trust issues that require structural intervention.
'Team building' colloquially means fun activities, and candidates pick the friendliest-sounding option, but the exam distinguishes social cohesion from task cohesion and psychological safety.
What to do instead
Diagnose the team problem first: unclear goals, unclear roles, poor processes, or interpersonal trust. Match the intervention to the diagnosis, such as a chartering session for goals and roles, working agreements for norms, or facilitated conflict for trust. Choose social activities only when the stem explicitly points to relationship familiarity as the gap.