I am a software engineer at a mid-sized
Ask
I am a software engineer at a mid-sized tech company. Over the past year, I somehow became the default organizer for our 15-person team:
- Taking detailed meeting minutes for 3 team syncs a week (~3 hours)
- Onboarding, setting up repos, and answering daily questions for all new junior hires (~4 hours)
- Organizing all team lunches, birthdays, and offsite logistics (~2 hours)
That's almost 9 hours every single week of invisible, non-promotable "glue work".
In my mid-year review yesterday, I brought up my promotion to Senior Engineer. My manager said: "Your technical commit volume and design doc output were lower this quarter compared to peers like Dave." Dave literally writes code all day and does zero team logistics or onboarding.
I left the meeting holding back tears of anger.
1. What is the exact speakable sentence I can say to my manager to offload or rotate this invisible work without being labeled "not a team player"?
2. If he pushes back and says "You're just so good and organized at it, it only takes a few minutes," what is my exact comeback?
3. How do I lay out this invisible labor inventory so it's impossible to ignore?
Answer
Before tears go to strategy: the work you've been doing isn't invisible — it's just uncounted. Here is the line to say, the line to say next, and the page that makes the 9 hours hard to wave away.
**1. To your manager — the ask, in one speakable sentence:**
> "I tracked about 9 hours a week last quarter on meeting minutes, onboarding, and team logistics. To protect my technical output, I'd like meeting minutes rotated across the team, onboarding Q&A moved to two scheduled windows, and lunches and offsite logistics reassigned to a rotating owner. Please confirm in writing by **[date]** who takes which from **[start date]**."
Three things to notice in that sentence: it states the number (9 hours), it proposes a **swap** rather than a stop (so the work still gets done — this is what protects you from the "not a team player" label), and it asks for a written yes/no by a specific date.
**2. If he says "you're just so good at it, it only takes a few minutes":**
> "Thank you for saying that. I still need a yes or no on rotating these, and the date it takes effect."
This is the *reassurance* shape — the compliment is real, but it isn't an answer. You acknowledge it once, then return to the request and the date. You are not arguing with the compliment; you are refusing to let it replace a decision.
**3. The inventory layout — six columns, no excuses:**
| Task | Frequency | Time | Who benefits | Currently assigned to | I am asking |
| --- | --- | --- | --- | --- | --- |
| Detailed minutes for 3 team syncs | 3× / week | ~3 hrs/wk | All 15 | Me (default) | **swap**: rotate |
| Onboarding, repo setup, daily Q&A for new hires | Daily | ~4 hrs/wk | Juniors + their manager | Me (default) | **swap**: scheduled windows; manager owns repo setup |
| Lunches, birthdays, offsite logistics | Weekly + ad-hoc | ~2 hrs/wk | All 15 | Me (default) | **swap**: rotating owner; budget line to my manager |
Total: **~9 hours/week**, none of it promotable on its current framing, and none of it in Dave's column. That parallel is the whole point — your mid-year review compared you to a peer whose week has 9 more hours of pure code time. The inventory makes the comparison honest without making it adversarial.
Saved it as a takeaway page you can bring into the meeting: Invisible-Work-Inventory-2026-09-16-c0739b80.pdf
What written-by date do you want to put on the sentence in #1? Pick one — Friday this week, next Friday, or end of month — and I'll lock it into the script.