My actual experience with 4 day work is the closer the team is to operations (2nd and 3rd shift 7 days per week) and the closer to contractor/consultants the ea

My actual experience with 4 day work is the closer the team is to operations (2nd and 3rd shift 7 days per week) and the closer to contractor/consultants the easier the transition. I would caution people to be careful what they wish for; my longest 4-day gig involved sun-wed and wed-sat shifts. 4-day doesn't necessarily mean mon-thr ever week for everyone. Another problem was our overlap day was wed thus "wednesday is non productive its for meetings and stuff" so you really only worked three days because you couldn't trust not to be interrupted on wednesday. Its probably of enormous productivity value to move all interruptions to exactly one day every week, however you don't need 4-day to do that, technically speaking. Another oddity probably of more interest to bean counters is our overlap day was wednesday so with all hands on deck we did maint and rollouts and upgrades on wednesday, but the rest of the world did maintenance windows on the weekend at 2am so our meaningless measure of fake uptime was lower than non-4day companies. Now does your employer value rolling out better stuff faster, or do they value a "better" meaningless heavily gamed number? So 4-day might be better or worse depending on if your local management lives in reality or spreadsheet-metric-land. "Oh no how will we get fake nine nines of uptime if we roll out new SaaS on Wednesdays?"