Someone has to take notes in the strategy meeting, and by the third quarter of most teams, everyone already knows who that someone will be. She's not the newest hire, not the most junior person in the room, and not even always the most agreeable person on the team — she's just the one who said yes once, eighteen months ago, and was never asked to stop. Ask her how she ended up owning the shared calendar, the intern onboarding checklist, and the notes from every cross-functional meeting, and she probably can't tell you either. Nobody assigned it. It just accumulated. That accumulation has a name now, and a growing body of research behind it.
What "Non-Promotable Work" Actually Means
In 2018, economists Lise Vesterlund, Linda Babcock, Laurie Weingart, and Maria Recalde ran a simple experiment: they asked small groups to select someone to write on a whiteboard, a task with zero strategic value and no bearing on anyone's future. Women volunteered roughly 50% more often than men, said yes more often when asked directly, and got asked directly more often in the first place. The researchers called this category "non-promotable tasks" — work that keeps an organization running but never shows up in a performance review, a bonus calculation, or a promotion case. The four professors later expanded the finding into a book, The No Club: Putting a Stop to Women's Dead-End Work, and the pattern they describe will sound familiar to anyone who has sat through a meeting waiting to see who volunteers first.
LeanIn.Org and McKinsey have tracked a related pattern in their annual Women in the Workplace report under a blunter label: "office housework." Taking notes, planning the team's holiday party, being the default onboarding buddy for every new hire, sitting on the diversity committee, cleaning up a project after someone else leaves the company — none of it is trivial, and someone genuinely has to do it. The problem isn't that the work exists. It's that the same handful of people do it, year after year, while a different set of colleagues spend those hours on the work that actually gets discussed when promotion decisions are made.
- Taking and distributing meeting notes
- Organizing team events, holiday parties, and birthday collections
- Acting as the informal onboarding buddy for every new hire
- Volunteering for the DEI or culture committee
- Documenting a departing colleague's work, because someone has to, and it's rarely the person who inherits their actual projects
Why Women Get Asked More — and Say Yes More Often
Ask why this keeps landing on the same people and you'll usually get a shrug, but the research isn't vague about it. Managers ask women to take on non-promotable work more often, largely because of an unconscious assumption that competence at logistics and care work is a female trait rather than a skill anyone can build. Women also say yes more often when asked, and the reason isn't a personality difference — it's that declining carries a bigger social cost for women than it does for men. In the original whiteboard study, when researchers removed the ambiguity and assigned the task at random instead of asking for volunteers, the gender gap in who did the work disappeared almost entirely.
If you've noticed you're the one who gets asked first, that's not a coincidence, and waiting for the pattern to correct itself is a bad bet — nobody's manager has ever spontaneously rebalanced a team's invisible workload without being asked to. The fix isn't becoming a different kind of person who's suddenly comfortable saying no. It's building a habit and, eventually, a system, because willpower runs out around the fourth "just this once" of the quarter.
The Real Cost: Where the Hours Actually Go
Six hours a week is a part-time job.
That's roughly what a mid-career employee juggling three or four "extra" responsibilities can lose to non-promotable work once note-taking, event planning, and ad hoc onboarding are added up — and most people underestimate it badly until they actually track it, because each individual task feels too small to matter on its own. A 45-minute meeting recap here, a two-hour party-planning call there, an afternoon spent walking a new hire through systems nobody documented: none of it looks like much in isolation. Stacked across a quarter, it's the equivalent of an entire extra project, minus the visibility, minus the credit, and minus any mention in a calibration conversation about who's ready for the next level.
Audit Your Own Task Load Before You Change Anything
Track every task for two weeks before deciding what to change — guessing doesn't work, because this kind of work is specifically the kind that feels small in the moment and enormous in aggregate. A simple four-column log does the job: what the task was, how long it took, whether it would ever appear in a performance review, and who actually asked you to do it. After two weeks, most people find at least one task that nobody remembers assigning — it just became "hers" because she did it once during a busy week and it was never reassigned to anyone else.
Once the log fills in, sort it by two questions: does this task have a visible outcome anyone above you will ever hear about, and could literally any other qualified person on the team do it instead of you specifically? Tasks that fail both tests are the ones worth renegotiating first, not the ones that feel most annoying in the moment — annoyance and career cost aren't the same measurement, and it's easy to spend your limited social capital pushing back on the wrong thing. A task might be tedious but genuinely rotate fairly across the team already; that one isn't the problem. A task that's quietly become "your" job because you're simply the person who never says no is the one to flag, even if it only takes twenty minutes a week, because the twenty minutes isn't really the cost — the precedent is. Once you've identified two or three of these, you have enough evidence to start the conversation instead of a vague feeling that you're doing "a lot of extra stuff," which is far too easy for a manager to wave away. Bring the log itself if the conversation stalls — a dated list is much harder to argue with than a memory.
Scripts for Declining or Redirecting
Once you know which tasks to target, the actual conversation is shorter than it feels like it will be beforehand. Three approaches tend to work better than a flat refusal, which often reads as more confrontational than intended and rarely gets a good result on its own.
- Redirect to a rotation: "I took the notes last quarter — let's rotate it, and I'll set up a template so it's quick for whoever's next."
- Decline with the trade-off named out loud: "I can't take this on without dropping the roadmap review — is that the trade you want, or should we find someone else?"
- Offering to build the system once but not own it forever works especially well for onboarding-style tasks: "I'll write the onboarding doc so nobody has to figure it out from scratch again, but I don't want to be the default buddy for every new hire going forward."
None of these scripts require confrontation, and none of them are really about this one meeting or this one new hire — they're about breaking the assumption that you're the default answer. Say a version of one of them three or four times and most managers stop asking you first; they start asking the group instead, which is the whole point.
When You Do Take It On, Negotiate Credit
Some non-promotable work is genuinely worth doing anyway — you like your team, you want the new hire to land well, and refusing every request on principle is its own kind of career mistake. When that's the case, the move isn't to decline. It's to make sure the work stops being invisible. Put it in writing to your manager before you start, not after: a two-line email — "Happy to lead onboarding for the two new analysts this quarter; flagging it as a deliverable so it's part of what we discuss at my review" — turns an assumed favor into a documented contribution.
The same logic applies to trades. If a manager asks you to take on the DEI committee, that's a reasonable moment to ask for something specific in return — a stretch assignment, sponsorship for a conference, or simply an explicit acknowledgment that the committee work will factor into your next calibration conversation. Vague gratitude doesn't move a career forward. A named trade does, even a small one, because it establishes that your time has a price, and that price gets paid in something other than goodwill.
Make the Invisible Labor Visible — Fix the System, Not Just Yourself
Individual scripts only go so far on a team that has no structure for this at all, which is why the more durable fix operates one level up, at the team level. A shared, rotating tracker for recurring non-promotable tasks — who took notes last month, who's running the next onboarding, who's on the culture committee this quarter — does more to fix the imbalance than any number of individual conversations, because it makes the pattern visible to everyone, including the manager who's been unconsciously asking the same person every time.
Documentation matters just as much as rotation. A task that lives entirely in one person's head has to go back to that person every single time, which is exactly how "just this once" becomes permanent. Writing the onboarding checklist down, once, properly, is an hour of work that saves the next six people from becoming the default expert by accident. Teams that adopt even a simple version of this — a shared doc, a rotating owner, a quarterly reset — tend to see the same names stop showing up for the same tasks within two or three cycles, not because anyone became more assertive, but because the ambiguity that let the pattern form in the first place got removed.
The most uncomfortable part of the original whiteboard experiment wasn't that women volunteered more often. It was that when researchers took the choice away entirely and assigned the task at random, the gender gap vanished by the next round. The fix was never about becoming a different kind of person who's better at saying no. It was about removing the exact moment where saying yes is easier than saying nothing at all — and that's a system problem, not a personality one.