Every product has two kinds of users: the ones who show up daily, and the ones who show up a few times a year with a specific job in mind. The second group is easy to lose, and not because the product failed them. They come back months later, cannot quite remember the name, start from a search engine instead, and may or may not arrive.
Building OneLifeVibe — a hub of focused, single-purpose sites behind one front door — turned into a design problem about that second group. The question was not how to make people visit more often. It was how to make a site worth returning to findable again at the exact moment its job comes back around.
What worked
One front door instead of many half-remembered names. Each site in the hub finishes a distinct everyday job: household organisation, mutual help between neighbours, bedtime stories, money tracking, classic wardrobe pieces, a daily reading. Asking a returning visitor to remember each name separately was asking too much. One bookmark at the top of the folder replaces a scattered set of names that are easy to half-remember, and from that one door every tool is a click away.
Grouping by job, not by name. The hub is organised the way a tidy bookmark folder should be: by the job being finished, not alphabetically. When a job comes up, the visitor scans by need rather than by title. That sounds trivial, but it changes the navigation model from recall ("what was that site called?") to recognition ("that is the one for this job"), and recognition is far more forgiving after a three-month gap.
Letting each tool finish its job and let the visitor leave. Occasional tools earn their place by being quick. A site that solves the problem in minutes and releases the visitor builds the trust that makes the bookmark survive the next monthly tidy. Every extra step added "for engagement" worked against the actual goal, which was being kept.
A plain monthly test. The standard applied to the hub is the same one a person applies to a bookmark folder: does this still work, does it still do the job it was saved for, and can it be found in seconds when that job returns? Features that failed that test — anything that made a returning visit slower than a fresh search — got cut, however nice they looked in a demo.
OneLifeVibe is where that pattern lives: single-purpose sites gathered behind one front door, each reachable in a browser, each finishing a distinct job.
What broke
Designing for the daily user by default. The first layouts assumed familiarity: dense dashboards, shortcuts that only make sense to someone who was here yesterday. Occasional visitors bounced off them. The fix was designing every entry point for someone who last visited in spring — plain labels, the job stated on the page, no memory required.
Treating search as a safety net. Early on, the assumption was that anyone who forgot a name would just search for it. In practice, a generic search returns a dozen similar names and the original is not obviously among them. Findability has to be built into the structure — one memorable door — not outsourced to a search box.
Adding sites faster than the organisation. As the hub grew, new sites were added where they fit technically rather than where a visitor would look for their job. The grouping quietly stopped matching how people think about their errands, and findability degraded even though nothing was technically broken. The grouping now gets reviewed whenever a site is added.
Lessons worth keeping
Occasional use is a design case of its own, and it is harsher than daily use: no habit, no memory, no patience. Recognition beats recall, one door beats many names, and a tool that finishes its job and lets people leave is the one that is still bookmarked next year.
How do you design for the visitor who only comes back a few times a year — one front door, better naming, or something else?
