.png?width=300&name=Webinar%20blog%20images%20-%20needs%20new%20colour%20(3).png)
Most sales leaders set team expectations in the same way: they decide what good looks like, write it down, present it to the team, and then spend the next six months wondering why the standards aren’t being held. The problem is not the standards. It is the process used to create them.
Setting sales team expectations that stick requires co-creation, not dictation. Alex Olley, Co-Founder and CRO of Reachdesk, recommends writing an expectations document for every role — from rep to VP — that defines what good looks like across activity, quality, and outcomes. But the step most leaders skip is building that document with the team. Expectations people helped create get internalised. Expectations handed down from above get tolerated at best, and quietly undermined at worst.
Why Dictated Expectations Erode Over Time
When a leader presents finished expectations to a team, two things happen. The team members who agree with the standards comply. The ones who don’t comply either leave or find ways to work around them. Neither outcome is what the leader wanted.
The mechanics of this are straightforward. Dictated expectations signal that the leader already knows what the job requires and the team’s job is to execute. This generates compliance without buy-in. And compliance without buy-in is fragile — it holds when someone is watching and slips when they’re not.
Kaitlen Kelly, Sales Leadership and Outbound Coach at MySalesCoach, frames the correct starting posture:
“You’re not there to overhaul everything on day one. You’re there to build trust, earn credibility, and get a real sense of what’s working and what’s not — from their perspective.”
That listening posture is not just good leadership practice. It is the foundation of expectations that last, because it signals to the team that their perspective shaped the standard — not just management’s assumptions about what the job looks like.
What to Define Before You Set a Single Expectation
Before co-creating anything, you need clarity on what the expectations document actually needs to cover. Alex Olley is specific about the three dimensions: activity, quality, and outcomes. This three-part structure — Define, Co-Create, Reinforce — is what separates expectations that stick from ones that fade within a quarter.
Activity expectations cover what reps should be doing and how often. Outbound volume, call cadence, pipeline coverage ratios, CRM hygiene. These are the observable, measurable behaviours that indicate a rep is doing the work. They should be specific enough to be tracked and fair enough to be reasonable.
Quality expectations are harder to define but more important. What does a good discovery call look like? What does a well-qualified opportunity look like before it advances to next stage? What does strong outbound messaging look like? Quality standards require examples — ideally pulled from your best performers’ work — because without them, “quality” is just a vague aspiration.
Outcome expectations cover the results: quota attainment, conversion rates, average deal size, pipeline creation. These are the lagging indicators that the activity and quality expectations are designed to produce. They should be ambitious but achievable, and grounded in the historical performance data you gathered during your diagnostic phase.
MySalesCoach’s State of Sales Coaching 2026 found that 76% of reps coached weekly hit quota, compared to 47% of reps coached quarterly or less. The consistency of the standard — and the consistency of coaching against it — is what drives that gap. Expectations are only as effective as the cadence that reinforces them.
How to Co-Create Expectations With Your Team
Once you know what the document needs to cover, the co-creation process has three steps.
Start with non-negotiables.
Some expectations are not up for debate: certain activity minimums, pipeline hygiene requirements, professional conduct standards. Alex Olley calls these “non-negotiables.” Be clear about which parts of the document are fixed before you invite input. This prevents the co-creation session from becoming a negotiation about whether standards should exist at all.
Invite reps to define what great looks like.
For each expectation category, ask the team: what does genuinely strong performance look like here? What makes a discovery call good versus average? What outbound volume is ambitious but achievable? You will find that your best performers already know what the standard should be — and getting them to articulate it is more persuasive to their peers than any leadership announcement.
Let the document reflect their language.
When reps recognise their own words in an expectations document, they feel ownership over it. This is not a cosmetic step. Teams that helped write the standard are more likely to coach each other against it, call each other out when it slips, and hold the bar without management prompting.
As Alex puts it:
“Great teams don’t just know what’s expected. They feel accountable to it. I would not dictate. Co-create expectations with your team to drive buy-in.”
How to Reinforce Expectations Once They’re Set
Co-creation builds the initial buy-in. Rhythm is what sustains it. Left without reinforcement, even well-built expectations fade as the pressures of daily work crowd them out.
The reinforcement structure Alex Olley recommends uses the existing cadence:
Weekly standups, sales 1:1s, pipeline reviews, and recognition moments should all echo the same standards. This does not mean repeating the expectations document in every meeting. It means calibrating what you praise, what you coach on, and what you address through each of those touchpoints against the same benchmarks.
When a rep closes a deal with a cleanly run discovery call, call out the specific behaviours that made it good. When pipeline reviews surface an opportunity that should not be there, address the qualification standard. When outbound quality slips, run a team call review session against the quality benchmark. The standard becomes culture when it is consistently applied — in recognition and correction — not when it is presented once and assumed to stick.
As Alex puts it:
“Consistency builds culture. When expectations are visible, fair, and reinforced with coaching — not just correction — you create a performance environment where clarity breeds confidence.”
That consistency is also what keeps your best people. The connection between clear expectations, consistent coaching, and retaining top sales performers is direct — high performers leave when they stop being stretched and recognised.
For the full context on how expectation-setting fits into the broader structure of your first 90 days, the First 90 Days as a Sales Leader guide covers where this work belongs in the three-phase framework. On how expectations connect to sales team management more broadly, that post covers the culture infrastructure needed to sustain them.
Frequently Asked Questions
What should a sales team expectations document include?
Three categories: activity (what reps should do and how often), quality (what strong execution looks like at each stage), and outcomes (quota, conversion, pipeline creation targets). Each category needs specific, measurable standards — not aspirational descriptions. Quality standards in particular should include examples pulled from top performer behaviour, because “what good looks like” without a concrete reference is not actionable.
Why do sales team expectations fail to stick?
Usually because they were dictated rather than co-created. When the team has no ownership over the standard, compliance is the best you get — and compliance is conditional on someone watching. Expectations that the team helped define get internalised as genuine standards rather than rules to be worked around. The co-creation step is slower upfront and saves significant management time later.
How do you get a sales team to hold each other to expectations?
Make the standard visible and specific enough that the team can self-assess against it. When reps can clearly describe what good looks like, peer accountability emerges naturally — particularly if the expectations were co-created and the team recognises their own thinking in the document. Recognition moments matter too: calling out excellent work in specific terms reinforces the standard more than any reminder about expectations.
When should a new sales leader set team expectations?
In phase two of your first 90 days — days 31 to 60. You need the diagnostic phase (days 1 to 30) first to understand what the gaps are and what the team’s current performance baseline looks like. Setting expectations without that context risks creating standards that miss the actual problems or are pitched at the wrong level. The diagnostic work also gives you credibility: the team sees that the expectations are grounded in evidence, not assumption.
How do you handle it when a team member consistently misses expectations?
First, check which category the gap falls into: is this a skill issue, a motivation issue, or a structural problem? The expectations framework identifies the pattern — the diagnostic work identifies the cause. A rep who understands the expectation and cannot consistently reach it needs coaching. A rep who can reach it but does not is a motivation or accountability conversation. A rep whose territory or comp makes the expectation unreachable needs a structural fix.
Build Expectations That Last
The leaders who set standards that endure are the ones who built them with their teams rather than for them. If you're not sure where to start, what sales leaders actually need from coaching is worth reading.
MySalesCoach works with sales leaders to develop the sales coaching techniques that reinforce expectations through consistent 1:1 coaching rather than repeated reminders.
Explore how MySalesCoach works or book a meeting to discuss how you can drive sales performance and be the best leader and coach you can be.
