The Decision to Start
Find the real reason the thing you already know to do keeps not happening, and put an anchor under it instead of another explanation.
By James Schramko · Updated August 2026
You can know exactly what to do and still not do it. Not once. Week after week, while agreeing with the plan every time it comes up.
I see this more than any other pattern in coaching, and it has nothing to do with capability. You already have the answer. It is voiced, it is on the list, and the week ends with it untouched. The knowledge is there, fully formed. What moves, or fails to move, is the decision to start, and something is quietly blocking that decision every time it comes up.
Knowing It and Using It Are Two Different Things
A formula understood is a different asset from a formula deployed. I have watched the same content formula taught to four founders in the same week. All four understood it. Zero of them posted by the end of that week. Comprehension and deployment sit on either side of exactly one step, and that step is the decision to start.
Not starting does not make you stupid, lazy, or unmotivated. Something about starting is uncomfortable enough that your brain keeps finding a version of "not yet" that sounds reasonable. Rework the deck one more time. Wait until the tool is fully set up. Run it past one more person first. Any one of these can be legitimate once. Repeated versions of them are a reason to look underneath the task.
How to Spot It in Yourself
The signal is repetition, not a single missed week. The same commitment, in the same or slightly reworded form, rolling over three or more weeks with no execution between them.
Count it. A repeat-commitment counter is the simplest diagnostic you can run on yourself: how many weeks in a row has this exact action been planned and not done? One is a scheduling problem. Two might be a real obstacle. Three or more means the missed action itself is no longer the whole problem. Something underneath it needs to be named, however busy the quarter looks.
A coaching business owner I worked with agreed to submit content weekly. Week one, agreed. Week two, agreed again, nothing submitted. Week three, same. By the third week in a row, the content itself was no longer the subject. The pattern was.
The tell that separates a capability gap from avoidance: ask yourself what specifically stopped the action this week. A concrete answer, an outage, a sick kid, a genuine blocker, gives you something to solve. A vague answer, some version of "just been busy", is a sign you have not found the real block yet, and it will produce a new version of itself next week.
Why a Better Plan Does Not Move It
Re-reading the plan rarely works, because you already know it. An ecommerce founder I worked with had a specific fix identified and untouched for weeks. Every session, the fix got reconfirmed. Every session, it stayed untouched. Confirming a correct diagnosis a fourth time does not make the fifth week different. It adds a fourth data point to the same pattern.
You are not disputing the plan. Disputing would at least be a conversation. Agreeing and not moving is quieter and harder to catch, because everything about it looks like progress.
What Actually Breaks It
Two things change the outcome, and they need to happen together. Name the block explicitly, out loud, as the subject instead of the task. Then attach accountability with a dated, specific first move small enough that there is no room left for almost.
A membership business owner I worked with had gone quiet on a core marketing channel for well over a year. Every session, the topic came up. Every session, it stayed a topic. The break came from one specific test: send a single email to the list by a set date, nothing more. That one email produced a strong response rate and hundreds of new community members inside three days. The list had not gone cold. He had gone quiet on it, and the quiet had nothing to do with the list.
A professional-services founder I worked with sat on a business consolidation decision for close to eighteen months, the same conversation resurfacing without resolution each time. Once the block was named directly rather than revisited as a strategy question, he finally made the move. The strategy had not changed in eighteen months. The willingness to act on it had.
A content creator I worked with had built a sizeable following over years without it ever converting into paying clients, and the pattern was old enough that it had stopped registering as a problem worth naming. The break came when he committed to one reframe around the actual anxiety his audience carried, and published it. Nothing about the platform changed. What changed was what he was finally willing to say on it.
None of these three moved on a better explanation of the strategy. They moved on a specific action, a date, and someone outside the founder's own head holding both.
The Anchor, Not the Plan
When you catch your own repeat-commitment pattern, stop re-planning and start anchoring. Three parts.
Name it plainly. One sentence, out loud: this is the third week this exact action has come up and not happened. Do not soften it into a maybe.
Ask what is actually in the way. Not the task-level obstacle, the real one. There is a good chance you have not said it out loud to yourself either. Write the answer down. Vague answers do not survive being written.
Set one small, dated, specific first move. Not the whole plan. The smallest version of starting that produces real evidence: one email, one post, one conversation, one call. Attach a date.
The size of the first move matters more than you expect. A single test email is easier to actually send than a full campaign, and sending the small version breaks the standing pattern of not starting. Once that pattern breaks once, it tends to keep breaking.
Hold your own date first. If private deadlines have already rolled over several times, they are made of the same material as the block, so make the next one public. Give the date to someone who will ask you about it on that date. A peer, a partner, a coach. Self-start first; the outside anchor is for the commitments that have already proven they roll.
Quick Reference
- Count the rollovers: same action, three or more weeks, no execution. That is the signal, not one missed week.
- A better plan changes nothing. You already have the plan.
- Concrete stopper means capability gap. Vague stopper means avoidance.
- Name the pattern in one sentence, out loud, as the subject.
- One small, dated, specific first move. Never the whole plan.
- If private deadlines keep rolling over, make the next one public. Someone outside your own head asks on the date.
This pairs with Deployment Discipline: that playbook is about a built asset that never gets deployed. This one is about the decision to start, on any action at all, which is the layer underneath it.
Naming the block and putting a real date under the first move is one of the things we work through inside Mentor when the same action keeps rolling into another week.