5 ms·
I think it's also important to note that many people struggle to achieve flow state when context switching between sleep cycles. There's a natural daily rhythm
by cheschire 3y ago
I think it's also important to note that many people struggle to achieve flow state when context switching between sleep cycles. There's a natural daily rhythm folks go through, and the older one gets, the more it tends to (but not always) shift earlier in the day. Think about that next time you want to schedule a mandatory synchronous event, especially one such as a daily standup.
Some of your team may already be 2 hours into their day by 9am, while others may be just rolling out of bed and not yet deep into something. And some of your folks are starting to wind down their focus period around 2pm to 3pm while others are ready to go deep into the night.
I'm not trying to assert there's a problem with standups or other meetings. I'm just saying if flow state is a priority for an organization, there has to be compromise made in how scheduling, status checks, and synchronization works.
- gausswho 3y agoWhen I was young I read that Vonnegut wrote most of material before the fam woke up. Around 4 to 7am. As a young night owl it was bonkers to me. Now I get it.
- escapedmoose 3y agoThere’s a book called ‘Daily Rituals: How Artists Work’ that details the daily routines of famous creative folks. The early morning work session is common, but so is the late-night session. Strict routines are common, but so is spontaneous creation on a whim. It’s cool to see all the ways people create; very neat book.
- epiccoleman 3y agoI had a professor in college who extolled the virtues of his unique sleep schedule - going to bed at 7 and waking up at 3am. He said he loved those few hours when everyone else was sleeping and got all his best work done during that time.
- wdfx 3y agoSure but by this logic there is no best time for everyone to meet, so there's no point even debating what time to choose, any will do.
- ghqst 3y agoI think it's more a warning that you're never going to be able to find a standup time that's the most efficient for every attendee
- resonious 3y agoMaybe a weird take, but I think stand-ups and scrum and such intentionally sacrifice flow state in exchange for visibility and consistency. The small tickets, triage, estimations, stand-ups, are all anti-flowstate. But they allow you to get closer to actually measuring developer performance. It lets you compare teams and "debug" late projects. But all at the cost of potentially faster but unmeasurable devs.