How do you coach reps to set their own development goals?

The outcome you should expect

When coaching shifts from assigning goals to extracting them, the first visible change isn't a metric — it's who's talking. In a GROW-style 1:1, the rep should be doing roughly 70% of the talking by the second or third session. If you're still narrating the plan back to them, the goal isn't theirs yet, and you should expect it to decay the same way assigned goals always do: acknowledged in the room, ignored by the following week.

The realistic outcome over a single quarter looks like this: a rep goes from being unable to name a development goal beyond a quota number, to producing a written, specific behavior goal — something like raising a multithread rate from 30% to 60% of new opportunities, or improving a discovery-call score inside Gong or Chorus by a defined number of points. That goal lives in an Individual Development Plan (IDP) that the rep updates, not one you maintain on their behalf. By day 30 you should see the rep initiating the check-in ("here's what I tried, here's what happened") rather than you chasing it.

The deeper outcome, and the one that actually matters for a RevOps org, is self-diagnosis. A rep who has been through this coaching loop twice starts arriving at 1:1s with a next goal already drafted, because they've internalized the Reality step — they know how to look at their own data and name a gap without you prompting. That's the actual product of this coaching model: not one good goal, but a rep who can keep generating their own goals after you stop asking. Expect this to take two to three full cycles (roughly one to two quarters) before it becomes habitual rather than performed for your benefit.

You should not expect quota attainment to move immediately, and you should be suspicious if it does — a development goal targets a controllable behavior, and behavior change shows up in leading indicators (call scores, multithread rate, follow-up speed) weeks before it shows up in bookings. Treat the outcome as a coaching-process outcome first, a revenue outcome second.

What drives that outcome (mermaid)

The single biggest driver of whether a rep sets a real development goal is correct diagnosis before you coach. Reps who resist self-directed goal-setting almost always fall into one of four gaps, and each needs a different move:

• Skill gap — the rep has never been taught what a development goal looks like. Every answer they give is an outcome ("hit 120%"), not a behavior, because no one showed them the difference.
• Will gap — the rep doesn't believe development changes their comp or career, so they'll nod through the conversation and produce nothing afterward.
• Knowledge gap — the rep genuinely can't self-assess. Without call data or a scorecard in front of them, they're guessing at their own weakness.
• System gap — the culture only rewards closed-won, 1:1s are always deal interrogations, and there's no protected time for a development conversation to even happen.

Diagnosis, not effort, is what drives whether the goal sticks. A manager who runs the identical GROW script on a knowledge-gap rep and a will-gap rep gets two different failures: the knowledge-gap rep produces a vague goal because they have nothing concrete to anchor to, and the will-gap rep produces a plausible-sounding goal they quietly never touch.

Once the gap is correctly identified, the coaching move that drives ownership is always the same underlying mechanic: put evidence in front of the rep before you ask them to commit to anything. A rep who sees their own five most recent calls scored against a discovery framework will name a real gap on their own about 80-90% of the time in practice — you rarely have to supply the answer once the mirror is in the room.

Benchmarks and realistic ranges

Because "coaching worked" is hard to see directly, track leading indicators with realistic target ranges rather than a single pass/fail metric:

• Goal authorship rate — the percent of the goal's language that came from the rep, not you. Aim for the rep supplying at least 80% of the wording by the second coaching cycle. If you're still writing the sentence, don't count the goal as rep-owned yet.
• IDP completion and currency — every rep on the team should have a live IDP with a review date inside the last 30 days. A realistic starting point on a team that's never done this is 20-30% completion in month one, rising to 80%+ by month three if the cadence holds.
• Behavior-change indicators — track the specific metric named in the goal, not a proxy. A common range for a multithreading goal is moving from roughly 25-35% of opportunities with a second stakeholder to 50-65% over one quarter. A discovery-call score on a 1-10 scorecard typically moves 1.5-2.5 points over the same window when the rep is actually drilling it weekly.
• Self-assessment accuracy — compare the rep's self-score on a call to your score on the same call. Early on, expect a gap of 2+ points on a 10-point scale; by day 60 of consistent self-scored review, that gap should close to within 1 point. Convergence is the signal that self-diagnosis is real, not performed.
• Goal-to-action latency — how many days between a written goal and the first logged drill, role-play, or call review against it. Under 7 days is healthy. Anything past 14 days without action is almost always a will or system gap, not a scheduling accident.
• Cadence adherence — the 30/60/90 check-ins actually happening on the calendar. Teams that skip the day-30 check lose roughly half their goals by day 90 in practice, because nothing forced a course correction when reality shifted.

Hold two active goals per rep per cycle — one skill goal, one outcome goal — never more. Reps given three or four simultaneous goals in early attempts at this model routinely make progress on none of them; splitting focus is the most common way benchmarks stall out flat.

Risks, edge cases, and failure modes

The most common failure mode is a manager who runs the GROW questions but still supplies the answer when the rep hesitates. If you fill the silence after "what skill would change your year?", you've reverted to assigning the goal — the rep just watched you author it and call it theirs. The fix is mechanical: let the pause sit for longer than feels comfortable, even 10-15 seconds, before you offer a prompt.

A second failure mode is treating quota as the development goal. Quota is an outcome partly outside the rep's control — territory, market timing, deal luck. A goal that is just "hit 120% of quota" isn't coachable as a behavior; when a rep offers it, redirect to the skill underneath ("what would make that number almost automatic?") rather than accepting it as the goal.

Skipping the Reality step is a frequent edge case with newer reps and with reps who have low self-awareness — without evidence (Gong scores, pipeline conversion by stage, win/loss notes), the goal they set is a guess, and guessed goals rarely target the actual gap. If a rep can't point to specific data about their own performance, do not let the conversation proceed to Options; go get the data first, even if that pushes goal-setting to the next 1:1.

Rescuing is a subtler risk: a manager who jumps into the rep's live deal to fix it teaches dependence, not development. It solves this quarter's number and undermines next quarter's coaching, because the rep learns the manager will step in rather than that the rep needs the skill.

Uniform coaching across a team is another failure mode — a top performer needs a stretch goal (something genuinely uncomfortable), while a struggling rep needs a foundational one (a single controllable behavior, not a portfolio of five). Applying the same GROW script with the same difficulty calibration to both produces a bored top rep and an overwhelmed struggling one.

Finally, know when this framework doesn't apply. If the real issue is a wrong-fit hire, a broken comp plan, or a territory that can't produce quota no matter what skill improves, no amount of development-goal coaching fixes it. Pushing goal-setting onto that situation just delays a conversation that should be about fit or a performance plan (PIP), not coaching. RevOps leaders running this model at scale should build that distinction into manager training explicitly, because conflating the two wastes a quarter on the wrong intervention.

A practical rollout plan (mermaid)

Roll this out as a standing cadence, not a one-time workshop. A realistic sequence:

Week 1 — set. Schedule a dedicated 1:1 explicitly framed as development, not deal review — tell the rep in advance so they arrive thinking about it. Run the four GROW stages in order: Goal (pull the skill, not the quota), Reality (pull up five recent calls and pipeline conversion together), Options (let the rep generate two or three paths — role-play, shadowing a top performer, a framework like MEDDIC), and Will (rep states the SMART version out loud, then writes it into their IDP that day).

Weeks 2-4 — practice. One drill or call review per week tied directly to the stated goal. Open every 1:1 in this window with a five-minute check: "what did you try, what happened?" Keep it that short so it doesn't crowd out deal work, but never skip it.

Day 30 — measure. Look at the leading indicator named in the goal together. If reality shifted (territory changed, the skill turned out to be the wrong target), adjust the goal rather than forcing the original one to stay valid.

Day 60 — reinforce. Rep self-grades against the scorecard before you give your score; compare the two. Converging scores confirm the self-diagnosis muscle is developing.

Day 90 — close the loop. Confirm whether the behavior change actually stuck under pressure, not just in drills. Bank the win publicly if it did, and — critically — ask the rep to propose the next goal before you do. That's the test of whether the coaching transferred.

For a RevOps team scaling this across a whole floor, build the cadence into the existing 1:1 calendar rather than adding a separate meeting — a development check folded into an existing weekly 1:1 survives; a new standalone meeting is the first thing that gets cancelled when pipeline gets busy.

Related questions

How do you coach a rep using their own call recordings in a 1:1?

Pull two or three specific moments from a recent Gong or Chorus call — not the whole recording — and ask the rep to narrate what they were thinking at that moment before you offer your read. This builds the same self-assessment muscle the Reality step in GROW depends on.

How do you coach reps to inspect their own pipeline?

Have the rep walk their own pipeline stage-by-stage in a 1:1, stating why each deal is at its current stage and what evidence supports it, rather than you reading the CRM at them. It surfaces the same ownership gap goal-setting does.

How do you coach reps to set next steps at the end of a demo?

Ask the rep to write the next step as a mutual commitment with a date and a name attached before the call ends, then review a sample of those commitments weekly for specificity — vague next steps predict stalled deals the same way vague goals predict stalled development.

How can I ask a question that helps a rep identify their own pattern of losing deals in the same stage?

Ask them to pull their last five losses and describe what's identical about the stage they lost at, before you point it out. Pattern recognition the rep discovers themselves changes behavior faster than a pattern you hand them.

FAQ

How is a development goal different from a quota target? A quota target is an outcome the rep only partly controls, shaped by territory and market conditions. A development goal names a specific behavior the rep fully controls, like raising a multithread rate or a discovery score. Coach to the behavior and the quota outcome follows from it.

What if the rep can't think of any goal beyond hitting their number? That's a knowledge gap, not resistance. Show them their own data — five recent calls, pipeline conversion by stage — and ask what the data suggests they're avoiding. Most reps name a real gap once they can see it in front of them.

Should I let a rep set an easy goal at first? Yes, briefly. An early, achievable goal builds belief that development is worth the effort. Pair it with the SMART test so it stays measurable, and stretch the difficulty at the 30-day check once ownership is established.

How many development goals should a rep carry at once? Two: one skill goal, one outcome goal. More than that splits attention and nothing moves. Keep a backlog in the IDP if useful, but only two goals stay active in any single cycle.

What if a rep sets a goal but never acts on it? Re-diagnose rather than repeating the ask. No belief it affects comp or career is a will gap — connect the goal to something the rep actually values. No time to act on it is a system gap — protect coaching time and fix the surrounding cadence.

Does AI coaching software change how you run this in 2027? It changes the Reality step, not the coaching itself. Tools like Gong and Chorus now auto-surface behavior patterns from calls, so the manager spends less time hunting for evidence and more time on the human part — pulling the goal out of the rep and holding the standard around it.

Sources

• The GROW Model of Coaching — Performance Consultants
• How to Coach Salespeople — Gong Labs Research
• The Sales Manager's Guide to Coaching — RAIN Group
• How the Best Sales Leaders Coach — Harvard Business Review
• Setting SMART Goals — MindTools
• Individual Development Plans for Sales Teams — Sales Hacker
• Sales Transformation Insights — Korn Ferry
• Coaching Frameworks for Revenue Teams — Winning by Design

Related on PULSE

• [How do you coach reps to set next steps at the end of a demo?](/knowledge/cg0070)
• [How do you coach reps to manage their own energy and time?](/knowledge/cg0149)
• [How do you coach a rep using their own call recordings in a 1:1?](/knowledge/cg0117)
• [How do you coach a rep to inspect their own pipeline?](/knowledge/cg0105)
• [How can I ask a question that helps a rep identify their own pattern of losing deals in the same stage?](/knowledge/cg0841)