The Offer Has Been in Drafts Since Spring
The Program You Did Not Write
The offer is ready. It has been sitting in drafts since spring.
You know the price. You know who it is for. You decided a long time ago. And every time you open it, something in you reviews it one more time.
It was not a flaw. It was built.
The program running underneath that moment is not a character flaw you developed.
It was built for conditions that were real at the time. Under enough pressure, repeated enough, it became your default. The threat assessment that fires before you speak in a room you own. The internal committee that reviews a decision you are already qualified to make. The bracing when the win lands.
None of that was random. It was the most adaptive response available to you when it was installed.
The room has changed. The program has not been told.
Why knowing why hasn't stopped it
Richard Nisbett and Timothy Wilson showed that people are very good at explaining their behaviour and not very good at knowing what actually drove it. Petter Johansson's work found people giving fluent reasons for choices they had not made. The explanation is written after the fact.
That is why you can explain exactly why you do it, and still do it.
Larry Squire and Eric Kandel's work on memory architecture points the same way. What you can state and what you perform sit in different systems. Schwabe and Wolf's research on stress and habit leans in the same direction: under pressure, people drift from the plan toward the default.
You do not run your plan. You run your default.
What it costs a business
The cost is easy to count. A price that never gets sent. A hire that has been in drafts for two years. A proposal rewritten at 10.40 pm because that was faster than letting someone else get it wrong.
Teams carry this too. The norms built into a team in 2010 are still running the room in 2026. Nobody decided to keep them. Nobody decided to update them either.
The National Standard of Canada names the psychological hazards in a workplace. It does not name the pattern underneath them. Two different problems, one framework.
The gap between them is where the real cost lives.
A level problem, not an effort problem
You have not been short on insight. You have read the books, hired the coach, built the plan.
The pattern runs below the level that insight reaches. You have been debugging a program you did not write, using tools that cannot reach the file.
That is not a failure of effort or commitment. It is a level problem. The answer is not more understanding. It is working at the level where the pattern actually runs.
If this is landing somewhere familiar, that is the gap talking. Let's discuss it further in a thirty-minute Connection Call.
Nisbett, R. E., & Wilson, T. D. (1977). Telling more than we can know: Verbal reports on mental processes. Psychological Review, 84(3), 231–259.
Johansson, P., Hall, L., Sikström, S., & Olsson, A. (2005). Failure to detect mismatches between intention and outcome in a simple decision task. Science, 310(5745), 116–119.
Johansson, P., Hall, L., Sikström, S., Tärning, B., & Lind, A. (2006). How something can be said about telling more than we can know: On choice blindness and introspection. Consciousness and Cognition, 15(4), 673–692.
Schwabe, L., & Wolf, O. T. (2009). Stress prompts habit behavior in humans. Journal of Neuroscience, 29(22), 7191–7198.
Arnsten, A. F. T. (2009). Stress signalling pathways that impair prefrontal cortex structure and function. Nature Reviews Neuroscience, 10(6), 410–422.
