People often assume a minimalist workflow should be equally simple for every kind of work. That sounds appealing: one routine, one list, one block of time. But a difficult writing task and a batch of routine email do not ask for the same kind of attention, and forcing them into identical structures can create needless friction.

Different work has different shapes

Consider a morning with two commitments: drafting a proposal and clearing several administrative messages. The proposal may need a long, uninterrupted stretch because the argument takes time to develop. The messages may be easier to handle in a short batch, provided there is a clear stopping point. If both tasks receive the same brief interval, the writing may be interrupted just as it becomes coherent. If both receive a long block, email can expand to fill time it did not need.
A workflow can stay minimal while changing its time shape. The important distinction is between a stable rule and a rigid schedule. A stable rule might be to give complex work a protected block and batch small tasks later. A rigid schedule would insist that every task fit the same duration regardless of context. One reduces repeated decision-making; the other can make the system brittle.

Why uniform systems are tempting

Uniformity has a real advantage: fewer formats to remember. A consistent timer, checklist, or desk ritual can reduce the overhead of starting. And when work is predictable, repeating the same interval may make it easier to compare sessions and notice interruptions. That is a strong case for consistency, especially for people who are building a routine from scratch.
But consistency should not be confused with sameness. A session length is a container, not proof that a task is complete. If the work requires more time, stopping at an arbitrary boundary may break a useful train of thought; if the task is small, extending it can invite unnecessary polishing. Flexibility matters most when the nature of the work changes, not whenever someone feels momentarily reluctant.

Keep the rule simple, adapt the block

A practical compromise is to choose the work before choosing the interval. Ask whether the task needs continuity, repetition, or a quick finish. Then pick a countdown or stopwatch arrangement that supports that purpose. A Pomodoro-style focus session can suit bounded work, while a longer countdown may fit a sustained draft. A simple timer can mark the session, but the judgment about the work remains yours.
Minimalism is not one-size-fits-all behavior. It is a way to remove avoidable complexity while leaving room for the task in front of you. I would rather keep a small set of time options than force every kind of work into one ideal interval. Do you value one repeatable routine more, or a few deliberate exceptions?
iOS: https://apps.apple.com/se/app/focus-timer-desk-clock/id6762793543?l=en-GB Android: https://play.google.com/store/apps/details?id=com.focus.timer.desk.clock