How to ask for help from people who don't know you(pradyuprasad.com) |
How to ask for help from people who don't know you(pradyuprasad.com) |
Body: a vague description of what the problem is and what they’ve tried. Leaving out key details that would drastically change the answer.
Response to answers: now that you have them hooked most answers will be actual questions about what your original post lacked to clarify. Be sure to respond to these as the more engagement on your post makes the algorithm show it to more people. And the second round of answers has a higher chance of answering your question.
Wait until a critical mass of people have seen and attempted answering your question to exhaustion. Hopefully you will be able to piece together a solution.
Gotta get them points?
a LOT of people miss this
1. Be Rich
2. Be Attractive if you didn't complete step 1.
3. If you failed to complete steps 1. and 2., don't bother.
Starting yet another project on my primary GitHub profile has zero return. My secondary profile with trivial code is getting job offers...
I've learned some of these lessons the hard way. I'll add a few. Proof of work is important, but it's not about the magnitude of energy you spend. I went through two iterations of reaching out to my college network. The first time I put so much time into handwriting notes and trying to provide my relatable background. 100 notes, not a single response.
The second time I sent emails that were a few sentences. I had a much clearer ask and devoted the effort into fitting my questions into the email. I wanted a conversation really, but I also tried to communicate what I planned to ask.
15% response rate and invaluable conversations. Less overall "work".
Secondly, and relatedly, don't ever waste someone's time. Don't ask for / accept a meeting if you don't have some semblance of a clear ask. It's hard, especially in early stage business where you're trying to discover what you don't know. But you can try to lay out your tier 1 "here's what I think", "here are the follow ups".
I sensed once that I had irritated someone by lacking the agenda. Another time I took a mutual connection up on an intro where I didn't know what I really needed. I regret both of these.
Thirdly try to pay it forward. It won't always come back around, but you can feel more comfortable asking for help and more cognizant of what a helper (so to speak) is thinking
This is a thoughtful gesture, but there are at least two problems with it
First, a handwritten note isn't easy to respond to. With an e-mail, you can leave the message in your inbox until you have time to respond and then it's one click to start responding. With a hand-written letter the recipient would have to context-switch from reading mail to using a digital device and they'd have to transcribe your e-mail address. It's not much work, but it's still work that someone has to make time for.
Second, it's an unusual thing to do. It's important to communicate with people through normal, comfortable communication channels where the etiquette is known. Having someone handwrite a letter and look up your mailing address is unusual. Unusual behavior triggers people's suspicions. You weren't trying to scam anyone, but you should be aware that one of the tricks used in scams is to invest unusual amounts of attention and energy into someone. It can trigger a suspicion that you're really after something else.
Your second round of sending short e-mails had neither of these problems. Easy to reply to, nothing unusual about it. It's the way to go.
Solid advice, (but to others reading) don’t optimize for not irritating people.
Especially your professional network. You built those relationships because you wanted to use them in the future, and the future is now… so, tap them! If they don’t like that, no big deal, no sweat, move on.
If you’re irritating multiple people constantly, then yea you’re probably doing something wrong. But if it’s one person once in a blue moon, that happens, don’t over optimize for avoiding that. You can’t make everyone happy
i'd rephrase as "visible lack of effort is problematic" - anything above that passes the bar for me, and other factors become critical
> Thirdly try to pay it forward.
The thing I've found is that often what's simple and easy for me (the person being asked) is difficult or overly cumbersome for the person asking (or even not asking). Often it's due to simply being in the right position or knowing the right people. We're all in this together and there's so much to success that's beyond talent and skill. All the small little actions add up even if you don't get to see how
My number one tip therefore is to try to put yourself into the perspective of the other side. Did you give them all the information they need to know? Of course you will know a lot of things about your project that are really obvious to you, but that you would need to mention to others so they understand what you are talking about. On the other hand if you want to hire a plumber, you don't need to tell them a long story about the roof of the house. Conceptually the plumbing and the roof may both be house-related issues in your mind, but you're wasting the plumbers time. So that means the time/patience of the person on the other side is a valuable resource.
Similar story. Sent out 900+ emails to scientific illustrators; about 25 accepted. Here's the result:
Women are way better at asking for help and getting it as compared to men.
there's some very well-known psychology tricks that you can use to get better outcomes. Cialdini's book and Munger's speech on psychological bias are first class.
you want to be opportunistic but not too attached to your ask.
ask for a lot and then back off works tremendously better even with kids
perception (looks, reputation, stereotypes) have an outsized impact on outcomes. look at any successful sales department for proof of this. perception can be faked unfortunately.
put hard limits (of time) on your ask. make it clear that its a one time ask.
The most counterintuitive aspect (covered in the article) is that you'll get a yes more often if it's easy for them to say no.
When I’ve been in positions where a lot of people ask for help, this is the #1 place I saw people drop the ball.
The advice to show proof of work up front is important. What isn’t so obvious is that the proof of work needs to go deeper than surface level. Putting up a single blog post or having Claude write some code that you upload to GitHub doesn’t cut it. You have to show that you’ve been putting effort into this for all the right reasons, not just as a ploy to appear like a serious person. When you get 10 requests for help every week you get very good at being able to tell who has been putting in the work and who thought they could appear like a serious person by putting on a little show.
This doesn’t end after you get the meeting. Following up is just as important. When someone makes time to hear you out and offer advice, you need to demonstrate that you tried what they suggested. You can choose not to follow their advice, but that’s probably the end of the help you receive. It’s a choice.
The easiest way to blow it is to ask for someone’s help, then ignore it or fail to follow through. If someone helps you, follow up with some contact to explain how it helped, or at least how you tried it. Nothing is more frustrating than setting aside time to help someone and then a month later you run into them and learn that they haven’t gotten around to doing the thing they wanted help with.
Is this person actively solving the problem, tried a bunch of approaches and ran into a road block where they're asking for help?
Or are they wishing the problem didn't exist, so they do as little as possible, hoping somebody else will solve the problem for them?
There's a big difference between:
"Hey, I saw this job at [company you work at], could you refer me please? I'm [lists skills and experience]"
and
"Hey I'm thinking of applying to [company you work at] for the product designer position and I want to make an impression, so I'm putting together a demo Figma with a couple of things I'd fix and how. I spotted those when I did the onboarding for your free trial. I'm curious if you could tell me whether [design flaw] is intentional to deter abuse or if that's something I could fix? Totally get if that's confidential"
The part where you're solving the problem instead of hoping someone else will solve it for you, that's much more important then how you word it.
I wrote about this from the perspective of someone with no connections [0] but I think even if you're well connected, reaching out to people from other networks is a useful way to gain access to great thinking, information, and opportunity.
[0] https://www.nair.sh/guides-and-opinions/marketing-under-pres...
Explain your rationale for picking that person you are trying to reach.
Put yourself at mercy of the helper.
Last but not least.
End the recording and turn of the camera on your R2D2 droid.
I've had people assume that person X must be asked several times a day for help when they're really asked once every few years. Alternatively, I know people who assume they are sending some totally unique request to someone who gets a dozen of the same inquiry every single day.
Until you get a good baseline figure of how competitive your request for help is, everything else is pre-mature optimization. The best thing is to just be lightweight about it and dash something off as soon as you think of it and to not be too emotionally invested in whether you get a response or not. Only when you gather evidence that the response rate is below what you expected should you try to optimize how you ask.
"Hello John, are you available to chat later today about Foo Product?"
Or sometimes just:
"Hello John"
I know they want something from me, but I have no idea what, how much effort it will require, how urgent it is, or whether I am even capable of helping.
A much better approach is more like this article outlines:
"Hello John. I'm looking into in a client-reported issue with Foo Product. The customer states they are unable to do X. The support ticket is <link to ticket>. I've done some investigation and think I have identified the root cause with <possible root cause>. Are you available for a brief 30 minute call this afternoon to discuss the issue as well as some potential fixes?"
That way I have some idea of context, priority, and what they are looking for from me. I can also review the details of the ticket prior to the call, which makes for a more productive conversation. Or if there is someone else who is more knowledgeable than me, I can request that we add that person as well.
If you're in the habit of starting work conversations on slack with just "Hello" - I would highly recommend that you start including additional context when initially reaching out.
It's especially effective if it's a timely event. People do talks and interviews to meet people and get some attention, so you're basically shaking hands with someone who's ready to shake yours.
On the other hand, at least make sure you have looked into what the LLM says about your questions. It is aggravating to get a request which an LLM can answer correctly.
Just say "hello/excuse me" in their language and then ask the question in your language. If they speak it, they will often answer you quickly. Sometimes you can even see a look dawn on their face after the fact as they realize you skipped the first step.
I'm trying to inoculate myself against the imaginary idea that I'm an idiot, but the reality is, by the time I get to idea #5, I'm probably grasping at straws. The 5 most obvious solutions might not be someone else's 5. What I need their help with is not coming up with idea #6 in terms of likelihood, but _their_ best first idea -- which might send me in a totally different direction!
Always start your email to a busy/important person with exactly what you want from them. Within the first two sentences. Then peel the onion, giving details from more important to less important.
This gives the reader opportunity to stop reading at any point having decided to help you or not, with the least waste of their time. In many case, the person can skill your description of your work, and just tell you what to do.
Especially when starting something yourself. It sounds obvious but it took me far too long to long to go to people actively talking about their problems and help them vs asking them for problems they are facing.
Making that switch was a big difference in terms of outreach.
I make sure to do this at work, when I’m asking questions about things outside of my domain. I do it when talking to tech support for my ISP or phone, when I contact maintenance for my apartment and when I take my car in for service.
But what about advice for giving help to someone?
There's plenty of ways that giving someone help can go horribly wrong, and I think that it's not uncommon for people to be blindsided by such a request.
I’m definitely borrowing the phrase “galloping neurosis” the next chance I get.
I did have in mind something more like the Socratic method, asking pointed questions of your mentee, guiding them but not pushing them. I suppose that in a weird way that essay is the Hunter S Thompson idea of the socratic method.
I really do think it's important to give thought to HOW to give help.
Especially in the technical communities, there's such an over-emphasis in "asking correctly". It perhaps started with usenet (think Eric S Raymond's INSUFFERABLE FAQ on "How To Ask Questions The Smart Way"), and ended with the persnickety and now thankfully moribund stackoverflow gameified and toxic question-and-answer forum.
https://www.catb.org/esr/faqs/smart-questions.html
It reads a bit harsh in some places but well warranted IMHO.
* No abbreviations like "plz"
* No wall of text (and no AI walls of text)
Nitpick but this phrasing always confused me. Who assigns it? God?
(Also I think that happens slightly before the birth!)
OTOH,
> make it easy to say no
is the best piece of advice amongst many other pieces of good advice
> asking for a resource to start with is better than “can I pick your brain?”
I wish people would just stop 'helping' each other (as it is currently). Help should only be given to people who are in dire need and it should only be enough to allow them to stay afloat. Helping someone to become a multi-millionaire is not 'help', it's injustice; it only exacerbates the problem. It creates a system where success is impossible without receiving help. This, in turn, creates a totalitarian system where people are just trading favors with each other since everyone who succeeded helped each other to various extents and everything they're doing is balancing favors.
'Paying forward' really means; giving favors to someone new in order to obtain favors from them in the future. It's not good for anyone.
Also, no real trust is being built here. It's not trust if you need to keep paying. It's dependency.
Show Respect, Be Polite, Be Specific and finally; always follow-up with a Thank You whether you got help or not.
In the second one it’s really obvious to me that they just want a referral. It would annoy me that they are making me read extraneous information.
The chance that I know whether or not it’s intentional is extremely low. If I don’t work on that part of the app, I’m not going to go chase down the product person would might know.
I think it’s much, much less likely to get any response, despite being higher effort on the sender. It’s too specific and too likely to step on a landmine of “I don’t know the answer and I’m not going to go on a side quest to find it for someone I don’t know…”
Out of 40 messages, 38 replied and agreed to a phone call, and none of them actually asked for the money.
[0] https://mtlynch.io/notes/designing-the-ideal-bootstrapped-bu...
I have run cold outbound to senior buyers for about twenty-five years, people who owe me nothing and get pitched daily.
Two things that I find move the reply rate more than anything else:
- First, a specific, bounded ask that names the twenty minutes and the exact question, so they can price the interaction in their head in one read. The article's "so short as to be unsummarizable" line is the same concept.
- Second, and this is the one people skip, evidence that you already know the answer to the easy version of your question, so the only thing left to ask them is the part that needs their judgement.
Offering to pay is a cruder version of both. It says the cost is real to you and you have thought about theirs.
The ones that land make the money almost incidental, the way Cohen's did. Make the ask cheap enough that saying yes costs them less than saying no.
Give them your answer to the easy version first, so the only thing left to ask is their judgement on the hard part. People will spend that on a problem they already feel daily, far sooner than they will do your thinking for you.
Success is impossible without receiving help. I have someone that I’ve never met who helps by ensuring that reliable power arrives via overhead wires to my house. Someone else’s help ensures that my garbage is carted away, clean water arrives under pressure, and 100s of other things that would be incredible drains on my time before I could do the first thing that was valuable to me or my family.
Take the help when you need it.
Give the help when you can.
Also, your examples of help are way more broadly defined than what the parent poster is talking about. It takes a stretch of imagination to classify the fact that people are working for wage to make sure I have water with specific programs that give arbitrary groups some advantage, even when this is done with the best possible intentions.
Also, I wouldn't frame the person who provides electricity as helping you if you're paying them. It's an exchange since you earned that money. This isn't the definition of help I'm pushing against.
Also, help might be OK and even necessary in a different system for example, but it doesn't work in the current system IMO. My view is context dependent based on my experience in the current system and how it seems to consistently weaponize help and altruism.
As a corollary, I'd also say that it's is the helper's best interest to help someone *'deserving' not just someone asking for help. This is easier said than done. For one the helper must do a lot more wok than helping.
*=one could have a big discussion on who is truly deserving.
Also we there are many definitions of 'help' which of course I'm sure you are aware of.
Some people think of the postman who brings them letters as "helping" but I don't consider it that way as they're being paid.
The people who volunteer to charities are helping, I guess... Though some of them may just be looking for future leverage/opportunities; e.g. padding their resumes...
Some people, especially who have money, tend to struggle to isolate the monetary incentive and discount the value of money being given to the person in exchange.
That's flaweed though.
First question that I will have would be - why do you need the what are you asking for. Because you are relying on my expertise and I do expect myself to deliver the best possible answer. And then we go into 10h+ land.