A month is not sessions times interval
Almost every executive asks the same question before starting a coaching process: how many months will this take. A short range answers it honestly enough — most processes run three to six months — and the range is accurate. What the range does not explain is where it comes from, and that turns out to matter more than the number itself.
The arithmetic looks simple: one meeting every two weeks, over six months, comes to twelve meetings. In practice, processes do not run on that arithmetic. Two engagements with the identical number of sessions can occupy very different amounts of calendar time, and the gap between them is not random.
On a corporate calendar, a month is a more visible unit than a session. A budget cycle, a performance review, a board meeting are all measured in months, not sessions. That's often why the question comes from the company sponsoring the engagement rather than from the executive themselves, and why the reasoning behind the number gets asked about as much as the number itself.
The pace of the early months
Early on, the rhythm is fixed: every two weeks, sixty to ninety minutes. That regularity is deliberate — frequent contact keeps a newly named issue on the table before it can drift back out of view. What keeps the first half of the process moving quickly is how recently the issue was named, not how motivated the executive is. We've written separately about the rhythm inside a single session.
How that early phase works is something we covered in the piece on session count. The question here is different, because what actually sets the total number of months is not decided in the early phase — it's decided in the second half.
A process ends by widening, not by stopping short
The rhythm changes in the second half of a process, and the change is not incidental. Meetings that began every two weeks stretch to every three, then to once a month. Frequency drops; the process has not ended, it has widened.
- The first two to three months: every two weeks, while the issue is still newly named.
- The middle stretch: every three weeks, while a behavior is tried out again in the actual week rather than in the room.
- The final phase: once a month, to see what holds without the room in it.
What stretches the interval grows the months, not the sessions
This last step grows the total month count independently of the session count. Six meetings held every two weeks close out a process in three months; the same six meetings, with the last two or three spread to a month apart, stretch that same process to five or six months. The number of sessions is identical. The calendar is not — and the number an executive is actually asking about is usually this second one.
These three stages don't run in the same order or at the same length for everyone; the middle stage might take six weeks for one executive and three months for another. The real measure isn't the calendar — it's how many times the issue has actually been tried out in a real week and carried back into the room. An executive who shows up every two weeks but tries nothing in between has logged twelve meetings without ever clearing the second stage.
Widening is a test, not a saving
Reading the widening as a way to shorten the process, or soften the budget, is a misreading. What gets tested once the interval opens is whether the room itself is still necessary. An executive who still needs to come back every two weeks has changed a habit, not the underlying pattern.
Moving to monthly check-ins is how the field tests whether a change holds without the room. A relapse in this phase — slipping back into the old pattern — is not a failure. It is information: it shows which part of the change still needs support, and the interval can be tightened again if it does.
It resembles a coach at a gym gradually spacing out sessions with an athlete: the point isn't to let the athlete go, it's to see whether they can still perform the movement without the coach standing there. The difference in coaching is what's being tested — not a movement, but whether a decision or a behavior still holds under pressure, and pressure only shows up in real weeks and real meetings, not in the room.
A relapse is a signal, not an ending
This is why a well-built widening phase expects a relapse, and sometimes looks for one. The observation criteria written down at the start of a process turn into a measuring instrument here: when the interval opens, do those observations still hold, or were they only holding because the room was showing up so often.
Moving to monthly check-ins is how the field tests whether a change holds without the room.
The same session count produces a different month count
The pattern from the field is this: an honest answer to "how many months" asks first whether a widening phase will happen at all, before it asks how many sessions are planned. A short, decision-focused process usually doesn't need one, because what's changing is a single decision being made, and there's no reason to monitor for months whether a decision holds.
In a process aimed at a behavior or a role, the widening phase is part of the work, not an optional extension. Skip it, and the process looks complete by session count while the durability of the change was never actually tested.
What the question is really asking
So underneath "how many months" usually sits a second question: how will we know the change has held. The month count depends on the answer to that second question, not the first — and we talk about it in the first meeting, as part of how we work from the start.
Skip that distinction at the start and both sides end up wrong. The executive treats the process as finished once the sessions run out; the coach still sees the widening phase as unfinished work. Both positions look reasonable, because each is answering a different question — one about sessions, the other about durability.
From the room
The shortest processes are the ones that never need a widening phase, because the issue was already narrow and a single decision away from being closed. The longest processes are not the failed ones — they are the ones that took the widening phase seriously; the month count grows there because that's where the real test happens.
Long is not the same as unsuccessful
A process running long is not a sign that it's going badly — it's a sign that a real test was run at the end of it. A short process that ends without ever widening may never have run that test at all; the change looked right in the room and was never tried outside it.
So the most honest answer to a client's question about months is not a number. It's a question of our own: will there be a widening phase at the end of this, or not. Once that's answered, the number of months writes itself.