Early in development, we had a simple rewards system: earn points, spend them on whatever rewards you have created. Dad rewards. Kid rewards. All from the same pool.
It took about a week of testing to see the problem.
The Conflict
Dads were hoarding points for their own rewards instead of redeeming bonding rewards with their kids. The system we built to encourage bonding was accidentally incentivizing the opposite.
The whole point of the app is time with your kids. If the reward system creates a conflict between dad's interests and family bonding, the system is broken.
The Fix: Two Separate Systems
We split rewards into two completely separate tracks:
Bonding Rewards work exactly like before. Dad earns points through sessions, and he spends them on rewards he enjoys WITH his kids. Ice cream dates, zoo trips, movie nights, camping weekends. The kids are part of the redemption, which means they are motivated to help Dad earn more.
Milestone Rewards are for Dad personally — but he does not spend points on them. Instead, he hits milestones (session counts, streaks, consistency goals) and his partner chooses the reward he gets at each milestone. These can be visible, surprise, or marked Kids Hidden for the... creative partners out there.
Why This Works
Dad never has to choose between his own reward and a bonding experience with his kids. The points always go toward family time. The milestones reward his consistency separately. And the partner gets to be part of the motivation system, which strengthens the family dynamic even more.
It is a small design decision that changed everything about how the app feels. Dad does not feel guilty spending points. Kids do not lose out. Partner is involved. Everyone wins.
Sometimes the best product decisions are not about adding features. They are about removing the conflicts that make good behavior harder than it needs to be.