Growth-Mindset Enablement Framework

The Core Idea

Growth-mindset language fails to stick when it's introduced as a training module instead of rebuilt into the actual mechanisms that already shape behavior: performance reviews, 1:1 coaching cadences, and comp conversations. This framework treats those three mechanisms as the rollout surface, not a fourth thing bolted on top of them.

Fixed vs. Growth Language — Swap Table

Phase 0 — Diagnose (before changing anything)

Audit current language across three artifacts:

• Pull the last 2 cycles of written performance reviews — count instances of fixed-trait language ("natural," "just isn't," "born") versus growth language ("built," "developing," "practicing").
• Pull the last 2 quarters of comp conversation notes or talk tracks — check whether pay is framed only around quota attainment or also around skill trajectory.
• Survey managers: "When a rep underperforms, do you default to explaining it by trait or by skill stage?"

Phase 1 — Leadership Language Shift (Days 1-30)

• Leadership team commits to using the swap-table language in every public forum — all-hands, forecast calls, Slack.
• Leaders name their own skill-building explicitly in team settings ("I'm still working on how I run calibration calls — here's what I'm trying differently this quarter").
• No new process yet — this phase is pure modeling, because language embedded top-down without modeling reads as a slogan.

Phase 2 — Coaching Cadence Embedding (Days 30-60)

• Add one standing question to every 1:1 template: "What skill are you actively building right now, separate from this month's number?"
• Replace "how's pipeline" openers with a growth-framed opener: "What's the hardest thing you're working on getting better at this month?"
• Managers log one specific "skill in progress" note per rep per month, separate from the deal notes.

Phase 3 — Review Cycle Redesign (Days 60-90)

• Redesign the written review template so at least one full section is explicitly "Skill Trajectory" — what was built this cycle, not just what result landed.
• Replace trait-based rating language ("strong closer," "weak prospector") with stage-based language ("developing — 2nd cycle," "proficient — consistent for 3+ cycles").
• Require every review to name the specific next skill being built, not just an overall rating.

Phase 4 — Comp Conversation Redesign (Days 90-120)

• Reframe comp conversations to include a trajectory statement alongside the number: "Your comp this cycle reflects [result]. Here's what building [named skill] unlocks for your comp trajectory over the next 2-3 cycles."
• Train managers to never let a comp conversation be purely retrospective — always pair the number with a forward skill-building path.
• Where possible, tie a specific comp lever (accelerator tier, role eligibility) explicitly to a named skill milestone, not just cumulative revenue.

Phase 5 — Reinforcement & Measurement

Track 3 adoption KPIs monthly, starting in Phase 1:

1. Language audit score — % of trait-based phrases vs. growth-based phrases in a monthly sample of written reviews and comp notes (re-run the Phase 0 audit quarterly).
2. Self-reported mindset survey — a short quarterly pulse: "I believe my skills here can meaningfully improve with effort" (1-5 scale), tracked by team over time.
3. Retention/internal-promotion correlation — track whether reps who report high growth-mindset scores show higher internal promotion and retention rates than those who don't, to make the business case durable beyond "it feels right."

12-Month Rollout Calendar