Pocket Planner
A dashboard-first operating system built by pushing Notion far past its default shape.
Pocket Planner started with a simple problem: most planners only work when the user is already doing well.
They expect consistency, manual upkeep, and a lot of self-management. The moment life gets messy, the system becomes one more thing to manage.
I wanted something else. I wanted a system that could carry more of the load itself. One that felt clear, responsive, and worth returning to. One that let the user work through dashboards instead of digging through raw databases.
Pocket Planner is the result. It turns Notion into a connected product experience built around re-entry, visibility, and action.
Built as a dashboard-first system
Pocket Planner was designed so the user operates through dashboards, not raw databases.
That decision matters. It changes the product from a pile of linked tables into a set of clear control panels, each with a specific job.
The Day Card turns overview into action
One of the clearest design decisions in Pocket Planner is the path from the Daily Dashboard into the Daily Planner.
The dashboard gives the user a fast read on the day: priorities, reminders, signals, context. The My Day card then acts as an intentional entry point into a more focused planning space.
That flow matters because it shortens the distance between seeing and doing. The user does not have to reconstruct their day or decide where to go next. The system already gives them a path.
This is a small interface move, but it says a lot about how the product was built. The goal was not just to store information. The goal was to move the user cleanly from orientation into action.
The Notification Center makes the system feel alive
The Notification Center is one of the strongest proof points in the whole project.
It takes signals from across the system and turns them into a single readable surface: task counts, completion progress, journal activity, habit status, projects, goals, and live summary messaging. Even the greeting matters. Notion does not naturally behave like that. Here, it feels like a product speaking back to the user.
That is important because the interface is doing more than displaying stored information. It is synthesizing state. It is telling the user what is going on right now.
This is where Pocket Planner starts to feel less like a workspace and more like a custom tool. It shows system awareness, priority logic, and a strong understanding of what makes an interface feel responsive.
The aesthetics are part of the design system
Pocket Planner is beautiful on purpose.
The glossy headers, pastel section banners, soft color coding, 3D labels, progress rings, clouds, and playful interface language are not decorative extras. They are part of how the system works.
They make categories easier to remember. They make dashboards easier to scan. They create emotional pull. They make the product feel good to return to, which matters more than people sometimes admit.
A tool can be logically correct and still fail if users avoid it. Pocket Planner treats aesthetics as a usability decision. The visual layer helps the system hold attention, reduce friction, and create momentum.
That is part of the systems thinking here too. The design does not stop at logic. It includes the conditions that make a person actually want to use the thing.
One task system, shown in ways that match real life
Under the surface, Pocket Planner is connected. On the surface, it feels organized by context.
That is a key part of why it works.
The system does not force the user to work from one giant flat list. Instead, tasks are surfaced through smart categories and dashboard sections that reflect the way daily life is actually experienced: work, home, life, priorities, reminders, weekly planning.
Those views are not static wrappers. They carry live indicators, progress states, and notification signals. The user is seeing real system behavior at the interface level.
This makes the product easier to scan and easier to trust. It also shows one of the core design choices in the project: keep the backend unified, but let the front-end speak the language of actual use.
Pocket Planner hides complexity without losing it
A big part of the project was deciding what the user should never have to think about.
Buttons, formulas, linked views, database relationships, and system rules all matter here. But the product is stronger because those mechanics are mostly hidden from day-to-day use.
The user works through dashboards that feel clear and responsive. The structure underneath keeps everything connected, updates the right surfaces, and preserves consistency across the system.
This is the part of the build that shows systems thinking most directly. The work was not just writing formulas. The work was shaping logic into an interface that a non-technical person could use without needing to understand how it was wired.
Why this project matters
Pocket Planner is a product, but it is also a record of how I solve problems.
It shows how I think about interface design, information architecture, motivation, visibility, and behavior. It shows how I simplify technical structure without flattening it. It shows how I use design to make a system feel usable, not just organized.
Most of all, it shows that I was not interested in making Notion look prettier. I was interested in making it behave differently.
Pocket Planner took a flexible but limited tool and pushed it into something more product-like, more connected, and more responsive to real use. That is the part of the project I care about most.
Want to talk about how I build things?
More work: ATS Partner Operations · Zendesk Support Intake · Job Search System