The session was good. The client was engaged, articulate about the goal, and entirely convincing in their expression of genuine desire for the outcome. By the end they had a specific next step: small, clear, time-bound. They said they would do it. A week later, they hadn't. This isn't the first time with this client, and the practitioner is working out whether the problem is motivation, commitment, or something else entirely.
It's something else entirely.
The wrong frame
"Motivation" is the most common explanation practitioners reach for when a client doesn't follow through, and it is almost always the wrong one. Not because motivation is unimportant — it matters — but because treating follow-through failures as motivation failures leads to the wrong interventions. You work on building the client's motivation through vision work, values clarification, and outcome visualization, when the actual problem is upstream of motivation. The client is already motivated. They want the goal. They said they would take the step and they meant it when they said it. The motivational state at the end of the session was genuine. The gap between that state and the absence of action isn't explained by insufficient desire.
The more precise frame is this: wanting and deciding are different cognitive states, and the client is often in the first without having crossed into the second. Wanting a goal is a state in which the goal is appealing, the outcome is desired, the person genuinely endorses its value. Deciding to pursue the goal is a different state — one that involves commitment, which includes a willingness to experience the discomfort, inconvenience, or cost that progress will require. Most people move through coaching sessions in the wanting state and do not cross the threshold into the deciding state, partly because the session environment is one of high support and low friction, and the decision would need to survive the following Tuesday's friction.
Implementation Intentions: The Research on If-When-Then Planning
The implementation intentions research
Peter Gollwitzer's research on implementation intentions offers one of the most practically useful bodies of evidence available here. Gollwitzer showed that follow-through increases substantially — more than exhortation, motivation-building, or accountability structures — when the intention is specified as an if-when-then plan. Not "I will exercise more" but "When it is Tuesday at 6:30am and my alarm goes off, I will get up and go directly to the gym without checking my phone." The specificity of the cue and the action is what drives the difference. The intention gets attached to a specific context, which then serves as the trigger rather than an internal state that may or may not be available when the relevant moment arrives.
What this means for practitioners is that the action step at the end of a coaching session needs to include the specific context, not just the action. "I'll have the conversation with my manager" is an intention. "When I'm in the Monday one-on-one and she asks how things are going, I will say 'I'd like to talk about the project timeline'" is an implementation intention. The latter is substantially more likely to happen — not because the client became more motivated, but because the cognitive work of deciding when and how to act has been done in advance, in a low-friction environment, while the motivation is still intact.
Wanting vs Deciding: Why the Gap Between Them Explains Most Stalled Goals
The identity dimension
There is a second barrier to follow-through that implementation intentions don't fully address: the action must fit the client's self-image to survive into the next Tuesday. If the action step requires the client to behave in a way that conflicts with their operational identity — who they understand themselves to be in an embodied, daily sense — the action is likely to be blocked not by lack of intention but by the identity system doing what identity systems do: maintaining behavioral consistency with the self-image.
A client who genuinely wants to start a side business and genuinely agreed to spend two hours this week working on the business plan is less likely to do so if their operational identity says "I'm someone who thinks about doing this, not someone who does it." The action step is clear. The intention is real. The identity system finds reasons why this particular Tuesday isn't the right one. This is not conscious resistance. It's the self-image running its default programming.
This is relevant for practitioners because it changes the target of the work. Following through on action steps repeatedly — even small ones, even imperfect ones — is not just about producing outcomes. It is the mechanism through which the operational identity updates. The client who takes the small step and records that they took it is adding to an evidence base that the identity system will eventually have to account for. "I'm someone who starts things" is a claim that becomes more available as a self-description when there are specific instances of starting things in the record.
What practitioners can do differently
The design of action steps matters more than their ambition. An ambitious step that doesn't happen produces no evidence and may produce negative evidence — the missed step becomes one more entry in the file that says "I say I'll do things and don't." A small step that happens produces positive evidence, and positive evidence compounds.
Some practical implications: The implementation intention specification — when exactly, where exactly, what exactly — should happen in the session, not be assigned as homework. If it's done in the session, the client leaves with a formed intention rather than a task to figure out later. The action step should be genuinely doable in the current context — not easy by design, but not requiring a Tuesday that's better than Tuesdays usually are. And the follow-through conversation should ask not just "did you do it" but "what did it feel like to do it" and "what does this tell you about who you're becoming." The identity-relevant information is embedded in those questions.
A structural tool
MyDopa operates as follow-through infrastructure in this context. The MyHGY™ Method gives clients a daily structure for recording what they actually did, in specific enough terms that the action becomes a data point in the identity file rather than just a task completed. In a coaching context, a client using MyDopa comes to sessions with a concrete record of what they followed through on and what they didn't, which changes the conversation from "what happened this week" to "what does this week's record tell us about what we're building." The tool doesn't replace the coaching relationship. It provides the evidence base that the coaching conversation can then work with — and it gives the client something to carry forward between sessions that builds the identity picture one entry at a time.