The trick is to show you are managing priorities, not dodging work. Lead with interest, then force a tradeoff: Happy to help. To fit this in, which of A, B, or C should I pause and what moves on the timeline? Follow with a time bound and scope check: I can do a 30 minute look today to flag risks. A full fix is 6 to 8 hours. Do you want a quick triage or a proper solution next week? If the answer is now, give a clear boundary: I am not available this weekend, but I can deliver a draft by 4 p.m. Monday. If it is not urgent, offer the next slot: I can start Wednesday after we ship X and have a first pass by Thursday EOD. Always send a recap email so it is documented: Recap from our chat. I will spend up to 3 hours on A by Thursday EOD for a first pass, and full implementation would be next sprint unless priorities change.
When a new task appears midweek, I ask three things in order and out loud: what is the deadline, what is success in one sentence, and what should I drop to make room. That keeps you out of the slacker bucket because you are choosing with them, not refusing. Small win I repeat every time a "quick" project shows up: I block one 60 minute slot on my calendar for unplanned work and make it clear that anything beyond that needs a tradeoff decision. Pitfalls I hit before I fixed this were agreeing to vague scope, not asking for a tradeoff, not emailing a recap, and explaining with personal reasons instead of business impact. If your boss pushes for weekends, calmly restate the boundary and give an option: I want to do this well without weekend work. I can either deliver a solid draft Monday or we can cut scope to X and keep Friday timing.
