Against the streak

A streak is a number that only goes down. That is the whole design. It climbs while you comply and collapses the first day life gets in the way, and the collapse is the point: the fear of it is what keeps you opening the app.

We shipped one. It lasted a quarter.

Why it works, and why that is the problem

The mechanism is not mysterious. A streak is a small, visible asset you have built, and loss aversion makes losing it feel worse than gaining it felt good. That asymmetry is powerful, which is exactly why habit apps reach for it. It also means the tool is running on a feeling you would not choose to install deliberately: low-grade dread about a number.

The defence is that the dread is in service of a good habit. Sometimes it is. But a timer is not a habit app. Opening Timato is not the behaviour anyone wants; doing the work is, and the streak cannot see the work. It can only see the opening.

What a streak actually measures

It measures consecutive days of opening a timer. Not hours, not output, not whether the work mattered. A person who logs four honest hours on Tuesday and takes Wednesday off ranks below one who starts a two-minute session every day to keep a number alive. Once you notice that, you cannot unnotice it.

The failure mode is not hypothetical. People told us they were starting sessions they did not need, at the end of the day, to protect the count. That is a tool teaching someone to lie to it.

A number that punishes a day off is not tracking your work. It is tracking your attendance.

The three days that break it

Watch what happens on the days a streak is most likely to snap, because those are the days that tell you what the feature is really for.

The day you are ill. Nobody believes a sick day should count against them. Yet the number does not care, and the app that was supposed to help now delivers a small, precise punishment at the worst possible time.

The day the work was not timer-shaped. Five hours of interviews, a day on a whiteboard, a long incident. Real work, none of it in blocks. The streak reads it as absence.

The day you finished early. You did the thing, you did it well, and you stopped at two. A streak has no opinion about this, but you now have a reason to start a session you do not need, which is where the corruption starts.

Every one of those is a day when the honest answer is "nothing to log", and the feature's job is to make the honest answer feel expensive.

What we show instead

Three things, all of which survive a day off:

• Time logged, per day, per project, over whatever range you ask for. It goes up when you work and stays flat when you do not. Flat is not failure.
• Completion, the share of started focus sessions you finished. It says something real about whether your blocks are the right length.
• The sentences. What you actually named each session. Six weeks later this is the only column that explains anything.

None of them make you feel watched, and none of them are worth gaming, because gaming them would mean doing the work.

We kept one streak-adjacent number: consecutive days with a completed session, shown quietly in the Sessions header. It is there because people asked where the week went, not to make anyone anxious about breaking it, and nothing in the interface reacts when it resets.

If you want the accountability anyway

Some people genuinely work better with a visible commitment, and dismissing that would be its own kind of arrogance. There is a version that does not rot: commit to a weekly floor rather than a daily one, and read it on a Friday.

A week is long enough to absorb a sick day, a day of meetings and a day that went sideways, so the number stops being a lie detector for your calendar and starts being a rough description of your capacity. Fifteen focused hours in a week is a real commitment. Fifteen consecutive days of pressing a button is not.

The same data supports it. Open the week, read the total, and decide whether next week needs to be different. You will notice this is the Friday ritual, and that is not a coincidence. Most of what a streak promises is delivered better by looking at the actual hours once a week and then getting on with it.