Identify which people need an introduction and why
Reasons out which specific people need to know you exist before you need their information or cooperation, and what each needs to understand about your role.
In / outOrg knowledge + advisory mandate → targeted intro list (people, rationale per person, what they need to understand about your role)
You might say…
“I kept hitting the head of product for data. He had no idea who I was or why I was asking. I should have fixed that on day one.”
What it does
Working from what you know of the org, reasons out which specific people need to know you exist before you start needing their information or cooperation, and what each needs to understand about your role. Produces a short targeted intro list. Used to scope the introduction work before asking the principal to broker.
Trigger: Use to scope introduction work before asking the principal to broker — so you're making targeted asks, not a scattergun list.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation