Flow Genome
Flow Genome maps what actually triggers flow state for a given person - psychological, environmental, social or creative conditions - so you can design work to produce it more often instead of waiting for it.
Four cards sit side by side, each one naming a different category of flow trigger.
Reach for this when…
- Someone does their best work occasionally but can't say what produced it.
- A team's peak output happens by accident and nobody's tried to reproduce the conditions.
- You're redesigning a workspace or role and want it to actually support deep work.
How to run it
- Complete the Flow Profile assessment.
- Identify dominant flow triggers: psychological, environmental, social, creative.
- Debrief when flow happens most and what conditions support it.
- Map current work against those triggers.
- Redesign environment and task structure to increase flow frequency and depth.
A worked example
Situation. Rafael Costa runs a small game studio in Recife, Brazil, where his best designers kept burning out on features that should have been their strongest work.
Applied. The Flow Profile showed his lead designer Beatriz's dominant triggers were environmental (uninterrupted blocks) and creative (novel problems), not social - she'd been placed in the noisiest, most collaborative slot of the week.
Result. Rafael gave her two protected mornings and moved her onto the studio's newest, least-defined feature. Her output on it matched what used to take a month under the old set-up.
The catch
Flow Genome draws on Csikszentmihalyi's research but its trigger taxonomy is looser and less independently validated - treat the profile as a conversation starter, not a diagnostic instrument. It also can't manufacture flow on demand, only remove some of the obstacles to it, and what triggers flow at 30 may not at 50.
Flow triggers describe conditions, not guarantees - clear the obstacle and flow becomes possible, not certain.
Origin: Mihaly Csikszentmihalyi (theory); Steven Kotler & Jamie Wheal (Flow Genome Project)