You're Losing Your Best People Because Your Feedback Is Garbage

Your star employee just gave notice.

I’ve watched managers act shocked when their best performers quit. “WTF? They were doing great.” Then comes the counteroffer scramble. Which almost never works.

Ok, so here’s the boondoggle. You spent a year and a half telling them they were “doing great” without ever giving feedback they could actually use to help them along in their careers.

You know the routine… and the problem was that it became a routine. Every one-on-one was a quick status check. Every review was the same recycled phrases: great team player, strong contributor, could be more strategic. Meanwhile, your hotshot performer wasn’t bored with the work—they were starving for real feedback that would help them level up.

But you kept serving them up some platitudes and called it a day.

Most managers think that these banal phrases are meant to recognize good work and help people grow. In reality, they’re handing out Successories-inspired praise that feels hollow and flinging out vague criticism nobody can act on. You notice their awesome output, but you never help them improve their job.

You’re not developing talent. You’re wasting their potential.

Your top performers don’t need you to tell them they’re doing well—they already know that. What they need is in-depth feedback. What exactly made their work excellent? What would take it from good to exceptional in your company?

It’s time to stop giving feedback that sounds like a deranged workplace support group but communicates nothing to the person being assessed.

Let’s use AI to help start delivering insights that actually help people get ahead in their careers.

10 LinkedIn strategies in one eBook!

When your best team member resigns, and you think “I told them they were the bees knees all the time, what do they want from me?,” instead of “Hold up here, did I ever show them how to actually kill it in this company?”—you’re feedback is the problem.

A lot of managers confuse spewing babble from some PDF they get from HR with actually communicating. Saying some generic “rah rah” phrases in a one-on-one doesn’t mean you gave useful feedback.

If the person walks away from that meeting with nothing they can repeat, improve, or change… it was just you talking to yourself to make you feel like you “did something.”

Here’s a prompt that helps you give constructive feedback that actually develops people and their careers—instead of the polite, meaningless drivel most teams are drowning in.

Act as an expert leadership development coach who understands that vague feedback is useless feedback. I need to transform my feedback from generic observations into specific, actionable insights that help people grow.
Here are my feedback failure details: [Insert how you currently give feedback, recent examples of feedback you've given, how people respond when you give feedback, complaints about lack of growth opportunities, and why you think your current approach works here]
Please:
1. Identify where your feedback is too vague to be actionable
2. Design specific feedback frameworks showing what good looks like versus what great looks like
3. Create growth-focused feedback approaches for high performers who need challenge not just praise
4. Suggest observation systems that capture specific examples instead of general impressions
5. Build measurement frameworks tracking whether feedback leads to actual behavior change

Want to stop your best people from hitting the bricks? The Mega-Prompts section offers a framework that turns your feedback from useless to transformational, helping you retain that high performer you really, really need to keep.

Let me tell you about Allie, a project manager who thought good feedback meant saying, “Nice job.”

Her one-on-ones were basically a written script.
“How are things going?”
“Any blockers?”
“Keep up the good work.”

Boring.

What she wrote in her report’s performance reviews wasn’t much better. Strong communicator. Solid delivery. Could be more proactive. So trite. If the co-worker pushed for specifics, Allie would smile and say, “You’re doing great—just keep doing what you’re doing.” In her mind, that was supportive leadership. Wrong-o!

Then her best project lead quit.

Allie was stunned. “But, but but… Jordan was absolutely crushing it. I told them that all the freaking time.”

Her director asked the obvious question that she missed: “What exactly did you help them get better at?”

She sat in silence and looked at her feet. She didn’t have an adequate reply.

Eighteen months of one-on-ones were completed, but she provided zero developmental feedback. Zip. It was all encouragement from the standard manager handbook, but no solid information. She finally realized that Jordan didn’t leave because they felt unappreciated. They left because they stopped learning.

And that’s when Allie finally saw the problem.

Saying “good job” tells people nothing they can repeat or take action on. Saying “be more proactive” without an example is just corporate mumbo jumbo.

So she used the High-Impact Feedback Framework Mega-Prompt, and rebuilt how she gave feedback.

Instead of praise, she started giving on-point critiques.
“Your kickoff surfaced the vendor dependency early—that saved the schedule.”
“In yesterday’s stakeholder meeting, you committed to timelines before checking with engineering. Here’s why that created risk.”

Her one-on-ones shifted from status updates to real growth conversations. Her top performers got the hardest feedback, the kind that actually helps them become the killers at the top of their game they want to be.

Six months later, things looked different. Engagement jumped. Nobody left. People actually asked for feedback because it helped them do their jobs better.

Turns out the lesson was simple… Nice feedback keeps conversations comfortable. But specific feedback actually makes people better.

But it can all be made easier by applying AI to feedback methods.

Pick up the Effortless PM course!

Ready to stop giving feedback that feels supportive but communicates nothing?

Here’s a preview of two power-up prompts that work with the High-Impact Feedback Framework Mega-Prompt.

The Specific Observation Capture System Power-Up Prompt

When to use: When your feedback is based on general impressions instead of specific examples and people can't act on it
Impact: 85% improvement in feedback actionability by replacing vague observations with concrete examples people can learn from
Key feature: Creates observation logging system that captures specific moments and behaviors in real-time, giving you actual examples to reference instead of relying on fuzzy impressions when feedback time comes

The Growth-Path Feedback Generator Power-Up Prompt

When to use: When your high performers are stagnating because you only give them praise instead of showing them how to reach the next level
Impact: 70% improvement in high-performer retention by giving top talent specific paths to excellence instead of generic validation
Key feature: Designs feedback frameworks showing the gap between current performance and next-level performance with concrete skills to develop, turning "you're doing great" into "here's how to become exceptional"

These prompts help you give feedback that develops people, rather than just making them feel good.

Share

Feedback without specific points to implement is just white noise. Real feedback provides information about what can be improved, and not just”good job.”

And no, this isn’t about being harsh or overly critical. It’s about being clear enough that someone can actually use what you tell them to get better at their career.

Even up until recently, if someone did good work… I’d say, “Nice job.” or “Good work.” If someone needed improvement, I’d say, “Be more thoughtful.” I convinced myself that keeping feedback positive and non-threatening meant I was being a good leader. I was a schmuck.

But then people would ask for specifics.

And I’d get defensive. “What do you mean? I give feedback all the time.”

Looking back, I thought my job was making people feel all warm and fuzzy in reviews. What I was really giving them was a giant nothingburger and then wondering why no one was growing.

Vague feedback is just useless feedback. It might feel good for a moment, but it doesn’t help anyone improve. “Good job” without explaining what was good actually means… means they can’t repeat what made it good.

Your best people don’t leave because they feel unappreciated. They leave because they stop gaining insight. That’s what most managers miss.

AI actually helped me see this more clearly. My so-called “touchy-feely feedback style” was really just a way of avoiding harsh truths.

So for reviews, give specific observations. Capture real examples. Show people what excellence looks like—and where the gap in their performance is.

Yes, it takes more effort. But people actually use the feedback.

And with AI, you save time and go deep on the feedback to help that employee grow.

Wanna see?

Share

Want to learn how to write for LinkedIn like a pro?

Before I started writing on LinkedIn, I took Justin Welsh’s LinkedIn OS Course.

VoxDeck - Makes AI presentations with animation and avatars.

Mastersheets - Unifies data with role-based spreadsheet workflows.

Claude in PowerPoint - An add-in that integrates Claude into your PowerPoint workflow.

GenPPT AI - AI PPT generator, powered by Claude Opus 4.6.

Want to automatically generate step-by-step guides for any digital process, like web or desktop workflows?

Check out Scribe—I absolutely love their software.

Why developers using AI are working longer hours

When AI Gives You “Brain Fry”

OpenAI’s Five AI Value Models

How AI is changing the labor market

Start delivering insights that actually help people get ahead.

These three prompts will dramatically change how you give feedback. No more vague observations that no one can act on. No more empty praise that sounds good but leads nowhere. Just clear, specific insights that help people improve and grow.

After running The High-Impact Feedback Framework Mega-Prompt, the two Power-Up prompts build on that foundation with: “Use the feedback transformation strategy and observation framework from the previous prompt as the foundation.”

Let’s design feedback systems that actually develop talent instead of typing up some generic “Yup, good work.” into their review.

Fire up ChatGPT 5 Auto or Claude 4.6 Sonnet to run these prompts and watch your retention improve while your team's capabilities grow.

✂️—CUT BELOW—

#ROLE
You are an Elite Leadership Development Strategist with 20+ years of experience transforming managers from generic feedback givers into development catalysts. You excel at identifying where feedback lacks specificity, creating observation systems that capture actionable examples, and building frameworks that help people grow instead of just feel validated. You've helped managers improve retention of top performers by 75% through feedback that actually contains useful information.
#TASK
First, ask the manager critical questions about their current feedback patterns and team development outcomes to ensure you have complete understanding of where vague feedback is preventing growth. Then design a comprehensive high-impact feedback framework that replaces generic observations with specific, actionable insights.
**Initial Questions (ask these first before proceeding with analysis). Ask one question at a time and proceed with the next question only after it is answered:**
1. How do you currently give feedback to your team members (frequency, format, content)?
2. Can you share a recent example of positive feedback you gave someone?
3. Can you share a recent example of developmental feedback you gave someone?
4. How do people typically respond when you give them feedback?
5. What happens after you give someone feedback—do you see behavior change?
6. When was the last time a high performer asked you for specific growth guidance?
7. How many of your best team members have left in the past year and why?
8. What do people say in exit interviews about learning and development?
9. How do you track whether your feedback is helping people improve?
10. What stops you from being more specific when giving feedback?
**After gathering this information, please follow this step-by-step process:**
1. Assess current feedback quality and specificity levels
2. Identify where vague language prevents action
3. Design specific observation capture systems
4. Create feedback frameworks showing what good vs. great looks like
5. Build growth-path guidance for high performers
6. Establish behavior change tracking mechanisms
7. Design measurement systems for feedback effectiveness
8. Create implementation plan for feedback transformation
#SPECIFICS
**Feedback quality assessment should identify:**
- Specificity level (concrete examples vs. general impressions)
- Actionability (can people act on it or is it vague)
- Information content (does it contain useful data)
- Growth orientation (helps people improve or just validates)
- Behavior change results (leads to improvement or ignored)
- High performer engagement (challenged to grow or stagnating)
- Retention correlation (feedback quality vs. departure rates)
**Vague feedback pattern analysis must evaluate:**
- Generic praise without examples ("good job," "great work")
- Abstract criticism without specifics ("be more strategic," "improve communication")
- Impression-based observations without data
- Lack of concrete examples to illustrate points
- Missing information about what to repeat or change
- Absence of growth paths for high performers
- Emotional validation replacing developmental guidance
**Observation capture system should provide:**
- Real-time logging of specific behaviors and examples
- Concrete instances instead of general impressions
- Context and impact of observed behaviors
- Pattern tracking across multiple observations
- Examples to reference in feedback conversations
- Before/after comparison capabilities
- Growth trajectory documentation
**Feedback framework must include:**
- Specific behavior or output observation
- Context and impact explanation
- What made it effective or problematic
- Concrete next steps for improvement
- Examples of next-level performance
- Skills to develop for growth
- Measurable outcomes to track
Format output in clear sections with actionable feedback approaches, highlighting specific examples and behavior change mechanisms.
#CONTEXT
This feedback framework will determine whether your organization develops talent or loses it to competitors who actually help people grow. Your design will directly impact retention of high performers, team capability development, and whether people see feedback as helpful or hollow. The approach you create must balance supportive tone with specific content that people can actually use.
#EXAMPLE
Input: Manager giving monthly one-on-ones, feedback includes "good job" and "be more proactive," lost two top performers to other companies in past year citing "no growth opportunities," doesn't track specific examples or behavior changes.
**OUTPUT SAMPLE: FEEDBACK QUALITY ASSESSMENT**
**Current Feedback Patterns:**
Positive Feedback Examples:
- "Great job on the project!" (No specifics on what was great)
- "You're doing really well, keep it up!" (No information on what to keep doing)
- "Nice work this sprint!" (No examples of what work was nice)
- "You're a strong contributor!" (No explanation of contributions)
Information Content: 0%
These statements communicate approval but contain zero actionable information. Person knows you're happy but has no idea what made it good or how to repeat it.
Developmental Feedback Examples:
- "You need to be more proactive" (No definition of proactive or examples)
- "Work on your communication skills" (No specifics on what's wrong or how to improve)
- "Try to think more strategically" (No examples of strategic thinking)
- "You should take more initiative" (No concrete actions)
Actionability: 0%
These statements identify problems but provide no path to improvement. Person knows you're unhappy but has no idea what to change.
**Team Development Outcomes:**
Retention Patterns:
- Top performer 1 (left after 14 months): Exit interview cited "no specific guidance on growth"
- Top performer 2 (left after 18 months): Exit interview cited "generic feedback, no challenge"
- Current high performers: Engagement scores dropping, actively interviewing
- Team sentiment: "Manager is nice but I don't learn anything"
Behavior Change Evidence:
- Feedback given: 100+ instances
- Documented behavior changes: 0
- People asking for more feedback: 0
- People reporting feedback helped them improve: 0
Team Capability Trends:
- Skills staying flat (not growing)
- No promotions in 2 years
- People leaving for growth opportunities elsewhere
- New hires ramp up but plateau quickly
**Diagnosis: Feedback lacks specificity to drive development, causing high-performer attrition.**
**HIGH-IMPACT FEEDBACK FRAMEWORK**
**Specific Observation Template:**
Instead of: "Good job on the project!"
Use This Format:
**What I Observed:**
"In yesterday's stakeholder presentation, you anticipated the CFO's budget concerns and had three cost scenarios prepared. When she asked about the higher estimate, you walked through the assumptions instead of just defending the number."
**Why It Mattered:**
"That preparation prevented a two-week delay where we'd have to go back and create those scenarios. Your assumption transparency also built credibility—she approved because she trusted your thinking, not just your numbers."
**What Made It Excellent:**
"Most people prepare one scenario and get defensive when questioned. You anticipated objections, prepared options, and showed your work. That's executive-level stakeholder management."
**How To Build On It:**
"The next level would be proactively sending scenarios before the meeting so she can review them. That positions you as strategic partner, not order-taker. Want to try that for next month's budget review?"
Information Content: High (specific behaviors, impact, growth path)
Actionability: High (knows what to repeat and how to improve)
**Vague to Specific Translation:**
Vague: "You need to be more proactive"
Specific:
"In this week's sprint planning, you waited for me to assign you work instead of identifying the highest-priority items yourself. Here's what I observed:
- Monday: You asked 'what should I work on?' when the backlog was already prioritized
- Wednesday: Feature X was blocked but you waited for standup to mention it instead of flagging immediately
- Friday: You finished your tasks but didn't pull the next item
Proactive would look like:
- Starting standup by saying 'I'm working on X because it unblocks Y'
- Slacking blockers when you hit them, not waiting 24 hours
- Pulling next-priority work when current work completes
Try this next sprint: At start of sprint, tell me which items you're taking and why. When blocked, flag it immediately. Let's see how that changes your velocity."
Vague: "Improve your communication"
Specific:
"In yesterday's technical discussion, you interrupted Sarah three times before she finished her point. Here are the timestamps from the recording:
- 10:23 - Sarah started explaining the database concern, you jumped in at 10:24
- 10:31 - She tried to finish, you cut her off with solution
- 10:45 - Same pattern again
The impact: Sarah stopped contributing. We made a decision without her input, then discovered the database issue she was trying to warn us about.
Better communication would be:
- Let people finish their complete thought before responding
- Ask clarifying questions instead of assuming you know their point
- Summarize what you heard before disagreeing
Next meeting: Practice waiting 3 seconds after someone stops talking before you respond. That pause ensures they're actually done. Let's debrief after and see how it felt."
**HIGH-PERFORMER FEEDBACK APPROACH**
**Growth-Path Framework for Top Performers:**
Instead of: "You're doing great, keep it up!"
Use This Approach:
**Current Level Assessment:**
"Your code reviews are consistently excellent at catching logic bugs and edge cases. In the past month, you've prevented 8 issues from reaching production. That's senior-level quality focus."
**Next Level Gap Analysis:**
"The difference between senior and staff engineer is architectural thinking. You catch implementation bugs, but you don't yet question the architecture itself.
Examples from this month:
- Feature X: You reviewed the code thoroughly but didn't flag that it duplicates logic from Feature Y
- Feature Z: You caught the null pointer but didn't notice it's solving a symptom of a deeper data model issue
Staff engineers would say: 'This works, but it's creating tech debt. Here's a refactor that solves the root cause.'"
**Specific Growth Path:**
"To develop architectural thinking:
1. Next 3 code reviews: Add one comment about architecture, not just implementation
2. Pick one feature this sprint: Before coding, diagram how it fits into overall system
3. Next design review: Challenge one assumption about the approach, not just implementation
Let's check in mid-sprint on how this is going. The goal is getting you ready for staff promotion in next 6 months."
Result: High performer knows they're valued AND has concrete path to grow
**OBSERVATION CAPTURE SYSTEM**
**Real-Time Example Logging:**
Create Running Log of Observations:
**Date: March 5**
**Person: Jordan**
**What I Observed:** Stakeholder meeting ran 30 minutes over because Jordan kept diving into technical details when asked yes/no questions
**Specific Example:** CFO asked "Will this be done by Q2?" Jordan started explaining sprint velocity and technical dependencies instead of answering
**Impact:** CFO got frustrated, meeting derailed, decision delayed
**Feedback To Give:** "Match answer depth to question. Yes/no questions get yes/no answers plus one sentence context. Save deep dives for when they ask 'how' or 'why'."
**Date: March 7**
**Person: Jordan**
**What I Observed:** Jordan simplified technical explanation beautifully in team meeting
**Specific Example:** Explained database migration to non-technical PM using analogy: "Like moving to a new house—you can move everything at once (risky, fast) or room by room (safer, slower)"
**Impact:** PM understood tradeoffs immediately, made informed decision
**Feedback To Give:** "That analogy was perfect. You matched technical depth to audience. That's the skill you need for exec presentations. How can you do that more consistently?"
**Pattern Tracking:**
After 5-10 observations:
"Jordan—I've been tracking patterns in your stakeholder communication. You're excellent at technical depth but struggle with executive-level brevity. Here are 5 specific examples from the past two weeks. Let's work on this."
Versus one-off general: "Jordan, work on your communication" (useless)
**BEHAVIOR CHANGE TRACKING**
**Feedback Effectiveness Measurement:**
For Each Piece of Feedback Given:
1. **Document What You Said** (specific behavior, why it matters, what to change)
2. **Set Check-In Date** (when you'll observe if behavior changed)
3. **Track Evidence** (did they change behavior? specific examples?)
4. **Follow Up** (acknowledge change or provide additional guidance)
Example Tracking:
**Feedback Given:** March 5 - Jordan needs to match answer depth to question
**Check-In Date:** March 19 (next stakeholder meeting)
**Observation:** March 19 - Jordan answered CFO's timeline question with "Yes, Q2" plus one sentence context. Perfect.
**Follow-Up:** "Jordan—I noticed you nailed the brief answer in yesterday's meeting. That's exactly what I meant about matching depth to question. That skill is going to serve you well with execs."
**Result:** Jordan knows feedback was useful because you noticed improvement
Versus: Give feedback, never follow up, repeat same feedback 6 months later
**GROWTH CONVERSATION STRUCTURE**
**Monthly Development One-on-Ones:**
Replace: "How are things going?" "Any blockers?" "Keep up the good work!"
With This Structure:
**Opening (5 min):**
"What's one skill you want to get better at this month?"
**Specific Feedback (15 min):**
"I've captured three specific examples from the past month I want to discuss. Two things you did really well and one growth opportunity. Let's start with what's working..."
[Share specific observations using framework above]
**Growth Path Discussion (10 min):**
"Based on these patterns, here's what I see as your next-level skills:
- Skill 1: [Specific examples of gap]
- Skill 2: [Specific examples of gap]
Which one do you want to focus on? Let me give you concrete ways to develop it."
**Action Planning (5 min):**
"So this month you're going to:
1. [Specific action]
2. [Specific action]
3. [Specific action]
I'll watch for these in our work and give you feedback on how it's going. Sound good?"
Result: Person leaves with clear growth plan, not vague "be better"
**IMPLEMENTATION PLAN**
**Week 1: Start Observation Logging**
Begin capturing specific examples:
- Create doc/system for logging observations
- Daily: Note 1-2 specific things you observe
- Include context, impact, what made it good/bad
- Build library of examples for feedback conversations
**Week 2: Transform One Feedback Conversation**
Pick one person:
- Review your observation log for them
- Schedule development one-on-one
- Use specific feedback framework
- Include growth path for next level
- Track their response
**Week 3-4: Expand to Whole Team**
Apply framework to everyone:
- Monthly development one-on-ones
- Specific observation-based feedback
- Growth paths for high performers
- Behavior change tracking
**Month 2+: Measure and Refine**
Track effectiveness:
- Are people changing behavior based on feedback?
- Are high performers staying and growing?
- Do people ask for more feedback?
- Are capabilities increasing?
**MEASUREMENT FRAMEWORK**
**Feedback Quality Metrics:**
Specificity:
- Percent of feedback with concrete examples (target: 100%)
- Percent of feedback people can act on (target: >90%)
- Information content (useful data vs. validation, target: high)
Behavior Change:
- Feedback instances leading to observed change (target: >70%)
- Time to behavior change (target: <1 month)
- Sustained change (target: >80% sustained 6 months)
**Development Impact Metrics:**
High Performer Retention:
- Retention rate of top performers (target: >95%)
- Exit interview feedback on development (target: positive)
- Internal promotion rate (target: increasing)
Team Capability:
- Skills developed per person per quarter (track)
- Promotion velocity (time to next level, target: decreasing)
- Engagement scores on "manager helps me grow" (target: >85%)
**Success Indicators:**
Feedback Transformation:
- Every feedback instance has specific examples
- People can repeat what you told them
- Behavior changes follow feedback
- People ask for MORE feedback
Development Culture:
- High performers challenged, not just praised
- Growth paths clear for everyone
- Capabilities increasing over time
- Retention of top talent high
Team Sentiment:
- "My manager helps me grow" (>85% favorable)
- "I know what I need to do to advance" (>80% favorable)
- "I get specific, useful feedback" (>90% favorable)

✂️—END—

Share

✂️—CUT BELOW—

#ROLE
You are a Leadership Observation Systems Expert specializing in helping managers capture specific, actionable examples instead of relying on vague impressions. You excel at creating logging frameworks that document concrete behaviors in real-time so feedback is based on data instead of fuzzy memory.
#TASK
Design a comprehensive observation capture system that logs specific moments and behaviors as they happen, giving you actual examples to reference in feedback conversations instead of relying on general impressions.
Use the feedback transformation strategy and observation framework from the previous prompt as the foundation.
**Please provide:**
**1. Real-Time Logging Framework**
- Daily observation capture process
- Specific behavior documentation format
- Context and impact recording
- Pattern identification across observations
- Example library organization
**2. Observation Categories**
- Behaviors to capture (communication, decision-making, collaboration)
- Positive examples (what to repeat)
- Growth opportunities (what to develop)
- Critical incidents (significant moments)
- Pattern trends (repeated behaviors)
**3. Documentation Standards**
- Minimum specificity requirements
- Context inclusion (who, what, when, where, why)
- Impact articulation (what happened because of this)
- Actionable insight extraction
- Example quality criteria
**4. Review and Retrieval**
- Pre-feedback conversation review process
- Pattern synthesis across multiple observations
- Example selection for maximum impact
- Timeline and trend analysis
- Growth trajectory documentation
**5. Integration Methods**
- Daily routine integration (when to log)
- Tools and systems (where to capture)
- Team meeting incorporation
- One-on-one preparation
- Performance review synthesis
Format as an actionable observation capture guide with specific logging templates, daily routines, and synthesis methods that replace fuzzy impressions with concrete examples.

✂️—END—

Share

✂️—CUT BELOW—

#ROLE
You are a Talent Development Architect specializing in creating growth paths for high performers who are stagnating from lack of challenge. You excel at identifying the gap between current performance and next-level performance, then designing specific skill development roadmaps.
#TASK
Create a comprehensive growth-path feedback framework that shows top performers the specific gap between their current excellence and next-level mastery, giving them concrete skills to develop instead of generic praise.
Use the feedback transformation strategy and observation framework from the previous prompt as the foundation.
**Please provide:**
**1. Current Level Assessment**
- Performance strengths identification
- Specific examples of excellence
- Skills at mastery level
- Impact and value delivered
- Recognition of achievements
**2. Next Level Definition**
- What distinguishes next level from current
- Specific skills/behaviors required
- Concrete examples of next-level work
- Gap analysis (what's missing)
- Promotion criteria clarity
**3. Growth Path Design**
- Specific skills to develop (not vague "be better")
- Concrete actions to practice new skills
- Stretch assignments to build capabilities
- Learning resources and support
- Timeline and milestones
**4. Challenge Without Criticism**
- Framing that honors current excellence
- Growth orientation (not deficit focus)
- Excitement about potential
- Support for development
- Partnership in growth journey
**5. Progress Tracking**
- Specific behaviors to observe
- Skill development milestones
- Check-in cadence and format
- Adjustment mechanisms
- Celebration of growth
Format as a comprehensive growth-path framework with specific templates for assessing current level, defining next level, and designing development plans that challenge top performers to grow.

✂️—END—