Why workload conversations usually fail
Most people raise workload in the worst possible way: emotionally, vaguely, and mid-crisis. "I'm drowning" invites reassurance, not change — your manager hears a feeling, offers sympathy, and everyone returns to the same workload. The conversation that works is built on three things: evidence, a specific diagnosis, and a concrete ask.
Step 1: Gather 4–6 weeks of evidence first
Before you say a word, log your real hours for at least a month. You want to walk in with:
- Your average workday vs. your standard day (e.g. 9h 9m vs. 8h)
- Weekly totals for the recent stretch (e.g. 43h 30m, 46h, 44h…)
- The trend — months where your average ran over, in a chart
- Specifics — weekend log-ons, average end time, shrinking lunches
WorkWize (free on iPhone) produces all four automatically: the home screen shows your average workday and its paid/unpaid split, the Weekly Summary gives totals and average start/end times, and Workday Details charts the monthly trend with overwork months highlighted. A month of 10-second daily logs is your entire prep.
Step 2: Frame it as a planning problem, not a complaint
Book a normal 1:1 slot — not the day after a blow-up. Then use a structure like this:
"I want to flag a capacity trend before it becomes a quality problem. I've been tracking my hours: my average workday has been over 9 hours for the last three months, including most weekends in April. I care about doing X and Y well, and at this load something will slip. Can we look at what to reprioritize?"
Notice what this does: it's factual (logged hours, not impressions), it aligns you with the team's goals (quality, not comfort), and it hands your manager a solvable problem (prioritization) rather than an accusation.
Step 3: Come with asks, not just data
Managers respond to options. Pick one or two:
- Reprioritize: "Which of these three projects should I deprioritize?"
- Redistribute: "Can we move the weekly reporting to someone with capacity?"
- Resource: "This is structurally 1.3 jobs — can we open a req or bring in contract help?"
- Recompense: if the load can't change, make the money follow it — your cost-of-unpaid-hours figure is a concrete anchor for a comp conversation.
Step 4: Follow up in writing and keep logging
Summarize agreements by email the same day. Then keep tracking: your next month of WorkWize data tells you whether anything actually changed. If the average workday drops, great — you have proof the fix worked. If it doesn't, you have proof it didn't, and grounds for the next conversation (or, per our overwork guide, a bigger decision).
If the answer is "that's just the job"
Sometimes it is. Then the question becomes whether the job — at its real hourly rate, not its advertised one — is one you'd choose again. Your true-pay number answers that, and our guide to stopping unpaid overtime covers the boundaries you can set unilaterally in the meantime.