Concept evolution: three stages to one thing at a time
Our first redesign concept was Ground, Play, Build. It started from the founder’s sketch, and I helped shape it into three stages a user would move through:
Stage 1: Ground
A soft landing: an AI agent offering light nudges and emotional support to help users stop spiraling.
Stage 2: Play
Designing small experiments to try on new identities, collect evidence, and discover who you are.
Stage 3: Build
Turning what you learned into ongoing habits and systems that support your goals.
As we worked through translating this concept into the product, the structure quickly grew complicated, and we realized that it relied on the assumption that people progress evenly in all areas of their life—moving linearly through grounding to play and build. However, in reality, someone might be ready to play in one area of their life while still getting grounded in another.
Of the three stages, Play held the most promise—getting people to take a lighter, action-first approach and to get out and try things instead of over-planning. The founder's next overhaul centered around the idea of doing one thing at a time, cutting overthinking down to a single small next step.
Around that core, the app was reframed around time:
Present: The whole loop lives here: talk through what's on your mind with the agent, set up one small experiment, go do it, then come back to reflect on how it went.
Future: A vision board for picturing who you want to become.
Past: A log of past conversations and what came of them.
The result was a clear core: talk it through, try one small thing, and reflect on how it went. Where the original app opened with 23 questions and quarterly goals, the new one opens with a single question and ends with one small action.

Selecting one central metaphor
The overhaul had also brought a new vocabulary. The area where users talked through what was on their mind and set up an experiment was called "The Space," but the name was vague—it sounded open and unlimited, which set the wrong expectation for users. In reality, it was a focused chat that funnels users toward setting up one small goal to act on soon.
Rather than rename it, I suggested removing the name entirely. Not every feature needs a name, and this one already lived under the Present tab, so a second name only added complexity. Instead, we edited the text of the lead-in page to give users a better idea of what to expect. We applied the same methodology across the app.
