"I'll Fix It Someday" Is Costing You Hours Every Week

The Real Cost of Procrastinated Improvements

You know the feeling. There's something in your workflow that's annoying - a repetitive task, a clunky process, a manual step that could be automated. It works fine, technically. But every time you do it, there's a little friction. A pause. Maybe you switch between windows twice when it could be once. Maybe you type out the same command with different parameters. Maybe you copy and paste data between three apps when a script could do it in seconds.

And so you think: I'll fix it someday.

The problem? Someday never comes. Not because you're lazy, but because these tasks live in a weird space - they're not urgent enough to demand attention, yet they're regular enough to waste your time over and over. And while you're waiting for that mythical someday, the cost is silently multiplying.

In my case, I remember how I had to open certain programs manually every day or even more often. How I used repetitive git commands like git add -A, git commit -m "..." and git push... over and over again.

The real damage is that you're losing time now, and you've already lost time in the past. Automation stops the bleeding.

Do The Math On Your Friction Points

Let's make this concrete. Imagine you have a task that takes 5 minutes and you do it three times a week.

Even if automation takes 4 hours to set up, you break even in 4 months and then gain 8+ hours back annually. That's just one friction point. Most people have dozens.

The math gets even better when you factor in mental friction - the cognitive load of doing something tedious. Even a task that only saves you 2 minutes but removes decision-making or attention-switching can dramatically improve focus and reduce decision fatigue. That's harder to quantify, but it's real.

The git commands I mentioned? Creating a script to replace three lines with one doesn't just save keystrokes - it cuts cognitive load. You stop thinking about the sequence and start thinking about the result. Same with opening programs: a script eliminates the manual step entirely. These aren't dramatic time savings in isolation, but they compound across dozens of daily habits.

When "Someday" Actually Kills Productivity

The insidious part is that you never see the compounding loss. You can't point to a moment and say, "There it is - my lost hour." Instead, it's invisible: thousands of small delays that add up to weeks of wasted time over a year.

But there's another cost that's even harder to see: the opportunity cost of doing unautomated work when you could be doing something that actually requires your judgment and creativity. Every minute spent on a task that could be automated is a minute not spent on something that can't be.

When Automation Actually Makes Sense

Not every friction point is worth automating. The sweet spot is when:

It's a regular task

You encounter it daily, weekly, or multiple times per week. One-off tasks usually aren't worth optimizing unless they're genuinely painful.

The payoff timeline is reasonable

If the automation takes 2 hours and saves you 5 minutes three times a week, it pays for itself in about 8 weeks. After that, it's pure time regained. Most worthwhile automations pay for themselves within a few months - the more repetitive the task, the faster the return.

It reduces mental load, not just time

This is the underrated one. Even if a task only saves you 2 minutes, if it eliminates a decision-making step, a context switch, or something you have to remember, it's worth doing. Mental friction is still friction.

You understand the problem clearly

If you're still figuring out how you should do the task, wait until you've done it enough times to know exactly what to optimize. Automating a half-formed process wastes more time than it saves.

The Exception: When Deferring Makes Sense

There are legitimate reasons to wait:

• The task is genuinely rare - You do it once every six months. Automation effort probably outweighs the return.
• Automation is genuinely uncertain - You're not sure how to approach it yet, and it would require significant learning or experimentation.
• You're in the middle of something else - You have a higher-priority deadline. But here's the key: write it down with enough detail that you could act on it later, not just a vague mental note.

The difference between a legitimate deferral and a "someday" trap is whether you can actually pick it back up. If you can't describe what you'd do to fix it, it's abandoned. If you CAN describe it, act on it while it still bothers you.

The Friction Audit: Where To Start

If you're not sure where to begin, look for these patterns:

• Tasks where you find yourself thinking, "There has to be a better way"
• Steps you do multiple times without thinking, on autopilot
• Processes that make you switch between tools or windows unnecessarily
• Data you copy and paste from one place to another
• Commands you type with minor variations repeatedly

For each one, ask: Do I do this regularly? Is there a quicker way? Would setting it up take less time than I'll save in the next 6 months?

If the answer is yes, yes, and yes - you've found your target.

The Real Shift: Treat Automation As Part Of Your Work

The breakthrough for most people isn't a specific automation tool or technique. It's treating small workflow improvements as part of the job, not something extra to do "later".

This is so true for me. I used to treat tasks worth doing as something to do outside my pomodoro time - extra work. But I realized that scheduling it during pomodoro time legitimizes it as real work, which eliminates the mental resistance that keeps tasks in 'someday' limbo. By treating it as scheduled work, I ensure it actually happens instead of being perpetually deferred.

When you notice friction, you fix it soon after - while the problem is fresh, you understand exactly what needs optimizing, and the pain is still vivid. You don't wait for mythical "someday." You carve out 30 minutes or 2 hours in the next few days and solve it.

This mindset shift changes everything because you're no longer fighting compound procrastination. You're making dozens of small decisions to improve your workflow as you go, and they accumulate into genuinely significant time savings.

Conclusion

Once you've identified a friction point worth automating, the best time to build the fix is this week - not someday in an imaginary future. The longer you wait, the more time you've already wasted. You'll be shocked at how much time it gives you back.

Found this helpful? Please share it with someone who also might find it helpful. Would you like more posts from me? Subscribe to the newsletter. Got questions? Send an email to commitnobug@outlook.com.