Imagine you are driving at full speed on an empty highway and then oops… You are hitting an hour-long traffic jam. Your 8 hours trip becomes 9 hours. How does it feel? Now imagine that getting back to the full speed takes at least 30 minutes, not ~10 seconds. Right, your trip is now 9 hours and 30+ minutes, 90 minutes longer. The reason for 30+ minutes is that any intellectually intense work requires . Flow is a mental state when the brain is most productive. Getting into the flow state takes time. flow Being in the is like at full speed on an empty highway. Being is like hitting a traffic jam. flow driving interrupted Then you are driving forward and hitting two more 15-minute traffic jams hours apart. Think you lost another 15+30+15+30=90 minutes? Unfortunately, it is a lot worse, you lost the whole day… Getting into the requires a lot of energy. With every next distraction, it’s a lot harder. flow Photo by Jens Herrndorff That is why programmers and everyone else who is making great stuff don’t like meetings. I’m not suggesting that you shouldn’t talk within a the team. You should! No meeting can generate so much waste as people running in opposite directions. I’m also not suggesting that all communication should be in writing. It shouldn’t! As we know, most programmers also don’t like writing whole a lot of text. Verbal communication is by far the most efficient, but only if you can keep short, small and at the right time. The definition of short is 5–15 minutes. The definition of small is 2–4 people. Help programmers to do their best jobs There are two simple rules: . Agree on a daily hour that works best and use it on-demand for your short and small talks. For teams in different timezones you will have to select something on the intersection. Do all the talks either at the beginning or better at the end of the work day Like daily, weekly and monthly. Recurring meetings include more people than needed for longer than necessary. They also make it hard finding time to discuss things that matter the most at the moment. Stop scheduling any recurring group meetings. This is how ideal programmer’s calendar looks: Week schedule to maximize the flow state Put in place this schedule for all programmers in your team. And you can ignore/forget all the lengthy advice out there on how to run “great meetings”. is a Co-Founder of , a team video chat scheduler that helps makers to be in the flow most of the work time. Gene Podolyak Meetter Best content on this topic [1] Paul Graham: Maker’s Schedule, Manager’s Schedule [2] Al Pittampali: “Read This Before Our Next Meeting” | Talks At Google
