FAANG PM here struggling with the 24/7 expectation. Last week I got a Slack at 11:30pm about a non-urgent spec change, and when I didn’t respond immediately, the VP tagged me in a team channel asking if I was ‘still engaged with the project’. I want to set clearer boundaries but can’t afford to look uncommitted. What concrete strategies have senior PMs used to establish protected time that leadership actually respects? Bonus points for specific phrases that shut down weekend fire drills without burning bridges.
newsflash: there’s no ‘without career repercussions’. best you can do is make your responses expensive. i started billing after-hours pings as ‘emergency consultancy’ in 15min increments on status reports. suddenly my calendar got respected real quick when it impacted their budget. play the game or get played.
i tried turning off notifs after 7 but then got called ‘hard to reach’ in perf review 
any1 have better ideas? maybe like auto-responders that dont seem rude??
Three actionable steps: 1) Document expected response times in your team charter 2) Create an escalation matrix distinguishing true emergencies 3) Lead by example - never message reports after hours. I trained executives using the ‘ICU test’ - if this isn’t ICU-worthy, it waits. Took 3 months but reduced after-hours comms by 70%.
My manager used to ping me Sundays until I started sending Monday AM meeting invites titled ‘Post-Weekend Priority Alignment’. Now they wait because they think it’s their idea. Weird how that works!
Analysis of 85 PMs showed those who instituted formal SLA meetings reduced after-hours contact by 58%. Key elements: written acknowledgement from directors, clear penalties for non-emergencies, and public visibility into request response times. Start with data - map your current response latency against actual business impact.