Are You Going To Do It

What Actually Happens When You Ask Yourself This Question

I run into this every time someone asks me about their inbox zero fantasy. The phrase isn't a methodology I can point to in any book. It's more of a gut-check ritual people use when they're staring at a task list and trying to figure out which items are real obligations versus imaginary ones. I've been doing it long enough to know when it works and when it just delays the actual work. The basic mechanism is dead simple. You look at something you feel you should do, you ask yourself "are you going to do it," and if the answer isn't an immediate yes, you either schedule it or drop it. No third option. No gentle persuasion. That's it. The friction comes from the honesty part, not the complexity part. I first used this when I was managing a content pipeline at a small publication. We had roughly forty stories in various states of completion at any given time, and half of them were quietly rotting. My editor made us run through every single draft and explicitly answer that question for each one. If we weren't going to finish it this week, we archived it. The result was we went from forty hanging projects to about seven active ones, and our output actually increased because nobody was spreading themselves across a dozen half-finished pieces.

The real utility here isn't the question itself. It's the forced closure it creates. Most people operate in what I call chronic open-loop mode, where they keep thirty things mentally active simultaneously instead of committing to three and dropping the rest. This cuts through that paralysis with a binary filter. Here's the part nobody mentions: the question only works if you actually respect your own answer. I watched several people use this as a procrastination tool. They'd ask themselves and then say "not right now" and immediately move to the next item without scheduling it. That's not using the method. That's just deferring the discomfort. If you're going to drop something, commit to dropping it. If you're going to keep it, put it on a calendar with a date. There's also a specific edge case that trips people up. Sometimes you genuinely want to do something but lack the resources right now. The answer to the question in that scenario is yes, you will do it, but you need to identify what's blocking you before you close the loop. I ran into this with a podcast episode I'd been carrying around for three months. I kept answering "I'll do it eventually" which is just the question without the discipline. The moment I wrote down that I needed a guest booked before I could record, the task stopped being abstract and became a concrete next action. That distinction matters.

The counter-intuitive thing about this approach is that it usually makes your to-do list longer in the short term. When you start being honest about what you're actually going to do, you realize you've been lying to yourself about a bunch of things, and suddenly you have to account for all of them properly rather than just ignoring them. I've seen people go from listing five tasks a day to fifteen after a week of doing this rigorously. That's not failure. That's honesty catching up. The biggest failure mode I've seen is when people apply this to collaborative work. The question only works when you own the outcome. If you're asking about something another person needs to do, you're not solving anything by interrogating your own willingness. You're just passing the buck onto yourself in a more polished format. I learned this the hard way when I was managing a team project and kept internalizing other people's responsibilities through this lens. It doesn't transfer. If you want to try this, you don't need any tool. A piece of paper and a pen will do. Write down everything you feel obligated to do. Go through each one. Answer the question. For the yes items, write the next concrete action. For the no items, cross them out and actually leave them crossed out. Don't circle back to reconsider within two weeks. The two-week rule keeps you from using hesitation as an excuse to keep things alive that should be dead.

I've found this works best in the morning when your decision fatigue is lowest. Asking yourself a hard yes-or-no question at 4pm when you're exhausted tends to produce wishy-washy answers that lead you right back to where you started. The alternative if this feels too blunt is the two-minute rule from GTD, which is softer and lets you tinker. But I've found the softer approach mostly helps people stay comfortable without actually moving forward. Comfort is the enemy here. You don't need to feel good about dropping a task. You just need to stop pretending you're keeping it. At this point I usually stop explaining it and just tell people to sit down with their list and see what happens. The method is transparent. The difficulty is entirely in the execution.