# Show HN no-signup barrier during the feedback window > Strip signups, email capture, and other gates off the first-use path during a Show HN launch so the thread produces real usage instead of polite intent. - Canonical HTML: https://growth.iangoh.com/growth-ideas/show-hn-no-signup-barrier-during-feedback-window/ - Source: [news.ycombinator.com](https://news.ycombinator.com/showhn.html) - GrowthDex source hub: [Show HN Guidelines](/sources/show-hn-guidelines-news-ycombinator-com/) - Last checked: 2026-05-27 - Rarity: uncommon - Budget: free - Channels: Hacker News, Onboarding, Website - Stages: activation, launch readiness, feedback loops, ux friction - Key metric: The guideline calls out no signups or emails as the preferred launch path ## Why this can grow A Show HN thread has a short half-life and a skeptical audience. Every extra gate wastes the best moment to learn whether the workflow stands on its own. If the product opens without friction, more people test it, more edge cases get exposed, and the comments stay grounded in actual use rather than guesses. That makes the launch better for both learning and trust. ## 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. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. 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 show hn no-signup barrier during the feedback window can create a measurable lift. 2. Turn the tactic into one offer, page, campaign, or workflow for the Hacker News and Onboarding channel. 3. Use the evidence from news.ycombinator.com 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 Show HN guidelines say to make it easy for users to try the thing out, ideally without barriers such as signups or emails, because that gets more feedback. ## Adjacent tactics in the same lane - [Show HN runnable surface before announcement page](/growth-ideas/show-hn-runnable-surface-before-announcement-page/) - same source, 1 shared channel, 2 shared stages - [HN 'Show HN' with an unusually specific hook](/growth-ideas/hn-show-hn-with-an-unusually-specific-hook/) - same source, 1 shared channel - [Show HN no booster comments or vote rings](/growth-ideas/show-hn-no-booster-comments-or-vote-rings/) - same source, 1 shared channel - [Repeat-usage gate before big launch](/growth-ideas/repeat-usage-gate-before-big-launch/) - 3 shared channels, 1 shared stage ## Read GrowthDex essays Browse the plain-English essay index at [GrowthDex Blog](/blog/). ## Related GrowthDex essays - [The launch thread only works if the product can finish the first job](/blog/the-launch-thread-only-works-if-the-product-can-finish-the-first-job/) - Hacker News, brand trust, launches ## Advisory If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.