Fjob Internal Network Plan

---
name: fjob-internal-network-plan
description: Builds a plan of six to ten people across other teams worth meeting for your work, with why each, what to ask and what you can offer, a short honest invite you write and send yourself, and notes after. Use for "run fjob-internal-network-plan", "meet people in other teams", "internal networking", "coffee chats at work", "who should I get to know", "I only know my own team", part of the Nail Your First Job with Claude Pack by Polar Bear.
---

# Internal Network Plan

## When To Use
You only know your own team and the work keeps crossing into others. A request stalls in another department, a handover goes wrong, or someone mentions a team you have never heard of. You want to know the people your work depends on before you need a favour from them.

## When Not To Use
Not for your own team and direct stakeholders: that is Who Does What Map. Not for finding more work to take on: that is Stretch Assignment Ask. And not for outreach outside your employer.

## Inputs
- Your current work in a few lines and the other teams it touches
- Your Who Does What Map, if you have one (roles, not the internal directory)
- Anyone a colleague has already suggested you meet
If you have none of this, I start from one piece of your work and the teams it passes through, and mark the output as a first draft.

## Approach
Two-way dependency mapping, a practitioner convention with no single public originator, extended beyond your team. You start from the work, not from job titles: who your work depends on, who depends on it. Every row carries what you can offer, so it never becomes a list of people to take from. The failure it prevents: a bulk "would love to pick your brain" message to twenty senior people, which reads as a template because it is one.

## Workflow
1. Ask at most three questions: which pieces of your work cross into other teams, who has been suggested to you, and what does your employer's AI policy allow (names and teams are personal data and may be internal, so on a personal account use roles and never paste the directory).
2. Start from the work: for each piece, which teams it depends on and which it feeds. List roles there first, then names you already know.
3. Six to ten rows: role (name optional), why for the work, what to ask, what you can offer (fresh eyes, notes from your side, help with a task), status. No row ranks anyone by usefulness or influence, and no notes on personality.
4. Two-way check: a row with nothing to offer is incomplete; find a real offer or drop the row.
5. Invites: Claude helps you draft each one as a model; you rewrite it in your own words. Short, honest, a specific ask and 15 to 20 minutes. One at a time, written and sent by you. Nothing sent in bulk, nothing scheduled or automated.
6. Pace and notes: one or two a week alongside your work, added to Weekly Plan. After each, note what you learned and any follow-up you promised, then keep the promise.

## Output Format
```markdown
# Internal Network Plan
## Where my work crosses teams
| My work | Depends on | Feeds |
|---|---|---|
| [piece of work] | [team] | [team] |
## People to meet
| Role (name optional) | Why, for the work | What to ask | What I can offer | Status |
|---|---|---|---|---|
| [role] | [link to work] | [question] | [offer] | [to invite / met on date] |
## Invite draft (rewrite in your words, send one at a time)
[Two or three lines: who you are, why them, the ask, the time]
## After the conversation
| Date | Role | What I learned | Follow-up I promised | Done |
|---|---|---|---|---|
| [date] | [role] | [note] | [action] | [yes / no] |
## Decision
[You decide who to invite this week and send each invite yourself; each person decides whether to meet.]
```

## Done When
- Every row links to a piece of your work
- Every row has a real offer
- Six to ten rows, no more
- Each invite is one person, one message, in your words
- Follow-ups have a date

## Quality Bar
- Roles before names; no internal directory pasted into a personal account
- Nothing ranks or scores people; the plan is about the work
- The invite says the real reason you are asking
- Notes record what you learned, never judgments of the person
- You write and send every invite yourself, one at a time; no automation, no mass messages, nothing invented about why you are asking.

## Next
Run fjob-weekly-plan (Weekly Plan) to fit the meetings into your week.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).