# HN Show label after substance, not before

> Do not rely on the Show HN label as the growth mechanic; make the product and repo worth the technical conversation first.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/hn-show-label-after-substance-not-before/
- Source: [arxiv.org](https://arxiv.org/abs/2511.04453)
- GrowthDex source hub: [arXiv: Launch-Day Diffusion: Tracking Hacker News Impact on GitHub Stars for AI Tools](/sources/arxiv-launch-day-diffusion-tracking-hacker-news-impact-on-github-stars-f/)
- Last checked: 2026-06-10T06:39:08.000Z
- Rarity: uncommon
- Budget: free
- Channels: Hacker News, Launch, Positioning
- Stages: Show HN, launch format, product readiness, technical conversation, demo access


## Why this can grow

The Show HN label can help set expectations, but it is not a growth spell. The diffusion paper found the Show HN tag showed no statistical advantage after controlling for other factors. The official Show HN guidance also points in the same direction: people should be able to try the work, not just read a signup promise. The useful founder move is to treat Show HN as a format for a ready artifact, not a shortcut around readiness. If the repo, demo, docs, and technical claim are clear, the label can frame the post. If they are weak, the label only makes the gap easier to notice.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. I would treat this as earning the right to be in the room, not dropping a campaign into a room. In community-led growth, the first job is to notice what people already care about, then bring a useful proof, tool, teardown, or question that makes the conversation better. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where hn show label after substance, not before can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Hacker News and Launch channel.
3. Use the evidence from arxiv.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

The Launch-Day Diffusion paper reports that the Show HN tag had no statistical advantage after controlling for other factors, while Hacker News guidelines emphasize submitting work people can actually try.

## Adjacent tactics in the same lane

- [HN posting-hour test before front-page hope](/growth-ideas/hn-posting-hour-test-before-front-page-hope/) - same source, 2 shared channels
- [HN star-window ledger before launch retrospective](/growth-ideas/hn-star-window-ledger-before-launch-retrospective/) - same source, 1 shared channel
- [HN public API launch tracker before vanity summary](/growth-ideas/hn-public-api-launch-tracker-before-vanity-summary/) - same source, 1 shared channel
- [Show HN runnable surface before announcement page](/growth-ideas/show-hn-runnable-surface-before-announcement-page/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The GitHub repo should be ready before Hacker News arrives](/blog/the-github-repo-should-be-ready-before-hacker-news-arrives/) - Hacker News, GitHub, developer marketing

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.