5 Myths About Doing Small Tasks Right Away, Busted

Rajesh Kumar

Rajesh Kumar is a leading expert in DevOps, SRE, DevSecOps, and MLOps, providing comprehensive services through his platform, www.rajeshkumar.xyz. With a proven track record in consulting, training, freelancing, and enterprise support, he empowers organizations to adopt modern operational practices and achieve scalable, secure, and efficient IT infrastructures. Rajesh is renowned for his ability to deliver tailored solutions and hands-on expertise across these critical domains.

A few years ago, a support engineer at a small software company told a story over lunch. Every Monday the engineer opened the task list and felt a sinking stomach. Sixty-one lines. When the engineer finally counted, forty of them were things like “update the wiki heading” or “reply to the config question”. Nothing on the list was difficult, yet the length alone made the week feel impossible. The team’s habit was to write everything down and deal with it later. The fix, borrowed from the two-minute rule, was to do anything small the moment it showed up. People pushed back with reasons that sounded sensible. Here are five of those objections, treated as myths, and a note on how each one fares once you try the habit.

Myth 1: “Writing it down is always the responsible thing to do”

Recording tasks feels diligent, and for large work it is. For small work, the record is often more effort than the job. A note takes thirty seconds to write and, afterwards, needs a place, a label and repeated glances. A twenty-second reply takes twenty seconds.

The reality: writing something down is a tool for things you cannot finish now. If you can finish it now, the finished task is its own best record. A short changelog line or a sent message already shows it happened.

Myth 2: “Doing small tasks first is just procrastination in disguise”

This one has a kernel of truth. There is a kind of busywork that hides from the hard thing: reorganising folders instead of writing the proposal. But the two-minute rule is not “do small things first”. It is “do small things the moment they arrive, then return to your main work”.

The difference is timing. Procrastination is choosing small tasks over a big one you are avoiding. The rule is handling a short interruption in one clean motion so it does not linger as a mental splinter. If you notice yourself hunting for small tasks to avoid a large one, you are no longer following the rule.

Myth 3: “It will break my focus”

Context-switching has a real price, so this myth deserves respect. The engineer in our story handled it by being clear about what counts as arriving: items that come in while the engineer is already at the desk, between pieces of work. During a protected focus period, messages could wait, but every one got an answer within the same working day.

The reality is that unfinished small things also break focus, quietly. A background hum of “I still need to reply to that” is itself a distraction. Many people find that clearing the small pile in the gaps between deep sessions gives them more steady concentration, not less.

Myth 4: “Everyone’s two minutes is the same”

It is not, and that is fine. A teammate who knows a codebase well can rename a function safely in two minutes; a new hire may need twenty, to check what depends on it. The rule is personal and honest: it applies when you already hold all the information required to finish. If you would need to look something up or ask someone, it is a different sort of task.

The sign of a healthy habit is that you occasionally misjudge, notice, and move the item to the list at the moment you realise. Nobody is penalised for that, and the estimate improves with practice.

Myth 5: “It only works for tiny, boring admin”

It certainly handles admin, but its reach is wider. Writing the first sentence of a document, sketching a diagram on a whiteboard before the memory fades, or leaving a short comment explaining a tricky line of code are all small, and all disproportionately valuable when done in the moment. The engineer’s team found that the best small tasks were the ones that stored context: a sentence of explanation written while the reasons were clear.

There is a wider cultural link too. Teams that respond quickly to small things build a rhythm of trust. A piece on managing cultural change when a team adopts DevOps habits makes a related point about small, visible behaviours shaping how a group works. Likewise, the connection between responsiveness and satisfaction is explored in an article on how delivery habits affect the customer’s experience.

A sixth idea, not a myth: the exceptions are real

Not every small thing should be done on the spot. Anything with consequences if wrong, such as changing access, touching production or sending a message to a large audience, deserves a pause and a second look. Anything emotionally charged, such as a reply to a heated thread, benefits from a few minutes’ delay. The rule is for low-stakes jobs that are cheap to finish and cheap to undo.

What the engineer learned after three months

The Monday list shrank to about a dozen lines, each one a piece of real work. The engineer wrote later that the biggest surprise was how much calmer the first hour of the week felt. Teammates noticed that questions got answered faster, and a couple of them adopted the habit without being asked. Nobody announced a new process; it spread because it was visible and low-cost to try.

A passing mention from outside the field

Some in that team followed unrelated hobbies online. One of them enjoyed browsing a community forum site centred on Indian listed companies, noting that the site itself says its content is not investment advice. The engineer’s comment was that this is how all public discussion should be read: as conversation, with your own decisions resting on your own careful work.

Try it for one week

  1. Count the small items on your list today. Write the number on a sticky note.
  2. For five working days, finish any new small task the moment it arrives, as long as you hold everything needed and the stakes are low.
  3. Move anything that turns out bigger onto the list immediately, with a first step.
  4. On the next Monday, count again and compare, and think about how the week felt rather than only about the number.

The myths fade quickly once you see the list get shorter. The point is not to be faster for its own sake, but to keep your attention for the work that deserves it.

Leave a Reply