Design Updates & Pivoting

Building a product in isolation is dangerous. You can easily spend months perfecting a feature that no one actually wants or a UI that no one understands.

With JupiterGoals, I wanted to get the design in front of users as early as possible. This post details how the initial concept evolved through feedback, mocked data, and confronting hard limitations.

The Initial Design & The Reality Check

The very first iteration of JupiterGoals was essentially a highly opinionated calendar. You inputted a goal, the AI broke it down, and it plotted it on a timeline.

However, early user feedback revealed a massive flaw: There was no commitment hook.

Users told me they liked the idea of the roadmap, but without a reason to actually do the tasks, it was just another to-do list they would eventually ignore. I realized I needed an accountability mechanism.

The Limitation: Why Monetary Penalties Do Not Belong in a Habit App

My first thought for accountability was a monetary penalty: charging a cash fee whenever someone missed a habit. On paper, loss aversion looks like a strong psychological motivator.

In practice, holding customer funds around personal habits introduces punitive stress for users and heavy regulatory complexity around restricted financial services. As a solo builder focused on sustainable software, I wanted zero part of cash penalties.

Instead, I built accountability strictly around software-based commitment credits (non-monetary in-app Pledges with zero cash value) and human connection. That design direction also shaped the AI coach (which challenges your excuses constructively) and “Habit Graduation” (unlocking higher milestones as you build consistency).

Refining the Design: The Radar Chart

As I moved away from just a “calendar view,” I realized users needed a way to visualize their overall life balance. If you are crushing your career goals but your health is failing, the system should reflect that imbalance.

This led to the introduction of the Identity Nodes (Vitality, Wealth, Career, Connection, Growth, Zen) and the central UI piece: the Radar Chart.

By mocking up data for these nodes, I was able to test two different UI approaches:

1. A deeply analytical “Dashboard” view (data-heavy).
2. A clean “Today’s Focus” view (minimalist).

Feedback heavily favored the minimalist “Today’s Focus” view, with the Radar Chart providing the high-level context only when requested.

The Next Pivot: Event-Based Habits

While testing the daily timelines, I hit another roadblock. Traditional time-blocking assumes a perfect day. If I schedule “Read for 20 mins” at 8:00 AM, but my kid wakes up sick at 7:45 AM, the schedule is broken, and guilt sets in.

Recognizing this limitation led to a potential pivot in how we handle triggers. Instead of purely time-based tasks, we are heavily exploring event-based approaches (Habit Stacking).

Instead of scheduling:

• 8:00 AM - Meditate

The system will encourage:

• When I finish brushing my teeth -> I will meditate for 2 minutes.

This subtle pivot changes JupiterGoals from a rigid calendar into a truly flexible, adaptive system that fits into real human lives.