How strongly do I recommend Flow?
7 / 10
Flow is kind of a long read and feels a bit academic. Over Flow, I would recommend Peak because it contains more practical applications while covering similar content.
Intuitively, many engineers know the feeling of flow. Csikszentmihalyi defines the components of flow, noting that they are not all required but frequently present together:
For me, flow represents the feeling experienced when deeply engaged in deliberate practice as presented in Peak.
Engineers love talking about optimization. Peak performance. Max throughput.
Flow introduces time to the equation. Peak performance is measured by a period of time, not a moment in time.
The longer you remain in flow, the higher your performance.
Csikszentmihalyi writes, “To be enjoyable, a relationship must become more complex. To become more complex, the partners must discover new potentialities in themselves and each other–so that they can learn what thoughts and feelings, what dreams reside in their partner’s mind.”
Relationship complexity grows with feedback. Feedback doesn’t mean a performance review; it means conversation where we intentionally address difficult topics in a collaborative way.
Our most complex relationships have plenty of feedback loops. When those feedback loops go dark, the relationship is likely failing.
The 7 components of flow previously listed all suggest a gamified task. As an engineering manager, we have plenty of ways to gamify the development process and encourage productive behaviors.
Green and red signals on automated tests, release counts, usage metrics, and fun emoji responses in Slack are just a few examples of how I leverage gamification within my team to encourage frequent releases, customer focus, and strong communication.
Csikszentmihalyi points out that men are particularly vulnerable to believing that work needs active attention, but home life will take care of itself. Wrong.
Your personal relationship and health require the same level of dedicated effort as your work.