Training
Built around Meridian Intelligence, the hypothetical company on the Case page. The programs and targets below are my own designs for this case and all numbers are illustrative. The four-pillar structure draws on Highspot’s Train and Coach Reps course. Other sources are at the bottom of this page and on the Sources page.
In brief: Meridian’s training program runs on four pillars: curriculum design, reinforcement, delivery, and measurement. It serves sales, customer success, and account management. Onboarding applies it to new hires, and Coaching keeps the skills in use. Each program is built with ADDIE, evaluating in every phase. Short on time? Read the next two sections, then the worked example at the end.
How training answers the Case
Training starts by asking whether it is the right fix. These are my working hypotheses, to be tested by interviewing recent hires, managers, and top performers.
1. Slow ramp: training supplies the personas, reinforcement, and delivery that the Onboarding plan runs on. The weak point is likely knowledge and unclear structure. The primary fix is an onboarding plan with a named owner.
2. Inconsistent discovery: a shared questioning framework, role-plays scored against it, and a certification gate. The weak point is knowledge (no standard) and reinforcement (no feedback). The primary fix is a shared framework, then coaching.
3. No CS health signal: a CSM track that teaches the six health signals, with scored practice on sample accounts. The weak point is knowledge and ability. The primary fix is the CSM track, then coaching.
4. Messaging drift: a quarterly messaging session shared with Marketing, and a readiness session at each launch. The weak point is reinforcement. The primary fix is that session, launch readiness, and call review.
The four pillars
Curriculum design: built around who is learning. Three personas (New Hire, Lateral Hire, Tenured Team Member), one shared library, one placement check in week 1, and the same certification gates for everyone.
Reinforcement: every piece of content is paired with a way to practice and recall it, through shadowing, debriefs, role-plays with rules, and short refreshers.
Delivery: virtual, in short sessions spread over time, capped at 90 minutes, with frequent low-stakes knowledge checks.
Measurement: designed before launch, working backward from the business result, using Kirkpatrick’s four levels.
Design choice: one shared library, with placement. Everyone draws from one library and meets the same gates, but a placement check in week 1 sets each person’s path. The alternative was separate tracks for new and experienced hires. Separate tracks drift apart and double the maintenance for a function of one person. It would change if the experienced-hire group grew large enough to need its own materials.
-
Hiatt’s ADKAR model describes five steps a person moves through when a change lands: awareness, desire, knowledge, ability, and reinforcement. The first weak step is where the effort belongs. Training mainly builds knowledge and ability. If the weak point is desire or reinforcement, the fix is sponsorship, incentives, or coaching. The Heath brothers make a similar point in Switch: a “people problem” is often a situation problem, so change the path as well as the person.
-
The program follows Knowles’s six principles: sessions open with what goes wrong without the skill, tenured people compare the new approach with their own, stable material is self-paced, training lands just before people need it, practice uses real situations, and each session connects the skill to what the person wants.
Learning that feels easy is often an illusion. Re-reading feels productive because the material looks familiar, but recognizing something is different from recalling it or doing it. So the program judges training by what people can do later, and uses the methods the research behind Make It Stick shows work: retrieval practice, desirable difficulty, spacing, interleaving, generation, and elaboration. The table below shows how each is applied. The test of any session is whether behavior changes, so each one ends with “What will you do differently on your next call or meeting?”
What makes learning stick (tap to open)
| Principle | What it means | How Meridian applies it |
|---|---|---|
| Retrieval practice | Pulling an idea out of memory strengthens it more than rereading | Each session opens with a few short recall questions from the last one and ends with a quiz. Live sessions include a knowledge check every 15 to 30 minutes. Refresher clips come with a question, not just a video. |
| Desirable difficulty | Effort that feels slow often produces stronger learning | Role-plays follow the "don't rescue" rule, so people work through the problem themselves. Facilitators explain up front why it feels hard. |
| Spacing | Revisiting material over time beats one intense session | A follow-up practice a week after each session, a scorecard check at 30 days, and monthly workshops that revisit earlier skills. Weekly blocks stay short. |
| Interleaving | Mixing related topics builds the skill of choosing the right approach | Role-plays mix scenarios (a discovery call, then an objection, then a positioning question) instead of drilling one at a time. CSMs score a mix of healthy and at-risk sample accounts, so they have to diagnose before they act. |
| Generation | Attempting an answer before seeing it makes the answer stick | Before the discovery framework is introduced, reps write how they'd open a call. Before the health-check, CSMs sketch the signals they'd watch. |
| Elaboration | Explaining and connecting an idea strengthens it | Participants restate concepts in their own words and link them to their own accounts. In the next session, each person teaches one concept to a peer. |
| Method follows the subject | The evidence for "learning styles" is weak, so the material should decide the method | Discovery and business reviews are practiced by doing. Product knowledge is learned by recall and scenarios. Formats vary to keep sessions engaging, but they aren't assigned by a person's supposed style. |
-
ADDIE (Analyze, Design, Develop, Implement, Evaluate) is the standard sequence for building a learning program. The common mistake is to treat Evaluate as the last step. Kirkpatrick’s guidance, which this site follows, is that evaluation starts in the first phase and runs through every one. The business result and behavior measures are set first, with a baseline recorded. The evaluation tools are designed with the program. A small group pilots it before rollout, and behavior is reviewed at 30 and 60 days.
ADDIE at Meridian (tap to open)
| ADDIE phase | What happens at Meridian | How evaluation is built in |
|---|---|---|
| Analyze | Ask whether training is the right fix, using the knowledge, ability, desire, and reinforcement test. Name the business result and the behaviors that would produce it. | The result (Level 4) and behavior (Level 3) measures are set first, and a baseline is recorded before anything is built |
| Design | Write the objectives and choose the delivery, using the four pillars, the certification gates, and the track scorecards | The evaluation tools are designed alongside the program: reaction questions (Level 1), knowledge checks and role-plays (Level 2), the scorecard (Level 3), and who collects each |
| Develop | Build the content, role-plays, and scorecards, then pilot them with a small group before any rollout | The pilot is a formative check: what the small group struggles with gets fixed before it reaches everyone |
| Implement | Deliver the sessions, then follow up through coaching and reinforcement, which is where the learning turns into behavior | Short knowledge checks during sessions, not only a survey at the end, and behavior reviewed at 30 and 60 days |
| Evaluate | Compare each cohort to its baseline, report training as a contributor to results and not the sole cause, and log every change | Not a final step. It runs through the other four, and its findings feed the next round of analysis |
-
Curriculum design: sales and CS leaders and managers name the top skill gaps, and Marketing and Product confirm content. A baseline is taken before and after (Opportunity Grading Agent scores and framework adherence for sales, health-score accuracy for CS, expansion-opening quality for account management). Every gate has a stated deadline, a defined path, a verbal commitment to the manager, and a scheduled check-in (the WHAT Model). Objectives are written as observable behavior, such as “write an upfront contract for a real upcoming meeting.”
Reinforcement: people shadow before they perform. Post-shadow debriefs ask “What made that walkthrough land?” Role-plays follow the “don’t rescue” rule, and sales mock calls are scored on the Opportunity Grading Agent as if the opportunity were real. Refresher clips tie to each gate, with flashcard decks revisited on a spaced schedule and Smart Brevity-style summaries of platform updates.
Delivery: weekly blocks capped at 90 minutes (every two weeks for people already on the team). Lateral Hires and Tenured Team Members can test out of general sales-skills content by showing the skill on the scorecard. Certification badges mark each phase, and a brief check every 15 to 30 minutes uses the Sandwich Approach (something they did well, something they can improve, something they did well) or the Magic Question (“How do you think you did?”).
-
Pick the business result, name the few observable behaviors that would produce it, define what people must know and practice, and design the learning last. Kirkpatrick’s four levels (reaction, learning, behavior, results) link the pieces. Highspot’s four categories fit the same chain: Feedback (Level 1), Competency (Level 2), Consistency (Level 3), and Productivity (Level 4). Feedback is read alongside Competency, since how learning feels is an unreliable guide to whether it worked. The Metrics page defines each measure. For the rules on reading results honestly, see Metrics, section 4. Transfer is specific to training: if learning is strong but behavior doesn’t change, the problem is usually the surrounding conditions, such as managers not coaching it, tools not supporting it, or conflicting incentives. The fix is there, not more training. That’s where Coaching comes in.
The Kirkpatrick chain for each Case problem (tap to open)
| Case problem | Level 4: Result | Level 3: Behavior | Level 2: Learning | Level 1: Reaction |
|---|---|---|---|---|
| 1. Slow ramp | AE time to full quota falls from nine months toward six | Live discovery calls meet the standard by day 60 | Certification gates passed | New Hire Pulse and session surveys |
| 2. Inconsistent discovery | A higher win rate | Structured discovery, the economic buyer identified, and success criteria recorded in the CRM | Role-play scored on the Discovery Questioning Framework | Survey on relevance and confidence |
| 3. No CS health signal | A higher early-flag rate (at-risk accounts flagged 90+ days before renewal) and a healthier renewal rate | Health-check completed on schedule, with risks logged and discussed in reviews | Scored practice on sample accounts | Survey on relevance and confidence |
| 4. Messaging drift | Consistent messaging across calls and Marketing assets, with fewer customer-reported mismatches | Approved positioning used in live calls | Positioning role-play | Survey on relevance and confidence |
Certification: what “ready” means
Ready means demonstrated, not completed. Each track has three levels: a short knowledge check, a role-play scored on the track’s scorecard, and a real, recorded interaction scored on the same scorecard. For sales, live discovery calls begin in week 7 and are certified in week 8, and the platform walkthrough and pitch are certified in week 10. Someone below the standard gets targeted coaching and a retake. The full process is on the Onboarding page.
Training after onboarding
Every two weeks: a 20 to 30 minute drill with a role-play and a recall check
Monthly: a 45-minute workshop on one skill, such as stakeholder mapping or business reviews
Quarterly: a joint messaging session with Product Marketing
At each launch: a short readiness session and a one-page reference
The handoffs get joint sessions. AEs and CSMs practice the Purchase handoff together in week 7 of onboarding, then once a quarter in a monthly workshop. CSMs and account managers agree who says what in the expansion opening, so the customer hears one voice.
Worked example: the upfront contract session
A design for a session I’ve delivered live, written the way I’d write it for a company. About 30 minutes, for all three groups, with every pillar showing up. The concept comes from Sandler’s upfront contract. The wording and structure here are mine.
The 30-minute run of show (tap to open)
| Time | Step | What happens | Method |
|---|---|---|---|
| 0:00 | Open | The facilitator delivers an upfront contract for the session itself, without naming it. Participants experience one before anyone explains it. | Demonstrate |
| 0:02 | Pre-test | Before any teaching, participants answer in the chat: What is an upfront contract? What would one include? What goes wrong in a first meeting without one? Wrong answers are expected, and the facilitator says so. The facilitator calls on several people to read theirs aloud. | Generation, desirable difficulty |
| 0:05 | Reveal and compare | The facilitator shows the definition and the four parts: purpose, time, agenda, and outcome. Participants compare them with their own answers, then identify where each part appeared in the opening. | Elaboration |
| 0:09 | Why it matters | Participants name a time a meeting drifted or ended without clear next steps. Then the facilitator shares the typical consequences and checks them against the stories. | Elaboration |
| 0:12 | Worked example, then build | The facilitator walks through one example script. Participants then write their own for a real upcoming meeting: a discovery call (AE), a kickoff or business review (CSM), or an expansion conversation (account manager). | Generation |
| 0:20 | Mixed scenarios | Quick rewrites under changing conditions: a prospect who only has 15 minutes, a customer who wants to skip the agenda, a renewal call with a new stakeholder. Roles swap scenarios, so everyone sees how the four parts adapt. | Interleaving, desirable difficulty |
| 0:25 | Closing quiz | Closed notes. The same definition question from the pre-test, then the four parts from memory, then one short scenario. Immediate feedback on each. | Retrieval practice |
| 0:28 | Close | Each person finishes the sentence "On my next call, I will..." and gets the assignment. | Applied, not just known |
Builds on: Case and GTM Strategy (the lifecycle and the handoffs).
Feeds into: Onboarding (the four pillars applied to new hires), Coaching (competencies and the reinforcement model), and Metrics (the Kirkpatrick chain).
Real work behind this page: Upfront contract session (delivered live), shown here in its updated 30-minute form. Discovery Questioning Framework (real, adapted), the discovery method taught here. Opportunity Grading Agent (designed), which scores the practice role-plays. Smart Brevity Summary Generator (built in a past role, rebuilt as a Claude project), behind the "digestible content" part. Details on Real Work.
Sources for this page: PMA Sales Enablement Fundamentals and Masters; Highspot's Train and Coach Reps (the four pillars); Make It Stick; Kirkpatrick's four levels; Knowles's adult learning principles; ADKAR; Switch; Sandler and Challenger (the discovery method); Smart Brevity (Axios). Full list on Sources.