HN Debrief

How to ask for help from people who don't know you

  • Startups
  • Careers
  • Communication
  • Management

The post is a guide to asking strangers or weak ties for help without sounding entitled or wasting their time. Its core advice is familiar but useful: identify yourself, explain why you chose that person, show some proof you have already tried to solve the problem, ask for something bounded, and leave the other person an easy exit.

Treat outreach as an interface design problem. Cut the cognitive load, show genuine follow-through, and give enough context that the recipient can answer, redirect, or decline in under a minute.

Discussion mood

Mostly positive and pragmatic. People liked the post, but the mood was less "great etiquette advice" and more "keep this ruthlessly short, concrete, and low-effort for the recipient," with extra skepticism toward performative effort and AI-polished outreach.

Key insights

  1. 01

    Reduce reply friction first

    The strongest practical refinement was that a message fails long before the recipient judges your worthiness. It fails when replying is annoying. Handwritten notes, vague Slack pings, and long preambles all add tiny bits of work that busy people refuse on instinct. Email or chat works better because the context is already there, the reply affordance is obvious, and the recipient can answer or redirect without a scavenger hunt. The same logic is behind nohello.net. Front-load the actual request so the person can decide immediately.

    Write the first message so it can be handled from a notification preview. If the recipient has to ask what you want, find your contact info, or schedule a call just to understand the issue, rewrite it.

      Attribution:
    • Aurornis #1
    • andyfilms1 #1
    • freetime2 #1
    • primaprashant #1
  2. 02

    Proof of work must be real

    Showing effort helps only when it proves you are genuinely trying to solve the problem. People who get many requests said they can spot fake seriousness fast. A bloated list of things you tried, an AI-generated repo, or a polished artifact made to impress does not help. It often hurts. The useful signal is simpler: you did enough work to hit a real roadblock, and you are likely to act on advice. That is why follow-up matters. Reporting back on what you tried after getting help is stronger evidence than any preamble.

    Show one or two concrete steps you took and the exact point where you got stuck. Then follow up later with what changed, even if the advice did not fully solve it.

      Attribution:
    • Aurornis #1
    • FinnLobsien #1
    • bbminner #1
    • rconti #1
  3. 03

    Do not over-optimize before you know demand

    A sharp point was that most people wildly misjudge how crowded a request category is. Some recipients get flooded. Others almost never get asked. Until you know which case you are in, elaborate outreach strategy is premature. Keep the ask lightweight, make refusal easy, and gather signal from actual response rates. The emotional side matters too. Treat low response as data, not as a verdict on you.

    Start with a simple template and send a small batch. If response rates are low, adjust one variable at a time such as subject line, ask size, or who you target.

      Attribution:
    • shalmanese #1
    • johnathan101 #1
    • kayo_20211030 #1
  4. 04

    Offering to pay changes the dynamic

    Paying for a short consult was framed as more than compensation. It is a seriousness signal and a consent mechanism. A note that says "how much for 20 minutes on questions A, B, and C" gives the other person clear options. They can quote a price, answer inline, decline, or waive the fee. The WPEngine anecdote reinforced that this can massively improve replies even when nobody actually takes the money.

    For expert outreach, especially on LinkedIn or adjacent professional channels, test a paid micro-consult ask. Put the scope and questions in the first message so the recipient can price it instantly.

      Attribution:
    • mrtb #1
    • mtlynch #1
  5. 05

    Personalization now needs stronger signals

    Referencing someone's work still helps, but commenters noted that generic praise has been cheapened by large language model outreach. "I loved your writing" no longer proves much. Timely and specific references still cut through because they show actual attention. Mentioning a recent talk, interview, paper, or book and tying it directly to your question remains useful when it is concrete enough that a template could not have produced it.

    If you personalize, anchor it to one specific artifact and one specific reason it is relevant to your ask. Generic admiration now reads like automation.

      Attribution:
    • lisper #1
    • currymj #1
    • muzani #1

Against the grain

  1. 01

    Hyper-specific asks can lower response

    Several people pushed back on the idea that more detailed and more bespoke always means better. A very narrow question can trap the recipient into a dead end if they are not the exact owner of that area. Then helping requires internal legwork they will never do for a stranger. A broader referral ask, when paired with a job link or resume, may actually be easier because it leaves room for redirection and serendipity.

    Keep the ask bounded, but do not make it so specialized that only one exact answer is useful. Leave space for "I am not the right person, but talk to X."

      Attribution:
    • hershey890 #1
    • sokoloff #1
    • hyperultra #1
  2. 02

    Twenty minute consults are not universal

    The paid micro-consult tactic is not a clean fit for everyone. One commenter said a serious question instantly expands into hours of thought because they feel responsible for giving a real answer, not a quick impression. For people like that, a "20 minute brain pick" understates the commitment and can cause an immediate no, even if they would happily help for free on something intrinsically interesting.

    When you offer payment, avoid assuming the work is naturally small. Frame the scope as your desired format, then invite the recipient to reshape it if the question needs more depth.

      Attribution:
    • lstodd #1 #2
  3. 03

    Help networks can entrench insiders

    One commenter rejected the whole pay-it-forward culture as favor trading that advantages people with access and turns success into a network game. That view was far outside the main mood, but it highlights a real downside of informal help systems. They reward people who already know how to navigate them and can make opportunity feel less merit-based.

    If you run a team or community, do not rely only on private backchannels for access. Pair personal outreach with public, legible ways for outsiders to get in front of you.

      Attribution:
    • jongjong #1

In plain english

GitHub
A website and platform used to host code and collaborate on software projects.
Slack
A workplace messaging and collaboration platform.
WPEngine
A company that provides managed hosting and related services for WordPress websites.

Reference links

Related essays on outreach and help

Tactics and examples

Books and letters mentioned

Example work shared by commenters

  • Impacts PDF
    Shared as the outcome of one commenter's mass outreach to scientific illustrators.
  • Impacts Bibliography
    Companion bibliography for the same outreach-driven project.