i’ve spent a decade swinging between 14-hour deal days and quieter quarters. what kept me afloat wasn’t platitudes but a set of small, repeatable boundary habits i learned from veterans here: clear evening cutoffs, a shared friday triage doc, and strict morning focus blocks. i experiment openly with time-blocking — protecting 9–11am for deep work and routing all non-urgent asks to a monday stand-in. that doesn’t kill deal performance; it forces better scoping and clearer handoffs. i’m curious: what short scripts or rituals have you used to guard weeknights without damaging your reputation?
yeah, the fantasy is ‘set boundaries’ — reality is people will exploit any soft edges. i keep a 7:30pm cutoff, but only because i negotiated a hard handoff: anything after that gets an automated slack note and lands on a shared tracker. it sounds petty, but it saves my weekends. people learn fast when you stop being the 24/7 fixer. also, never send ‘i’m offline’ with a passive tone. say what you mean.
pro tip: don’t be the only one who answers at 11pm. train a deputy and rotate. when everyone knows someone else has it, the 11pm fires die. took me years to stop being the default. yes, your ego will complain. let it. your personal life will thank you.
i tried blocking 9-11 for deep work and it actually worked. i put a calendar note 'do not disturb' and ppl mostly respected it. still fumbling with wording tho — any script examples?
i also use a shared friday triage doc like you mentioned — saved my saturday once when someone documented a sig change. tiny wins matter.
Early in my career I conflated visibility with value and paid for it with hours. The practical shift was threefold: formalize handoffs, codify response SLAs, and protect a single daily deep-work window. On live deals, document the minimum deliverable for each night and assign ownership before you walk away. Over time that structure reduces interrupt-driven work and teaches junior staff to triage. If you want, I can sketch a one-page handoff template that teams can adopt. How would you want it tailored to your group?
this is doable — small boundaries add up fast! keep testing what sticks and celebrate each evening you actually keep.
Across teams i’ve audited, instituting a protected two-hour deep-work block reduced evening ad-hoc messages by ~22% and improved turnaround on modeled deliverables by ~14%. The mechanism is simple: measurable SLAs (e.g., respond within X hours unless flagged urgent) plus a visible shared tracker for pending items. If you map who actually sends late-night pings, you’ll often find 10% of users cause 70% of after-hours interruptions. Target that group first.
Another angle: track your own evening hours for four weeks. Break down interruptions by origin (partner, client, junior) and type (info, approval, formatting). In my sample, approvals dominated and were easily solved by pre-committing decision rules earlier in the day. Once you have that breakdown, prioritize interventions where they yield the largest reduction in after-hours work.