I’ve done enough Mon–Thu flights to know the “on the beach” fantasy collides with utilization, client workshops, and late dinners. I’m trying to design a path that gives me occasional long weekends by the coast without getting a “lightweight” label. If you’ve managed this, what actually mattered—practice choice (ops vs diligence vs PMO), aligning to regional clients, becoming the person who can run remote analytics, or building goodwill with staffing so you can push for 3–4 day on-sites? What trade-offs did you accept (e.g., fewer transformation workshops, more data-heavy sprints), and how did you frame it to partners so it read as “effective” not “checked out”? If you made this work, what exact scripts and metrics kept you on a promotion track while still getting beach time?
the “beach lifestyle” exists right up until a VP decides there’s a steering committee on friday. if you want this to work, stop saying “beach” and start saying “regional staffing” and “remote-friendly analytics.” get tight with staffing, be the person who can run model reviews over zoom, and pick diligence or PMO sprints over workshop-heavy transformations. you’ll still travel. but fridays at home become defendable when you’re the one pushing clean deliverables by thursday noon. don’t overshare the lifestyle part. share the reliability.
i asked staffing to tag me for 3–4 day onsite cases and built a “friday deliverables” routine. didn’t say beach, just “regional + remote‑capable work.” partners cared about output, not where i typed.
Two levers matter most: predictability and perceived indispensability. Anchor yourself in modules that tolerate remote delivery—analytics, PMO cadence, financial modeling. Establish a reputation for crisp Thursday readouts so senior clients are comfortable deferring Friday face-time. With staffing, frame the request as outcome-oriented: regional alignment for continuity, not location preference. Accept that you’ll likely trade some marquee transformations for sprint-based work and a few high-visibility moments for steadier throughput. Track utilization and lead a recurring workstream to demonstrate scope growth. The phrasing that works: “I can increase continuity and speed-to-insight if we structure this as Mon–Thu on-site with remote Fridays for synthesis and pre-reads.” It reads mature, not lifestyle-driven.
You can absolutely do this! Focus on results, build trust, and ask for regional, remote-tolerant work. Show you deliver by Thursday, and Fridays become yours. Keep it consistent—you’ve got this!
I tried the “sneak in beach time” thing while staffed on a West Coast diligence pod. I stopped saying beach entirely and just framed it as “Thursday wrap, Friday synthesis.” Once I consistently hit clean Thursday outputs, the partner stopped caring where I was. I’d take an early flight to San Diego, do Friday storyboard edits from a coffee shop, and be back on calls by 9am. The trick was being the person who sent pre-reads before anyone asked. Reliability bought me flexibility.
Post-2020, many firms normalized partial-remote delivery, but travel is still common. In my experience: diligence/analytics pods often run 60–80% remote by design; large-scale transformations skew 80–100% on-site for workshops and alignment. Regional staffing increases odds of 3–4 day on-sites. What enables flexibility is measurable reliability: Thursday pre-reads delivered, stakeholder notes circulated, and decision logs maintained. If you can show consistent on-time outputs and stable client NPS, partners typically accept remote Fridays. Frame it as operational efficiency, not personal preference.