The rushed solution
Most first sessions open with a single sentence: 'I need to solve this.' The mind dislikes a vacuum; it wants to convert uncertainty into action as quickly as possible. But every rushed solution is built on a problem not yet defined — and undefined problems, whatever you build on them, only grow as you solve them.
Someone newly seated in a large chair almost always rushes the same thing in a first quarter: a visible move. A restructure, a change of personnel, a refreshed set of targets. None of these is wrong in itself. What is wrong is behaving as though a company has been understood when it has only been inherited.
The hurry tends to arrive from outside rather than from within. A new leader feels that something is expected and mistakes the expectation for a diagnosis. Those opening months are the only quiet interval in which an organization can be heard speaking in its own sentences; once the interval is filled, it does not come back.
The pressure rarely takes the form of a request. Nobody asks a new arrival to move in the opening weeks; everyone simply wonders what they will do, and unspoken curiosity presses harder than an instruction would. The urge to fill the silence belongs to the person, not to the company.
Something else is lost in the hurry. For a short while a newcomer holds a licence nobody else in the building has — the licence to ask questions that sound as though everyone already knows the answer. Why is the work arranged this way, who reads this report. The licence closes on its own, and knowing is assumed.
The coach's first job is not to speed things up but to slow them down. Because for a leader the most expensive thing is a right answer to the wrong question: it works flawlessly, advancing with great energy — in the wrong direction.
That cost rarely announces itself as a malfunction. An organization travelling the wrong way does not look chaotic; visitors tend to admire it. Meetings begin on time, the reporting holds together, everyone knows by midweek what is expected of them. The only thing missing is anyone able to ask out loud why the work is being done at all.
In a company like that the error is invisible in any single decision and obvious only in the sum. The year closes with everything delivered and nothing changed. So we treat slowing down as an act of navigation rather than a delay.
Not a problem — competing needs
What arrives as 'a problem' is almost always a collision of several legitimate needs. To grow without losing control. To decide quickly while keeping the team alongside you. To set a boundary without closing the door. These are not problems to be 'solved'; they are tensions to be balanced.
Making that distinction is half the work. Mistake a tension for a problem and try to 'solve' it in one move, and you snap the other end — which returns a few months later, usually as a larger crisis.
A founder often brings us what they call a team problem. The team is slow, waits for approval, takes nothing on. A few sessions in, that same team turns out to be circling one decision that has been pending for weeks; nobody moves because nobody has been told which way movement points. The slowness we were asked to fix is the shadow of a postponement.
This is not negligence on the founder's part. The delay usually protects two legitimate needs at once: staying flexible and appearing certain. The moment the decision is made, one of them eats into the other. Postponing is an attempt to hold both a little longer, and the team pays for the attempt in ambiguity.
In family companies the sentence we hear most concerns handing over: I want to delegate, and somehow I never do. As the conversation goes on, competence turns out not to be the subject. The tension underneath is usually this: the founder's place in the company and their place in the family hang from the same hook, and delegation pulls the hook out of the wall.
Seen that way, a handover is not a procedure but a negotiation about identity. Signing authority can cross a table in one meeting; where a person recognizes themselves cannot. Handovers made without separating the two are quietly reversed within a season.
That a problem was defined wrongly usually shows itself weeks later, in a single symptom. The remedy has been applied, nobody objected, and then the same matter returns under another name. A resourcing question comes back as one of authority, and the authority question comes back as one of communication. The same tension takes its seat each time in more acceptable clothing, and each time it is recognized later.
Working with a tension rather than a problem has a plain practical meaning. Instead of cutting one end away, we keep both ends named and adjust the ratio between them. The question stops being which side is right and becomes which side carries more weight this quarter, and when we will look at the balance again.
A right answer to the wrong question works flawlessly — in the wrong direction.
Writing the right question
In a session we spend the most time not on answers but on the question itself. We work until the problem is reduced to a single, clear sentence. Because a well-written question already carries half of its solution.
The work takes longer than anyone expects. The first sentence is nearly always a complaint: the team is slow, the board will not back me, there is no time. A complaint puts the cause outside the person, which is exactly why it comforts. The second sentence is usually a draft solution wearing the costume of a question. The real one arrives after several attempts, once the speaker has written themselves into it.
People ask why reducing a question to one sentence should take so long. Because the shorter the sentence, the less room there is to hide. A long question holds several possibilities at once and keeps its author in the comfort of having chosen none. A short one makes the choice visible; what gets discarded along with the words is the postponement.
The right question is generally smaller than the one we started with. How do I grow this company cannot be answered in an afternoon; when will I decide who runs which business next quarter can be. Large questions inspire, small questions move.
More often than not the leader already knows the answer; what they don't know is which question they're answering. Clarifying the question usually removes the last obstacle between a person and trust in their own judgment.
One more thing reduces clarity, and it arrives with the best intentions: a crowd of advisers. Each experienced person around a leader asks the question of their own trade. The lawyer asks about exposure, the finance director about cost, the board about reputation. Every answer is correct and no two belong to the same question. A leader leaves that table holding more information and less direction.
We have learned to recognize the moment in the room. Once the question is written properly, the answer does not keep us waiting; there is a short silence, and then the person says it as though they had known it for months. They had. What was missing was never information, it was permission.
A good question, then, does not produce an answer so much as expose one. And once written it stays — a sentence a person can put to themselves on a Tuesday morning with nobody else in the room. That sentence is what remains after the coach has left.
A decision is a point
The decision and the movement are easy to confuse. A decision is a point — a single moment, a single sentence. The movement is its consequence, spread across days and weeks. People rarely get stuck because they cannot decide; they get stuck because they spread the deciding across a process.
Spreading a decision across a process looks like prudence from outside. One more meeting, one more analysis, two more people consulted. Each step is defensible on its own; the sum is a condition in which nothing has been settled. The company believes it is waiting for an answer, when it has long since understood that no answer is coming.
The line between consulting and not deciding is a thin one. Taking a view serves the decision as long as it adds information; the moment it distributes responsibility it replaces the decision. The test is plain enough. A leader preparing to ask the same question a third time is no longer looking for information but for permission.
The price is usually paid by everyone except the person deciding. Uncertainty held at the top multiplies below it. Teams begin acting on their own best guesses, and a scatter of small contradictory decisions takes the place of the large one nobody made.
A good session compresses uncertainty into a decision: 'From here I will do this, because…' We place the resistances and risks plainly beside it. A risk shrinks when it is visible; it grows when it is hidden.
It matters that the decision fits in one sentence, because a decision that will not fit has not yet been made. Beside it we put a date and a condition for return: the signal that would bring us back to this sentence. A decision with a way back is easier to make than one without.
A decision also has to be announced, and that is separate work. Settled privately and never said aloud, it has not been made as far as the company is concerned.
What follows a decision asks for a different temperament. An organization changing direction shows nothing in its first weeks except noise. Reading that noise as proof the decision was wrong is how sound decisions die young.
The first lesson
The first lesson of coaching is not a technique but a stance: to see before you solve. Seeing slows you down; but here slowness is not a luxury, it's a discipline. The one who sees clearly moves fast.
In practice the stance is a modest one. Rewriting a sentence until it is honest, naming both ends of a tension, putting a date beside a decision. Nothing extraordinary happens in the room; what is extraordinary is how seldom any of it happens at a desk.
With the newly appointed executive, with the founder complaining about a team, with the family business trying to hand something over, we begin from the same place: naming what has actually arrived on the table. A tension that has been named becomes manageable long before it is resolved.
The usual objection is that weighing everything this carefully leaves no room to move. The opposite holds. Time given to seeing is paid once, at the front; the cost of work begun unseen is paid again every month.
Seeing on its own is not sufficient, and we know it. Clarity found on a Thursday afternoon does not defend itself through the following week; the calendar takes it back without a sound.
In the next piece we'll turn to the second lesson: finding clarity once is not enough — you have to turn it into a system. The third takes up choosing, because for a leader who has both clarity and a system the remaining difficulty is accepting that every yes is a no spoken somewhere else.