This page is about work design, not clinical advice. If you are struggling, speak to a professional or a service in your country; nothing here substitutes for that.
Why the role is structurally hard
Three features combine badly, and they are inherent to the job rather than signs of a bad team:
- Rejection is the base rate. Most touches produce nothing. A rep doing
everything right still hears no far more than yes, all day.
- Performance is public and continuous. Few roles publish individual
output daily on a screen everyone sees.
- Control is low. A rep cannot choose the market, the product, the price,
or usually the list. High demand plus low control is the standard description of a burnout risk.
Naming this matters, because reps who believe the difficulty is personal failure carry it worse than reps who understand it is the shape of the job.
What management commonly makes worse
Leaderboards as the primary motivator. They work for the top three and demoralise the rest, every day, in public. Use them sparingly and pair them with something other than raw output.
Activity targets that reward volume over judgement. A rep told to make 80 dials will make 80 dials, including to accounts they know are wrong, which is both demoralising and useless. See sales development as project management for the alternative: states and next actions rather than a task count.
Coaching that only appears when numbers drop. If the manager conversation is always remedial, every conversation becomes a threat. The weekly rhythm in SDR coaching exists partly for this: routine coaching is not a warning.
No visible path. Uncertainty about progression is corrosive, and it shows up as churn at month seven. See building an SDR team.
What a manager can actually change
Without lowering the bar:
- Give back control where you can. Let reps choose which call to review,
which accounts to prioritise inside a tier, when to block calling time. Small amounts of genuine autonomy have outsized effect on the demand-control balance.
- Measure outcomes, not motion. Meetings held and next steps rather than
dial counts. It rewards judgement, which is both better work and better for the person doing it.
- Make rejection legible. Publish the team's actual connect and reply rates
so a rep can see that a 4% reply rate is normal rather than personal failure. Most reps privately assume everyone else is doing better.
- Protect recovery. Back-to-back call blocks all day is a scheduling
decision, not a requirement.
- Separate the person from the number in every conversation. "This week's
connect rate is low, let us look at the list" is a different sentence from "you are behind".
The connect-rate example
Worth knowing because it removes a common source of self-blame: a falling connect rate is usually infrastructure rather than effort. Carrier spam labelling, number reputation, and list decay all suppress answer rates no matter who is dialling. See why nobody answers your calls.
A manager who responds to that with call coaching is treating a rep for a telecoms problem. That is demoralising and it does not work.
Where this sits
This is Mastery in the Tenbound Pipeline Architecture Standard. Mastery covers how people get good at the work, and sustainability is part of that: a team that burns out its reps at month nine never accumulates the experience that makes the other five pillars run well.