There's a category of work that keeps teams functioning but almost never shows up in a demo, a ticket, or a retrospective.
It's the coordination that happens before anyone was ready to coordinate. It's the person who absorbed ambiguity for weeks so their teammates didn't have to. It's what Tanya Reilly — a staff engineer and writer who has written extensively on engineering culture — calls "glue work": the essential labor that holds the architecture together but often goes uncounted because it doesn't result in a pull request.
The gap between feeling seen for that work and feeling invisible isn't abstract. People notice. And when they realize their impact has no home, they quietly start updating their resumes.
Structure determines visibility
Any team structure — pods, squads, or matrixed orgs — consolidates visibility around its own outputs. If your contribution lives cleanly inside that structure, there's a natural home for it.
If your work connects across structures, or enables the work happening inside them, you're operating without a container. Your impact is real, but it has no obvious place to land. This isn't unique to any one way of organizing — the structure simply determines which contributors fall through the gaps.
The definition of done is a visibility trap
If you're building for end users, the project isn't done when the code ships. It's done when people are actually using it — when it's available, accessible, and stable in their hands.
This is where the last mile becomes a visibility trap. It's the person who spent hours on documentation so the API is actually usable. It's the one who monitored the first few hours of traffic to catch the edge cases before they became outages.
A project lifecycle that ends at "released" erases everyone who carried the work across that final threshold. A lifecycle that ends at actual use naturally surfaces those contributors — not as an afterthought, but as part of the definition of done.
Retros as a visibility practice
Project-level retros — not the generic quarterly ones, but smaller conversations tied to a specific body of work — are the most reliable way to catch contribution before it evaporates.
Visibility starts with the invite list. If only the people on the official team are in the room, you've already reproduced the gap. The pre-work is worth doing: trace back through the project, find the dependencies that nearly broke things, and identify the people who resolved them — especially the ones who aren't on the official roster.
When those people are in the room, the retro stops being an audit. It becomes a space where recognition happens peer to peer, where the people who were actually in it get to name what worked. Recognition that comes from the room feels different than recognition handed down from above.
This isn't just process hygiene. It's an act of leadership — the kind that requires slowing down to see the people who are usually too busy supporting others to advocate for themselves. That attention is what determines whether someone doing invisible work feels like they belong to the story of what got built. Or whether they're already out the door before anyone thought to ask.