Glue Work: The Invisible Work That Doesn't Promote You

The work that makes the team succeed and the work that gets you promoted are two different lists — and glue work is only on the first one.

Origin

The term comes from Tanya Reilly's 2019 talk "Being Glue" (noglue.work). Her observation: on every team there is someone who onboards the new hires, writes the docs nobody asked for but everybody uses, takes the meeting notes, chases the other team for the API change, coordinates the release, notices the flaky test and files the ticket, and unblocks three colleagues before lunch. This work is glue — it holds the project together. Remove it and the team visibly degrades. And yet, at review time, the glue person's packet is thin: "great team player" but "where are the technical contributions?" Reilly's talk hit a nerve because thousands of engineers recognized themselves — or the person on their team who was quietly stalling.

Glue work is not busywork. It is genuinely high-leverage: one hour spent unblocking a teammate can save the project a week. That's exactly what makes it seductive and dangerous.

Why It's Invisible: The Mechanics

Promotion systems don't measure impact directly — they measure legible evidence of impact. A promo committee of people who've never worked with you must decide, in twenty minutes, whether you operate at the next level. They can only weigh artifacts: designs you authored, systems you shipped, diffs with your name on them, launches you led. These are legible — attributable, countable, comparable across candidates.

Glue work fails every legibility test:

No artifact. There is no diff for "the release didn't slip because I noticed the dependency conflict on Tuesday."
Diffuse attribution. When glue works, the project succeeds and the credit flows to whoever owned the visible deliverable. Glue's success is the absence of failure, and absences don't show up in packets.
Counterfactual invisibility. Nobody sees the disaster you prevented. The org only prices coordination work after it stops happening — and by then you're gone or burned out.
It reads as personality, not skill. "She's so helpful" is a character compliment, not a promotion argument. The committee hears conscientiousness where they should hear operational leadership.

There's a second mechanism: glue work is a commons problem. Everyone benefits from the docs and the coordination; nobody individually pays for the absence of it. So it defaults to whoever has the lowest tolerance for team dysfunction — the most conscientious person in the room. Reilly documents that this disproportionately means women, who are both more often expected to volunteer for it and penalized more for declining. The result is a systematic pattern: the most team-spirited people accumulate the least promotable portfolios.

The Seniority Asymmetry

Here is the twist that trips up technically strong engineers: glue work is not intrinsically career-negative. The same work has a different price depending on your level.

At staff+ levels, glue work is the job description: aligning teams, unblocking projects, mentoring, driving process. A staff engineer who coordinates a cross-team migration gets promoted for it, because at that level the org has already granted them the credibility to have coordination read as leadership.

At junior and mid levels, the org is still asking a different question: "can this person do hard technical work independently?" Every hour of glue is an hour not spent producing the technical evidence that answers it. Worse — a mid-level engineer doing staff-level glue doesn't get staff-level credit; they get "helpful" while their peer who hid in a corner and shipped the gnarly migration gets "strong technical contributor." Same work, different level, opposite outcome. You must earn the license to do glue work before it pays.

When It Hits You

Concrete cases you will recognize:

You're the onboarding buddy. Again. Third new hire this year. Each one costs you a month of half-productivity, and your manager's calibration notes say "output slowed this half."
You're the note-taker and follow-up-chaser in every meeting, because if you don't, decisions evaporate. Nobody assigned this; you just couldn't watch it fail.
You're the cross-team liaison. You know everyone, so every dependency runs through you. Your calendar is meetings; your peer's calendar is deep work.
You fix the CI, the runbooks, the on-call docs — infrastructure of team velocity — while feature credit goes to feature authors.
You unblock people all day and end the sprint with your own tickets untouched, then work evenings to catch up. This is the trap in one sentence: so helpful you never grow.

Countermeasures

The fix is not "stop caring." It's forcing the org to price the work — or refusing to sell it below market.

Make it legible. Write it down as it happens: what you did, what it prevented, what it saved. Quantify where possible ("onboarded 3 engineers to productivity in 4 weeks vs. team baseline of 8"). Turn recurring glue into artifacts — an onboarding doc, a release checklist, a process RFC — because artifacts survive promo committees and hallway help does not.
Force an explicit deal with your manager. The killer question: "I'm spending ~30% of my time on X. Is that in my goals for this half?" Two acceptable answers: it goes into your written goals and counts at review, or your manager explicitly reassigns/deprioritizes it. The unacceptable answer is the default one — you keep doing it and it counts for nothing. Making the tradeoff explicit converts an invisible tax into a negotiated assignment, and puts the cost on your manager's books instead of yours.
Timebox it. Glue demand is infinite; it expands to fill all available conscientiousness. Cap it (e.g., one hour a day, protected mornings) and let some things visibly drop. Visible drops are a feature — they're the only way the org learns the work exists.
Trade, don't hoard. Rotate the note-taking, the release captaincy, the onboarding. Rotation spreads the tax and makes the work visible as work rather than as your personality.
Or change roles so glue IS the job. If you genuinely love this work, TL and EM tracks price coordination correctly. That's a legitimate move — the only illegitimate move is doing the EM's job on an engineer's scorecard.

The Diagnostic

If you deleted every non-technical thing you did this quarter from your promo packet, would the packet get shorter — or would it just get honest?