Why the timer should be boring

When a Timato session ends, the ring stops and the time lands in your history. There is no animation, no sound beyond the one you chose, no message telling you that you are on fire. Several people have told us this feels unfinished. It is the most deliberate decision in the product.

Celebration is a claim about what happened

A confetti burst is not decoration. It is the software asserting that something good occurred, and it makes that assertion from a position of total ignorance. It knows a timer reached zero. It does not know whether you solved the problem, wrote something you will delete tomorrow, or sat through twenty-five minutes of staring while the counter ran.

Rewarding all three identically teaches the only thing it can teach: that the reward is for running the timer. That is a measurable behaviour, which is why it gets optimised, and it is the wrong one.

A tool that congratulates you for using it is measuring itself, not your work.

The three things celebration teaches

Reward shapes behaviour, and a confetti burst is a reward attached to a specific, measurable act. It is worth being precise about what that act is.

It teaches you to start timers. The reward fires on completion of a countdown, so the cheapest way to earn more of it is to run more countdowns. Nothing about that requires the work to have gone anywhere.

It teaches you to pick easy blocks. A twenty-five minute block you are confident of finishing pays out. A ninety-minute one on something genuinely hard might not. Over months, that is a gentle, invisible pressure away from the work that matters.

It teaches you to distrust the tool. This is the one people underestimate. When software congratulates you for a session you know was bad, you learn that its judgement is worthless, and that lesson generalises to the parts of the interface you actually needed to believe, like the numbers.

The streak is a debt

We had a streak counter briefly. The argument for it is well known and not stupid: a visible run of days is a cheap commitment device, and loss aversion is real.

The problem is what happens on day forty-one. You are ill, or on holiday, or you had a day that went sideways, and the tool that was supposed to help now takes something away from you. People respond to that in two ways. Some feel bad, which was not the deal. Others open the app and start a session they do not intend to work through, which corrupts the only thing the product is actually for: a record of where the hours went that you can believe six weeks later.

We removed it. Nobody has asked for it back.

The case for the other side

There is a real argument for gamification and it deserves better than a strawman. For some people, at some times, an external nudge is the difference between doing the thing and not doing the thing. Beginning a habit is genuinely harder than maintaining one, and a tool that is fun to open in week one may still be being used in week fifty.

We think that trade is a bad one for this particular product, for a specific reason: a timer's output is a record, and records only have value if they are true. A habit tracker that inflates your step count has produced a mildly annoying lie. A time log that inflates your hours has destroyed the only reason to keep it.

Everything downstream, the invoice, the estimate correction, the answer to where the week went, depends on the log being an honest description of what happened. Anything that gives you a reason to start a session you did not need is attacking the foundation to decorate the roof.

What we kept instead

Something has to close the loop, or the session ends in a void. The difference is between acknowledgement and applause.

• The number lands somewhere. The session appears in today's log, on the task, in the project total. That is feedback, and it is made of facts.
• The day is legible. You can see the shape of today without anything interpreting it for you.
• Nothing is scored. No levels, no badges, no comparison to last week unless you go and look.

Boring is a feature with a long tail

Novelty interfaces are optimised for the first week, because that is when the screenshots are taken. A tool you open five times a day for three years has the opposite problem: every flourish becomes an irritation, and every irritation eventually becomes a reason to stop opening it.

The test we apply is whether a thing will still be tolerable on day eight hundred. Almost no celebration passes it. The number, the log and the quiet do.

Boring is not the same as bare

None of this is an argument for an ugly or thoughtless interface. Getting out of the way is harder than showing off, and most of the work in Timato has gone into things you are not supposed to notice.

The ring drains rather than fills, so the thing shrinking is the thing you have left. The time is set in a monospaced face with tabular figures so the digits do not shuffle sideways every second. The session you were running survives a refresh, a crash and a closed laptop, because a timer that loses your afternoon is not boring, it is broken.

That is where the effort goes: into a tool that is unremarkable on day eight hundred. No celebration, no scoring, no opinion about your Tuesday. The number lands in the log, the log stays true, and the rest is your business.