RESEARCH_FILE
Invisible Infrastructure Work
Invisible infrastructure work describes the engineering labor — on-call rotations, system maintenance, dependency updates, documentation, code review, community management — that keeps software systems running but generates no visible output in conventional contribution-tracking systems. Champion et al.'s 2024 empirical study finds this work is systematically under-credited relative to feature development, creating a recognition gap that shapes career trajectories and self-perception for the engineers who do it.
SEE THE PRACTICE
Turn a thought this research explains into one clear move.
THE THOUGHT
“Nobody sees the systems that don't break”
YOUR RECORDED RESPONSE
“Silence is my system’s loudest metric; I can still record it.”
ONE PRIVATE MOVE
Open a blank note and list three things you kept from wobbling today, then add one short phrase after each: “held,” “cleaned,” or “prevented.” Save it privately.
How it sounds in your head
The inner script: 'I spent three months migrating us off the deprecated database driver and nobody noticed — maybe I should just focus on features people can see.' The research names this as a structural recognition problem, not an individual failure to communicate value: the contribution-tracking systems don't count migration work, so it disappears.