What a sales team assessment actually looks at
Most assessments produce a slide deck nobody uses. This is the list of things worth examining, and what each one tells you.
Assessment · 8 min read
An assessment is not a survey. You do not learn much by asking a sales team how they think the sales process is going. You learn by watching them work a deal, then comparing what you saw against what the pipeline claims is happening.
Everything below can be observed in two or three weeks. None of it requires new software.
1. Whether a sales process exists in practice
Almost every company has a sales process written down somewhere. The question is whether two reps working the same kind of deal would take the same steps. Usually they would not.
The fastest way to find out is to pick five open opportunities at the same stage and ask each rep what has to be true for that deal to move forward. If you get five different answers, the stage is a label rather than a stage.
What to look for
- Stage definitions that describe buyer behavior instead of seller activity
- Exit criteria a manager could verify without taking the rep's word for it
- Deals sitting in one stage far longer than the average close cycle
- Opportunities that skip stages entirely on the way to closed won
2. Pipeline accuracy
A forecast is only useful if the underlying pipeline is honest. Look at the last two quarters of closed lost deals and check when they were last updated before they died. If a deal was marked commit three weeks before it went dark, the problem is not forecasting discipline. The problem is that nobody knew what stage the buyer was actually in.
Pull the numbers that show whether the pipeline reflects reality:
- Average days in each stage, compared across reps
- Win rate by stage entered, not just overall win rate
- Percentage of closed lost deals that were forecast to close
- How many open deals have had no buyer activity in 30 days
3. Discovery quality
Discovery is where most B2B deals are won or lost, and it is the easiest thing to assess because you can listen to it. Recorded calls, or ride-alongs if calls are not recorded.
Shallow discovery has a recognizable shape. The rep asks about the problem, gets a one sentence answer, and moves straight to a demo. Nobody ever finds out what the buyer tried before, what it cost them, who else has to sign off, or what happens if they do nothing. Those four things are the deal.
If a rep cannot tell you in one sentence why the buyer would spend money this quarter rather than next year, the discovery was not deep enough.
4. Objection handling
Every team hears the same six or seven objections. Ask each rep to name them and explain how they respond. The answers will vary more than anyone expects, and some reps will not have an answer at all. That is a training gap, not a talent problem.
5. How managers spend their week
This is the finding that surprises people most. In a struggling sales organization, the sales manager is usually working deals rather than coaching reps. That feels productive and it hides the underlying issue, because the manager closes the quarter and the team learns nothing.
Look at the manager's calendar for the last month. Count the hours spent in one on one coaching on real deals. In most teams the number is close to zero.
6. Whether the team shares a goal
Individual quotas are normal. What is not normal, and what separates a group of sales people from a sales team, is when nobody can describe what the team is trying to accomplish beyond the sum of those quotas. Reps hoard what works. Pipeline review turns into a status update. Nobody helps on someone else's deal because there is no reason to.
What comes out of it
A useful assessment ends with a written document that says what is broken, what it is costing, and what order to fix it in. Not twenty recommendations. Three or four, sequenced, with the reasoning visible so the sales leadership can argue with it.
The order matters more than the list. Training a team on a process that does not exist yet wastes everyone's time. Redesigning a process before you understand why the current one is ignored produces a second process that also gets ignored.