Why Do I Procrastinate Even When I Have Time?
What would you do with an extra 20 hours a week just to work on your business?
Not theoretically. If I handed you those hours tomorrow, could you tell me exactly what you would work on, when you would work on it, what order the work needed to happen in, and what had to be finished before you moved on?
One of my clients, Chris, had those 20 hours. She was using them, too. Emails got answered. Ideas got researched. Files got reorganized. Plenty of things came off the list.
But the networking wasn't happening. The blogs weren't getting finished. And the work most likely to grow the business kept getting pushed to next week.
It would be easy to call that procrastination. More specifically, it looked a lot like productive procrastination: doing legitimate, useful work while the actual priority stays unfinished.
But calling it procrastination doesn't tell us what to fix.
Chris didn't need more time. She needed those 20 hours to come with better instructions.
Chris's situation is a useful example of a broader problem: having enough time and having an executable plan are not the same thing. When someone has time available but still isn't completing the intended work, it is tempting to jump straight to motivation, discipline, distraction, or procrastination. Before doing that, I want to know how much decision-making the plan is still leaving until the moment of action.
A calendar can tell you when to work. It cannot make a vague task executable.
Key Points
- Having enough time does not automatically mean you have an executable plan.
- Tasks that contain unresolved decisions create additional work at the exact moment you are trying to act.
- Productive procrastination describes what you are doing, but not necessarily why you are doing it.
- A useful test for clarity is whether you can begin the task without first making another decision.
- Once a task is clear enough to execute, more planning can become another way of postponing action.
- If clearer instructions do not change execution, it is time to investigate a different cause rather than endlessly refining the task.
How Many Decisions Are Hiding Inside Your To-Do List?
A task can look specific because the words are familiar. “Network.” “Write the blog.” “Follow up.” “Work on the offer.” You understand what all of those mean in a general sense, but understanding the category is not the same thing as having an executable next action.
Consider how much work can still be hidden inside four ordinary business tasks:
| Your plan says | Decisions still hiding inside it |
|---|---|
| Network | Who should I contact? Why them? What should I say? What am I asking for? Where will I track the conversation? |
| Write a blog | What topic? What angle? Which search intent? What examples? What CTA? What standard makes it ready to publish? |
| Follow up | With whom? About what? By email or LinkedIn? What should I say? What outcome am I trying to create? |
| Work on my offer | Which part? What needs to be decided? Which document should I open? What specific output am I creating? |
This does not mean every decision needs to be made days in advance. Running a business requires judgment, and no useful planning system eliminates that. The issue is whether your plan leaves so many decisions unresolved that you have to reconstruct the work every time you sit down to do it.
When that happens, execution time quietly becomes planning time.
That also helps explain why easier work can become so appealing without assuming you are consciously avoiding anything. An email already contains its next action. The vague project does not. One offers an obvious place to begin, while the other asks you to create one.
Productive Procrastination Is a Behavior, Not a Diagnosis
This is where I think the usual conversation about procrastination becomes too simplistic.
If you planned to spend an hour on sales and instead answered email, I can observe what happened. The priority was replaced by another useful task. That fits what I describe as productive procrastination.
What I cannot determine from that behavior alone is why the replacement happened.
Perhaps the sales task was vague and you did not know which leads to contact. Perhaps you were trying to fit more work into the day than your actual capacity allowed. Perhaps the sales strategy itself was poor, and continuing to execute it would not have been a particularly good use of your time. Perhaps the strategy was fine but the way you were trying to implement it did not fit your business. Or perhaps the task was clear, reasonable, and workable, but something consistently changed when it was time to sell.
Those situations can look remarkably similar from the outside. They do not require the same solution.
This is why simply deciding “I procrastinate” has limited practical value. It may accurately describe the pattern, but it can also send you toward discipline, accountability, habit trackers, or productivity systems before you have established that any of those things address the actual cause.
A better question is not only “Why am I procrastinating?” but “What is this task still requiring from me before I can act?”
A Simple Test for Whether Clarity Is the Problem
One of the fastest ways to test this is to choose a task that keeps getting carried forward and ask:
This is a more demanding question than whether you generally know what to do.
Suppose “follow up with networking contacts” has been on your list for three weeks. You understand networking. You know follow-up is important. You may even have time reserved for it.
But if you sit down and still have to decide who to contact, which person should come first, where their information is stored, what you are following up about, what you should say, and what you want to happen next, the task is not as ready to execute as it appeared.
The problem is not that decision-making is inherently bad. The problem is when the decisions are being made. If every work session begins by reconstructing the purpose and sequence of the work, part of every work session is consumed before execution really begins.
In that situation, I would not start by trying to become more disciplined. I would finish enough of the instructions to make the next action obvious and then see whether execution changes.
What an Execution-Ready Task Actually Looks Like
Making a task executable does not require turning your business into a collection of 14-step standard operating procedures. In fact, excessive planning can create its own execution problem. The goal is not maximum detail. It is enough detail that the work can begin without another round of unnecessary decision-making.
That is usually enough structure to turn a vague intention into something you can actually begin.
Too vague: Work on the blog.
Better: Draft the blog.
Execution-ready: Wednesday at 9:00 AM, open the Week 3 outline and draft the first 500 words. Stop at 500 words. Editing happens Thursday.
Too vague: Network.
Better: Reach out to potential referral partners.
Execution-ready: Monday at 10:00 AM, open the approved networking list and send the saved introduction message to the first three people. Log each contact after the message is sent.
The second versions carry more of the decisions for you. You do not have to determine the scope after the work block begins, and you have a clear point at which the current action is complete.
This matters because vague completion criteria can create almost as much friction as vague starting points. A blog can always be improved. A website can always be updated. A networking list can always contain more names. If “done” means there is no possible improvement left to make, the task has no functional finish line.
For business execution, done usually needs to mean that the work has met the standard required for its current purpose.
When Getting Clearer Becomes Another Way to Procrastinate
There is an important limit to this advice.
Once you discover that vague tasks can create execution problems, it is very easy to start solving everything by making the plan more detailed. You break a task into steps, then break those steps into smaller steps, reorganize the project-management system that holds them, and perhaps research a better method for organizing all the newly clarified tasks.
At that point, clarity is no longer reducing the distance between intention and action. It is increasing it.
You need a stopping rule.
Before beginning, you should know the next observable action, have what you need to complete it, know when you intend to do it, and have a reasonable definition of completion. Once those conditions are met, the useful next step is no longer additional planning. It is execution.
This is particularly important if you tend to stay in research mode. Research can be a necessary part of a project, but there is a point at which another article, tool comparison, training, or round of preparation stops answering a necessary question. It simply postpones the point at which the plan has to be tested.
A clear plan should make action easier to begin. If your attempts to create clarity continually postpone action, you have reached the point where planning itself needs to be questioned.
What If Clarity Does Not Fix the Problem?
This is the part I do not want skipped, because otherwise “make the task clearer” simply becomes another universal productivity prescription.
Suppose you take the task that keeps stalling and make it genuinely executable. You know the next action. You know when you intend to do it. You know what follows it and what completion means. You have the necessary information and resources.
Then the work block arrives and the action still does not happen.
That result does not mean you failed to create enough clarity. It may mean clarity was not the primary problem.
At that point, continuing to break the task into smaller pieces can become a distraction from the next diagnostic question. You need to look elsewhere.
The strategy itself may be wrong. A perfectly clear action can still be a poor business decision. Your capacity may not support the plan you created. The strategy may be sound, but its cadence, channel, workflow, structure, or expectations may not fit the person or business actually responsible for executing it.
And sometimes those practical pieces hold up. The action makes sense, the instructions are clear, the workload is realistic, and the execution method fits, yet the same specific action still stalls when you try to do it.
That is when investigating an execution block becomes much more useful.
This sequence matters because I do not want to turn every stalled action into an internal problem. If the task is vague, fix the task. If the strategy is poor, fix the strategy. If the plan does not fit, change the plan. Block work becomes appropriate when the practical explanations have been addressed and something is still consistently interrupting execution.
If you want to look at that broader diagnostic process, Why You're Stuck and How to Fix It Fast is the useful next read.
Before You Diagnose Procrastination, Test the Instructions
If an important task keeps moving from one week to the next, you do not need to diagnose your entire relationship with productivity. Start with one stalled action and examine what it actually requires.
Ask whether you could begin it without first deciding what the task means. Check whether the next action is visible, whether it has a real place in the week, and whether you know what completion looks like. If those pieces are missing, finish the instructions and then run the plan.
The important part is the test.
If clearer instructions change execution, you have useful evidence that clarity was contributing to the problem. If they do not, that is useful evidence too. You can stop endlessly reorganizing the task and move to the next possible cause.
The goal is not to create the perfect plan. It is to make the plan clear enough to reveal what happens when you actually try to execute it.
That is how you stop guessing at procrastination and start solving the problem that is actually there.
Watch the Video
In this week's video, I use Chris's 20-hour workweek to show what a clarity problem can look like and where Clarity fits in the larger execution diagnostic.
Why Do You Keep Saying One Thing and Doing Another?
If you keep making a reasonable plan and then doing something different when it is time to execute, my free 7-block self-scan can help you look at where the breakdown may actually be happening.
Use the Free 7-Block Self-Scan
About Jennie Hays
I'm Jennie Hays, the Execution Block Specialist, a Brainspotting Practitioner, and business coach for coaches, consultants, and service-based entrepreneurs.
My Aligned Execution Method combines Strategy Alignment and Rapid Block Resolution so we can identify whether execution is being interrupted by the practical plan or by an internal execution block and work on the problem that is actually there.
Sometimes that means challenging the strategy or changing the structure, workload, cadence, workflow, or expectations. When those practical pieces are workable and an internal execution block remains, Brainspotting is one of the tools I may use to work directly with that block.
The point is not to get better at forcing yourself through the wrong solution. It is to solve the right problem.
Frequently Asked Questions
Why do I procrastinate even when I have enough time?
Having enough time does not guarantee that the work is ready to execute. If you still need to decide where to start, what comes next, what resources you need, or what counts as finished, unresolved decisions may be contributing to the stall. Making the next action executable is one practical explanation to test before assuming the problem is motivation or discipline.
Is procrastination always caused by a lack of clarity?
No. Procrastination or stalled execution can have several causes. The task may be unclear, the strategy may be poor, the workload may exceed your capacity, the execution method may not fit, or an internal execution block may be involved. Clarity is one possible cause to test, not a universal explanation.
What is productive procrastination?
Productive procrastination is when legitimate, useful work repeatedly replaces the action you intended to prioritize. You may finish plenty of tasks while the work you specifically intended to complete keeps moving to another day.
How do I know if a task is specific enough?
A useful test is whether you could begin the task without first making another decision. You should know the next observable action, have the information or resources needed to do it, know when you intend to act, and have a reasonable definition of completion.
Can breaking tasks into smaller steps become procrastination?
Yes. Breaking a task down is useful until you have enough information to begin. Once the next action is clear, continuing to outline, organize, research, or redesign the system can become another activity that replaces execution.
What if I know exactly what to do and still don't do it?
Stop assuming you need to make the task even smaller. Check whether the strategy is sound, whether the execution method fits you and your business, and whether you realistically have the capacity. If those practical pieces hold up and the same action still repeatedly stalls, an execution block becomes more useful to investigate.
Read the Full Video Transcript
Jennie Hays (00:00)
What would you do with an extra twenty hours a week just to work on your business? No, really. What would you do with it? Could you create a clear plan for all twenty hours? Would you know exactly what to work on, when to work on it, and what needed to be finished before you move to the next thing? I had a client, Chris, and that was her exact problem.
She had twenty hours every week set aside for her business. She answered emails, researched ideas, reorganized files, crossed plenty of things off her list. But the networking never happened. The blogs weren't finished. And the work that could grow her business just kept getting pushed to next week. Chris didn't need more time.
She needed to know exactly what those 20 hours were for. Hi, I'm Jennie Hays I'm the Execution Block Specialist, and I help coaches, consultants, and service based entrepreneurs figure out why the strategies that they're using are not becoming consistent action and turning into results. In the last video we looked at S for strategy. Today we're moving to C for clarity. Chris thought she knew what to do. Market the business, write blogs.
Network. Follow-up. Those sound like instructions until you try to execute them. Work on marketing is not a task. It's a category, and it contains actions as well as decisions. And every time Chris would sit down, she still had to decide what matters most, where do I begin? What comes next? And when is the work finished?
The first part of every work block was spent rebuilding the plan. That's when easier tasks start looking extremely productive.
There's always an email to answer or a tool to research or a file to organize. The tasks still were real, but they consumed the day without completing the work the business needed. She needed clients. This often gets called productive procrastination.
But let's be honest, you can't consistently execute instructions that you haven't written yet. A goal tells you where you want to go. Strategy is the map. Clarity is knowing exactly what step and in what order.
A goal tells you where you're gonna go, like a map. I want to go to the aquarium. Strategy is the plan to get there. Well we're gonna go through Victoria and on down to Corpus Christi. Clarity is knowing that I leave the driveway, I make a left, I go to the end of the road and make a right, knowing what step, in what order, what to do next and what being done means. I get to the aquarium.
Launch the offer is a project, not a plan. Open the sales page draft and write the section explaining who the offer is for. That's an action. If you cannot begin without making another decision, you probably haven't narrowed it down to what the next action is yet.
Chris's networking time still required her to decide who to contact, why they made sense, what to say, and what she wanted to happen afterwards.
The calendar contained the time, but it didn't contain the instructions. It didn't contain the clarity. Clarity also requires an order. A blog might require choosing the topic, outlining, writing, editing, adding links, uploading, and finally publishing.
Call all of that write a blog, and you've hidden seven different actions inside one task. A list tells you what exists, a sequence tells you what happens next. And then you need the finish line. A blog can always be improved. A website can always be updated. A networking list can always include more people.
If done means nothing could possibly be improved, the task never will end. Done should mean that the work has met the standard required for its current job.
For Chris, we stopped treating those twenty hours as one large container called business time. Similar work was grouped together, higher value work received defined time before the administrative tasks could consume her day. She did not need every minute controlled. She needed to enter a work block without having to renegotiate its purpose every time.
Once the plan carried more of those decisions for her, she actually needed less time and she started finishing the work that had been sitting on the list undone. From the outside, it looked like productive procrastination. but calling it that doesn't tell us what to fix.
The plan was just asking her to make too many decisions instead of a single forward motion. Now I want you to look at the task that you keep carrying forward. Do you know exactly what your next step is, the next action? Do you know when it will happen? What comes after it, and what done actually means? If not,
Finish the instructions before you diagnose it as a stall. Then try the plan. If the work moves, clarity was the issue. But if the strategy makes sense, the instructions are clear.
But you're still not getting forward movement? Now we go on to A for alignment. Because a perfectly clear plan can still fail when it was designed for a person or business that doesn't exist.
In the next video, we're going to look at what happens when the strategy makes sense for what you're doing. The instructions are actually quite clear.
But the way you're trying to execute them doesn't fit.
