I was sitting in a waiting area watching people drift in and out of a small clinic. Some stayed long enough to get their turn, others stepped out after a few minutes, distracted or impatient, saying they’d come back later but rarely doing so. The room kept filling, but it never really felt full. It was more like a constant rotation than a buildup.
That same feeling came back when I opened the CreatorPad task and started going through the flow. I wasn’t doing anything complex—just interacting with the campaign, checking the activity feed, submitting an entry, then refreshing to see how things moved. At one point I paused on the leaderboard and noticed how quickly new names appeared, pushing older ones out of view before they had time to settle. It didn’t feel like growth. It felt like replacement.
While completing the task, specifically when I submitted an entry and then refreshed the leaderboard to see where it landed, I noticed how the interface quietly rewarded immediacy over persistence. The task board updated, the feed shifted, and newer submissions instantly occupied visible slots, while slightly older ones—sometimes only hours old—were already buried. That moment didn’t feel like participation being accumulated; it felt like attention being redistributed in cycles.
I don’t think most new users are actually being retained here. I think they’re being activated just long enough to serve a moment.
That realization sat oddly with me because the surface narrative suggests onboarding, growth, and expansion. But what I experienced felt closer to a system that depends on constant fresh input rather than sustained presence. The energy isn’t coming from users staying—it’s coming from users arriving. And once they’ve interacted, the system doesn’t necessarily need them to remain active, just to have been active at the right moment.
It changes how I interpret engagement entirely. Instead of asking whether users are finding value over time, it starts to look like the system is optimized for short bursts of visibility. A new user logs in, completes a task, sees their name briefly appear somewhere, and that small moment creates the illusion of progress. But the structure doesn’t seem to hold them there. It cycles them through.
What makes it more subtle is that nothing explicitly pushes users out. There’s no friction, no clear drop-off point. It’s just that the environment keeps moving in a way that quietly deprioritizes anyone who isn’t continuously feeding it. And most new users won’t do that. They’ll try it once, maybe twice, and then fade into the background as newer participants take their place.
Using this project as the example, it starts to feel less like a community forming and more like a throughput system. The value isn’t necessarily in who stays, but in how many pass through. Retention becomes secondary, almost irrelevant, as long as activation remains high enough to keep the surface looking active.
That’s the part that unsettled me. Because it suggests that what looks like growth might actually be churn that hasn’t been acknowledged as such. The system doesn’t break if users leave—it expects it. In fact, it might even rely on it.
And if that’s true, then the real question isn’t how many people are joining.
It’s how many ever needed to stay in the first place.