Integration over destination

Why wellness programs fail, and what CleanLeaf taught me about designing for how people actually behave.

Stop building destinations. Start showing up where people already are.

We proposed CleanLeaf at Syracuse University’s Martin J. Whitman School of Management Dean’s Sustainability Challenge and walked away with 2nd Judge Favorite.

The proposal started with a question: why do wellness programs always fail, even though they are meant to help people?

The answer is not hard to figure out. They fail because they treat wellness as a personal problem you can solve with a single tool. Download this app. Track what you eat. Stay motivated on your own. The dropout rates are brutal, and the people who stick around are the ones who already had the habit in the first place.

But the real win for me was stress-testing a philosophy I keep coming back to in every problem I work on.

This is not just a wellness problem. The same pattern exists across the tech industry. Instead of asking where people’s attention already is and putting the solution there, we keep building new platforms and expecting people to come to us. Instead of designing for how people actually behave, we design for how we wish they would. The result is always the same: abandoned tools, wasted spend, and the assumption that the user failed when really the design did.

We now have more marketing tools than ever and worse marketing than ever. That is not a coincidence. Every new tool in the stack is another layer between the marketer and the actual customer. The pattern is similar in any other business function.

The principle underneath all of this is simple. Stop designing for how you wish people behaved and start designing for how they actually do. The best solutions find where attention already lives, where the workflow already runs, where the decision is already being made, and they remove whatever friction stands between that moment and the better outcome.

CleanLeaf was our attempt to apply that thinking to wellness. Instead of building a standalone app, we designed an ecosystem where challenges reach people through the group chats that already exist within universities and workplaces, on Teams, Slack, or WhatsApp. You photograph your meal, our engine scores it, and your progress is gamified within your community through leaderboards, streaks, and peer accountability.

The model is B2B2C because it builds on something that already exists: we are naturally organized into communities as students at a university or employees of a corporation. Research is consistent that habit formation is most effective when it happens within exactly these kinds of communal environments. The institution pays for the platform, their people benefit from it, and every meal logged is already a data point in their sustainability reporting. Both sides get what they need from the same action.

I think integration over destination is where all of business design is headed, not just wellness.