Flow

Why more talking never fixed your team — and what my father taught me that the professors couldn't

Here's the friction, named before I waste your time: you think the fix for a team that keeps stumbling is more communication. It isn't. The real prize is the opposite — the point where a team barely has to talk at all, because they've done the thing together so many times it runs on muscle memory. That's flow, and the endless coordinating you're doing right now is the tax you pay for never having built it.

Let me put myself in the chair first, because I got this backwards for years. When my team was grinding, my instinct was always to add: another check-in, another standup, another meeting to "get aligned." I thought the answer to friction was more words. What I was actually doing was pouring more talking onto a team that had never built the wordless rhythm underneath — like trying to fix a band that can't keep time by giving everyone a longer sheet of instructions. More paper. Same stumble.

What my father was really teaching me

My father had one line he repeated my whole life: all I want to see is elbows and assholes. Crude, sure. He wasn't a man who wasted words on polish. But underneath it was one instruction, and it was a good one: I want you bent over the work and already moving — elbows down, reaching for the next thing before I have to point at it. Anticipate the next step. Be right there with me before I ask. Don't wait to be told the obvious.

For years I heard it as him being demanding. It wasn't. He was describing flow — the same flow state Steven Kotler and Jamie Wheal spent a whole book, Stealing Fire, mapping. My father never read it. He'd found the thing itself decades earlier, on framing jobs, a board and a nail at a time, and his name for it was elbows and assholes. He wanted me one move ahead, so the work moved between us without narration. That's the whole thing. Wisdom is everywhere. It does not have to live in a university — sometimes it's a man on a scaffold who worked out with his hands what people with letters after their names would spend careers proving in a lab: how a group stops being a pile of individuals waiting for instructions and starts moving as one body.

You have seen it, even if you have never named it

Flow isn't mystical. You've watched it your whole life.

Two pilots who've flown together for years run an emergency checklist with almost no conversation — a hand moves, a switch flips, the other is already on the next item. A kitchen line on a Saturday night is a hundred plates of controlled chaos, and the cooks barely speak; they've done it enough that the rhythm carries them. Two parents with a newborn, six weeks in, hand the baby back and forth in the dark without a word because they've built the pattern. Elite military teams move through a room as a single organism — no debate, no narration — because they've drilled the same sequence until it lives below thought.

None of those people are talking more than a rookie team. They're talking less, and getting more done, because the coordination moved out of their mouths and into their bodies. That is the destination. That is what good actually looks like.

Why more talking is the wrong medicine

Here's the trap, and it's a comfortable one. When a team is friction-heavy — dropped handoffs, redone work, "wait, I thought you had that" — the visible symptom is a communication problem. So the owner reaches for the obvious cure: communicate more. More meetings. Longer emails. A new channel for updates.

And it helps a little, which is exactly why it's a trap — just enough relief to keep you doing the thing that isn't the real fix. Because all that talking is a splint, not a cure. A team in flow doesn't need the splint. The reason they're not in flow isn't that they haven't talked enough. It's that they haven't repeated enough — they haven't run the same handoff, the same sequence, the same play enough times for it to go automatic. You can't meeting your way to muscle memory. You can only rep your way there.

The goal was never to communicate more. It was to build the reps until you need to communicate less.

There is a kind of talking that builds flow instead of taxing it, and I gave it its own piece — Communication Friction — so I'll keep it short here. The fix isn't more words; it's the readback. When you hand someone a task, make them say the action back to you — not "got it," but the actual thing they're about to go do. That one move does three jobs at once: it confirms their clearance before they burn an afternoon on the wrong runway, it teaches them the pattern by making them speak it, and it earns the trust flow runs on, because now you both know they actually have it. And when they come to you with a question, don't always answer it — sometimes you send them off to figure it out, build the report, and come back and teach it to you. Being handed the answer grooves nothing. Working it out and teaching it back grooves everything. The pattern has to be agreed on and the trust has to be earned before a single rep counts — and that agreement gets built one readback at a time.

But flow needs one thing first

I have to be honest about the order, because it's where people go wrong. You cannot build flow on top of chaos. Two pilots only flow because they're both flying the same procedures — same checklist, same words, same standard. Take two skilled pilots who each learned a different way and put them in one cockpit, and you don't get flow, you get a fight. The reps only compound into flow when everyone is repeating the same pattern.

So flow is earned in a specific sequence: first you set the shared standard — the one way the handoff is done — and then you run it, together, over and over, until the standard disappears into instinct. Skip the standard and your reps just carve two different grooves that grind against each other forever. Set the standard first, then the reps turn a group of individuals into something that moves as one. That's not a personality trait some teams are lucky to have. It's a thing you build on purpose, in that order.

Why this is the whole game

Almost everything an owner wants — speed, fewer errors, less of their own time spent refereeing — is downstream of flow. A team in flow is faster because the coordination is free; it happens without meetings. It's more accurate because the pattern is grooved, and grooved patterns don't drop handoffs. And it gives you your life back, because you stop being the switchboard every decision routes through. The friction you feel every day — the sense that nothing moves unless you're personally pushing it — is very often just the absence of flow, and the presence of a team still waiting to be told each next step.

The move for Monday

You don't build flow with a speech about flow. You build it one rep at a time. So here's the move: pick a single recurring handoff between you and one person — the report that comes back wrong, the task that always needs a second pass — and run it the exact same way, ten times in a row, before you change a single thing about it. Same standard, same steps, every time. Somewhere around rep six or seven you'll feel it start to go quiet — they'll be reaching for the next piece before you say it. That's the first thread of flow. Then you do it with the next handoff, and the next, and one day you look up and realize the room is moving without you narrating it.

That's what my father wanted the whole time. He didn't have the word for it. He just wanted elbows and assholes — everybody bent over the work, nobody standing around waiting to be told the next move — and it turns out the smartest people in the world spent decades proving he was right.

I'm not the expert here. I'm the guy who spent years adding more meetings to a team that just needed more reps, until I finally shut up and let the pattern do the work. Take what fits. Leave the rest. Flow.