How to Brainstorm Across Timezones

Eight people, four timezones, one Zoom call somebody had labeled "brainstorm." The head of product spoke first. She floated an idea about the onboarding flow, a decent one, and for the next forty minutes the call quietly became a search for reasons her idea was good. People built on it. Refined it. Nobody proposed anything that wasn't a cousin of the first thing said. The engineer in London had joined at 9pm her time and said maybe eleven words. We left with one idea, which happened to belong to the most senior person in the room, and we called the meeting a success because it felt like one.

I've run that meeting. I've sat in that meeting a hundred times. And somewhere along the way I stopped believing the story we tell about it, which is that getting everyone in a room is how good ideas happen.

The whiteboard was never as good as it felt

There's a myth that brainstorming needs a room. Energy in the air, people riffing, one half-thought sparking the next, someone scrawling on a whiteboard. It feels productive, and the feeling is the problem, because the live group format is mediocre at generating ideas even when everyone's in the same building. This has nothing to do with remote. It's baked into how the format works.

Start with the simplest constraint: in a live brainstorm, only one person can talk at a time. So while someone is speaking, the other seven are either half-listening or sitting on an idea they're trying not to forget, and by the time the floor opens the idea has either evaporated or started to feel not worth saying. Then there's anchoring. The first idea on the table sets a direction, and the group unconsciously orbits it, so the order people happen to speak in quietly decides what the session is even about. And people censor themselves. Nobody wants to say the weird thing in front of their manager and three skip-levels, so the safe, obvious ideas get air and the strange ones stay in people's heads.

The result is that the loudest, most senior, fastest-talking person sets the agenda, and the quiet person with the genuinely different idea says nothing. Researchers have known this for decades. Groups where people generate ideas alone and pool them afterward reliably beat groups that ideate out loud together, on both how many ideas come out and how good they are. The whiteboard session felt like collaboration. Mostly it was one person thinking and everyone else reacting.

Now take that already-flawed format and stretch it across timezones. Live means somebody is on the call at a bad hour, tired, contributing at a fraction of their capacity, and you're spending the scarce overlap window that's your most expensive resource to run your least effective process. You've taken the worst way to generate ideas and paid a premium for it.

Brainstorming is two jobs, and the meeting does both badly

Here's the thing that unlocks the async version. What we call brainstorming is actually two separate jobs wearing one name. The first is divergence: generate a lot of options, hold off on judging any of them, get quantity and range on the table. The second is convergence: sort through what you've got, argue about it, narrow, and pick.

A live meeting smashes these together, which is exactly why it's bad at both. You can't diverge freely when someone might shoot your idea down mid-sentence, and you can't converge cleanly when half the ideas never surfaced. Pull the two apart and each one gets better on its own terms. Divergence wants people thinking independently, without an audience. Convergence wants a real discussion and, eventually, a decision. Those are different activities that want different conditions, and the meeting gives them the same forty minutes and the same power dynamics.

Run divergence silent and solo

The async divergence phase has an old, unglamorous name: brainwriting. People write ideas down independently instead of saying them out loud in sequence. It sounds less exciting than a whiteboard and it produces more.

The mechanics are boring on purpose. Post a sharp prompt somewhere everyone can reach, a channel or a shared doc. One clear question, enough context that nobody has to ask what you mean, and a deadline written in each reader's own clock so the person in Manila and the person in Denver both know exactly when it closes. Then everyone adds their ideas on their own time, thinking before they read what anyone else wrote. Give it a real window. Forty-eight hours, not forty minutes, so that the person who needs to sleep on a problem actually can, and so nobody's contribution depends on being awake for a specific hour.

Two things go up immediately. The number of ideas goes up, because nobody is waiting their turn to speak and a dozen people can "talk" at once. And the diversity goes up, because nobody has been anchored by whatever the senior person would have said first. The engineer who does her best thinking alone in a quiet block, the same deep-work hours the office never let her protect, finally gets to contribute the idea she'd never have blurted into a call. The one rule that matters during this phase is no shooting anything down. Divergence is for adding, not editing. Judgment comes next, and keeping it out of this window is the whole reason the window works.

Converge on purpose, and name who decides

After a couple of days you'll have thirty raw ideas, some brilliant, most not, a few that are the same idea in different clothes. Now you narrow, and this is where async brainstorming most often falls apart. The failure mode isn't too few ideas. It's forty good ones and no decision, a doc full of promise that nobody ever closes.

So run convergence as its own deliberate step. Cluster the duplicates, open a thread under the strongest few, let people argue the trade-offs in writing. Then someone owns the call. This is the same discipline that making a decision without a meeting runs on: a decision doesn't need consensus and it doesn't need everyone awake at once, it needs one person accountable for reading the input and choosing. A brainstorm that generates and never chooses isn't collaboration. It's a more pleasant way to waste everyone's morning.

When you should still get in a room

I don't want to oversell this, because live brainstorming does have one thing async can't fully replicate. When a small, high-trust group riffs in real time, one person's half-formed idea sparks another's, and you get a chain of build-ons that a shared doc doesn't quite reproduce. That fast, associative energy is real, and for early, exploratory problems it can be worth the timezone cost.

But notice what makes it worth it. The live spark is valuable for building on ideas, not for producing them cold. So use each format for what it's good at. Diverge async first, so everyone shows up to the call with ideas already written down and already read. Then spend the precious shared hour building on those and pushing them somewhere new. A live session where everyone arrived having thought is a completely different animal from one where the senior person thinks out loud and the rest of the room nods along. The meeting stops being where ideas are born and becomes where they get sharpened, which is the only job a meeting was ever good at.

None of this is a workaround forced on you by distance. It's the same lesson async-first teams keep relearning in every corner of the work: the room was never the source of the good ideas. The quiet was. Remote just takes away the room and makes you notice.

Give Your Team a Deadline Everyone Reads the Same Way

An async brainstorm lives and dies by its window, and "ideas due Thursday 5pm" quietly breaks the moment it crosses a timezone. Timely converts every time mention in Slack to each person's own clock automatically, so the deadline you set on the divergence phase, or any other, lands correctly whether your teammate reads it in London or Denver, and nobody misses the window because they did the math wrong.

Add Timely to Slack — Free · See how it works