My grandfather had a workshop. Saturday mornings, he'd go in after breakfast and come out before lunch. Not because the project was done. Because the morning was. There was no alarm. No rule. He just knew.

I've been looking for that sense in my phone for years. Haven't found it.

Most digital products run on one assumption: more is better. More time on the platform, more sessions, more content. The metrics that get tracked, daily active users, session length, return rate, all point the same direction. Toward more. The design follows the metric.

This isn't a conspiracy. It's incentives doing what incentives do. The result is a product category where enough doesn't exist. Where the end of an interaction is a problem to solve rather than a place to stop. Where any gap in attention gets filled with a suggestion, a notification, another thing to tap.

Eat enough of something and the appetite closes. Not because you forced it. Because the signal landed. The body has a version of enough, and it works reliably when nothing is interfering with it.

The mind is the same. A question answered feels different from a question interrupted. A task completed has a different texture than one stretched out past its end. The mind wants to close loops. Given the chance, it does.

Most apps are designed to prevent that closing. The next video starts before you chose to watch it. The feed has no bottom. The notification arrives the moment you've put the phone down. The appetite stays open. Low-grade wanting that never quite becomes rest.

What would it look like to design for enough?

Not a screen-time warning buried in settings. Not a guilt-colored nudge telling you that you've spent forty minutes here today. Those are patches on top of a system that still wants to keep you. The architecture is still pointing the wrong way.

Designing for enough means something structural. A reading app that finishes a chapter and stops, without immediately queuing the next. A social feed that shows you what's new and then goes still. A task tool that marks the day done and steps back.

None of that is a compromise on good design. It's what good design looks like when it trusts its users.

He left the workshop before lunch every time. Came back the next Saturday. The work continued for years. Each session ended before it ran out. Stopping wasn't failure. It was how the work stayed worth doing. Time to reflect, to recover, to remember why he showed up in the first place.

Most digital experiences are missing that. Not willpower. Not better habits on the user's part. Just form. Something that knows when it's done.

Enough isn't a failure state. It's the whole point.