Train from the customer problem toward product language. Before learners explain the product, they should recognize who has a problem, what keeps it in place, what makes it urgent, and what outcome the product can support. Problem training gives salespeople a basis for questions that uncover problems; product description alone leaves them talking about what they sell.1 Treat each lesson as a rehearsal for a customer conversation. If the learner cannot turn a customer situation into a relevant question, the lesson is unfinished.
Prepare the training
Show the route before training starts. The brief should show how customer context becomes a problem conversation and how that conversation connects to the product.
A representative cannot be trained into a system that does not yet exist.2 Write a working brief that names the target company, target individual, business problem, cost of doing nothing, urgency signals, expected outcome, product use case, and differentiator. Use the same brief for teaching, practice, and review so the learner sees one path from account choice to conversation.
Define the target customer
Start with the customer's world. The learner needs enough context to recognize a situation that deserves attention and enough empathy to discuss it without sounding like a product catalogue.
Open onboarding with customer understanding. It gives a new hire the empathy needed for sales success.3 An ICP describes the ideal company and individuals to target.4 Build the profile around company characteristics, persona characteristics, responsibilities, daily work, concerns, problems, and how the product helps.5
Use real account patterns to make the profile concrete. Review inbound leads and current customers, then look back at what was happening before the account became an inbound lead.6 Ask: "Were there new hires? What tech were they using? What was happening internally?".7
Move on when the learner can describe the company situation, the persona's work, and the event that makes the problem worth discussing. If the description could apply to almost any account, keep narrowing it.
Teach the problem
Give the learner a problem to diagnose and explain. The business consequence should be clear enough to support a useful conversation. Feature lists do not replace that work.
Train them on the business problem the company solves, the cost of doing nothing, the signals that indicate urgency, and the outcomes customers can expect.8 They should know which problems they solve so they can ask questions that uncover them.9
Have the learner explain the problem in plain language, then write questions that would reveal it. Ask them to connect the answer to the consequence, the urgency signal, and the outcome. Move on when the questions sound like they belong to the customer's situation and the learner can explain why each question matters.
Connect the problem to the product
Teach product knowledge in response to a diagnosed problem. Keep the connection narrow enough that the learner has to choose what matters for the situation.
The manager should be able to learn and teach the ICP, key persona, competitors, and product differentiators.10 Product and positioning fundamentals should include use cases.11 Require the learner to know the solution's value proposition or proof points thoroughly.12
Give the learner a customer situation and ask for the relevant use case, product connection, differentiator, and proof point. Stop the exercise when they start listing everything the product can do. Move on when they can explain why this product connection fits the problem in front of them.
Turn knowledge into questions
Knowledge becomes useful when it changes what the learner asks. Practice moving from a known problem to a question that lets the customer confirm, reject, or refine the situation.
Build messaging around a specific audience with a specific problem.13 Give the learner an account pattern and a persona, then ask them to write an opening question, a follow-up about impact, and a question about urgency. Useful prompts include: What changed? Where does this show up in the team's work? What happens if it stays unresolved? What would a better outcome look like?
Listen for questions that uncover the trained problem. Move on when the learner can explain which answer would create relevance and which answer would tell them to leave the account alone.
Verify with behavior
Treat completion as something you can observe in a conversation. A lesson is complete when the learner can perform the behavior without leaning on a script or a topic list.
Make every checklist line something someone can watch happen, listen to, or read.14 Record what the learner actually says or writes. Check whether they can:
- Describe the target company and persona in concrete terms.
- State the business problem, the cost of leaving it alone, the urgency signal, and the expected outcome.
- Ask a question that uncovers the problem.
- Choose a relevant use case and explain its value proposition or proof point.
- Explain the differentiator that matters for that customer situation.
Keep objection handling downstream of audience fit. Objection handling requires knowing whether the representative is reaching the right people.15 If the learner cannot identify the right audience, return to the customer profile before rehearsing responses.
What not to do
Tie each check to something the learner can demonstrate.
- A covered topic does not show that a representative can perform it, and an attendance checklist tells a manager nothing when it matters.16
- An item that cannot be verified by watching, listening, or reading does not belong on a checklist.17
- Do not coach objection handling before you know whether the representative is reaching the right people.15