A single-file, offline-first workspace that unifies tasks, follow-ups, and links across a multi-product portfolio, built because no enterprise tool treats "who am I waiting on" as a first-class thing.
Running a multi-product portfolio means a different work-item board, doc space, and stakeholder cast for every product. None of it aggregates at the personal level. Capturing a quick "follow up with someone about this Thursday" meant either a heavyweight work-item ticket or a sticky note that would be gone by Friday.
Two weeks of structured self-observation (logging every time I reached for a tool and what I actually wanted from it) surfaced the clearest finding: follow-up work has a distinct mental model from task work. It needs an owner and a source, and it needs its own review cadence. No tool at the personal level modeled that; it was always an afterthought bolted onto a generic to-do.
I made follow-ups a first-class type, with an owner, a source, and its own board, rather than a tag bolted onto a task. And I built the whole thing as a single-file, offline, browser-storage app with zero backend, specifically so it needed no security review, no hosting, and no approval to start using immediately on a locked-down work laptop.
The cheapest tool that ships beats the ideal tool that doesn't. Choosing zero-approval, zero-infra architecture was the actual reason this exists in daily use instead of as an unbuilt "someday" idea.
Model the user's mental model, not the domain's vocabulary. "Blocker" and "dependency" felt like statuses but were really reasons, a small reframe that removed constant classification hesitation.