The Accompanist's Dilemma: Why Invisible Labor Never Gets Its Due

One-line summary

Support roles are systematically undercredited because those who benefit from your invisibility have no incentive to change it.

This article explores how accompanists and support professionals—from harmonium players to build engineers—remain invisible despite their critical contributions. Using the story of Mehmood Dhaulpuri, the first harmonium player to receive the Padma Shri, it demonstrates that recognition for support work requires intervention from outside the immediate ecosystem. The author argues that waiting for lead performers to advocate for you is a losing strategy; instead, support professionals must make their contributions legible to those whose incentives don't depend on keeping them invisible.

Mehmood Dhaulpuri spent decades as the harmonium accompanist to vocal legends like Bhimsen Joshi and Kishori Amonkar. The harmonium was introduced to India as a colonial accompaniment instrument, and its physical design locks it into that role: no meend, no sustained note-bending, no way to produce the slides that a vocalist’s voice or a sitar’s string can. It is an instrument built to support, not to solo. Dhaulpuri’s genius was in making the lead artist sound better—filling harmonic space, anticipating phrasing, never pulling focus—but that genius was always expressed within the constraints of a supporting architecture. He received the Padma Shri in 2006, the first harmonium player ever to get it. The recognition came from the state, not from the artists he spent his career elevating. That detail matters. The system that benefited from his invisible labor had no incentive to upgrade the status of his role; it could simply label him an exception and leave the category untouched. I see the same pattern in engineering organizations. The build engineer who makes every other programmer more productive, the tools developer who cuts iteration time in half, the QA lead whose test architecture catches regressions before they embarrass the team—these roles are structurally defined as support. When someone in one of them performs exceptionally, the organization doesn't conclude that the role is undervalued. It concludes that this particular person is "really great for a tools programmer." Linda Babcock’s research on non-promotable tasks documents the career penalty: support work is measurable, it disproportionately lands on certain people, and it rarely translates into promotion velocity. The attribution of credit follows narrative salience, not causal contribution. Dhaulpuri’s story is not a lesson in patience or humility. It’s evidence that recognition for a support role, when it comes at all, arrives through an intervention from outside the immediate performance ecosystem—a body with a different set of incentives. If your enabling work is invisible to the decision-makers who control your trajectory, waiting for the lead performer to advocate for you is a losing strategy. The people who benefit most from your invisibility are not positioned to end it. Make your contribution legible to someone whose incentives don’t depend on keeping you in the accompanist’s chair.

The Accompanist's Dilemma: Why Invisible Labor Never Gets Its Due · Soulstrix