After 30 Days — Can Your User Feel the Win?

Days 489–496 out of 1095

This past week, we paused. Not to stop — but to realign.

After 489 days of building, and with just under two-thirds of the journey ahead, we knew it was time to ask the question that shapes everything:

What does success look like for our user after 30 days of using the product?

Start with the end

If you don’t define what “winning” looks like for your user after one month, your roadmap might be full of features — but not direction.

We asked ourselves:

• What should someone feel, not just do?
• What mindset should they reach?
• What would make them come back — not from habit, but from value?

We landed on five clear, emotional, behavioral signals.

The 5 outcomes we expect after 30 days

1. “I want to help or support someone else.”
2. “I want to strengthen my own resilience and support myself.”
3. “I want to know that my support actually helps.”
4. “In a moment of crisis, I know what to do or who to call.”
5. “There’s something in this product that keeps pulling me back.”

Each one is a proof point. Not just of engagement — but of meaning. It’s not retention. It’s resonance.

And now, as we shape the next MVP, this list is our North Star.

What happened this week (Days 489–496)

• We tested these assumptions through live user interviews — from field units to frontline therapists.
• We redefined KPIs around emotional wins, not just time-in-app.
• We reworked onboarding to trigger at least one of the five "wins" within the first 10 minutes.
• And we cut two features that were helpful, but not aligned to transformation.

10 practical tips for defining user success

1. Write your user’s emotional state before the product — and 30 days later.
2. Ask: “Would a coach or therapist call this growth?”
3. Design onboarding as a bridge, not a checklist.
4. Test for value before testing for scale.
5. Define success in sensory and emotional terms.
6. Build in a self-reinforcing emotional loop.
7. Validate with users who challenge you, not confirm you.
8. Track intent, not just behavior.
9. Let every product meeting ask: “Which of the five are we serving?”
10. Revisit your definition every sprint — not just quarterly.

A sentence that changed how we build

One of our users — a combat medic — said this:

“I didn’t open the app because I needed support. I opened it to remind myself that I can give it.”

That sentence told us more than any analytics dashboard.

The takeaway

Don't wait for version 3 to define success. Define it before your next sprint.

If your user doesn’t feel like they’re growing — they won’t stick around.

So ask yourself this: What does “winning” look like after 30 days with your product? And what are you willing to change to help them get there?

Another week, another step in building for people under pressure — and those supporting them.

Back to work.

Eliav