The order runs from giving attention to asking for something: you start by letting a colleague talk about their own work, close that loop with specific thanks, then learn what another role's week really contains so the resource you share in step 4 actually fits. Only after three steps of curiosity and one of giving do you ask a senior person about their own history, and only then do you say out loud what you want. Nothing lands as a favor request, because by step 6 you have already been useful twice.
Step 1: Open With Their Work, Not Yours
Colleagues rarely get asked about their own work, so this opening question costs nothing and gives the other person the floor. Because it's the first of six, keep it to one conversation in one setting — a coffee walk, a five-minute gap after a meeting, not a scheduled 'pick your brain' invite. Ask the question, then stay quiet for a beat longer than feels natural; the useful answer usually arrives in the second sentence, after the first polite one. Example: 'What part of the job do you wish more people understood?' If they say 'reporting,' follow with 'what makes it harder than it looks?' The common failure: turning it into an interview where you nod and wait for your turn to talk about yourself. The goal here is only to learn one specific thing and leave them feeling heard.
Step 2: Close The Loop With Detail
By now you've had one conversation, so you have a little vocabulary to work with; this step uses it to close a loop. Gratitude aimed at a specific moment lands far harder than general praise, so name both the thing and the situation: 'When you walked me through the vendor spreadsheet in March, the column you said to ignore first — I still skip it.' Send it in writing, not in passing, because a message can be reread on a bad day. Don't attach a request; the moment you add 'and by the way, could you...' the thanks becomes a transaction. What most people get wrong is vagueness: 'thanks for everything you taught me' is pleasant but forgettable, and it gives the person nothing in particular to be proud of.
Step 3: See Another Role's Real Week
Now that you've practiced asking one good question and giving one clean thank-you, widen the circle past your own team. People in adjacent roles — finance, support, operations, design — are usually happy to describe their week because nobody asks. Request fifteen minutes and spend most of it on logistics rather than ambition: which meetings recur, which days are heaviest, what they produce weekly versus quarterly. 'What does a Tuesday look like?' gets a truer answer than 'what do you do?', which invites a job description. Take notes on the friction they mention, because that is the raw material for the next step. Skipping this because you assume you already know what another role does is the usual shortcut, and it's why so many people recommend a tool that solves a problem nobody had.
Step 4: Give Something Without An Ask
This is where the sequence reverses and you give something away. Step 3 told you what someone's week actually looks like, so you now know which contact is fighting the problem your article or tool solves. Send a single link with one line of why it fits them: 'You mentioned chasing approvals on Thursdays — this template cut that step for us.' No ask attached, no meeting request, no 'let me know if you want to chat.' If an introduction is the better gift, check with both people first and say in the middle email what each of them gets out of it. A generic 'thought you'd find this interesting' blasted to five people undoes the work; one specific send to one named person does more than a newsletter.
Step 5: Ask What Surprised Them
Five steps in, you've been curious, grateful, and useful, which gives you standing to ask someone senior a question about their own history rather than a favor. The phrasing matters: 'which skill got more important than you expected?' invites reflection, while 'what should I learn?' invites advice so generic it could be printed on a mug. Listen for the second-order answer. People often name something unglamorous — writing clearly, running a meeting that ends on time, being the person who writes things down — because they only discovered late how much it compounds. Ask when they first noticed it and you'll get a story instead of a slogan. The way this goes sideways is treating their answer as a syllabus; one remark from one person is a hypothesis, not a plan.
Step 6: Say What You Want, Once
Save this for someone who has already seen you work — a former manager, or the peer from step 1 or 3 — because by now they hold evidence, not just a claim. Say what you want in plain, checkable terms: 'I'd like to spend more of my week onboarding new clients' beats 'I'm looking for growth opportunities.' Then stop talking. The silence is the point; it gives them room to volunteer a name, a project, or a warning, and most people will fill it. Nothing here should read as a job request: no resume attached, no 'if you hear of anything.' The reliable way to spoil this is to hedge so hard your sentence carries no content, or to pivot into asking them for something in the same breath. Say the true thing once and let it sit.
A phone reminder vanishes the instant you dismiss it, leaving no trace that you ever intended to do the thing. A narrow paper strip taped near your monitor gets visibly shorter as you tear off each finished line, and it stays there until the sixth conversation actually happens. Keep the last strip in a drawer as a record of who you now know.