In "agile" software practices, a 2-week "sprint" is common. But the 2-day weekend in the middle of the spring, for me, always felt like a major drag. I would lose all the momentum I had gathered for work, and now I have to rest, while simultaneously "being in the sprint".
What if we ditched this and just focus on work for some time, then focus on resting for some time, without the construct of weekdays/weekends?
This to me feels far healthier.
I prefer this way more because I can actually properly rest. Work life balance can make sense here. Work wise, I can focus on the work and keeping my momentum. Finding time to go on a holiday is no longer an issue. If others are still on the 5/2 schedule, I don't need to leave work to catch early-closing-only-open-on-weekends establishments (ahem, banks).
Sure, it would be weird at first...but weekends have always felt like a waste where I'd rather have worked & use the rest later..
@slims I'd like this if ONLY because my day-to-day support work means I have about literally zero time for documentation or process building. Being able to work while our "main" system is shut down (K-12 district) would be incredibly helpful just from a concentration perspective.
We've recently been asked to review a bunch of NIST documentation to align our internal policies with and, bluntly, several of us have said "With what time?"
slims 
πβ
γΈγ§γ·γ₯γ’