Turn a Leadership Aspiration Into an Observable Experiment

I want to be a better leader sounds like a reasonable thing to say in a coaching session, but it gives you nothing to work with. You cannot observe someone being a better leader. You cannot score it, and neither can they. Your job in this conversation is to take a broad aspiration and turn it into something small enough to see, test, and review before the next session. Do that well and the leader leaves with an experiment instead of a slogan.

Why This Conversation Goes Wrong

Most coaches accept the aspiration at face value and ask when the leader wants to check in again. That feels supportive, but it sets up a review with no evidence to look at. Four weeks later you ask how the leadership growth is going, and the leader gives you a feeling, not a fact. Progress becomes a matter of opinion, and opinions are hard to coach.

The other common failure is treating the aspiration as a personality problem. A leader who wants to be more strategic hears that framing and starts working on being a different kind of person, which is slow, diffuse, and nearly impossible to practice between sessions. A behavior in a specific meeting is something a person can rehearse on a Tuesday afternoon. A trait is not.

There is also a trust cost. When a leader brings you a real aspiration and the conversation stays abstract, they learn that coaching produces good feelings and little else. The fix is not more encouragement. It is a sharper question about where this shows up in their week.

How to Prepare Before the Session

Before the leader arrives, think through the settings where their stated goal would actually appear. If someone says they want to build trust with their team, that shows up in specific moments, a one on one where they usually talk more than they listen, a status update where they smooth over a problem instead of naming it, a hiring decision they made without asking anyone else. You do not need to guess the exact moment. You need three or four candidates ready so the conversation moves quickly once the leader names theirs.

Prepare your questions in a fixed order. Ask where the team would notice a difference. Ask what the leader could specifically do in that moment. Ask how they would know whether it worked. Resist the urge to suggest the behavior yourself. A behavior the leader picks is a behavior they will actually attempt. A behavior you hand them is homework, and homework gets skipped when the week gets busy.

Also decide in advance how you will handle a vague answer. Leaders often answer the first question with another abstraction, such as I want people to feel heard. Have a follow up ready that forces specificity, something close to what would you do differently in the next meeting where that matters.

What to Say in the Room

Coach Malik asked, "When would your team notice you leading differently." Priya said, "During quarterly planning. I rush through the purpose because I assume everyone already knows it." Malik asked, "What would you do differently at the next session." Priya answered, "I would open with the customer problem first and name the one decision I need from the room before we go further."

Malik asked, "How will you know whether that changed anything." Priya said, "I will ask each functional lead to say back the decision in their own words right before we close the meeting, and I will compare their answers to what I actually asked for." Malik said, "What could get in the way of that." Priya paused, then said, "A short agenda. If we run out of time, I will skip the summary and just assume it landed."

That last exchange matters as much as the first two. Malik did not stop once he had a behavior and a signal. He asked what could interfere, because an experiment that only works under ideal conditions teaches nothing. Priya now has a plan for the meeting and a plan for what happens if the meeting goes sideways, which is the more likely outcome anyway.

Mistakes to Avoid

Do not let the leader set a goal for the whole quarter. A goal that spans three months of meetings cannot be reviewed cleanly, because too many other things change in the meantime. Keep the experiment inside one meeting or one conversation.

Do not accept a behavior with no visible signal attached. If the leader says they will be more open, ask what someone in the room would see or hear that counts as open. If they cannot answer, the behavior is still too vague to test.

Do not skip the review, and do not let the review start with judgment. Ask what happened before you ask whether it worked. Leaders read a judgment first question as a test they might fail, and they start managing your reaction instead of reporting the facts.

Do not treat one attempt as proof of anything. One meeting does not make Priya strategic, and it does not make her not strategic either. It gives her one data point about whether her opening changed what the room understood. Say this plainly to the leader, because it takes the pressure off the first attempt and makes them more likely to report an honest result.

How to Practice and Score It

Write the experiment on one card with four parts. First, the setting, meaning the specific meeting or conversation. Second, the behavior, stated as something another person in the room could point to. Third, the signal, meaning what the leader will look at afterward to judge the result. Fourth, the review date, set close enough that memory of the attempt is still fresh.

Score the coaching conversation itself on whether you got the leader to name a real setting instead of settling for a category like meetings or communication, whether the behavior described could be observed by someone else in the room, and whether you asked about interference before the leader left. If all three are missing, the leader will show up at the review with an impression instead of an account.

This is a conversation worth rehearsing before you run it with a real leader, since the difference between a useful session and a vague one usually comes down to two or three follow up questions asked at the right moment. DealSpeak's HR and Leadership practice conversations let you run this exchange against an AI leader who answers in vague terms at first, the same way most people do, so you can practice pulling a real behavior out of a broad aspiration. The same discipline carries into harder conversations, such as when you need to Receive a Report About Behavior at a Work Related Offsite Event or when you need to Clarify a Chronology When an Employee Recalls Events Out of Order. Both start the same way, by turning something vague into something specific enough to act on.

Make the Experiment Small Enough to Keep

An aspiration is a direction. An experiment is something a person can actually attempt on a Tuesday and report back on by Friday. Give the leader the second thing, and the aspiration takes care of itself over time.

You can rehearse this exact conversation in the HR and Leadership practice conversations library before it happens for real. When you have this one down, read Receive a Report About Behavior at a Work Related Offsite Event next.