Help a New Executive Listen Before Announcing Changes

A new executive shows up with a mandate, a deadline already forming in her head, and pressure to prove the company made the right call. Announcing a fix feels like leadership. Asking questions feels slow and uncertain. Your job as a coach is to slow her down long enough to learn how the work actually happens before she starts changing it, because the changes she is picturing right now are based on almost nothing.

Why New Executives Skip the Listening Step

Most new executives do not skip listening because they are careless. They skip it because everything around them rewards speed. A board or a sponsor wants to see momentum in the first ninety days. Prior roles taught them that hesitation reads as weakness. And the people reporting to them, especially directors eager to make a good impression, tend to hand up a smoothed version of reality rather than the messy one.

That smoothed version is the trap. A new chief customer officer who only talks to her three directors hears the directors' priorities, not the actual friction in the process. She does not hear about the analyst who patches together data every Monday because a report runs late, or the account manager who quietly makes exceptions for two clients because the standard process does not fit them. When she announces a new account review cadence based on what the directors told her, she is solving for a version of the job that does not match how the job gets done. People notice immediately, and the new executive spends the next six months rebuilding trust she did not need to lose.

Prepare the Executive Before the Conversations Start

Preparation starts with naming the trap out loud. Ask the executive what she already believes needs to change, then ask her how she knows that. Most of the time the answer traces back to one or two conversations with people who report directly to her. That is a thin base for a decision that will affect dozens of people.

From there, help her build a short list of people two or three levels down who touch the process daily, not just the directors who manage it. She should include people from adjacent teams too. If the change touches account reviews, she needs someone from finance who supplies the data, someone from service who handles escalations, and someone from account management who owns the customer relationship. Six or seven conversations over one or two weeks is enough to surface real patterns without turning into a research project.

Give her three questions she asks in every conversation, worded the same way each time so the answers can be compared. Something like, walk me through the last time this process ran, what part took the most effort, and what would you change if you owned it. Coach her to open each conversation by stating plainly that she is there to learn, not to decide, and that nothing said in the room commits her to any outcome. That single sentence removes a lot of the guardedness people bring into a meeting with a new boss.

What to Say in the Room

Picture Elena, newly hired as chief customer officer, three weeks in. She tells her coach she plans to announce a new account review process at next week's leadership meeting. Her coach asks her who she has talked to about how reviews currently work. Elena says she has met with her three directors and feels ready to move.

Her coach asks her a harder question. "What have you heard directly from the people who prepare those reviews every week, not just the people who manage them?" Elena admits she has not talked to anyone at that level yet.

"Before you set a new rhythm, what do you actually need to understand?" Elena thinks about it and says she needs to know where data arrives late, which customers require exceptions to the standard process, and who is responsible for each handoff along the way. Her coach asks her to name one person from finance, one from service, and one from account management who could describe those points firsthand, and to reach out to each of them this week.

Elena schedules six conversations over the next ten days and opens each one the same way. "I want to understand how this works today before I propose anything. Nothing said here commits me to a decision." She asks the same three questions in every session, about a recent example, the hardest part of the process, and what the person would change if they owned it. Her chief of staff groups the answers by theme, data timing, exceptions, and decision rights, without attaching any comment to a name in the summary Elena reviews. When Elena finally talks to her directors, she tells them what she heard, which parts need more review, and the date she will bring back a proposed plan. She moves with purpose, and the people she talked to can see their input in what she says next.

Mistakes That Undermine the Listening Plan

A few habits quietly wreck this approach. The first is talking only to direct reports and calling it listening. Directors filter, sometimes without meaning to, and a plan built entirely on their input misses the frontline reality every time.

The second mistake is taking notes that trace back to individuals. If someone hears their exact words repeated in a leadership meeting, they stop being honest in the next conversation, and so does everyone who hears about it. Summaries should group themes, not quote people by name.

The third mistake is promising action and then going quiet. If the executive says a plan is coming by a certain date and that date slips without any word, the listening tour reads as theater. The fourth is treating listening as a box to check rather than a real question. People can tell the difference between a leader who is curious and one who is running through a script waiting to announce what she already decided. The fifth is letting listening stretch on too long. Six conversations over two weeks builds trust. Six weeks of vague meetings with no proposed date starts to look like stalling.

How to Practice and Score This Conversation

This is a hard conversation to get right on the first try, because it requires holding back an instinct to solve. Rehearsing it before the real meetings helps far more than reading advice about it. In a DealSpeak session, the executive can practice against an AI counterpart playing a defensive director who feels bypassed, or a frontline employee who is unsure whether it is safe to be candid. Running the same scenario with different reactions from the other side prepares her for the range of responses she will actually get.

Score the rehearsal on specific behaviors. Does she state clearly at the start that no decision is being made in this conversation. Does she ask open questions instead of leading ones that fish for a specific answer. Does she resist the urge to jump into problem solving the moment someone names a pain point. Does she close with a concrete next step and a real date rather than a vague promise to follow up. Those four things separate a listening conversation that builds trust from one that just delays an announcement everyone already saw coming.

If you coach executive transitions regularly, browse the HR and Leadership practice conversations for more scenarios built around this same moment, including how to Help a New Manager Understand Documentation Ownership and Access during a similar early period. It also helps to Define a Practice Outcome for Newly Promoted Managers so the rehearsal has a clear target instead of a vague sense of doing better.

Listening well in the first weeks does not slow an executive down. It gives her a plan that survives contact with the people who have to run it, and it tells everyone below her that their knowledge counts before a single decision gets made.