6 min

Getting Into Flow

Key takeaways from a conversation about flow states and how to make it easier to get into one.

I’ve been a regular listener of The Knowledge Project for the last several years. I sincerely appreciate the work Shane Parrish puts into it. After listening to the most recent episode, “Steven Kotler: The Science of Doing Your Best Work”, I thought it had some good insight worth writing a short post on.

Kotler is the executive director of the Flow Research Collective and has spent decades studying flow states so that topic is the basis of the conversation. The key insight I took from it is that flow isn’t a mindset you magically transition into. Instead, there are deliberate actions a person can take to improve the likelihood that they can get into flow when carrying out any activity.

Quick disclaimer: I’m not a scientist. I can only speak as a programmer, and for me, getting into flow on demand is one of the most sought-after skills there is. Unless I link something else, everything below is Kotler’s claim. In other words, don’t shoot the messenger!

Flow begets flow

Kotler talks about a primary flow activity: something you’ve done since you were younger that you tend to get completely absorbed in. For him, it’s skiing. For others it’s dancing or playing an instrument. The most common activity is reading. For me, I think it’s exercise or walking in nature.

Even though we might not be working, time spent doing a primary flow activity makes it much easier to get into flow when working on a task. It’s a focusing skill, so time spent in flow on Sunday makes it easier to get there on Tuesday.

His idea is that spending time in flow outside of work can make it easier to find flow at work. He suggests two to four hours a week in that primary activity.1

He also says that if you’re burned out, doubling down on your primary flow activity is the way back, which I found to be particularly surprising. When you’re burned out, it seems like getting into a flow state would be on the opposite end of the spectrum.

Stretch without snapping

Flow shows up when a task is just a little harder than your current skill. This is the challenge-skill balance idea, which has been revised over the years. Kotler puts a number on it: 4%.

So you want to stretch, but not snap.

He’s upfront that 4% is a back-of-the-envelope figure and not science. He’s also called it arbitrary and said it changes for every person. It lines up with the Yerkes-Dodson law, where performance rises with stress up to a point and then falls off. Too easy and you’re bored. Too hard and you’re anxious.

This part resonated with me as I once had a mentor inform me that he was deliberately putting me outside my comfort zone as this is where we learn the most. It felt nice to connect the dots there.

Design your environment

After spending time in your primary flow activity, you’re going to want to get rid of distractions. Kotler’s version: phone off, one channel open for emergencies, batch your messages.

I recently bought a timed lockbox for my phone and it’s been incredibly helpful. I used to toss it somewhere random in the house and forget about it. Now, I just throw it in there, set the timer for 2-3 hours, and I end up leaving it there much longer.

Kotler also says to clean your desk. His reasoning is that a tidy space lowers cognitive load, and the brain redirects that energy to attention.

Building your flow capacity

Kotler says sleep runs in cycles of roughly 90 to 110 minutes, and your awake and alert cycle is about the same length. The idea traces back to Nathaniel Kleitman’s basic rest-activity cycle, and a 1994 study found cycles of 90 to 100 minutes in task performance and EEG. The waking version is still contested though, so it’s best to treat 90 minutes as a good starting point and not a law of nature. That said, you don’t need to start at 90 minutes.

Start by starting.

If you can only focus for 10 minutes, start with 10. Then 15, then 20. Kotler says people who stick with it are surprised when they suddenly hit 90. I’ve started planning 90-minute work blocks into my days since coming across this information, and it’s had a significant impact on my output. I’ve also found that it makes sticking to a pre-planned schedule easier.

Find the part of the task that matters to you

Kotler argues that ADHD is really “hyperflow”. The problem isn’t focusing, it’s focusing on things you don’t care about - a scenario I know all too well.

Kotler says attention and autonomy are tied together, so you have to find the part of a task that’s yours. His example is an early journalism assignment about data caves. He didn’t care about data caves, but he did care about learning how Wired structures its stories.

The developer version: maybe I don’t care much about AWS itself, but I do want to develop a deep understanding of how to integrate a load balancer into a system. That provides a way into a task. It’s one idea to try, not an explanation for every person’s experience with ADHD.

What’s happening in your head

During flow, Kotler says most of the prefrontal cortex turns off as an “efficiency exchange.” The brain shuts down noncritical structures and puts the energy toward focus and attention. The name for this is transient hypofrontality, proposed in Arne Dietrich’s 2004 paper.

The imaging work is more nuanced than “it turns off.” A 2014 fMRI study of 27 people found less activity in the medial prefrontal cortex and amygdala during flow, and more in the left inferior frontal gyrus and putamen. Kotler also says researchers look at chemicals like norepinephrine, dopamine, serotonin, anandamide, and endorphins.

His takeaway is that flow is a measurable state and not an imaginary concept, and measurable things can be trained.

Play beats repetition

Kotler compares deliberate practice (repetition with small improvements) to deliberate play (repetition with improvisation). Outside fields like math or violin, he says play wins, because it brings more neurochemicals and those tag an experience as worth saving.2

As a software engineer I can read the docs for a new library, or I can build a project with it. I’m choosing the project route every time as it allows me to directly interface with the library, and also always results in me gaining a deeper understanding than I would’ve acquired if I simply read text.

Recap

I have nothing to gain by pushing propaganda. The fact is: I’ve applied concepts from this chat into my life. I’ve found that I’m able to plan my days out at night, and much more easily follow my schedule closely the next day. To recap the key takeaways:

  • Clear your distractions and your desk.
  • Pick work that sits a little outside your comfort zone.
  • Start with whatever focus block you’ve got and build toward 90 to 110 minutes.
  • Make time for your primary flow activity. Mine is going for a walk.

If this topic interests you, I encourage you to check out the episode for yourself!

Footnotes

  1. This is the number Kotler gives in the episode, and I couldn’t find the study behind it. A 2021 Psychology Today piece puts his weekly guidance at two to six hours, so treat the exact range as a rough guide. ↩

  2. Kotler says his own lab compared the two, but I couldn’t find a published paper. The closest I found is a Flow Research Collective Radio episode where he talks about the distinction. Take it as his claim for now. ↩

Thomas Greco writes about software engineering, life, and what he’s learning and building.