Manage Glue Workers

---
name: manage-glue-workers
description: Use when managing engineers who gravitate toward glue work (onboarding, documentation, unblocking) and need burnout protection, visibility, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how do I protect my glue person", "glue worker promotion", "coaching someone who's always helping others", "my engineer is drowning in non-promotable work".
---

# Managing Glue Workers

Coaching, protecting, and developing engineers who consistently take on glue work—often invisible, non-promotable coordination, documentation, unblocking, and process improvement.

**Key premise (Tanya Reilly):** Glue work is technical leadership that many organizations don't recognize. Fix the mismatch—make it visible and promotable, or strategically reduce it.

## When to apply

- A report does 30%+ glue work; promotion stalled
- One person always mentors, updates the roadmap, coordinates
- Burnout signs (exhaustion, cynicism, reduced coding time)

Skip when:
- The engineer wants to move to management/TPM (role-change conversation; use `report-career-architect`)
- The glue is genuinely non-essential — run `glue-audit` first to validate it's load-bearing
- Failing deliveries; everyone on core work temporarily

## Prerequisites

Run `glue-audit` first (it can scope to one person) — you need itemized tasks with time estimates.

## The diagnostic questions

1. **Work profile:** typical week and rough time breakdown; which accomplishments were glue-mediated vs solo; "what breaks first if they're out two weeks?"
2. **Career goals & ladder:** target level; what the ladder values there; gap between current work and the ladder.
3. **Credit & visibility:** who knows the glue work; do they frame impact as "helping" or "leading"?
4. **Dependency & burnout:** are they the go-to for everything? What happens when they say no?
5. **Skill development:** growth goals; does glue work develop or crowd out those skills?

## Manager actions: before promotion season

### 1. Credit amplification
- **Public attribution:** retell glue wins as technical leadership (e.g. a design review that saved two weeks of rework).
- **Document artifacts:** have the report save evidence (design comments, Slack threads) in a wins log.
- **Coach the narrative:** "I helped onboard Bob" → "I designed an onboarding flow that cut Bob's time to first PR from 14 days to 6."

### 2. Workload rebalancing
- **Rotate glue explicitly** — shared ownership, not defaulting to one person.
- **Protected time:** block core-work hours; auto-defer non-urgent requests.
- **Delegate:** train others; transfer ownership gradually.
- **Say no for them:** intercept non-essential requests on their behalf.

Don't remove all glue — aim for *balanced* glue.

### 3. Before the promotion packet
- **Run `promo-case-glue` together;** pressure-test each framing.
- **Fill ladder gaps:** if the ladder says "writes production code," plan a small visible core project pre-promotion, glue temporarily reduced.
- **Get a senior advocate:** ensure director+ understands their impact; pre-brief talking points.

### 4. If the promotion fails
- Ask: "What evidence would have convinced you?" Re-check for bias.
- **Cynical solution (Reilly):** if the org won't promote glue-heavy ICs, temporarily reduce glue and ship a clearly technical project to "check the box."
- If the org won't budge, a TPM or EM role may fit.

## Coaching the glue-heavy engineer

1. **Glue as leadership, not service:** reframe "I help people" → "I enable team velocity through coordination and system improvement."
2. **Artifact habit:** save design-review comments, timestamped onboarding docs, Slack unblocks (with permission).
3. **Strategic volunteering:** take high-visibility glue aligned with growth goals; decline invisible glue.
4. **Negotiation language:** *"I can't take that this sprint — my priority is [core project]. Can [name] handle it?"*
5. **Calendar as shield:** recurring focus blocks, treated as unbreakable.
6. **Skill expansion:** regular core technical work — pair on a bug weekly, own a small service, lead a narrow design.

## If the team needs the glue but the org doesn't value it

1. **Ladder advocacy:** propose *"Senior ICs demonstrate impact through code AND by multiplying team effectiveness."*
2. **Title change:** Tech Lead or Principal IC with explicit glue mandate.
3. **Hybrid IC-TPM role** if coordination is what they love.
4. **Protect and pay anyway:** adjust comp if promotion stalls — temporary only; they'll eventually leave if stuck.

## Operating principles

- **Believe the report** when they say the work isn't counted.
- **Make glue visible** — if the committee can't see it, they won't value it.
- **Team glue dependency is a red flag** — distribute it, don't celebrate it.
- **"Good at glue" ≠ "should be manager."** Don't push glue-workers to EM.
- **Protect learning time** for IC-track growth.
- **Bias interrupt:** catch yourself asking a woman/junior person to take notes — ask someone else.

## Composition with other skills

- **`glue-audit`** — run first to establish baseline
- **`promo-case-glue`** — co-create the report's narrative
- **`workload-equity`** — team-level audit if multiple reports do glue
- **`report-career-architect`** — growth plan for IC-track reports
- **`coaching-mode`** — ask, don't tell, when coaching

## Anti-patterns to flag

- **Manager taking credit.** Name the report; they did the glue.
- **Overloading the glue person.** "Alice will do it" is exploitation, not development.
- **Pigeonholing.** "The documentation person" is a dead-end unless formally recognized.
- **Ignoring burnout signals.** Glue is endless without boundaries.
- **"Next cycle."** The current cycle's work must count.
- **Confusing glue with low-value work.** Good glue is high-impact system work.