PlanTrackWhy I built PlanTrack
I did not set out to build another task manager. PlanTrack began with a personal problem that repeated year after year.
At the start of a year, I would write down my goals. They were not empty resolutions. I genuinely wanted to change important parts of my life: health, work, personal projects, and relationships. The list felt convincing when I made it. Surely I only needed to remember it and keep working.
Then ordinary life resumed.
Urgent tasks were more concrete. Meetings already had a time. Messages were waiting for an answer. A large goal could wait one more week, so it quietly waited for months. When I opened the original list again, there was often a wide gap between intention and outcome.
I tried building the system myself
I used documents, spreadsheets, calendars, and Notion databases. Over time, the structure began to look right: important life domains, yearly goals, shorter plans, daily tasks, and reviews.
The diagram worked. In practice, the system needed an operator — me.
I had to remember which page to open, move information between tables, maintain relationships, update templates, and make sure no step disappeared. As the setup became more sophisticated, more attention went into maintaining the system instead of pursuing the goals it was meant to support.
That was the central contradiction: a tool designed to reduce chaos had created another kind of work.
The problem was not the task list
Different tools handled different parts of the process well:
- one place stored long-term goals;
- another managed the calendar;
- a third held notes;
- the weekly review lived in a separate document, if it happened at all.
The weak point was the space between them. A goal could exist without changing the week. A weekly plan might never reach a specific day. An unfinished task could be moved repeatedly without prompting the question of why.
I did not need a nicer task list. I needed one continuous chain:
Life domains → Goals → Plan → Tasks → Review.
Each step should follow from the previous one, and closing a period should naturally lead into the next plan.
A guided process instead of a toolkit
That became the central idea behind PlanTrack: the system should do more than store information. It should guide the process in the right order.
Start by identifying the important domains of life and the gap between their current and desired states. Set goals from that context. Bring them closer through shorter time horizons. Choose concrete actions for the day. Then compare the plan with the outcome, deal with unfinished work, and adjust the next step.
It works like a checklist: your decisions remain your own, but an important stage cannot quietly disappear.
PlanTrack is therefore intentionally opinionated rather than endlessly configurable. I had already tried the approach where you first program your own productivity system and then maintain it for years. Here, a ready-to-use process matters more than maximum flexibility.
Seeing drift sooner
One of the most useful outcomes of planning is not a perfect completion rate, but an early signal.
Moving a task once is normal. Moving it again and again deserves attention. The task may be too large. It may have no realistic place in the week. The goal may no longer matter, or the plan may consistently exceed the time available.
The same signal appears when an important life domain almost vanishes from the calendar while its goal remains formally active.
PlanTrack makes that drift visible during regular reviews. The point is not guilt; it is the chance to change the plan before another year passes.
AI came later
As the system collects goals, tasks, reschedules, and reviews, it builds useful context. That context is difficult to hold in your head all at once, but it gives an AI coach something meaningful to work with.
The coach can discuss a period plan, point out repeated reschedules, or suggest a concrete change. But AI should not quietly manage a person’s data. In PlanTrack, it proposes and the user confirms.
AI strengthens the process; it is not the foundation. PlanTrack still delivers its core value without AI: connect what matters to what you do, then compare the plan with reality.
Who I am building PlanTrack for
First, it is for people who recognize this gap. They can define meaningful goals and may have tried Notion, Todoist, spreadsheets, or paper plans, yet their long-term direction and daily work still live apart.
PlanTrack does not promise to achieve anyone’s goals for them. It does something more practical: it keeps those goals from quietly disappearing from everyday decisions.
That is the system I needed myself. It is why I continue to build PlanTrack.