Essay 02 — Bruce Eickelman

Why Insight Is Not the Problem

Knowing something and deciding it are two different things. Only one of them changes anything.

Most founders who engage this practice already know what is wrong. The first session is rarely a revelation. It is a confirmation. What they are missing is not a new understanding of the problem. It is the structure that makes the response final.

This is not a criticism. It is an accurate description of what insight actually is and what it cannot do on its own.

Insight is a cognitive event. It occurs when a pattern becomes visible that was not visible before, or when a pattern that was dimly sensed becomes sharp. A founder who recognises that their business stalls because authority is concentrated, or that their pricing erodes because they never wrote down the floor, or that their best people leave because the decision-making environment is exhausting — that founder has had a genuine insight. The insight is true. The insight is useful.

And then nothing changes.

The coaching trap

The professional development industry has spent decades teaching people to equate insight with progress. A session that ends with a good realisation feels productive. The consultant who surfaces the root cause feels valuable. The founder who can name the problem clearly feels that something has shifted.

Sometimes something has shifted. But if there is no document at the end of the conversation, the decision is still open. The insight lives in the founder's head, which is exactly where it was before the session. The clarity that was produced in the room depends entirely on the founder's memory, their current state of mind, and the next pressured week that arrives and competes with everything they understood in that room.

Insight is volatile. It does not age well. The understanding that was vivid on Tuesday afternoon is hazier by Friday, and nearly gone by the time the quarter closes and the next crisis appears. This is not a failure of intelligence or commitment. It is how human memory works. Insight that is not committed to a structure dissolves back into the noise it was extracted from.

The coaching model, at its best, is very good at producing insight. It is almost entirely silent on what happens between sessions. The assumption is that insight, once produced, will translate itself into changed behaviour. Sometimes it does. Usually it does not, and no one explains why, because the model has no language for the gap between knowing and deciding.

The gap between knowing and deciding

Knowing something is a mental state. Deciding it is a commitment. Those are not the same thing, and the distance between them is where most founder-led businesses spend a great deal of time.

A founder can know, clearly and articulately, that their business needs a different pricing model. They can explain the structural reasons. They can describe the consequences of the current model. They can predict what a more appropriate model would look like. They can do all of this while continuing to operate the current model unchanged, for another twelve months, because knowing it has not become deciding it.

Deciding requires commitment to a specific outcome. It requires a named conclusion. It requires a record of that conclusion that exists outside the founder's head, in a form that persists past the current conversation and past the next competing pressure. Without that record, the decision is not a decision. It is a thought. A well-articulated, intelligent, accurate thought that has not yet become structural.

This is the distinction between coaching and architecture. Coaching is a conversation. Architecture is a construction project. The conversation produces clarity. The construction produces something that stands up when the conversation is over.

What makes a decision final

A decision is final when three things are true. The conclusion is named. The commitment period is specified. The trigger that would reopen it is written down in advance.

The named conclusion means a specific outcome has been stated, not a direction. Not "we will improve the pricing model" but "the floor rate for this service is X, effective from this date, reviewed in twelve months." Specificity is what makes the conclusion real rather than aspirational.

The commitment period means the decision is not permanently revisable under pressure. Decisions that can be reopened whenever they become inconvenient are not decisions. They are preferences with documentation. A commitment period of twelve months, or six months, or whatever is appropriate to the decision, means the conclusion holds for that period regardless of how the founder feels about it in month four.

The pre-agreed trigger is the most important element. It is the only thing that prevents the commitment period from becoming a cage. The trigger specifies the conditions under which the decision would be revisited before the period ends. A major market shift. A specific financial threshold. A change in ownership structure. The trigger is agreed at the time of closing the decision, not invented later as a justification for reopening it. Without the trigger, the decision is either rigid or meaningless. With it, it is a living structural commitment.

Until that document exists, the insight is still insight. The decision is still open. The founder still knows what is wrong, and the business is still paying the cost of that knowledge not being structural.