Flow of a company

The speaker defines 'flow' as the baked-in tempo and constraints of an organization — promotion timing, team throughput, decision speed — distinct from the cognitive state also called flow. Using analogies (a river current, a crowded subway, a body where uncontrolled production becomes 'cancer'), the speaker warns that fighting an organization's flow exhausts you and often ruins careers.

Promotion flow: large and mature employers (cited: Microsoft, Google, the three M's) formalize promotion schedules; the speaker contrasts that with early-stage fluidity. He cites McKinsey and Boston Consultant Group as examples of explicit rules: 'two years', a 'six month window', 'up or out'. Anecdotes like 'John in accounting' who was promoted faster usually hide an advocate several levels above (examples: Rajesh, Irene, Phil, Brian) who pulled the person up. If your manager does not begin preparation conversations 'six months or a year' before promotion, you are likely off-track.

Work-product flow: lone contributors who try to run ahead get isolated and slowed by the system; small companies allow more wiggle room but two dozen pushers can break the system. The practical sequence the speaker gives: stage one (first '90 to 180 days')—join the flow and be accepted; stage two—be competent and trusted; then expect manager-led prep for promotion on the company's cadence.

Recommendations (verbatim language used by the speaker): 'identify the flow', 'settle into the flow', 'swim perpendicular to the flow', and 'determine what downstream island you want to go to'. In short: stop fighting the current, find the organization's rhythm, and move toward your target within that rhythm rather than attempting to outrun it.