Most executive coaching engagements run six months at two sessions a month. Three months suits a single defined problem, such as a transition or a particular relationship. Nine to twelve months suits a structural change in how a leader operates. The length should follow from the kind of problem, not from a package or the seniority of the client, and the engagement should end when the stated outcome is visible to others and the leader can sustain it alone.
The question of length comes up in almost every first conversation, usually phrased as "how long will this take," and I have learned to answer it with a question of my own: what kind of problem is it? The honest answer depends on that almost entirely, and a coach who quotes a length before knowing is quoting a product rather than a plan.
The Typical Range
Across the field, engagements cluster between three and twelve months. Six is the median, and for good reason. It is long enough for a pattern to become visible, for several rounds of experiment and adjustment, and for the people around the leader to notice a difference. It is short enough to keep the work pointed at an outcome.
Sessions in that period usually happen every two weeks and last sixty to ninety minutes. That rhythm gives the leader time to try something in a real meeting and see what happens before we examine it. Weekly sessions make sense in an acute period: the first weeks of a chief executive role, a crisis, a board situation moving fast. Monthly sessions almost always lose momentum; the conversation becomes a report on the month rather than work on a pattern.
What Sets the Length
Three kinds of problem, three rough durations.
A defined situation: about three months. A leader preparing for a specific board conversation, working through the first ninety days of a transition, repairing one important relationship, or getting a particular difficult decision made. The question is clear, the outcome is observable, and the work ends when it is reached. Some of the most satisfying engagements I run are this short.
A recurring pattern: about six months. The leader who takes delegations back, who avoids the hard conversation, who dominates meetings they intend to open up, who produces the same conflict with each successive chief of staff. The pattern is identifiable, but changing it takes repeated experiments, a few failures, and enough time for the new behavior to stop feeling like an act. I have written about several of these, including delegation and the conversations leaders avoid.
A structural change: nine to twelve months. Something about how the leader fundamentally operates, often lifelong: perfectionism that has become a constraint, a need for control that has outgrown its usefulness, an identity so fused with the company that every business decision is a personal one. These patterns are older than the role, they have served the person well for decades, and they do not yield to a quarter of good intentions.
What Shortens It
Readiness, above all. A leader who arrived voluntarily with a specific question moves faster than one who was sent. A leader who can hear something unwelcome without a week of defensiveness moves faster still. And an accurate diagnosis at the start shortens everything, which is why I spend the first sessions on assessment rather than action.
The other great accelerator is honesty about what the problem actually is. Engagements stall when the stated goal is the acceptable one and the real one is unspoken. The chief executive who wants "better delegation" and actually cannot trust anyone since a betrayal five years ago will make slow progress on delegation until the trust is named.
What Extends It
Two things, most often.
The first is a problem that turns out not to be a coaching problem. A leader whose indecision is an early depressive episode, whose irritability is untreated anxiety, whose "performance dip" is six months of four-hour nights and a bottle of wine every evening, will not improve on a coaching timeline no matter how well the sessions go. The honest response is to say so, refer appropriately, and either pause or reshape the engagement. I have written about where that line falls, and about why being able to see it early is the most valuable thing a clinical background brings to this work.
The second is the engagement that never ends. Coaching is a pleasant thing to have in one's calendar: a confidential hour with someone intelligent whose only interest is you. It is easy for that to continue past its usefulness. When I notice an engagement has become maintenance rather than work, I say so, and we either find a new question worth working on or we close.
When to Stop
An engagement should end when three things are true. The outcome we stated at the start is observable to the people around the leader, not just to the leader. The leader can notice the old pattern reasserting itself and correct it without a session. And the leader knows what the early warning signs of relapse look like and what they will do about them.
The close should be planned, not abrupt. Over the last few sessions we consolidate what changed and rehearse what the leader will do without me. Some return later with a new question, which is entirely appropriate. What I try to prevent is the relationship that drifts on because neither party raised the question of its purpose.
If you want an honest estimate of how long your particular problem would take, that is something a free consultation can usually answer, and I will tell you if the answer is "this is not a coaching problem at all."