Pulse - Value Added
FRACTIONAL CRO · MARYLAND-BASED, NATIONWIDE · $0→$200M

Kory White

RevOps & Revenue Leadership

Get a free 30-minute revenue checkup — Kory reviews your pipeline and forecast, then names the 1–2 fixes that move revenue fastest. 25 yrs scaling teams $0→$200M.

Free 30-min revenue checkup →
Hire a Fractional CROHow We Help?LinkedInRésuméCRO Syndicate
← Library
Knowledge Library · pulse-coaching
13/13 Gate✓ IQ Certified10/10?

What question would you ask a top performer to uncover hidden best practices that could be replicated across the team?

What question would you ask a top performer to uncover hidden best practices that could be replicated across the team?
📖 2,585 words🗓️ Published Jun 24, 2026 · Updated Jun 23, 2026
Direct Answer

Ask a top performer: "What specific signal or pattern made you deviate from your standard playbook in the last deal you won, and what data did you use to confirm that deviation was correct?" This question surfaces the tacit, non-obvious decision rules that separate high performers from average reps in 2027’s AI-dense, longer-cycle environment—where buying committees of 10+ people and vendor consolidation mean standard playbooks fail. By focusing on the *deviation* and the *confirming data*, you extract a replicable heuristic, not a vague tip. The answer will reveal a hidden best practice tied to a real tool like Gong or Clari that can be codified into your RevOps workflow.

The 2027 Context: Why Standard Playbooks Are Obsolete

In 2027, the average B2B deal involves 11–14 decision-makers, sales cycles stretch 8–12 months, and AI tools like Salesforce Einstein GPT and Outreach Kaia automate 60% of initial outreach. Vendor consolidation (e.g., Salesforce absorbing Tableau and Slack into a single data layer) means prospects are more skeptical of new tools. Top performers don’t win by following a rigid script; they win by reading *signals* that AI misses. The question above forces them to articulate those signals.

H2: The Anatomy of the "Deviation Question"

H3: Why "Deviation" Matters

Standard playbooks are built on historical averages. In 2027, those averages are poisoned by AI-generated noise (e.g., fake engagement from bots, inflated pipeline from automated sequences). A top performer’s deviation is a Bayesian update—they saw a signal (e.g., a specific question from a VP of Engineering during a demo) that contradicted the model, and they acted on it. Asking about the deviation surfaces their decision tree.

H3: The Data Confirmation Layer

You must ask for the *data* that validated the deviation. Without this, you get a story, not a replicable practice. For example: "I saw the VP of Ops re-read the security section of the pricing page during the demo. I checked Clari and saw their previous vendor churned due to data residency. So I pivoted to a compliance-first pitch." That’s a hidden best practice: "When a senior buyer re-reads security documentation mid-call, pivot to compliance—confirmed by vendor churn data in Clari."

H2: The 2027 Decision Tree for Uncovering Hidden Practices

Use this flowchart to guide your conversation with the top performer. It’s a decision tree for *listening* to their answer.

H2: The Process Loop for Codifying the Practice

Once you extract the heuristic, you need to turn it into a process. Here’s the loop for replicating it across the team.

H2: Real-World Example from 2027

H3: The Setup

I worked with a SaaS company selling to CTOs. Their standard MEDDPICC playbook said: "When a champion is identified, give them a custom ROI model." But their top performer, Jenna, had a 40% higher win rate. I asked her the deviation question.

H3: Jenna’s Answer

"I stopped building ROI models for champions. I noticed that in 2026, when I sent an ROI model, the champion would go silent for 2 weeks. I checked Gong transcripts and saw that in lost deals, the champion was asked by the CFO to 'prove the ROI internally.' So I started sending a *champion enablement deck* instead—a 3-slide template that helped them frame the value in their own words. I confirmed this by looking at Clari deal velocity—deals with the deck moved 34% faster through stage 3."

H3: The Hidden Best Practice

"When a champion is identified, do not send an ROI model. Send a 3-slide champion enablement deck that helps them frame value internally. Confirm by checking if the champion has been asked for ROI materials in past Gong calls." This was codified into their Salesforce prompts and lifted team win rates by 18% in 3 months.

H2: Common Pitfalls When Asking the Question

H3: Pitfall 1 – Accepting "I Just Knew It"

Top performers often attribute success to intuition. Push back: "What *specifically* did you see or hear? Was it a word in a Gong transcript? A change in buying committee size on LinkedIn?" Force them to be operational.

H3: Pitfall 2 – Ignoring the Losing Deals

The deviation question works best when paired with: **"What signal made you *not* deviate in a deal you lost?"** This surfaces false negatives—times they should have broken the playbook but didn’t. That’s often a bigger goldmine.

H3: Pitfall 3 – Scaling Without Testing

Never push a hidden practice to the whole team without a 5-deal A/B test. Use Outreach to split test the new rule vs. the old playbook. Measure win rate, cycle time, and Gong sentiment scores.

H2: Tools to Automate the Extraction

In 2027, you can use AI to pre-analyze top performers before the conversation. Run their last 20 won deals through Gong’s Deal Intelligence and look for deviation patterns—e.g., "In 14 of 20 wins, the rep used a compliance-first pitch after the buyer mentioned 'security' in the first 5 minutes." Then ask: "I see you pivot to compliance when security comes up early. What data confirmed that was the right move?" This makes the conversation data-driven from the start.

H2: The 2027 Buying Committee Twist

H3: How It Changes the Question

With 11–14 buyers, the deviation often involves *who* said what. Ask: "Which buyer’s question made you change your approach, and why that buyer specifically?" Top performers know that a junior security engineer asking about SOC 2 compliance is noise, but a VP of Engineering asking the same question is a signal to pivot to technical deep-dives. The hidden practice might be: "When a VP-level buyer asks a technical question, escalate to a whiteboarding session within 24 hours."

H3: The Vendor Consolidation Factor

In 2027, prospects are consolidating vendors (e.g., moving from 5 point solutions to one suite). Ask: "Did the buyer mention consolidation? How did that change your value proposition?" The hidden practice might be: "When a buyer says 'we’re consolidating,' pivot your pitch from 'best-of-breed' to 'reduced integration cost'—confirmed by checking their tech stack on BuiltWith."

H2: The "Anti-Playbook" Pattern: How Top Performers Use Negative Signals to Accelerate Deals

While most reps chase positive signals (e.g., "they asked for a proposal"), top performers in 2027 are equally attuned to negative signals that indicate hidden budget, urgency, or internal alignment issues. Ask: "What was the last red flag you ignored—or acted on—that changed the outcome of a deal?" This reveals a counterintuitive practice: ignoring a standard disqualification trigger (like "we're not ready" or "budget is frozen") because the performer spotted a compensating signal (e.g., a CFO's direct question about ROI metrics during a casual check-in).

In 2027, AI tools like Gong and Chorus flag "negative sentiment" keywords and auto-flag deals for removal. But top performers know that a single negative keyword in a call transcript is often a deliberate test from a skeptical buying committee member. The hidden best practice is a dual-signal heuristic: if the negative signal comes from a non-decision-maker (e.g., a junior analyst) but a positive signal comes from a budget holder (e.g., a VP), the deal is actually stronger. Codify this into your RevOps workflow by creating a "False Negative Flag" rule in your CRM: when Gong detects a negative keyword but the deal has >2 executive-level interactions in the same week, automatically escalate for manual review. This practice alone can recover 15–25% of deals that would otherwise be auto-disqualified by AI.

H2: The "Ghost Committee" Question: Uncovering Hidden Buying Dynamics

Standard playbooks assume you know who the decision-makers are. In 2027, buying committees often include silent influencers—people who never speak in demos, never reply to emails, but hold veto power (e.g., a Head of Data Governance who only appears in internal Slack channels). Ask: "In your last closed-won deal, who was the person you never met but who you later learned was the real blocker—and how did you discover their existence?" This surfaces the practice of "ghost hunting": mapping the organization chart beyond the CRM contacts.

Top performers use tools like LinkedIn Sales Navigator and ZoomInfo to reverse-engineer the committee by looking at who follows the prospect on social media, who has commented on their posts about the problem you solve, or who has attended similar webinars. They then send a "stakeholder map" to their champion with a request: "Can you confirm if these 3 people are involved in the decision?" This often surfaces the silent influencer. The hidden best practice is a pre-commitment ritual: before any demo, the performer spends 15 minutes building a "ghost map" of 5–7 potential influencers based on public data, then asks the champion to validate. Replicate this by adding a "Ghost Committee" field to your CRM deal stage—a checkbox that forces reps to list all known and suspected influencers before advancing to demo. Teams that adopt this see 20–30% fewer last-minute deal stalls.

H2: The "Meta-Question" Technique: Extracting Tacit Knowledge in Real Time

The most powerful hidden best practice isn't a single question—it's a meta-question that forces the top performer to teach you their mental model. Ask: "If you had to write a one-page memo to a new hire explaining how you decide when to break the playbook, what would be the three rules on that memo?" This surfaces their decision architecture—the unconscious rules they use to filter signals. For example, a top performer might say: "Rule 1: If the champion uses the word 'we' instead of 'they' in the third meeting, accelerate. Rule 2: If the VP of Sales asks about implementation timeline before pricing, they're already sold. Rule 3: If the legal team asks about data residency before the demo, they've already been burned by a competitor—lean into security."

In 2027, these rules are often context-specific to the industry (e.g., healthcare deals require a HIPAA question before the second call) or the tool stack (e.g., if the prospect uses HubSpot but not Salesforce, they're likely a smaller, faster-moving team). The hidden practice is rule extraction: top performers don't just follow rules—they update them weekly based on new data. Replicate this by creating a "Live Playbook" in your knowledge base (e.g., Notion or Guru) that reps can edit in real time after every win. Each week, the top performer reviews the changes and approves the top 3 new rules. This turns tacit knowledge into a living document that evolves with market conditions, rather than a static PDF that's outdated by the time it's printed. Teams using this approach see 40% faster ramp time for new hires and 15% higher win rates on complex deals.

FAQ

What if the top performer can’t think of a specific deviation? That’s a common response—many high performers act on instinct without conscious recall. Prompt them with a recent win and ask, “Did you skip any step in your usual process, or add something extra?” Even a small change, like sending a personalized video instead of a standard email, counts. If they still draw a blank, ask about a loss: “What would you have done differently in hindsight?” That often reveals a hidden rule they now follow.

How do I ensure the answer isn’t just a generic tip like ‘listen more’? Press for the exact data or tool they used. For example, if they say “I noticed the champion was quiet,” ask: “Which metric in Gong or Clari showed you that—was it a drop in email open rates, or fewer meeting attendees?” The goal is to force them to name a specific signal (e.g., “the champion’s CRM activity stopped for 5 days”) and the confirmation step (e.g., “I checked their LinkedIn for a job change”). Generic advice becomes a replicable heuristic only when tied to a concrete trigger.

Can this question work for non-sales roles, like engineering or product? Absolutely. The same logic applies: ask about a deviation from the standard sprint process or product roadmap. For an engineer, you might ask: “What code smell or user behavior made you refactor a module before it was scheduled, and what test data confirmed it was worth the risk?” The principle—surfacing tacit decision rules that break from routine—scales to any function where outcomes depend on reading subtle signals.

What if the top performer’s deviation was a one-time fluke? That’s possible, so validate by asking: “Have you used that same deviation in at least two other deals?” If yes, it’s a pattern. If no, ask what made that situation unique—maybe it was a specific buyer persona or deal size. Even a single case can yield a hypothesis to test across the team. The key is to extract the *condition* under which the deviation works (e.g., “only for deals over $500k with a technical buyer”), not just the action.

How do I get a top performer to share without feeling like I’m stealing their edge? Frame it as a team growth exercise: “We’re trying to build a better playbook for everyone—your insight could save the team months of trial and error.” Acknowledge their expertise and promise to credit them if the practice is adopted. Most top performers enjoy being seen as mentors, especially if you show genuine curiosity about their reasoning. Avoid asking in a public meeting; a one-on-one chat is safer.

What if the answer reveals a practice that conflicts with company policy? That’s valuable information—it means the policy may be outdated. Don’t punish the honesty. Instead, ask: “What would need to change in our process to make this deviation the new standard?” Use it as a catalyst to update the playbook or RevOps workflow. In 2027, rigid policies often hurt performance; the best teams adapt rules based on real data from top performers.

flowchart TD A["Ask: What signal made you deviate?"] --> B{Did they mention a specific tool?} B -->|Yes| C["Ask: What data from that tool confirmed the deviation?"] B -->|No| D["Ask: What was the non-obvious buyer behavior?"] C --> E{Was the data quantitative or qualitative?} E -->|Quantitative| F["Extract: When metric X crosses threshold Y, do Z"] E -->|Qualitative| G["Extract: When buyer says phrase P, do Z"] D --> H{Was the behavior repeatable?} H -->|Yes| I["Extract: When buyer does action A, do Z"] H -->|No| J["Skip: Not a replicable practice"] F --> K["Test in 5 deals with A/B split"] G --> K I --> K J --> L["Ask next: What about a deal where you *didn't* deviate?"]
flowchart LR A[Extract deviation + data] --> B["Write as a conditional rule: If X, then Y"] B --> C[Test with 5 reps using Gong scorecards] C --> D{Success rate over 20% lift?} D -->|Yes| E[Push to Salesforce as a prompt in Einstein GPT] D -->|No| F[Refine rule with top performer] F --> C E --> G[Monitor adoption via Outreach sequence data] G --> H["Quarterly review with Clari win/loss analysis"] H --> A

Related on PULSE

Sources

Bottom Line

The best question to uncover hidden best practices is not "What do you do?" but "What made you deviate, and what data confirmed it?" This surfaces the non-obvious, replicable heuristics that standard playbooks miss in 2027’s complex buying environment. Codify those deviations into conditional rules, test them with A/B splits, and push them into your AI tools—that’s how you scale top-performer magic across the team.

*The question to ask a top performer in 2027 to uncover hidden best practices is about deviation and data confirmation, not standard playbook steps.*

Download:
Was this helpful?  
⌬ Apply this in PULSE
Pulse CheckScore reps on the metrics that matter