Every coffee guide makes the same quiet assumption: you own the right equipment, you measure carefully, and nothing goes wrong. Then you stand in a real kitchen with the kettle you actually have, your hand slips, and you pour too much. The guide has nothing to say to you now, except perhaps to start again.

That gap is why I started building Evencup, and it taught me something I did not expect to learn from coffee.

Instructions describe a perfect person

Most software works the same way as those guides. The happy path gets the attention, because it is what we picture when we design. Errors get a red message, written late, telling you what you did wrong and leaving you to work out the rest.

But the moment something goes wrong is when a person most needs help. It is also when they are most likely to give up on the thing altogether. Treating that moment as an edge case means ignoring the part of the experience people remember.

Recover, don’t restart

So in Evencup, a mistake is a normal part of the flow. If you pour too much, the app works out how to correct it from where you are now, and shows you what to do next. It does not scold you, and it does not throw away what you have already done.

The useful question is not “what should have happened?” It is “given what did happen, what now?”

That sounds simple, but it changes the engineering. The app has to understand the current state of the cup, whatever that is, rather than following a fixed list of steps. I wanted the same situation to always produce the same advice, so that it could be tested thoroughly, which is why the core is a plain calculation engine and not an AI guessing at your coffee.

The same idea, elsewhere

Once you notice this, you see it everywhere. A form that keeps what you typed after an error. An undo button instead of an “are you sure?” box. A cold storage ledger where a correction is added and the original mistake stays visible. They all assume that people will make mistakes, and they plan for it instead of blaming them.

Kinder, and better

Designing for the mistake made the whole app kinder, and I did not need to add a single friendly sentence to do it. Kindness in software is mostly structural. It comes from having thought about the person on their bad day, not only on their good one.

Evencup has not been released yet, so this idea still has to survive real kitchens. I look forward to finding out which mistakes I did not imagine.

Photo: JoeSeyd, CC BY-SA 4.0, via Wikimedia Commons.