Top 10 questions to identify gaps in a rep's product knowledge in 2027

The outcome you should expect

The point of these ten questions is not to grade recall — it is to surface *where* knowledge fails to convert into a moment in a live deal. A trivia quiz tells you a rep can recite the spec sheet; behavioral questions tell you whether they can deploy that spec when a prospect pushes back. The two are only loosely correlated, which is why memorization-heavy onboarding so often produces reps who ace the certification and then freeze on the third discovery call.

When you run this set correctly, you should expect three concrete outputs within the first cycle. First, a ranked gap map per rep — not a single score, but a short list of specific weak spots: "strong on positioning, thin on technical depth, avoids saying 'I don't know.'" Second, a team-level pattern. If seven of ten reps cite the same customer misunderstanding, you have not found a rep problem — you have found a product-marketing or messaging problem, and the fix belongs to enablement or the RevOps content owner, not to individual coaching. Third, a remediation queue you can act on in two weeks, not next quarter.

Expect the questions to feel uncomfortable the first time. Reps who have coasted on a rehearsed pitch will give vague, non-specific answers ("it went fine, they liked the demo"), and that vagueness *is* the signal. The reps who thrive will volunteer exact moments — the sentence they used, the objection they reframed, the feature they wished they could point to. Over three to four cycles the vagueness should shrink measurably as reps learn that "walk me through the exact moment" is the standard, and they start paying attention to their own decision points in real time. That self-monitoring is the real, durable outcome — better than any single answer you collect.

What drives that outcome

Four mechanics make behavioral product-knowledge questions work where quizzes fail. The first is retrieval under context: asking "where did you pivot from your standard pitch on your last discovery call?" forces the rep to reconstruct a real situation, which is far harder to fake than "what does feature X do?" A rep who cannot name a single pivot in a complex B2B deal almost certainly ran a linear, script-bound call — a strong proxy for shallow use-case understanding.

The second driver is verifiability. Every question here can be cross-checked against evidence you already collect: call-recording platforms like Gong or Chorus for the actual conversation, your CRM pipeline for stage and outcome, and product-usage tools like Pendo or Mixpanel for what customers actually do with the features the rep describes. When a rep claims they explained role-based access controls mapping to an audit requirement, you can pull the recording and confirm. This closes the gap between what reps *say* they know and what they *demonstrated*.

The third is graded difficulty by seniority. The same ten questions probe different depths depending on tenure. For a new hire, "explain the product to a ten-year-old" tests whether onboarding produced clarity or jargon. For a senior enterprise rep on a six-figure deal, "what's the most technical question you've ever been asked and how did you answer?" tests whether they can hold a conversation with an engineering buyer. You do not need separate question banks — you calibrate the expected answer.

The fourth driver is psychological safety. These questions only produce honest data if reps believe the exercise is developmental, not punitive. Frame it as "let's find where the product is hard to sell," acknowledge what the rep does well first, and the "I don't know" question stops being a trap and becomes a healthy admission you can coach.

Benchmarks and realistic ranges

Treat the following as planning ranges to calibrate a program, not as universal laws — every team's baseline differs by product complexity and segment. The value is in the *relative* movement you track, not the absolute number.

Cadence. Run the full ten-question diagnostic monthly, not weekly. A monthly rhythm roughly matches most B2B sales cycles and gives you time to act between checks; run it too often and reps rehearse the answers, which destroys the signal. A practical split: use two or three lightweight questions (the "what surprised you this week?" and "your last I-don't-know") in weekly one-on-ones or stand-ups, and reserve the deeper set — competitor-feature envy, technical-depth, feature-to-remove — for the monthly review.

Scoring. A simple 1-to-5 scale per question works better than a pass/fail. Anchor the endpoints: 1 = "I'd check the docs," 5 = "I explained it cold, with a specific example and a metric." Score across the ten questions and you get a profile, not a grade. In practice a healthy tenured rep lands in the 3.5-to-4.5 band; consistent 2s in one category (say, technical depth) is your coaching target. Don't over-index on a single perfect answer — look for the low outliers.

Team dispersion. Watch the spread, not just the mean. If your team average looks fine but three reps sit a full point below the rest on competitive positioning, you have a targeted training need, not a systemic one. Conversely, if *everyone* is weak on the same question, escalate it to enablement — that is a content or messaging gap.

Remediation window. Set a two-week follow-up on every identified gap, not a quarterly one. Gaps that get a same-cycle intervention — assigned documentation, a shadowed call with a top performer, a focused role-play — close far faster than gaps parked on a quarterly plan, because the deal context is still fresh in the rep's memory.

Scale. The framework holds from a team of ten to several hundred reps, but the *instrumentation* changes. Below roughly twenty-five reps a manager can run these questions manually in one-on-ones. Above that, you need a conversation-intelligence tool to sample recordings and a shared objection/answer repository (Guru, Notion, or your enablement CMS) so scoring stays consistent across managers. Standardize the rubric before you scale, or every manager will score differently and your data becomes noise.

Risks, edge cases, and failure modes

The biggest failure mode is turning a diagnostic into an interrogation. If reps feel the questions are a test they can fail, they will give you rehearsed, safe answers and morale drops. The fix is framing: open with a genuine strength, state that the goal is finding where the *product* is hard to sell, and never tie a single diagnostic answer to compensation. The moment these questions feed a performance-improvement plan without context, honest answers evaporate.

A second trap is mistaking a messaging problem for a rep problem. When many reps independently cite the same customer misunderstanding or wish for the same competitor feature, the gap is upstream — in your positioning, battle cards, or documentation. Coaching individual reps on a systemic issue wastes everyone's time and frustrates good performers who correctly sense the real problem is the material, not them.

Third, perfect answers don't guarantee quota. A rep can score 5s across the board and still miss because the bottleneck is objection *handling*, pipeline hygiene, or discovery — not product knowledge at all. Use this set as one input, then triangulate with call recordings and deal velocity before concluding that knowledge is the constraint. Firing a knowledgeable rep for a pipeline problem is an expensive misdiagnosis.

Fourth, question-market fit matters. For a single-feature, low-complexity product, "walk me through where you pivoted from your standard pitch" can feel forced — there may be little to pivot on. Substitute the "what surprised you this week?" and "most common misunderstanding" questions, which work regardless of complexity. Conversely, for a deeply technical product, "explain it to a ten-year-old" may reward harmful oversimplification; ask "explain it to a CTO in sixty seconds" instead. Match the question to the product and the buyer.

Fifth, overconfidence hides gaps. The rep who never admits a competitor strength and never says "I don't know" is not necessarily your strongest — they may be the one most likely to fabricate an answer on a live call and lose the deal at technical validation. The "which competitor feature do you wish we had?" and "your last I-don't-know" questions exist specifically to surface this, so weight them heavily for your most confident people and cross-check against win/loss data.

Finally, watch for rehearsal drift over time. Because the question set is fixed, reps eventually learn the pattern. Rotate the specific scenarios (different industries for the transfer question, different deal stages for the objection question) and lean on the "walk me through the *exact* moment" follow-up, which is much harder to pre-script than the top-level question.

A practical rollout plan

Roll this out in four stages rather than launching all ten questions to every rep at once. A staged rollout lets you calibrate scoring, build the supporting content, and win rep trust before the program carries any weight.

Stage one — calibrate (weeks 1-2). Pick three to five reps across tenure levels and run the full question set yourself. The goal here is not to grade anyone; it is to anchor your 1-to-5 scale with real answers so that when you scale, every manager scores consistently. Write down what a 2, a 3, and a 5 actually sound like for each question. Simultaneously, stand up the supporting infrastructure: a shared repository of common objections with product-based rebuttals, and a technical-FAQ with verified answers for the enterprise questions.

Stage two — pilot with feedback (weeks 3-6). Run the diagnostic with one full team, explicitly framed as developmental. Collect the gap maps, but also collect reps' reactions — if the exercise feels punitive, fix the framing before you scale. Start cross-checking a sample of answers against call recordings so reps learn that claims are verifiable and that specificity is the standard.

Stage three — instrument and standardize (weeks 7-10). Codify the rubric, train other managers on it, and wire the diagnostic into your existing rhythm — deep questions in the monthly review, lightweight ones in weekly one-on-ones. Connect the outputs to your enablement content so a flagged gap automatically points to the right documentation or top-performer shadow.

Stage four — operate and iterate (ongoing). Run monthly, track per-rep profiles and team-level patterns over time, and rotate scenarios to prevent rehearsal. Review team-wide gaps with enablement quarterly to catch messaging problems. Retire questions that stop discriminating and add new ones as the product evolves.

Related questions

Which single question should a manager start with?

Start with "walk me through your last discovery call — where did you pivot from your standard pitch?" It has the highest diagnostic precision because it forces recall of a real, contextual moment and is easy to verify against a call recording. If the rep cannot name any pivot, you have found a shallow-knowledge signal in one question.

How is this different from a product certification quiz?

A certification tests whether a rep can recite specs in a low-pressure, isolated setting. These questions test whether the rep can *apply* product knowledge inside a live customer conversation and adapt it to specific pain points. The two correlate weakly, which is why certified reps still freeze on hard calls.

Can the same questions work for new hires and veterans?

Yes — you calibrate the expected answer rather than swapping questions. For a new hire, "explain the product to a ten-year-old" checks onboarding clarity. For a senior rep, "the most technical question you've been asked" checks enterprise depth. The identical prompt reveals foundational gaps in one rep and strategic blind spots in another.

What if many reps give the same weak answer?

That is a systemic signal, not an individual one. When reps independently cite the same customer misunderstanding or the same envied competitor feature, the gap lives in your positioning, battle cards, or documentation. Route it to enablement or product marketing rather than coaching each rep separately.

How do I turn a gap into action without hurting morale?

Frame the finding as development, acknowledge a genuine strength first, then assign a specific remedy — targeted documentation, a shadowed call, or a focused role-play — with a two-week follow-up. Reps who feel supported stay honest about weaknesses; reps who feel tested start rehearsing safe answers.

FAQ

How often should I run these questions to check a rep's product knowledge?

Run the full set monthly as a diagnostic, not a daily quiz. A monthly cadence roughly matches most B2B sales cycles and gives you time to act on findings, while asking too frequently produces rehearsed answers. Sprinkle two or three lightweight questions into weekly one-on-ones between the deeper monthly checks.

Do I need special software to verify the answers?

No. Conversation-intelligence tools make verification faster at scale, but manual call reviews, role-plays, and asking for specific recent-deal examples work fine for smaller teams. The key is looking for concrete details — the exact sentence, the specific objection, the named metric — rather than accepting generic statements at face value.

What if a rep gives perfect answers but still misses quota?

Perfect knowledge does not guarantee execution. The bottleneck may be objection handling, discovery, or pipeline management rather than product knowledge. Use these questions as one data point, then cross-reference call recordings and deal velocity to identify the real constraint before you conclude anything about the rep's knowledge.

Can these questions backfire and hurt rep morale?

They can if used punitively. Frame the conversation as a development tool, open by acknowledging what the rep does well, and never tie a single answer directly to compensation. Reps who feel supported are far more likely to admit "I don't know," which is exactly the honest signal you need to find real gaps.

How do I keep reps from memorizing the questions over time?

Rotate the specific scenarios — different industries for the transfer question, different deal stages for the objection question — and always follow up with "walk me through the exact moment." The top-level question is easy to pre-script, but a demand for the precise sentence and context in a real call is much harder to fake.

Which questions best expose an overconfident rep?

The two that require admitting limits: "which competitor feature do you wish we had, and why?" and "walk me through your last 'I don't know.'" A rep who cannot answer either may be fabricating answers on live calls. Weight these heavily for your most confident people and cross-check against win/loss data.

Sources

• Gartner — Sales Enablement Insights
• Winning by Design — Resources
• Gong Labs — Sales Research and Call Analysis
• Salesforce — State of Sales Research
• Harvard Business Review — Sales
• Sales Enablement Collective
• SiriusDecisions / Forrester — Sales Enablement

Related on PULSE

• [Top 10 questions to measure a rep's product knowledge depth](/knowledge/cg0830)
• [How do you coach product knowledge to a brand-new salesperson?](/knowledge/cg0016)
• [Top 10 discovery questions to uncover a rep's pipeline gaps](/knowledge/cg0907)
• [How do you create coaching playbooks for common rep gaps?](/knowledge/cg0197)
• [What question assesses a new rep's grasp of your top three differentiators?](/knowledge/cg0856)
• [How do you coach a sales team through a major change like a new product?](/knowledge/cg0199)