Original Summary

I build group buying for online stores. A shopper opens a group at a lower price, other people join it, and the discount only unlocks if enough of them commit before a deadline. If it does not fill, everyone gets refunded automatically. The thing I got most wrong early was the empty state. I assumed a group with two people in it was still better than no group, because at least it showed the offer existed. It is not. A counter sitting at 2 of 10 for days tells every new visitor that other people looked at this deal and walked away. A product page with no group on it at all converted better than one with a stuck group. It took me a while to see why. Nobody reads a half-used feature as neutral. A missing button is invisible. A button that clearly tried and stalled is evidence, and the evidence says no. The fix was not a better discount. It was smaller targets. Early on I set group sizes too big, and the groups that never filled cooled everyone off. Smaller groups complete more often, the stuck stretch is shorter, and a completed group is the only social proof that does any work. I still do not have a clean rule for how small is too small. At some point a group of three is a coupon with extra steps. The general version is a check I now run on anything I ship: what does this look like when only a few people have used it, and is that worse than it not being there at all? Has anyone else shipped a feature that hurt more half-used than absent? What did you do about the empty state?   submitted by   /u/AffectionateTop2247 [link]   [comments]

  • 情报分类：综合情报
  • 分类依据：内容未命中明确的垂直分类规则，归入综合情报
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/23 03:07:15