Marcus wants to move from accounting into product management. He has found a woman on a professional networking site who made the same switch eight years ago. He has drafted a message to her four times. Every version starts with "I hope this finds you well" and ends with "Would you be open to grabbing coffee sometime?"
She will probably not answer. Not because she is unkind, but because the message asks her to do work: figure out who he is, why he picked her, what he wants and whether it is worth an hour. Busy people answer requests that are easy to say yes to. The good news is that making a request easy is a skill, and it can be learned in an afternoon.
Why vague requests get ignored
A request for "coffee" or "picking your brain" hides its real cost. The reader has to guess how long it will take, what will be asked and whether she has anything useful to offer. Guessing takes effort, and when someone receives many messages, the effortful ones slide to "later," which usually means never.
Specific requests do the opposite. They tell the reader exactly what is being asked, so she can decide in a few seconds. Often the specific question can be answered in the reply itself, with no meeting at all. That is a feature. The goal is the advice, not the coffee.
The four parts of a good request
A message that gets answered usually has four short parts.
1. Who you are, in one sentence. Not your life story. "I'm a staff accountant at a mid-sized logistics company, four years in." That is enough for her to place you.
2. Why her, specifically. This is the part most people skip and the part that matters most. "I saw that you moved from finance into product at a software company, and you wrote a post about how your budgeting work helped you prioritize features." This proves you are not sending the same note to fifty people. It also tells her which part of her experience you value.
3. One question she can answer in a few minutes. Not "how do I get into product management?" which is a book. Try "If you were in my position, would you look for an internal transfer first, or apply to product roles at other companies?" She can answer that in three sentences.
4. An easy exit. "If you don't have time, no worries at all. I appreciate you reading this far." This lowers the pressure. People are more willing to help when declining is clearly allowed.
Put together, Marcus's message is about a hundred words. It takes a minute to read and two minutes to answer.
Do your homework first
Before you ask anyone a question, check whether they have already answered it in public. Many people who have made an interesting move have written about it, spoken on a podcast or given an interview. Asking a question she has already answered at length tells her you did not look. Asking a follow-up to something she said publicly tells her you did.
Homework also sharpens your question. After reading her post, Marcus realized his real uncertainty was not whether to switch, but how. That shift turned a vague request into a sharp one.
Follow up once, then let it go
If there is no reply after a week or two, a single short follow-up is reasonable. Keep it to two lines and restate the question so she does not have to scroll back. "Following up in case this got buried. My question was whether you'd suggest an internal transfer or an outside application first."
If there is still no answer, stop. Silence is an answer, and it is usually about her calendar, not about you. Repeated follow-ups turn a respectful request into a burden and close a door that might have opened later.
When she does reply
Two habits turn a single reply into a relationship.
Say thank you, specifically. Not just "thanks so much!" but what you took from her answer. "Your point about transfers being faster because the hiring manager already trusts your work was the piece I was missing."
Report back later. This is the habit almost no one has. A month or six months later, send two lines about what you did with her advice. "I talked to our product lead about a transfer. I start a trial project next week." People who give advice rarely learn whether it helped. Telling them is a gift, and it is the moment when a stranger often becomes a mentor. They have seen you act on what they said, and they are invested in what happens next.
Asking people you already know
The same rules apply to colleagues, former professors and family friends, even though the relationship already exists. Familiarity tempts us to be vague. "Can we chat sometime about my career?" is just as hard to answer from a former boss as from a stranger. Be specific about the question, and suggest a short format. Fifteen minutes on a call is easier to fit into a week than a long lunch.
What this is really about
A good request for advice is a small act of respect. It says: I know your time is limited, I have done my part, and I am asking for something you can give without strain. Many people are glad to help when they are asked this way. Mentorship, for most of us, does not begin with a formal arrangement. It begins with one clear question, answered well, and followed by a note that says it mattered.