Forced Implementation

Insight creates a window. It is brief. It is fragile. And it closes faster than most people realize.

Most learning systems defer action. They end with encouragement: go apply this, try this when you get back. This sounds respectful. It is also ineffective.

The window closes on the walk to the car.

Forced implementation does not mean coercion. It means designing learning so that the first meaningful action happens before exit.

Not a worksheet about the action. The action. A conversation held. A calendar block placed. A default changed. A message sent. A standard named in front of the people who will have to live with it.

When people act, even imperfectly, they stop seeing themselves as someone who intends to change and start seeing themselves as someone who has begun.

Intention feels like work. The brain files it next to completion. That is why a powerful session can produce a quiet week: the person already had the experience of having decided.

Implementation before exit interrupts that filing. It converts a state into a fact. Facts commute. States do not.

If the first move is allowed to wait for a better afternoon, it will wait for a better quarter. Design the first move as part of the session, or admit you designed a feeling.

It looks like time on the agenda that cannot be stolen by more slides. It looks like the real tool, not a facsimile. It looks like a witness — a partner, a manager, a peer — who will see whether the move occurred.

It looks slightly uncomfortable, because the greenhouse is being asked to produce a field plant before the doors open. That discomfort is the point. Transfer starts while the conditions of learning still exist, then walks out with the person.

Leave intending to start, and the environment will finish the sentence for you. Leave having already begun, and the environment has to contend with a behavior that already has a history.