Your organization spent $50,000 on executive coaching this year. When finance asks what you got for it, what do you tell them? "Sarah feels more confident"? "The team says good things about their sessions"?
That's not measurement. That's anecdote.
But here's the problem: the usual measurement approaches are worse than useless. Satisfaction surveys tell you people enjoyed the sessions, not whether they changed. Quarterly 360s come too late to catch what's actually happening. And trying to tie coaching to business outcomes is mostly fantasy (you can't isolate coaching's impact from the ten other things that changed in the same quarter).
So most organizations either abandon measurement entirely or settle for theater. Neither helps you understand what's working.
The real measurement challenge isn't proving ROI. It's tracking behavioral change as it happens (or doesn't happen). Because the gap between "good coaching session" and "actually doing things differently three weeks later" is where most coaching value disappears.
You leave the session committed to delegating more effectively. Three weeks later, you're still the bottleneck making every decision, but you don't notice because you're too busy to notice. Your coach asks "how's the delegation going?" in your next session, and you genuinely believe you've improved. You haven't. You just can't see what you're doing.
This is the noticing gap: the space between knowing what to change and seeing when you're not changing it.
Traditional coaching measurement tries to solve this with quarterly check-ins. But quarterly is far too slow to catch backsliding. By the time you get the data, you've reinforced the wrong pattern for three months.
AI changes this because it can notice for you.
Not in some dystopian "your boss is watching" way. In a "here's what you actually did this week vs. what you said you'd do" way. AI can analyze your communication patterns, surface your defaults under pressure, and show you the exact moment you stopped delegating and started solving.
It's a mirror that doesn't require you to remember to look in it.
The Framework: What to Track
When I work with clients on coaching and development, we use a simple structure: Insight → Action → Evidence. You need to know what you're trying to change (insight), experiment with doing it differently (action), and gather proof that something shifted (evidence).
The problem is the evidence part. Most organizations either abandon measurement entirely ("you can't measure soft skills") or default to theater (satisfaction surveys that tell you nothing about behavioral change).
The middle ground is triangulated observation: multiple signals, both quantitative and qualitative, that let you see patterns without pretending you can reduce human development to a single number.
AI fits here perfectly. Not as the measurement system, but as the pattern-recognition tool that makes your own behavior visible in real-time.
How This Actually Works
Instead of reviewing your quarter once every three months, you can review your week every Friday. You feed AI your actual communication (emails, Slack messages, meeting notes) and ask it to show you your patterns.
Not vague "how am I doing?" questions. Specific behavioral analysis tied to what you're trying to change.
Don't overthink the selection process. Open your calendar, find the most stressful meeting you had last week, and export the emails you sent in the hour immediately following it. That's your data.
Here's one example. This month's focus is resilience (so let's look at how you show up under pressure).
Prompt: Pressure Degradation
I want to understand how my behavior changes under pressure. Below are two sets of messages - Set A (business as usual) and Set B (high pressure/crisis mode).
Compare them and tell me:
1. What specific language disappears when I'm under pressure?
2. What shows up instead? (Quote exact phrases)
3. Do I get shorter, longer, more direct, more vague?
4. What do I stop doing when stressed that I do when calm?
5. Give me one early warning sign that I'm shifting into pressure mode
Be specific - quote my actual language so I can catch this pattern in real-time.
What you feed it: 6-10 emails or Slack messages (half from normal times, half from high-pressure situations (you'll know which is which)).
Data Safety: If you aren't using an Enterprise instance of ChatGPT/Claude, please anonymize your text before pasting. Strip out specific names, dollar amounts, and proprietary strategy details.
Cadence: Monthly pattern check, or after any high-pressure period
What this surfaces: Your stress tells. The specific ways your communication degrades under pressure. Most people don't realize they have a "stressed version" of themselves that shows up predictably. This prompt makes it visible.
The AI won't sugarcoat it. It'll quote your exact language back at you and show you what disappears (context, empathy, clarity) and what shows up instead (shortness, vagueness, command mode). That's behavioral evidence you can work with.
Maybe you discover you stop explaining "why" when you're stressed and just start announcing "what." Maybe your sentences get clipped and your tone shifts to pure transaction. Maybe you stop asking questions and start directing.
Whatever your pattern is, you can't change it if you can't see it. This makes it visible.
The Full Prompt Library
Resilience under pressure is one pattern. But most leaders I work with are struggling with three core behavioral shifts: change management, conflict, and delegation.
Here are five more prompts that make those patterns visible, plus a custom GPT that acts as your coaching assistant between sessions.
Change Management
Most leaders announce changes like proclamations. Then they wonder why people resist or why adoption is slow. The problem isn't the change (it's how you communicated it).
Prompt: The Announcement Pattern
I'm working on leading change more effectively. Below are the last 3 times I communicated a significant change to my team [paste emails/Slack announcements/meeting notes].
For each one, analyze:
1. Did I explain WHY this change matters, or just WHAT is changing?
2. What did I say about the impact on people's work? (Quote specific phrases)
3. Did I acknowledge difficulty/resistance, or present it as straightforward?
4. What question did I NOT answer that people likely have?
5. On a scale of "command" to "invitation," where does my language sit?
Give me one specific sentence I could add to each announcement that would shift it toward more effective change leadership.
What to feed it: Last 3 change announcements (emails, all-hands notes, team meeting summaries)
Cadence: After any major change communication
What this catches: Whether you're explaining or announcing. Whether you're acknowledging reality or spinning. Whether you're leaving space for questions or shutting them down preemptively.
Search Tip: Go to your 'Sent' folder and search for "urgent" or "ASAP." Or, simply scroll to the date of your last board meeting or crisis and grab the first 5 emails you sent that afternoon.
Prompt: The Resistance Response
I want to improve how I handle pushback on changes. Below are 5 exchanges where someone questioned or resisted a change I introduced [paste the back-and-forth].
For each exchange, identify:
1. Did I defend the decision or explore the concern?
2. Quote the exact moment where I shut down or opened up the conversation
3. What emotion is visible in my response? (defensive, dismissive, curious, frustrated)
4. What did the other person stop saying after my response?
Then tell me: What's my pattern? And give me three specific phrases I could use next time someone pushes back.
What to feed it: Email threads or Slack conversations where people questioned your decisions
Cadence: Weekly review
What this catches: Your default when challenged. Most people think they're open to feedback. Most people are defensive and don't realize it because the defensiveness is subtle. This prompt quotes your language back at you and shows you where you shut the conversation down.
Conflict
Leaders avoid conflict in predictable ways. They soften language, add unnecessary setup, use euphemisms. Then they wonder why difficult conversations don't go anywhere.
Prompt: The Avoidance Detector
I tend to avoid conflict. Below are 10 recent messages where I disagreed with someone or needed to address a problem [paste emails/Slack messages].
For each one, analyze:
1. Did I name the disagreement directly, or soften/avoid it? (Quote my exact words)
2. What euphemisms did I use? ("just checking in," "quick question," "wondering if we could...")
3. What's the ratio of setup/cushioning to actual substance?
4. If I were being direct, what would I have said instead?
Then show me: What's the pattern in how I avoid? And write me 3 opening sentences that would be direct without being aggressive.
What to feed it: Messages where you needed to address problems, give critical feedback, or disagree
Cadence: Bi-weekly
What this catches: Your avoidance patterns. The cushioning language. The setup that delays the point. You'll see how much time you spend not saying what you mean. And you'll get specific alternative language that's direct without being a jerk.
Search Tip: Search your Slack DMs for phrases like "just checking in," "thoughts?", or "a bit confused." These are often the breadcrumbs of soft conflict.
Prompt: Conflict Recovery Time
I want to understand how long it takes me to get back to effective after a difficult conversation. Below are three sequences - each one includes the difficult conversation plus my communication in the 48 hours after.
For each sequence:
1. What changed in my communication after the conflict? (Quote specific differences)
2. How long until I'm back to my normal baseline?
3. What shows up during recovery? (avoidance, over-compensation, stiffness)
4. What does "back to normal" look like for me? (Quote language that shows baseline)
Then: What's my recovery pattern? And what could help me get back to baseline faster?
What to feed it: 3 difficult conversations plus your follow-up communication over the next 2 days
Cadence: After any significant conflict or difficult conversation
What this catches: Your recovery time and what happens during it. Some people bounce back immediately. Some people avoid for days. Some people over-correct and become weirdly formal. Knowing your pattern helps you manage it.
Delegation
Most people think they delegate. Most people assign tasks with detailed instructions and call it delegation.
Prompt: Task vs. Ownership
I'm trying to delegate more effectively. Below are the last 5 times I assigned work to someone [paste the initial delegation email/message + any follow-up exchanges].
For each one, analyze:
1. Did I explain WHY this matters and how it connects to bigger goals, or just WHAT to do?
2. Did I define the outcome or prescribe the method?
3. How much context did I give? (Quote what I said about background/constraints)
4. What decision-making authority did I actually give them?
5. Grade this: Task assignment or ownership delegation?
Then tell me: What's my pattern? And rewrite one of these delegations as true ownership transfer.
What to feed it: Your last 5 delegation messages
Cadence: Weekly
What this catches: Whether you're actually delegating or just redistributing tasks with instructions attached. The AI will quote your exact language and show you where you prescribed the method instead of defining the outcome. Where you kept decision-making authority instead of giving it away.
Search Tip: Don't hunt for delegation emails. Just search from:me to:[Name of Direct Report] and grab the last 5 emails that are longer than two sentences.
Prompt: The Take-Back Pattern
I want to understand when and why I take work back from people. Below are 3 situations where I re-involved myself after delegating [paste the original delegation + the moment you jumped back in].
For each one:
1. What triggered me to jump back in? (Quote what was said or what I saw)
2. What story was I telling myself? (infer from my language)
3. Did I coach them through it or take it over?
4. What would have happened if I hadn't intervened?
Then: What's my pattern for taking things back? And give me a question I can ask myself before jumping in next time.
What to feed it: Examples where you re-engaged after delegating
Cadence: Monthly reflection
What this catches: Your trust issues. The moment where delegation becomes micromanagement. The story you tell yourself about why you need to step in. Most leaders don't realize they're taking work back (they think they're "supporting"). This shows you the difference.
How to Customize These Prompts
These six cover the most common leadership behaviors I see people trying to change. But your coaching goal might be different.
Here's the template for building your own:
1. Name the specific behavior (not "be a better leader" (that's useless)). Examples: "Stop being defensive in peer meetings," "Give feedback that changes behavior," "Follow through on commitments"
2. Identify what evidence exists. What communication do you already create that would show this pattern? Emails, Slack, meeting notes, 1-on-1 summaries, decision logs?
3. Write the prompt structure:
- Context: "I'm working on [specific behavior]"
- Data: "Below are [X examples] of [when this behavior shows up]"
- Analysis request: "For each one, tell me [3-5 specific things to look for]"
- Pattern recognition: "What's my pattern?"
- Action: "Give me [specific alternative] I can use next time"
4. Test it once, refine it. The first prompt won't be perfect. Run it, see what the AI surfaces, then tighten the questions to get more useful output.
The Custom GPT: Your Coaching Assistant
If you want something easier than copying and pasting prompts, I've built a custom GPT that understands this framework and can guide you through the analysis.
The Human Stack: Coaching AssistantIt has the full Insight → Action → Evidence framework built in, understands the three core behaviors (change management, conflict, delegation), and acts like a coaching assistant that adapts to your needs rather than forcing you into rigid templates.
You can just paste your communication and say "analyze my delegation patterns" or "help me see how I handle conflict" and it'll guide you through useful analysis.
It's trained on the methodology I use with clients (so it knows to quote your exact language, surface patterns, and give you specific alternatives rather than generic advice).
What Good Output Looks Like
Bad AI output: "You could improve your delegation by being clearer about expectations and giving people more autonomy. Consider scheduling regular check-ins to support their development."
That's generic garbage. It could apply to anyone. It doesn't quote your actual language. It doesn't show you your pattern.
Good AI output: "In all 5 examples, you explained WHAT to do but not WHY it matters. Example: In email #3, you wrote 'Can you pull together the Q3 numbers by Friday?' with no context about the board deck. You also prescribed the method in 4 out of 5 (email #2: 'Use the same format as last quarter' removes their decision-making authority). Your pattern: You delegate tasks with instructions attached, not outcomes with ownership. In email #4, you asked for 'the Q3 analysis' but specified the format, timeframe, and presentation style (that's not delegation, that's task assignment)."
See the difference? Specific quotes. Pattern identified. Behavioral evidence.
Integration with Your Coaching Work
These prompts don't replace coaching. They create a feedback loop between sessions.
The cadence:
- Weekly: Run 1-2 prompts on your recent communication
- Note the patterns that surface
- Bring them to your coaching session as evidence
- Adjust your experiment based on what you're seeing
- Repeat
This gives your coach (or your own reflection) something concrete to work with. Not "I think I'm improving" but "here's what I actually did this week, and here's the pattern that keeps showing up."
In framework terms:
- Insight: What behavior are you trying to change? (From coaching)
- Action: What are you experimenting with? (From coaching)
- Evidence: What patterns are showing up? (From AI analysis)
The AI doesn't tell you what to do. It shows you what you're doing. Then you decide what to do about it.
Where This Goes Wrong
Mistake 1: Vague goals. "Be a better leader" (AI can't help you with that). "Stop solving problems for my team" (AI can track that).
Mistake 2: Cherry-picking data. If you only feed it examples where you think you did well, you'll only get validation. Feed it the full week, including the exchanges that felt off.
Mistake 3: Ignoring uncomfortable patterns. The AI will surface things you don't want to see. That's the point. If you only accept feedback that confirms you're improving, you're not using measurement (you're performing it).
Mistake 4: Measuring instead of changing. Data collection isn't behavior change. Running these prompts weekly and doing nothing with the output is just sophisticated procrastination. The point is to notice the pattern, interrupt it, and experiment with something different.
Mistake 5: Using this to generate reports. These prompts are for you, not your boss. The moment you start thinking "I need to show evidence of improvement," you'll game the measurement. Use this to see yourself more clearly, not to prove anything to anyone else.
Start Here
Pick one behavior you're trying to change. Run one prompt this Friday on your last week of communication. See what patterns surface.
Don't try to change everything at once. Just notice what you're doing. That's the first step.
The noticing gap is why most behavioral change fails. AI can close it (not by telling you what to do, but by showing you what you're already doing).
Most people can't see their own patterns. Now you can.
What behavior are you actually trying to change? And what communication do you create that would show whether it's working?
Those two questions are where measurement starts. Everything else is just data collection.