There's a piece of advice I try to follow: if you can get it done in under two minutes, do it now. Don't write it on a list, don't push it off, just do it. That way the small stuff doesn't pile up and overwhelm you later. But the key is recognizing exactly what tasks will honestly take you two minutes or less.

When I was younger and just starting out as a developer and consultant, I was absolutely horrible at estimating how long things would take. What I thought was a "quick two-minute job" often turned into two hours, because I would keep thinking, "Oh, then I can add this," or "Oh, I should fix that while I'm here." Before I knew it, I was way beyond two minutes. I had the same issue with clients. I'd look at a project and say, "No problem, two days max." I'd promise delivery in a week, and three weeks later I was still hammering away.

But here's the thing: that's a skill you get better at over time. The more projects you do, the better you get at recognizing what's really involved. When a client describes something that "should only take two minutes," I know from experience it almost never does. What looks simple from the outside usually means opening the database, digging into the code, testing, retesting, and making sure nothing else breaks. Quoting jobs, setting boundaries, and knowing what truly qualifies as a two-minute task are all practiced skills. I'm much better now at spotting those real two-minute tasks, and I try to knock them out right away when I see them - but I also know when to push back if someone else is underestimating for me.

And this is exactly why I stopped accepting file attachments a long time ago. People would email me their Access databases and say, "Can you take a quick look?" But even before I can open it, I've got to save the attachment, run it through a virus scan, and then manually check the VBA code to make sure there's nothing malicious hiding in there before running it from a trusted folder. That alone takes five minutes. Only then can I even start looking for their actual problem. Suddenly the "quick two-minute fix" has already eaten up a chunk of time.

I eventually blocked images too - my mail server just deletes them. If someone wants help, I tell them to post screenshots in the forums instead. That way I can skim through at my own pace when I have time. Sometimes you have to set those boundaries. Because even something as simple as opening an email attachment isn't really quick - it can take five to ten minutes, and in consulting, that's billable time. (1)

And this sneaks into all aspects of life too. In fitness, you finish a set of chest presses and think, "I'll just do one more quick drop set." But that "quick" set really means changing weights, adjusting the bench, resting, and now it's 10 minutes instead of two. Or take driving. Google Maps says the appointment is 15 minutes away, so you leave exactly 15 minutes before. But that doesn't count time to put your shoes on, start the car, lock up the house, tell your dogs you'll be right back, or hit a couple of red lights. That's why I say, if you're not early, you're late.

The truth is, humans are pretty bad at predicting how long tasks will actually take. We underestimate, we get distracted, or we keep "gold plating" things that were already good enough. Which is why I try to keep Scotty's wisdom in mind: always overestimate your completion times. He would tell Kirk a repair would take four hours, then finish in one, and look like a miracle worker. That's not deception, that's buffer.

So yes, if you can truly get it done in under two minutes, do it right now. But if you're like me, make sure you're honest with yourself about what "two minutes" actually means. If it's going to sprawl, put it on the to-do list where it belongs.

LLAP
RR

(1) I don't even do consulting anymore, but I still like to help people when I can. I don't mind hopping in the forums now and then to answer questions, and my moderators do a fantastic job of that too. But I had to set a boundary for my own sanity. I don't accept technical questions by email anymore. A little question here and there doesn't seem like much, but some days I was getting a dozen of them, and that can eat up half a day. That's why I had to make a strict rule: all technical questions go in the forums.