Skip to content
andydataguy
Wiki Corpus

Sales Enablement. Inspect a rep's practice work before assigning an independent sales task.

OPERATIONAL SYSTEMS · Reading guide~12 min read · 2,645 words

I worked with agency founders who struggled to reproduce their own quality through a team. They still had to close deals, help deliver the work and deal with whatever broke. My work included building sales procedures and reviewing recorded sales calls, then using those recordings to identify improvements and create training materials.

I'd start sales enablement by connecting a recorded call to work the new rep can demonstrate. A new hire can watch a senior rep diagnose a prospect's problem and still struggle to write a useful deal summary afterward. The manager needs to see whether the new rep can identify the problem, explain the evidence and propose an appropriate next step.

A curriculum gives the rep a way to learn and practice that work. A playbook supplies the team's current rules. A call library shows those rules applied in conversations, including the conversations that ended without a sale. The manager reviews what the rep does and uses the gaps to decide what happens next.

WHEN THE REP IS PERFORMING 30 90 DAY 30
Both curves reach the same height. The grey one takes ninety days and calls it ramp. The orange one takes thirty because the ramp was engineered instead of waited out, which buys back two months of a rep's quota every hire.

The ramp illustration uses day thirty and day ninety to show the intended difference. Treat those curves as an illustration, not measured onboarding results. A team can choose a review date, but permission to handle an opportunity independently needs evidence of ability. The calendar alone can't provide it.

A curriculum has to change what a rep does

Shadowing gives a new rep access to someone's experience. Its usefulness depends on which calls happen to occur and how much the senior rep explains. A call may show a polished proposal without showing the discovery that made it appropriate. Another may end with an objection the new hire hasn't heard before. The learner gets pieces of the job and has to work out how they fit.

The manager can make that learning more deliberate. Name the task before selecting the material. A rep learning discovery needs to recognize an unresolved customer problem, ask for evidence and decide whether the business can help. Watching a call becomes useful when the rep can explain those decisions and then attempt them.

A hand tips a watering can over a row of differently shaped clay pots. Wide pots catch plenty of the spray and narrow ones only a few drops, so the seedlings inside grow to very different heights.
Conceptual illustration of uneven watering. Select calls for the task being taught, then review what the rep can do.

Coach the work the rep will perform

My work on a Facebook ads coaching program used that kind of applied feedback. I helped put together the course, took sales calls and served as head coach in the community. It was a team effort. During group coaching, I worked from participants' businesses, challenges and ad accounts so the feedback addressed what they were doing. The program also offered implementation for people who needed that level of support.

A sales manager can use that same connection between instruction and application. A recorded explanation gives everyone access to the principle. A practice task shows how someone interprets it. Reviewing the task exposes the point where that interpretation needs correcting. Another explanation of the whole course may leave the same gap untouched.

Teach an offer the team can deliver

The business has to deliver what sales promised. A rep has to understand what the business can deliver before promising it to a customer. Coaching someone to close an unsuitable deal can create a delivery problem for the rest of the team.

An unclear offer needs attention before it becomes a curriculum. Establish which customers the team can help, what the engagement includes and where the limits are. The new hire then has a real operating model to learn. Senior reps can coach against the same model instead of answering each question from memory, and the manager can tell whether a difficulty belongs to the learner or to the process being taught.

Advance a rep when the work meets the standard

A competency names something a rep can do without someone supplying an answer. Product knowledge is part of it, but being able to recite the product's features doesn't establish that a rep can diagnose a customer's situation. Define the action and the evidence together.

Teach the prerequisites in the order the job needs them

Discovery requires enough product knowledge to ask useful questions and recognize a bad fit. A proposal depends on the discovery: the rep needs a diagnosed problem, an agreed outcome and a scope the team can deliver. Negotiation adds decisions about terms and authority. The rep needs to know which commitments they can make and which require approval.

Those dependencies give the curriculum its order. A manager who finds a weak proposal should be able to look back at the discovery summary before prescribing more proposal training. Missing information at discovery can't be repaired by making the document more persuasive.

Stone steps rise to the right, each closed by a small gate. A person on the second step places a finished piece into a slot and that gate swings open with warm light, while the higher gates stay shut. Off to the left, a grey conveyor carries another person along at a fixed pace.
Product knowledge comes before discovery calls, discovery before proposals, and negotiation last. A rep climbs a step by passing a demonstration, like a recorded mock call or a reviewed deal summary, instead of waiting for the calendar.

Make the demonstration specific enough to review

Take discovery as a proposed training exercise. Give the rep an approved practice scenario, have them run a mock conversation and ask for a written deal summary. The summary should distinguish what the prospect said from what the rep inferred. It should also name unresolved questions and explain the next step.

The manager can organize that exercise around the decisions they need to assess. Adapt these example criteria to the team's offer.

Work to demonstrate Evidence to inspect Review question
Diagnose the problem Recording and deal summary Did the rep establish the problem with evidence?
Assess fit Qualification notes Can this business deliver the outcome being discussed?
Choose the next step Written recommendation Does the proposed action follow from the diagnosis?

Instruction, practice and assessment have different jobs. A short explanation introduces the principle. Practice lets the rep make mistakes with feedback. The reviewed demonstration establishes whether they can apply it. Size the material to the task; a module's running time tells the manager little about what a rep can do afterward.

The reviewer records a pass, or identifies the failed criterion and what the rep should practice before trying again. That feedback needs to be more useful than a general instruction to improve the call.

Passing controlled practice also has a limit. It supports a decision about the next level of responsibility. It doesn't establish sustained performance across live deals. Start with work the rep has demonstrated, keep an escalation route available and review the transfer into real opportunities.

Write the decisions into the playbook

A rep needs a current answer to a practical question: what does someone on this team do next, using which information and within which limits? A playbook puts that answer somewhere the rep and reviewer can both use it. It can be a document or a small connected set, provided the team can identify the current version.

Connect an observation to an action

I helped a solar agency aggregate performance across its client accounts and turn the findings into operating decisions. The media buyers compared the current day's performance with the previous three days and the previous seven days. They used those comparisons to decide which ads to stop and which to keep.

The useful detail is the link between the observation and the action. The instruction told a buyer what to inspect and what decision followed. A general instruction to improve performance would leave the buyer to invent that relationship.

That was historical paid-media work, and the rule belonged to its circumstances. It isn't a prescription for running a sales team or managing today's advertising. We also found markets where familiar winning ads failed, and some markets never became profitable. I couldn't reliably reconstruct a particular account rescue from memory. Those limits belong alongside the method: shared learning gives the team something to test, not permission to assume every case is the same.

Keep the sales process and the training in agreement

A sales playbook needs the same operational detail. Its discovery section explains what a rep must establish. Qualification defines which opportunities to pursue or decline. A proposal template identifies the commitments the team can offer. Objection handling explains the evidence behind an answer, and follow-up gives the rep a next action after the conversation. Escalation and renewal need their own decision rules where the rep owns that work.

Keep entries short enough to use during the job. Link each one to the relevant example or template, and put exceptions beside the rule they qualify. A rep deciding whether to promise a service needs to see its limits before making the commitment.

Give someone responsibility for maintaining the playbook. A scheduled review helps, and changes to pricing, delivery or qualification also need an update when they happen. Record what changed so a manager can distinguish a training gap from advice that's become stale.

The curriculum can then teach directly from the playbook. Practice uses its definitions; the reviewer applies its criteria. The rep learns one operating model, and a change to that model identifies which lessons and examples need attention.

Two ramp curves on the same axes, day zero to day ninety against performance. The default curve rises slowly and only reaches its plateau near day ninety. The engineered curve rises steeply, plateaus near day thirty, and stays there, with milestone markers at week two, day thirty and day sixty.
The default ramp depends on osmosis and lands near day ninety. The engineered ramp uses a competency-gated curriculum and lands the average rep performant by day thirty.

Curate calls around the judgment being taught

A folder of recordings gives the team raw material. A call library needs someone to choose what a learner should hear and explain why it belongs. The selection should follow the competencies in the curriculum, so the rep can find an example of the work they're practicing.

Explain the decision behind the recording

Choose different calls for different lessons. Discovery can show how a rep established a problem. An objection-handling clip can show what evidence made an answer credible. A technical demonstration can show which part of the product addressed the diagnosed need. A recovered deal can reveal how a misunderstanding was resolved. A loss can show a missed question, or a sound decision to stop pursuing a customer the business couldn't help.

The outcome alone won't tell the learner which of those lessons applies. An annotation needs to supply the context the recording leaves out. For a discovery clip, I'd ask the curator to identify what the rep knew beforehand, the question that changed the diagnosis and the evidence supporting the next step. A missing fact can become a practice question for the learner.

On the left, a person pulls one record at random from a dim heap of records and tapes piled toward the ceiling. On the right, another person listens at a turntable beside a short shelf where a few records are each lit by their own warm spot.
Conceptual comparison of an unsorted collection and a selected shelf. Choose and annotate calls for the judgment being taught.

Use the example and keep it current

The learner should do something with the example. Ask for a diagnosis before revealing the senior rep's notes, then compare the reasoning. Have the rep practice the task afterward. The manager can review whether the lesson changed what the rep did, which watching the clip alone can't establish.

A library also needs maintenance. Give a curator responsibility for replacing calls when the product, pricing or qualification rules change. Keep the useful lesson and remove advice the team no longer follows. There isn't a universal correct number of recordings; a rep needs to be able to find an appropriate example and understand why it was selected.

Existing reps can use the same material to prepare for an unfamiliar objection or review a difficult deal. Keep customer recordings within the access and consent arrangements that permit their training use, and remove sensitive information that the lesson doesn't require. Reusable teaching shouldn't depend on circulating a customer's private details beyond the people authorized to see them.

Use the metrics to find what needs reviewing

A rep can pass a demonstration and still struggle with live opportunities. Sales results help the manager investigate whether the training transferred, but each measure leaves something out. I'd use time to first deal, competency completion and win-rate variation together, with the underlying calls available for review.

Compare first deals from similar starting points

Time to first deal counts the days between a rep's start date and their first closed-won deal. The median can show how that interval changes across groups of new hires. Define the starting event consistently and record how the rep got the opportunity.

A rep who inherits a nearly completed deal has a different starting point from someone building a pipeline. Lead availability, deal size and the customer's buying process can also change the interval. A shorter time to first deal is a useful reason to investigate what improved. It can't isolate the effect of enablement on its own.

Also record hires who haven't closed a deal. Reporting only the people who reached closed-won would leave out the new hires the manager may most need to help. Keep hires who haven't closed a deal visible alongside the first-deal results.

Inspect the competency behind the completion rate

Choose a review milestone and define which competencies belong in it. The completion rate is the proportion of eligible new hires who passed all those competencies by that milestone. Keep the criteria and denominator visible when comparing groups.

A low rate could reflect a difficult task, missing practice, unavailable materials or too little reviewer capacity. Look at which criterion people fail and the feedback they receive. A high rate needs context too: the team may be teaching well, the assessment may be easy, or the hires may already know the work. Live-call review helps distinguish those possibilities.

Choose a milestone and assessment criteria for the work this sales role requires. A target completion rate alone can't establish that the curriculum teaches that work.

Investigate differences between reps before explaining them

Win rate needs a shared definition, such as closed-won deals divided by closed-won plus closed-lost deals in a defined group. Exclude open opportunities consistently when comparing reps on that definition. Compare similar lead sources and examine differences in territory, deal size, tenure and opportunity assignment before attributing the spread to execution.

The standard deviation of those close rates describes their spread. A wide spread is a reason to inspect calls and playbook use. A narrow spread could mean consistent execution, or consistently poor outcomes. Read the spread alongside the team's win rate and the number of deals behind each rep's rate.

Two archery targets. On the grey one, arrows are scattered across the outer rings and a few lie on the ground. On the other, the arrows sit in a tight cluster around a glowing center.
The targets illustrate different amounts of spread. Compare reps on similar opportunities, and inspect calls before attributing differences to playbook use.

The review should connect an outcome to a task the manager can inspect. A stalled deal may expose a missed discovery question. It may also expose a product limitation or an unsuitable lead. Correct the demonstrated gap, and keep the other explanations available until the evidence rules them out.

Build the next hire's gate from a real sales task

Start with a part of the job the next hire will need to handle. Discovery is a useful candidate when the team already has a defined offer and a way to qualify opportunities. The output could be a deal summary that another person can use to decide whether to prepare a proposal.

The starting point depends on what the team already has. A manager with clear competencies can select examples for them. A team with useful recordings can work back from a call to the judgment worth teaching. Either route needs an explicit demonstration before the manager can assess the rep's ability.

Give the learner and reviewer the same criteria

Build a complete training exercise around the chosen task, so the rep has something to practice and the manager has something to review.

  1. Write the task and its prerequisites. State what the rep should establish about the customer and which product or delivery limits they must understand first.
  2. Select a relevant call and annotate the decisions it illustrates. Pair it with the current discovery and qualification entries in the playbook.
  3. Ask the rep to practice, give feedback and then run the demonstration. Name the reviewer and pass criteria before assessing the work.
  4. Save the recording, the rep's deal summary and the review. A failed criterion should lead to specific practice and a repeat of the affected work.
  5. Use supervised live opportunities to assess whether the rep can apply the lesson outside the exercise. Keep the escalation path explicit.

Change the training when the evidence points there

The failed demonstration can reveal a curriculum problem as well as a learner problem. A reviewer may ask for information the lesson never taught, or the selected call may rely on an exception missing from the playbook. Correct the teaching material before asking the learner to repeat an unchanged exercise.

Keep those corrections with the competency so the next hire benefits from them. Look at live outcomes as well: a rep who writes a convincing summary but repeatedly misses a delivery constraint needs feedback on that specific judgment.

A recording alone doesn't establish that a rep can perform the work. The useful handover is a task the next person can perform, with evidence the manager can inspect. Ask the next hire to produce that work, review it against the current process and use what happens to decide what they can take on independently.

Visuals 5

Keep reading