Adapting the Directive Approach for Executive Coaching

A problem is a repetitive sequence of behavior that fails to produce the outcome the client wants. In an executive setting, those sequences run on power, status, and the organization of the hierarchy. You do not look for the cause in the history of the individual. You look for it in the current interactions of the team. If a Chief Financial Officer fails to deliver reports on time, the early life and the inner motivations are beside the point. You examine who asks him for the reports, how they ask, and what happens when he misses. The problem is a cycle that involves at least two people.

The same strategic techniques that work in the consulting room translate directly to the boardroom, provided you change the language around them. A directive is an instruction to perform a specific action outside your meetings. You do not suggest. You do not recommend. You tell the client what to do, and you do it without apology, because the moment you hesitate the client senses your uncertainty and stops following through.

What follows is how to carry the Haley and Erickson toolkit into coaching: spotting the reward inside the stuck pattern, framing directives as experiments, prescribing symptoms, building ordeals, using pretense and secrecy, and exiting cleanly once the new sequence holds.

Finding the reward hidden in the stuck pattern

Every pattern that persists is paying off for someone. Your first job is to locate the payoff the client cannot see, often because their own courtesy or busyness is what feeds the loop.

A Director of Operations once complained that his subordinates interrupted him all day. They walked into his office without knocking to ask about scheduling and office supplies, and he had no time left for strategic planning. When I observed him, I saw that he smiled and offered coffee every time someone interrupted. He was rewarding the intrusions with his attention and his hospitality while complaining about them. His behavior invited the very thing he claimed to hate. Staying busy with small details also spared him the pressure of finishing the large strategic plan he had been avoiding. The symptom was doing useful work for him, and no insight about his character would have changed that. Only a directive that altered the social arrangement of the office could break the loop.

Once you have located the payoff, you redefine what the behavior means before you move it. Reframing does not change the facts. It changes the category the client files the behavior under, which lowers their defenses and hands you the authority to manage it. If a Chief Executive obsessively checks every email the marketing team sends, you do not call it a lack of trust. You call it a high level of dedication to the brand. You explain that this surveillance is protective vigilance that served the company well in its early growth. Once you have named the micromanagement as a tool for quality assurance, you can ration its use. A high-intensity tool wears out if you run it on every task. So you instruct the executive to apply that vigilance only between ten and eleven in the morning. For the rest of the day, he practices a different form of leadership you call observation without interference.

Hierarchy is the backbone, and most symptoms grow from confusion in it

When a client has a problem, the lines of authority are usually blurred. A boss behaves like a peer. A subordinate makes decisions that belong to the executive. Jay Haley held that a confused hierarchy produces symptoms throughout the system, and in a company those symptoms show up as missed deadlines, low morale, and constant friction between departments.

A founder once could not bring himself to fire a childhood friend who served as Head of Marketing and kept missing targets. By refusing to act as a boss, the founder taught the rest of the leadership team that the rules did not apply to everyone, and they lost respect for his authority. The friend’s poor performance was never the real problem. The founder’s refusal to occupy the top of the hierarchy was. I told him to spend one hour every Tuesday morning asking the friend for a detailed report on his recent failures. He was to stay silent while the friend spoke, offering no advice and no comfort. The directive moved the founder into the seat of the one who judges performance. The friend would either improve or find the scrutiny intolerable enough to leave.

A Senior Director had the opposite trouble. She had grown too friendly with her direct reports, lunching with them daily and trading personal secrets, so when she enforced a deadline they ignored her as an equal. The hierarchy had collapsed. I told her to stop eating in the common breakroom at once and to eat alone in her office or at a restaurant her staff did not frequent. I gave her a secret task as well: each week she would choose one person and give them a small piece of positive feedback that no one else was allowed to hear. The mystery and the controlled flow of reward re-established her at the top of the local hierarchy. The physical separation did the rest.

Framing the directive as a leadership experiment

Executives reject clinical suggestions and accept experiments that produce data. So you tell the client you need more information about how the system reacts to a specific change in their behavior, and you let them collect it.

A manager who struggled with a dominant employee got an experiment for her next staff meeting. I told her to agree with every criticism the employee raised, however absurd, and to respond each time with a task. She would say, “You are right that we could improve that, and I want a four page report on how to fix it by tomorrow morning.” The employee enjoyed complaining and did not enjoy the labor the complaint now generated. Once the cost climbed high enough, the complaining stopped.

A Chief Executive felt his board was micromanaging his daily decisions, so he sent them long defensive emails justifying every move, which only prompted more questions. I told him to stop the emails entirely for two weeks. When a board member called, he was to say, “I am working on a comprehensive report that will answer all your questions, and you will have it at the end of the month. Until then I cannot discuss the details.” By withholding information he forced the board to wait for his lead and reclaimed his position as the company’s leader rather than a subordinate to their curiosity.

Prescribing the symptom to an executive

When a leader insists they cannot stop doing something, you do not tell them to relax. You tell them to do more of it, on your schedule and under your conditions. Once a client can perform a symptom on command, they can also stop it on command. You take the power away from the behavior and hand it back to the executive.

A client who could not stop worrying about a competitor was told to worry harder, in a fixed slot. He set aside exactly thirty minutes every morning at six o’clock, sat in a hard wooden chair, and thought only about the ways the competitor might beat him, writing every possible disaster in a notebook. If a worry arrived at two in the afternoon, he told himself to hold it until six the next morning, the designated hour for professional worrying. The involuntary dread became a voluntary assignment.

Sometimes you prescribe the symptom by capping it. A Vice President of Operations named Arthur could not stop correcting subordinates in meetings. Every time a manager presented, Arthur interrupted to flag a clerical error or a font he disliked, which demoralized the staff and ran meetings two hours long. I did not ask Arthur about his childhood or his need for control. I told him his eye for detail was the reason the company was profitable, but that he was spending his most valuable asset on trivial problems. For the next three meetings he was required to find exactly three errors and point them out. A fourth was forbidden. If he spotted one, he wrote it on a slip of paper and kept it in his pocket until the meeting ended. By limiting the behavior I was prescribing it, and Arthur grew so absorbed in choosing which three errors deserved his attention that the impulsive interruptions stopped. He recovered his standing as a strategic leader.

Building an ordeal that costs more than the symptom returns

An ordeal is a task more troublesome to perform than the symptom is to give up. You attach the ordeal to the unwanted behavior so the behavior carries a price the client will not pay for long.

A client spent four hours a day checking email to avoid making difficult prospecting calls. I told him he could check his email as often as he liked, but only while standing on one leg in the middle of the company break room. The moment his foot touched the floor, the laptop had to close. The avoidance was now physically uncomfortable and socially awkward. Within a week he decided the phone calls hurt less than the exercise, and his pattern had become too expensive to maintain.

The structure is the same for procrastination. If a client stalls on a project, you let them stall, but every delay triggers a task they dislike. For one executive that meant cleaning the office kitchen or filing a stack of old receipts by hand, immediately after the procrastinating occurred. He soon found that finishing the project hurt less than the ordeal, and the symptom priced itself out of existence.

Using pretense when an executive feels like an imposter

Haley noted that a person who can pretend to have a problem can also pretend to have the solution. When a leader is paralyzed by a new responsibility, you do not offer reassurance. You hand them a script.

A newly promoted manager who felt like a fraud was told to pretend to be a manager who is not afraid. For the next board meeting I gave specifics: sit with hands flat on the table, and wait three full seconds before answering any question. I did not ask her to feel confident. I asked her to act as if she were. The board reacts to behavior and never sees the private feeling underneath it, and when they treated her with respect she began to carry more authority. The pretense became real through the feedback loop of the hierarchy.

Secrecy, gesture, and story

Secrecy protects the intervention. If subordinates know the executive is following a script, they see a puppet and the work loses its force, so you tell the client to keep the directives private from staff and often from a spouse.

A client being bullied by a senior partner got a small, odd assignment. Every time the partner raised his voice, the client was to adjust his glasses or touch his tie in a steady rhythm, and never explain why. The unexplained action shifted the dynamic. The bully grew confused and distracted, which broke the pattern of his verbal attacks, and the client felt a private power because he alone knew the rules of the game.

The same logic governs how the client talks about their own change. One executive wanted to announce to his team that he was working with a coach to improve his communication. I forbade it. His new behavior had to read as a natural evolution of his character, because confessing the source would cost him the mystery that authority depends on. Power is often maintained through what is not said.

Story carries the secret instruction when a direct directive has no purchase, as happens when a client faces a peer of equal structural power. You deliver the move inside a narrative that slips past the conscious resistance of a high achiever.

A Chief Executive feared a coup from his Chief Financial Officer. I told him about a gardener who noticed one tree growing too fast and stealing light from the rest of the orchard. The gardener did not cut it down. He trimmed the roots on one side so the tree had to spend its energy staying upright instead of growing taller. The executive understood without explanation. He reassigned the CFO to a complex international expansion that demanded all the man’s attention, moving the threat away from the center of power while appearing to hand him a promotion.

A Vice President was paralyzed by a peer who undermined her in meetings. I told her about the training of guard dogs, where the trainer wears a heavy padded suit. The dog bites the suit and believes it is winning while the trainer stays unharmed and fully in control. I had her wear a particular piece of jewelry to stand for that suit, and each time the peer attacked she touched it and reminded herself he was only biting the padding. Her posture changed from defense to amused observation, and the peer stopped, because the emotional reaction he wanted was no longer on offer.

Working with resistance instead of against it

The client will tell you why the task cannot work or why they cannot do it. You do not argue. You accept the resistance and fold it into the next directive. If a client claims to be too busy for a task, you tell them they must be busier still, and assign ten minutes every morning spent doing nothing but thinking about how busy they are. The resistance now moves them toward the goal.

You also expect systemic pushback as the change takes hold. When a leader shifts, subordinates often escalate the old problem to force a return to the familiar sequence, and you warn the client that the escalation is a sign of success. A director who began leaving the office at five to reclaim his time found his assistant suddenly delivering urgent, non-essential crises at four fifty-five. I told him to thank the assistant for the information and file it in a locked drawer, unread, until nine the next morning. By refusing to engage, he forced the assistant to either solve the problem or wait. Within two weeks the end-of-day crises stopped.

Checking the experiment at follow-up

Follow-up meetings check the results of the experiment. If the client followed the directive, you ask what happened in the system. If they did not, you treat the refusal as information about their readiness to change rather than something to scold.

A Sales Manager was told to praise his most difficult employee three times a day. He returned saying he could not, because the employee did nothing worth praising. I told him his failure to follow the instruction showed he preferred his resentment to a functioning department. The remark was not a judgment. It forced him to choose between his pride and his professional success.

You also redirect clients who try to turn the final session into a theory seminar. If an executive says they feel more confident, you ask them to name the specific actions they took this week that they could not have taken three months ago. One manager spent ten minutes of our last meeting praising my approach. I interrupted to ask whether his department had met its production goals. When he reported beating them by fifteen percent, I told him those numbers were the only evidence of his improvement that mattered. You take the blame for any odd directive so the client can save face with their team. Success is measured by the change in the organization. The client’s comfort during the process does not enter into it.

Reading the body and changing it first

A client’s posture announces the state of the hierarchy before they say a word. An executive slouching while their assistant stands over them shows you a confused power structure, and you do not need to discuss the assistant’s ambition or the leader’s confidence. You tell the executive to sit in a higher chair and to require the assistant to sit down before anyone speaks. The change in physical position changes the social reality of the office. You alter the behavior first, and the new professional identity follows it.

The same holds for visible tension. When a client says they are frustrated, you watch for the tightening jaw or the tapping pen, then you build the physical evidence into the directive. You tell them to tap the pen even faster when they speak to the person who frustrates them, turning an involuntary tic into a deliberate act. By the end of the session the client is no longer a victim of their frustration. They are a person choosing how to move their hands. You favor the smallest move that produces the largest disturbance in the failing pattern, because a change in where someone sits or who speaks first in a briefing can reorganize a whole team. Every interaction is a move on the board, and the opponent is never a person. It is the stuck pattern that keeps the organization from functioning.

Exiting before you become a crutch

You define the end of your involvement by the absence of the symptom and the stabilization of the new hierarchy. You do not wait for the client to feel confident or for the organization to applaud. You wait for the problematic sequence to fail to repeat even when its old triggers are present.

A senior partner in a law firm could not stop checking his junior associates’ work at two in the morning. After six weeks of a directive to check it only while sitting on a hard wooden stool in his kitchen, the behavior stopped. I did not ask how he felt about the new habit. I waited until he reported that the associates had completed three major filings without his midnight interference, and once that independence was established I told him our work was finished. Further conversation only risks returning the client to dependence on your direction, so you exit the system the moment the functional change occurs.

You let the client own the victory, because ownership is what makes them maintain the new behavior. I once saw an executive two years after our work ended, and he told me he had worked out the solutions to his problems on his own during a long flight. I agreed with him and never mentioned the six months of directives I had issued. A year after another engagement, a Chief Operating Officer reported that the secret meetings and back-channel complaints that had plagued his office never returned. He did not know why the culture had changed, only that the new rules for communication still held. You have succeeded when the client no longer remembers that a different way of working ever existed.

Your final tasks are often ones the client performs alone, without reporting back, marking the shift from directed action to independent leadership. I told a managing director to spend one hour every Friday morning sitting in a public park, watching how groups form and dissolve, with no phone and no notepad. The task reinforced his role as an observer of systems rather than a participant in every conflict, and because he knew he would never report on it, it belonged entirely to him.

The closing lesson you leave is that change is a matter of action rather than insight. The client does not need to understand why they had a problem. They need to follow a directive that makes the problem impossible to continue. A plant manager bullied by a union representative was told to invite the man to a meeting and spend the whole time asking his advice on a trivial matter, such as the best brand of floor wax. That moved the representative into the role of a helpful consultant on something unimportant and dissolved his aggressive stance on the serious issues. A Chief Technology Officer who explained technical details to the board was told to speak only in terms of risk and resource allocation, which forced the board to treat him as a peer in leadership rather than a technical subordinate, and the shift in vocabulary changed his compensation and his influence.

You ensure the executive can now issue their own directives. I told a department head that her job was not to be the most talented person in the room but to make sure the most talented people were doing theirs. That definition let her stop competing with her subordinates and start directing them. When the lines of command are clear, the work runs efficiently, and a practitioner who understands these principles can walk into any organization and find the missing link in the chain of authority within thirty minutes. Your task is to supply the directive that restores it. Control of the organizational sequence belongs to whoever is most willing to define the rules of engagement.