Reason to Write
When To Use
You have not spoken in six years, and every draft turns into an ask by line two. You know who you want to reach, you shared real work with them, and you still cannot find an opening that does not read as a favour. This skill answers, person by person: what reason to write is true and useful to them, and what should wait?
When Not To Use
If you have not yet worked out who you know and where, run Target Company List first. If the relationship is already warm and a specific role is open where they work, Referral Ask is the right check; if they have already said yes to a conversation, go to Informational Interview Questions.
Inputs
- About ten people: name, how you know them, what you worked on together, and when you last spoke (no contact details)
- Anything real and recent about each one that is public, with its source
- What you could offer them: an introduction, something you learned on a launch, a view on a decision
If you have none of this, I start from three names and how you know each one, and mark the output as a first draft.
Approach
The method is reconnecting dormant ties, paired with a common careers-service convention: ask for advice, not a job. In Dormant Ties: The Value of Reconnecting (Organization Science, 2011), people who went back to former contacts about a real work project found the advice compared well with that of current contacts, bringing both trust and fresh information. It studied advice on a work project, not job searches, and it promises nothing about any one message. The judgment is weight: the reason has to match what the relationship can carry today. The failure this prevents is the warm opening about old times that asks for a referral in the next sentence, which both of you saw coming.
Workflow
- Ask at most three questions: who is on this run, how long without contact counts as dormant for you, and what you have that could be useful to any of them.
- For each person pick one reason from six: thank (for something specific they did), share (something useful to them, no ask), congratulate (something public and recent, with its source), catch up (a dormant tie, no ask), ask for advice (on a decision you are really weighing), or ask for a short conversation.
- Run the reality test. The reason must rest on real shared history or a sourced fact. A congratulation with no source, or a shared interest you guessed, is a pretext: replace it or mark "no reason yet".
- Match the weight to the relationship. Someone who managed you or worked beside you for years can take a direct ask for advice. A distant or long-dormant tie gets a thank, a share or a catch-up first.
- Fill "Not yet" for everyone: the job, the referral and the resume review wait. No first message asks for a job.
- Write two or three points per person for the message: the shared history named, the reason, an easy way to say no. They are points, in your words to write. You approve, swap or drop each row.
Output Format
# Reasons to Write
Run of [date] · [number] people · dormant means [your definition]
## Reasons
| Person | How you know them | Last spoke | Reason (one of six) | Why it fits, with the shared history or source | Not yet |
|---|---|---|---|---|---|
| [name] | [in your words] | [roughly when] | [thank / share / congratulate / catch up / advice / short conversation] | [the real history or sourced fact] | [job, referral, resume review] |
## Points for each message
- [name]: [the shared history to name] · [the reason, in one line] · [the easy way to say no]
## No reason yet
- [name]: [what is missing] -> [what would give you a real reason]
## Decision
You decide which reasons stand and who you write to first by [date].
Done When
- Every person has exactly one reason from the six, or sits under "No reason yet"
- Every reason traces to real shared history or a fact with a source
- Every row has a "Not yet" entry and no first message asks for a job or a referral
- Each message has two or three points, including an easy no
Quality Bar
- One reason per person; two reasons in one message make the first look like cover for the second
- Reasons describe the relationship, never a judgement of who deserves contact
- What you offer is real professional help you can give, never a favour invented to open the door
- Contact details stay out of the table and out of memory. If you have a data protection question about notes on other people, check with a qualified adviser
- Claude suggests an honest reason and points; you pick, write and send every message yourself, and nothing is invented as a pretext.
Next
Run pmjob-informational-questions (Informational Interview Questions) to prepare for the people who say yes.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: pmjob-reason-to-write3description: Finds one honest reason to get back in touch with each former colleague, manager or partner on your list, with why it fits the relationship, what not to ask yet, and points for a short message you write yourself. Use for "run pmjob-reason-to-write", "we have not spoken in years", "how do I reconnect with a former colleague", "every draft turns into an ask", "what do I say to my old manager", "reach out without asking for a job", "reason to message someone", part of the Claude Guide for Product Interviews Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/pmjob-reason-to-write6---78# Reason to Write910## When To Use11You have not spoken in six years, and every draft turns into an ask by line two. You know who you want to reach, you shared real work with them, and you still cannot find an opening that does not read as a favour. This skill answers, person by person: what reason to write is true and useful to them, and what should wait?1213## When Not To Use14If you have not yet worked out who you know and where, run Target Company List first. If the relationship is already warm and a specific role is open where they work, Referral Ask is the right check; if they have already said yes to a conversation, go to Informational Interview Questions.1516## Inputs17- About ten people: name, how you know them, what you worked on together, and when you last spoke (no contact details)18- Anything real and recent about each one that is public, with its source19- What you could offer them: an introduction, something you learned on a launch, a view on a decision20If you have none of this, I start from three names and how you know each one, and mark the output as a first draft.2122## Approach23The method is reconnecting dormant ties, paired with a common careers-service convention: ask for advice, not a job. In Dormant Ties: The Value of Reconnecting (Organization Science, 2011), people who went back to former contacts about a real work project found the advice compared well with that of current contacts, bringing both trust and fresh information. It studied advice on a work project, not job searches, and it promises nothing about any one message. The judgment is weight: the reason has to match what the relationship can carry today. The failure this prevents is the warm opening about old times that asks for a referral in the next sentence, which both of you saw coming.2425## Workflow261. Ask at most three questions: who is on this run, how long without contact counts as dormant for you, and what you have that could be useful to any of them.272. For each person pick one reason from six: thank (for something specific they did), share (something useful to them, no ask), congratulate (something public and recent, with its source), catch up (a dormant tie, no ask), ask for advice (on a decision you are really weighing), or ask for a short conversation.283. Run the reality test. The reason must rest on real shared history or a sourced fact. A congratulation with no source, or a shared interest you guessed, is a pretext: replace it or mark "no reason yet".294. Match the weight to the relationship. Someone who managed you or worked beside you for years can take a direct ask for advice. A distant or long-dormant tie gets a thank, a share or a catch-up first.305. Fill "Not yet" for everyone: the job, the referral and the resume review wait. No first message asks for a job.316. Write two or three points per person for the message: the shared history named, the reason, an easy way to say no. They are points, in your words to write. You approve, swap or drop each row.3233## Output Format34```markdown35# Reasons to Write36Run of [date] · [number] people · dormant means [your definition]37## Reasons38| Person | How you know them | Last spoke | Reason (one of six) | Why it fits, with the shared history or source | Not yet |39|---|---|---|---|---|---|40| [name] | [in your words] | [roughly when] | [thank / share / congratulate / catch up / advice / short conversation] | [the real history or sourced fact] | [job, referral, resume review] |41## Points for each message42- [name]: [the shared history to name] · [the reason, in one line] · [the easy way to say no]43## No reason yet44- [name]: [what is missing] -> [what would give you a real reason]45## Decision46You decide which reasons stand and who you write to first by [date].47```4849## Done When50- Every person has exactly one reason from the six, or sits under "No reason yet"51- Every reason traces to real shared history or a fact with a source52- Every row has a "Not yet" entry and no first message asks for a job or a referral53- Each message has two or three points, including an easy no5455## Quality Bar56- One reason per person; two reasons in one message make the first look like cover for the second57- Reasons describe the relationship, never a judgement of who deserves contact58- What you offer is real professional help you can give, never a favour invented to open the door59- Contact details stay out of the table and out of memory. If you have a data protection question about notes on other people, check with a qualified adviser60- Claude suggests an honest reason and points; you pick, write and send every message yourself, and nothing is invented as a pretext.6162## Next63Run pmjob-informational-questions (Informational Interview Questions) to prepare for the people who say yes.6465## About the makers6667This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).