Time Blocking But Shorter
The basic idea is simple enough that most people dismiss it immediately. You take whatever task you're avoiding, you set a timer for ten minutes, and you work on it without stopping until the timer goes off. That's the entire mechanism. The psychology behind it is just friction reduction. A ten-minute commitment feels manageable to your brain, which is why you actually start instead of scrolling through email for three hours like you normally do. I picked this up around 2019 when I was dealing with a massive backlog of documentation work at a logistics company. Every spreadsheet needed updating, every SOP was three years out of date, and the team kept putting it off because the pile felt insurmountable. We started using short sprints during our weekly planning sessions. Someone would pick one document and commit to finishing a section in ten minutes. Usually by the time the timer went off, they were already in flow and kept going for another twenty or thirty minutes without anyone prompting them. It took us about six weeks to clear the entire backlog that had been sitting untouched for eight months.
The Power Of 10 Minute Time Unlocking Efficiency And Productivity In A Busy World
Here's how you actually implement it without it becoming just another gimmick you try once and abandon. First, identify the task you keep putting off. Not the big project, just the smallest possible unit of it. If your goal is to reorganize your filing system, the ten-minute task is opening the top drawer and sorting papers into three piles. That's it. Most people blow past this step and try to use ten minutes to "work on the project," which means they spend ten minutes thinking about what to do and then quit. Set a visible timer. Phone timers are fine but browser-based ones are better because they can't easily be swiped away. A physical kitchen timer or a dedicated device is ideal since it removes the phone from the equation entirely. When the alarm goes off, you have two choices: stop completely or keep going. The magic happens in that second choice. You've already overcome the activation energy required to start, so continuing is significantly easier than starting from scratch.
Do this at least twice per day, ideally spread across different parts of your workday. Morning for the task that requires the most cognitive load, afternoon for administrative or repetitive work. Track which tasks consistently spill past ten minutes — those are your high-friction items that need better systems or delegation. I hit a specific edge case last year that I hadn't anticipated. I was using the method for code review work on a TypeScript migration. Ten minutes in, I'd identified a cascading type definition issue that threaded through four files. Stopping at ten minutes meant I had no context for where the problem actually lived, so restarting the next day cost me another twenty minutes of reorientation. The workaround was straightforward: if a task is inherently contiguous and can't be meaningfully split, I extended the block to twenty-five minutes. Not a compromise on the principle, just an adjustment for the work type. The ten-minute version works best for discrete, interruptible tasks. There are some nuances most tutorials skip over. The method only works for tasks with a clear definition of "done." Vague goals like "get organized" or "figure out my finances" will make you stare at a timer for ten minutes and accomplish nothing useful. You need to be able to state the completion criteria before you start. "Sort invoices from March into the Q1 folder" is a valid ten-minute task. "Organize finances" is not.
Get the Full Details
Another thing nobody mentions is that your first few attempts will feel uncomfortable and unproductive. This is normal. Your brain isn't used to working in short, concentrated bursts, so the early sessions will feel like you're not doing enough. Give it two weeks. The compounding effect shows up around day ten when you realize you've cleared three things you'd been putting off for months without ever feeling the need to schedule a special "deep work" block. The limitations are worth being honest about. This approach falls apart for creative work that requires extended incubation periods, complex debugging sessions that need sustained context, and collaborative work that depends on other people's availability. If your blocker is someone else, no amount of ten-minute sprints will unblock you. In those cases, the method still helps with the parts you can control, but don't pretend it solves everything. You'll also find that the same tasks eventually stop being avoidable. After you've consistently knocked out small chunks, the resistance fades and the tasks become routine. At that point, you should move on to harder problems rather than claiming credit for the easy wins. The method is a ladder, not a permanent workspace.
People usually ask about app recommendations. There's no dedicated software needed. A browser tab with a countdown timer is enough. Some use Pomodoro apps, but those are built for twenty-five minute blocks and add unnecessary complexity. The simplest tool is the right tool here. If you want to try this, pick one task you've been avoiding for at least two weeks. Set a timer for ten minutes right now. Don't think about whether it's the right task or whether you have time. Just start the timer and begin.
