UpOrbit: Free Productivity Tool Built From Personal Need

This did not start as a product idea or a content play. It started because the productivity tools I tried kept failing me in the same ways. They all assumed I could hold fifteen tasks in my head, switch between them cleanly, and somehow remember why each one mattered by 3pm. None of them were designed around how my brain actually works. I needed something simpler: one thing per day, a reason attached to it, and a system that does not punish me for losing momentum.

I started building UpOrbit for myself. A single must-do with a “why” anchor. A brain dump that auto-sorts scattered thoughts. A focus timer that frames the ask as “just start for five minutes” instead of demanding a full session. Wellness nudges that check in on basics like water and movement. It worked well enough for me that I thought other people might get something out of it, so I made it free and put it online. No account required. No paywall. Everything stored locally in the browser.

The North Star: One Thing

Every productivity app wants you to manage twenty things at once. UpOrbit’s entire design revolves around a single question: what is the one thing that matters most today? That constraint is not a limitation. It is the core differentiator. You pick one thing. You attach a reason it matters to you. That reason resurfaces when you inevitably lose the thread.

The research behind this is practical, not theoretical. Reducing decision load to one task lowers the barrier to actually starting. Attaching a “why” creates a personal anchor that is harder to forget than a bare task name on a list. Every other feature in UpOrbit exists to support that single daily decision rather than competing with it.

How the System Shows Up

That design philosophy needed a system to support it at scale. The same framework I apply to client work shaped how UpOrbit is structured for discoverability, comprehension, and conversion. In this case, “conversion” means someone actually using the tool or finding an article that helps them. This is one of several projects documented under my content strategy and architecture work, where every build follows the same methodology with different subject matter.

Six Design Pillars

Here is how that single-focus philosophy shaped what was actually built. Every feature maps to a specific challenge that research documents and that I experience firsthand. Nothing exists because it seemed like a good product feature. Everything exists because it addresses a real pattern that makes getting things done harder than it needs to be.

The Chrome Extension

The web app works. But I kept forgetting to open it. The tool I needed was one tab away and I never got there. So I built a Chrome extension that turns every new tab into the launchpad.

Every time you open a new tab, you see your #1 Must-Do, a focus timer, and a smart task capture field. It eliminates the gap between intention and action by removing the step of navigating to the tool. One fewer step sounds trivial. In practice, it is the difference between using something every day and forgetting it exists. This is the current primary focus of the project.

300+ Articles: Filling Gaps I Found Personally

The content library did not start as a content strategy. It started because I could not find what I was looking for. When I searched for how specific medications interact with caffeine, or what the real cost of getting a diagnosis looks like, or why I lose track of time on certain days, the results were either clinical abstracts with no practical takeaway, or thin content rewriting the same surface-level paragraph for the fifteenth time.

So I started writing the articles I wished existed. Each one sourced from peer-reviewed research, written in plain language, and structured around the actual question someone is searching. The gap was not a lack of information. It was a lack of useful, readable information organized around real intent. I used public research databases to collect the best available data and compiled it into something genuinely helpful for the person typing the query.

Research Standards and Trust

When you write about mental health, trust is not optional. UpOrbit is not a medical resource and does not claim to be. But every factual claim is sourced, every medication guide references peer-reviewed literature, and every page includes a clear disclaimer. That is not a legal checkbox. It is a design decision that shapes every piece of content on the site.

Product Recommendations

UpOrbit includes a curated set of product recommendations organized by the specific ADHD challenge each product addresses. Fidget tools for attention regulation. Noise-canceling headphones for sensory overload. Visual timers for time blindness. Standing desk converters for movement needs. Each category opens with the research explaining why the category matters, not a sales pitch.

Some links are affiliate links, and that is disclosed transparently at the top of the products page. The revenue helps keep UpOrbit free. But the recommendations are based on usefulness, not commission rates. There are no sponsored placements. No product was included because a company asked for it.

Retrospective

Building a personal tool is one kind of work. Turning it into a public resource is a different kind entirely. Here is what held up and what I would approach differently.

What Went Wrong

Now that you have seen the design philosophy, the content strategy, and the Chrome extension, here is the part that portfolios usually leave out.