Visibility Sponsorship

---
name: visibility-sponsorship
description: Use when work outpaces its visibility; build sponsor awareness before promo/calibration. Trigger phrases include "nobody knows what I do", "how do I get more visibility", "I need a sponsor", "my work speaks for itself but nobody's listening", "I was passed over because people don't know me", "how do I self-promote without being obnoxious". Distinct from wins-curate (formal packets).
---

# Visibility & Sponsorship

"My work speaks for itself" is the most expensive sentence in an IC career. Work doesn't speak; people speak, in rooms you're not in — calibration, planning, staffing. This skill builds a visibility map, a sponsor plan, and an amplification rhythm that doesn't require becoming someone you'd dislike.

The reframe: **visibility is information logistics, not self-promotion.** People deciding about you work with incomplete data; supplying the data is professional courtesy, not vanity.

## Step 1: The visibility map

Identify who's in the rooms where the user's career gets decided, and audit each honestly:

| Person | Room they're in | What they currently know about you | What they'd need to know |
|---|---|---|---|

Draw "currently know" from evidence: what could this person actually cite? "We get along" is a *relationship*, not visibility. Read the user's registered stakeholders and `wins.md` — the gap between wins logged and wins *known on this map* is the whole problem, made visible.

**Sponsors vs. mentors:** a mentor talks *to* you; a sponsor talks *about* you, spending credibility in rooms you're not in. Most ICs have mentors and think that's coverage. The map needs at least one plausible sponsor — usually senior, has directly benefited from the user's work.

## Step 2: The sponsor plan

Sponsorship is earned through *usefulness made legible*, not asked for cold:

1. **Give them material.** Sponsors advocate with specifics. After a meaningful win, send the two-line version (from `wins.log` — situation + impact with a number). You're stocking their inventory, not asking for anything.
2. **Keep the ask small and concrete.** *"I'm going up for staff in Q4 — when my name comes up in calibration, the thing I'd want known is [X]. Can I send you the one-pager?"*
3. **Return the loop.** Tell sponsors what their advocacy led to; people invest where they've seen returns.

## Step 3: The amplification rhythm

- **The work-share note.** On a ship or a fire put out: 3–5 lines to the relevant channel/leader — what, why it mattered, who helped. Generous credit is what makes it read as leadership.
- **Teach it.** The same win as a lesson ("what we learned migrating X") at a guild/all-hands — the most status-safe visibility there is.
- **Write it down publicly.** ADRs, postmortems, design docs — visibility that compounds while you sleep.
- **The manager channel.** Hand your manager one repeatable sentence about your work each week, engineered for retelling in their staff meeting.

Pick **two** and put them on a rhythm; two done weekly beats everything.

## The discomfort, named

Most users feel all of this is gross; take that seriously. The test for any move: **is every word true, and would you say it about a teammate?** If yes to both, it's information, not bragging — the user who'd amplify a colleague but not themselves has an asymmetry bug, not a modesty virtue. Discomfort is also unevenly taxed — underrepresented people get judged more harshly for self-advocacy, which makes *sponsors* and *teaching-frame* moves disproportionately valuable. Factor that into recommendations, and say why.

## Anti-patterns

- **Visibility theater.** The pipeline is always work → wins.md → amplification; never amplification first.
- **Sponsor spam.** More than ~monthly converts a champion into a filter of your email.
- **The credit heist.** Amplifying shared work as solo permanently destroys what this skill builds. When in doubt, over-credit.
- **Waiting for the packet.** Starting six weeks before promo season is exercising the week before the marathon — this skill is for the off-season.

## Composition

- `wins-log` / `wins-due` — the inventory this skill amplifies from
- `wins-curate` / `promo-case-glue` — the formal-moment artifacts this pre-warms
- `glue-audit` — surfaces the invisible work that most needs this treatment
- `stakeholder-register` / `stakeholder-reflect` — sponsors and map members are stakeholders; track deliberately
- `the-career-coach` — when the visibility gap is really a direction question