Support rep career development plan (IDP)

An individual development plan (IDP) is the forward-looking half of managing someone. Your coaching 1:1 handles this week; your performance review scores last quarter. The IDP is the only document that asks where is this person going, and what are we doing about it — and it is the rep's document, not the manager's. The manager's job is to react, fund, and unblock.

Keep it to one page and two or three goals. A plan with eight goals is a wish list nobody revisits. It matters because development is the cheapest retention lever you have: 94% of employees say they'd stay at a company longer if it invested in their career development (LinkedIn Workplace Learning Report 2018). Replace everything in [brackets] and fill it in together in one 45-minute session.

Plan header

---

1. Where you are now (rep drafts first)

The rep writes this before the session; the manager adds a second view. Honest and specific beats flattering.

• Two strengths I want to build on: […]
• Two things I want to get better at: […]
• What energizes me in the work: [hard technical cases / calming angry customers / writing / process]
• What drains me: […]
• Manager's read (added in session): [one strength they undersell, one gap they don't see]

2. The direction (pick one, name it out loud)

Growth is not automatically "up." Before setting goals, agree on a direction so the goals point somewhere. Use your career ladder if you have one.

• Deeper in role — master the current level, own a specialty (billing, API, security)
• Next level, same track — toward [Senior Rep / Staff]
• Toward lead / management — start developing others
• Lateral / cross-functional — toward [QA, WFM, KB, product, CS]
• Not sure yet — this period's goal is to find out (valid, and common)

Name whether this is a plan to close a known gap or a plan to explore. Both are legitimate; conflating them is how IDPs drift.

3. Goals (two or three — no more)

Each goal is specific and checkable. "Get better at technical tickets" is not a goal; the row below is.

4. Turn each goal into action (70 / 20 / 10)

For every goal, plan development across three channels, not just a course. Managers habitually over-weight formal training because it's easy to assign — but people learn roughly 70% from doing challenging work, 20% from other people, and 10% from formal study (Center for Creative Leadership). Front-load the 70.

Goal 1 — [title]

(Copy this block for Goals 2 and 3.)

5. What the manager owes (fill this in — no blanks)

An IDP where only the rep has actions is a to-do list, not a development plan. The manager commits too.

• Access to the work: route the stretch tickets / project the plan needs — [what, by when]
• A named mentor or reviewer: [name], introduced by [date]
• Time & budget: [X hrs/week off-queue], course budget [$Y] approved
• Air cover: it's understood the rep will be slower on [stretch area] while learning
• The next opening: flag [the relevant role / project] when it comes up

6. Check-in cadence

The plan is worthless if it's opened once and archived. Add a recurring line to the existing 1:1.

• Standing check-in booked: [monthly / quarterly]
• Each check-in: what moved, what's stuck, does any goal need rewriting or killing
• Progress noted below so a fair review later holds no surprises

Pitfalls that kill IDPs

• Too many goals. Three is the ceiling. Cut, don't add.
• All 10, no 70. A stack of courses with no real work attached teaches nothing that sticks.
• It's actually a PIP. Development is for growth. If someone is underperforming, run a performance conversation — don't disguise it as an IDP.
• Manager owns it. If the rep can't say what their own plan is without opening the doc, it isn't theirs.
• Promotion promised. An IDP builds readiness; it is not an IOU for a title. Say so plainly.
• Set and forgotten. A plan not revisited within a month is already dead.

Adapt before you adopt

• Match the direction options in §2 to your real career ladder and pay bands
• Set a cadence you'll actually keep — monthly for new reps, quarterly for tenured
• Decide where this lives (shared doc per rep) and who else can see it
• Keep it separate from the review form — same inputs, different purpose