you can’t put the genie back in the feed
the internet has a funny way of breaking things, quietly, irreversibly. it takes something scarce like knowledge, attention, intimacy, creativity & floods the system. what was once precious becomes ambient. accessible. abundant. and once that happens, in most cases there’s no going back.
this is a hard truth most product people still haven’t internalized is that once the internet makes something abundant, you will likely not succeed by trying to make the same thing scarce again.
but they keep trying. desperately.
one profile a day. one post. one chance to reply. “designed scarcity” is the go to strategy for anyone hoping to recreate magic in a system that now feels cheapened by scale. the thinking is that artificial constraints will restore focus. bring back meaning. but the truth is brutal.
the human mind doesn’t respond to artificial scarcity after it’s tasted abundance.
it’s like giving someone oxygen for years, then locking them in a vacuum & saying: “breathe better.”
they won’t thank you. they’ll leave.
nostalgia isn’t strategy
when early social apps felt electric, part of it was constraint. a limited network. a tight loop. fewer voices. less noise. but the magic wasn’t just in scarcity—it was in novelty. in being first. in not knowing what came next. that’s gone now. the novelty’s decayed. everyone knows what infinite looks like.
today, scarcity doesn’t feel novel. it feels broken. patronizing. like your product is trying to impose structure not for the user’s benefit, but because you don’t know how to make abundance meaningful.
artificial scarcity is an aesthetic. and not a good one.
scarcity only works when it’s:
• intrinsic: grounded in a real constraint (e.g. bandwidth, curation, time, labor)
• beneficial: clearly improving the user’s outcome (e.g. focus, clarity, quality)
• believable: doesn’t feel like a gimmick or imposed limit
if it fails on those dimensions, it becomes annoying at best, manipulative at worst.
this is what people building “slow” apps don’t get. the problem isn’t pace. it’s signal density. if you want to make people slow down, give them something worth slowing down for. don’t throttle the flow. upgrade the substance.
abundance isn’t the problem. meaningless abundance is.
we don’t need fewer options. we need better filters. more context. tighter loops. tools that know us, shape to us, evolve with us. people aren’t exhausted by access—they’re exhausted by junk access. solve that, and you don’t need to limit anything.
some advice, if you’re building:
• if you’re using constraint as a differentiator, ask: is it real, or just aesthetic?
• assume users have already experienced abundance. design from that baseline, not from nostalgia.
• build for trust, context, & curation. not for artificial deprivation.
• make it feel valuable—not because it’s rare, but because it’s right.
the internet made things abundant. it broke scarcity as a mechanic.
you can’t reimpose it with timers & daily limits. that’s not strategy.
that’s just denial.