# Describe how you’d train a sales team on a new product or major feature update. What format works best?
> How to design launch training so reps can pitch the feature afterward, which format to choose and why, a worked example, and how to tell if it worked.

Source: https://mokk.ai/pmm-questions/content-campaigns/train-sales-on-new-feature (updated 2026-09-22)
Markdown: https://mokk.ai/pmm-questions/content-campaigns/train-sales-on-new-feature.md

For a major feature, a short live session built around practice works best, backed by a brief recorded demo and a one-page cheat sheet. Open with the customer problem, give most of the time to reps pitching aloud in pairs, and have managers review a few recorded pitches before launch. Train a week or two ahead, then check at thirty days whether the feature comes up on calls and changes deals.

## What a sales training question is scoring

Most people who have sat through a feature training remember the slides and none of the pitch. Interviewers have too. The question asks for a design built around what a rep can do when the session ends. The second half, what format works best, asks you to commit to one.

Communication is half the score here, next to cross-functional influence. The rubric rewards adjusting detail to the audience. Reps are a specific audience. They learn by saying the pitch out loud and hearing how a buyer reacts, far more than by watching a demo.

## Match the training format to the size of the change

Sales training formats by size of product change
| Size of change | Format | Why it fits |
| --- | --- | --- |
| Small update to an existing feature | A short written note and a recorded demo of two or three minutes | Reps need to know it exists and have one line to say |
| Major new feature for current buyers | A live session of about forty minutes, mostly practice, plus a recording and a one-page cheat sheet | Reps need to pitch it and handle the first objections |
| New product or new buyer | A program over several weeks, with practice, call reviews, and manager sign-off | Reps need new discovery skills as well as a pitch |

Commit to one in the interview and say what would change it. Hedging across all three sounds thorough and gives the interviewer nothing to push on.

## A training plan for a major feature launch

1. **Two weeks out, a live session.** Ten minutes on the customer problem, ten on a demo, and twenty with reps pitching in pairs.
2. **The same week, assets.** A three-minute recorded demo and a one-page cheat sheet with the pitch, two objections, and a proof point.
3. **Before launch, a skill check.** Each rep records a short pitch, and managers review a few and send feedback.
4. **Thirty days after launch, data.** How often the feature comes up on calls, how often it attaches to deals, and whether reps who practiced do better.

## A worked answer from a spend management company

**Strong answer (invented example)** "What matters is what a rep can do when the session ends, so I’d build everything around reps pitching out loud. Picture a spend management company launching bill pay for its mid-size customers. Two weeks before launch I’d run a forty-minute live session. Ten minutes on the problem, which is finance teams paying vendors from three different tools. Ten on a demo. Twenty with reps in pairs, one pitching and one playing a skeptical controller who asks about approval rules and fraud. I’d walk the room and listen. Afterward there’s a three-minute recording and a one-page sheet for anyone who missed it or forgets. Before launch, each rep records a ninety-second pitch, and managers review five and send notes. At thirty days I’d check how often bill pay comes up on calls and how often it attaches to new deals. I’d also compare reps who practiced with reps who skipped, knowing the best reps tend to show up to everything, so I wouldn’t read too much into that gap."

The last sentence is the analytical move that lifts the answer. It measures the training and admits the limit of the measurement. The fraud objection is also well chosen, since a controller who is about to let software move company money will raise it on the first real call, and a rep who has answered it once in practice sounds far calmer.

## Trade-offs in launch training

- **Live against recorded.** Live sessions allow practice and feedback, and recorded ones reach every time zone. For a major feature, run the live session twice and record one.
- **Depth against time.** Every extra slide costs practice time. Cut the architecture detail and put it in the sales engineers’ notes.
- **Certification against speed.** A formal sign-off raises the bar and slows the rollout. Use it for a new product and skip it for an update.
- **Training on an unfinished feature.** Early training gives reps time to practice, but the demo may change. Train on the problem and the pitch, and send a short update when the product settles.

## Where launch training answers lose the room

**A complete deck that trains nobody (invented example)** "I’d build a comprehensive training deck covering the problem, the feature, how it works, pricing, competitive positioning, and FAQs. I’d present it live, record it for anyone who missed it, and add a short quiz in our learning platform so every rep is certified before launch."

This is organized and complete, and it will produce reps who pass a quiz. Passing a quiz and pitching to a controller are different skills. The answer never has a rep say the pitch aloud, and it stops measuring at certification. Swap the quiz for a recorded pitch that a manager reviews, then check calls a month later.

## Follow-ups on sales launch training

Follow-up questions about training sales on a launch
| Follow-up | The worry underneath | A strong reply |
| --- | --- | --- |
| How would you train a team spread across time zones? | Practical planning | Run the live session twice, pair reps within each region, and keep the recorded pitch review the same everywhere |
| What if reps skip the live session? | Reinforcement | The recorded pitch is required for everyone, so skipping the session doesn’t skip the practice. Managers follow up. |
| How do you train on a feature that isn’t finished? | Handling uncertainty | Train on the problem and the pitch, flag what may change, and send a short update when it settles |
| How do you know the training worked? | Measurement | Mentions on calls, attach rate on new deals, and manager reviews of pitches, read with care about who chose to practice |

## More questions in this category

- [Sales feedback into strategy](https://mokk.ai/pmm-questions/content-campaigns/sales-feedback-loop)
- [Saving a deal at risk](https://mokk.ai/pmm-questions/content-campaigns/helped-sales-win-at-risk-deal)
- [Enablement by sales role](https://mokk.ai/pmm-questions/content-campaigns/enablement-by-sales-role)
- [Enablement for an upmarket move](https://mokk.ai/pmm-questions/content-campaigns/enablement-for-upmarket-move)
- [All content and campaigns questions](https://mokk.ai/pmm-questions/content-campaigns)

## Frequently asked questions

**Should I recommend one specific training format?** Yes. Give one, defend it, and say what would change it, such as team size or how big the update is. A clear recommendation gives the interviewer something to push on, which is where the conversation gets useful.

**When should training happen relative to launch?** A week or two before, so reps can practice and ask questions. Training on launch day means the first real pitch happens in front of a buyer.

## Practice

**Answer it out loud.** A Mokk session asks this question, follows up on your answer, and scores it on five competencies.