CRST common mistakes
CRST · Understand the traps and how to avoid them.
Writing learning objectives that describe what the trainer will present ("cover the five objection-handling steps") instead of what the learner will be able to do afterwards, and never checking whether each objective names an observable behaviour plus a condition or standard.
Candidates draft objectives quickly as a formality before moving to content design, mirroring the agenda-style language they see in slide decks and trainer guides rather than the performance language the exam expects.
What to do instead
For every objective, rewrite it as 'Given [condition], the learner will [observable action verb] to [standard].' Ban the verbs know, understand, cover, and be aware of. Cross-check that each objective's verb matches the level of the assessment you plan to use, and delete any objective you cannot assess.
Treating a training request as automatically a training problem, skipping the gap analysis that separates a knowledge/skill gap from an environmental, tooling, incentive, or process gap, and never stating the business goal the program serves.
Stakeholders often arrive with a solution already chosen and a deadline attached, and candidates absorb that framing instead of pushing back to define the performance gap and its cause.
What to do instead
Before designing anything, write a one-paragraph gap statement: current performance, desired performance, measured difference, and the evidence that the cause is skill or knowledge rather than environment. If the cause is not skill-based, recommend the non-training intervention and say why. Tie the gap to a business metric you can name.
Designing delivery around lecture and slide review for content that requires practice, and failing to build in the practice, feedback, and spaced retrieval that the target skill demands.
Lecture is the fastest content to prepare and the easiest to control in a live room, so under time pressure candidates default to telling rather than having learners do.
What to do instead
For each objective, select a method by matching it to the verb: declarative knowledge gets retrieval practice and worked examples; procedural skills get demonstration followed by guided then independent practice with feedback; interpersonal skills get role-play with structured observation. Write the practice activity into the lesson plan with its time allocation before writing any slides.
Describing adult learners only in terms of 'they need relevance and respect' without applying the specific implications: drawing on their existing experience, letting them direct part of the learning, and framing content around problems they actually face on the job.
Candidates memorise a short list of adult learning principles as vocabulary and then write generic justifications that could apply to any audience, rather than converting each principle into a concrete design decision.
What to do instead
For each principle you cite, state the design decision it produced. For example: 'Because learners have 5+ years of sales experience, the opening activity asks them to diagnose a real stalled deal from their own pipeline, and the trainer uses their examples as the case material for the objection-handling module.' If you cannot name the design decision, drop the principle.
Mapping a sales training program to generic topics (communication, relationship building, closing) rather than to the organisation's actual sales process stages, the specific competencies required at each stage, and the customer interactions where performance is weakest.
Generic sales content is widely available and feels safe, and candidates may not have internalised that a sales training curriculum must be anchored to the defined process and the buyer's journey.
What to do instead
Build a matrix with the organisation's sales stages on one axis and required competencies on the other, then mark where the performance evidence shows weakness. Design each module to target one cell, and state which stage and which customer interaction the module changes. Include the customer-facing behaviours, not just internal sales tactics.
Presenting product knowledge as a feature inventory to be memorised, without linking features to customer problems, proof, and the questions that uncover need.
Product material usually arrives from marketing as a feature-and-benefit list, and candidates transfer it into the curriculum unchanged instead of converting it into usable selling knowledge.
What to do instead
Convert every product module into a three-column structure: customer problem or trigger, capability and the proof that substantiates it, and the discovery question or demo moment that surfaces it. Assess with scenario questions ('the buyer says X, what do you ask and what do you show?') rather than feature recall.
Writing a session plan as a content outline with no timings, no transitions, no interaction points, and no contingency, so the delivery plan cannot be executed or recovered when a segment runs long.
Candidates plan from the slide deck outward, treating the plan as a table of contents, and underestimate how much time practice and discussion consume relative to presentation.
What to do instead
Produce a plan with a row per segment showing start time, duration, method, trainer activity, learner activity, materials, and the evidence of learning you will collect. Total the durations and add a 10-15 percent buffer. Mark two segments as cuttable and write the transition sentence between each pair of segments.
Giving feedback in the form of general praise or general criticism ('great job', 'you need to be more confident') instead of describing the specific observed behaviour, its effect, and the concrete alternative.
Candidates want to keep the room positive and avoid discomfort, so they soften feedback into vague encouragement that the learner cannot act on.
What to do instead
Use a behaviour-impact-request structure: 'When you [specific observed behaviour], the effect on [customer/learner/outcome] was [effect]. Next time, try [specific alternative].' Require at least one observable detail in every feedback statement, and practise writing three examples before the session so the habit is set.
Evaluating a program only with end-of-session smile sheets and reporting those scores as evidence of effectiveness, without any measure of learning, behaviour change, or business result.
Reaction surveys are easy to administer and produce immediate numbers, and stakeholders often accept them, so candidates stop there rather than designing measurement up front.
What to do instead
Build an evaluation plan at design time with at least one measure at each level you can realistically capture: reaction, learning (a scored assessment or skills demonstration), behaviour (a field observation or manager checklist at 30/60/90 days), and results (the business metric from the gap statement). State the data source, timing, and owner for each. Report reaction data only as a diagnostic, never as proof of impact.
Handling a compliance or ethics topic by distributing policy text and obtaining a signature, without assessing understanding or addressing the situations where the rule is ambiguous in practice.
Compliance content is treated as a legal box-ticking exercise with a fixed time slot, and candidates assume attendance plus acknowledgement equals competence.
What to do instead
Design compliance training around realistic scenarios with grey areas, require a decision and a rationale from each learner, and assess with applied questions rather than policy recall. Document the assessment results and any remediation. Keep the trainer's own conduct in scope too: state how confidentiality, data handling, and fair assessment will be maintained.