What is a Schelling point in simple terms?

A Schelling point (or focal point) is the choice people naturally land on when they have to coordinate but can't communicate. The classic example: asked to meet a stranger in New York with no way to talk, most people pick noon at Grand Central — not because it's best, but because it's the obvious, guessable answer both sides can reason their way to. Wikipedia defines it as "a solution that people tend to choose by default in the absence of communication."

What's a Schelling point example for a remote team?

Any time teammates converge without discussing it. If everyone "just knows" that decisions live in one doc, that "done" means merged, or that the Tuesday working session is where things get settled, those are focal points. The trouble starts when the obvious choice isn't actually obvious to everyone — a newcomer, someone in another tool or time zone — and people quietly pick different answers. That mismatch is most remote coordination failure in one sentence.

Is a Schelling point the same as a focal point?

Yes. "Focal point" is the original term Schelling used in his 1960 book The Strategy of Conflict; "Schelling point" is the name that stuck in his honor. They mean the same thing: a salient, default solution to a coordination problem that people reach without communicating. Game theorists and economists use the terms interchangeably.

How do you create a Schelling point on a team?

You engineer salience. Make one unmistakable home for each kind of work, default to conventions a newcomer could guess rather than clever ones, anchor recurring coordination to a fixed shared moment (like a standing live session), and write the conventions down so people who weren't there can inherit them. The goal is common knowledge — not just that a place exists, but that everyone knows everyone knows it's the place.

Does this mean remote teams should communicate less?

No — it means communicating about the right things. Focal points handle the predictable, repetitive coordination (where does this go, what does this word mean) so you don't burn synchronous time on it. That frees your real conversations for the genuinely ambiguous and high-stakes calls, where tacit coordination breaks down and you actually need to talk. Focal points are a complement to communication, not a replacement.

The Schelling Point: Coordinating Without Communication

Here is a game with no rules explained and no winner announced. You have to meet someone in New York City tomorrow. You don't know who. You can't call, text, or email them — and they're under the same constraint. You have to name a time and a place, betting that a stranger you've never met picks the exact same one. Where do you go?

When the economist Thomas Schelling ran this thought experiment, something strange happened. People didn't scatter across the five boroughs. They converged. The most common answer, as Wikipedia documents, was "noon at (the information booth at) Grand Central Terminal." No communication. Near-total agreement. Schelling had a name for that point of convergence — a focal point, now usually called a Schelling point.

It's the most useful idea your remote team has never heard of. Because your team plays this exact game all day: which doc is the real one, which channel this goes in, what "done" actually means, when we actually talk. Usually without realizing it. Usually losing. Here's what a Schelling point is, why distributed work quietly destroys yours, and how to build them back on purpose.

The stranger you have to meet in New York

Start with the experiment, because the result is genuinely counterintuitive. Schelling asked people how they'd "determine the time and place to meet a stranger in New York City, but without being able to communicate in person beforehand," per the same source. With no way to talk, classical game theory says you're stuck — any time and any place is as good as any other, so you should be lost. Instead, people landed on the same answer over and over.

Why Grand Central at noon? Not because it's the best place to meet — a quiet bar would be more pleasant, and any number of spots are more central to where you actually are. It's because it's the obvious one. The station's prominence as a transit hub and noon as the unmissable middle of the day make those choices leap out. Wikipedia's definition is precise: a focal point is "a solution that people tend to choose by default in the absence of communication in order to avoid coordination failure." The magic word is default.

This wasn't a parlor trick. Schelling introduced the focal point in his 1960 book The Strategy of Conflict, the work that, decades later, helped earn him the 2005 Nobel Memorial Prize in Economic Sciences "for having enhanced our understanding of conflict and cooperation through game-theory analysis." His informal findings were later "replicated under controlled conditions with monetary incentives by Judith Mehta." The headline holds up: coordination without communication isn't just possible. It's predictable — if there's an obvious point to converge on.

Your remote team plays the New York game all day

Now translate it. Almost every act of coordination on a distributed team is a version of the New York game — two or more people trying to land on the same choice without stopping to talk it through. Which of your six tools does this conversation belong in? Where does the "real" version of the spec live? When someone writes "EOD," whose time zone is that? What counts as done — code merged, or shipped, or announced? Who owns this now that it's been mentioned in three threads?

Every one of those is a coordination problem you're solving silently, dozens of times a day. In a shared office, you barely notice, because the room is full of focal points. There's one whiteboard, so that's where the diagram goes. There's a 10 a.m. standup, so that's when you sync. You overhear that someone already pulled the churn numbers, so you don't. Physical proximity manufactures obvious answers for free.

Remote work strips those answers out, and the cost shows up in the data. Atlassian's State of Teams 2025, a survey of 12,000 knowledge workers and 200 executives, found that "leaders and teams waste 25% of their time just searching for answers" — a quarter of the week spent failing to find the obvious place. Worse, "1 in 2 knowledge workers say their teams often work on the same things without knowing it." That's not a fluke; it's what failed convergence looks like at scale: two people building the same deck, a decision re-litigated for the third time, a doc rewritten because nobody could find the original. When there's no Schelling point, everyone guesses — and guesses don't line up.

Why the obvious answer stopped being obvious

Here's the part that explains why this gets worse as teams go remote, not just harder. A focal point works on one ingredient: shared salience. Grand Central is the answer only because it's obvious to you, and obvious that it's obvious to the other person, and obvious that they know you know — all the way down. Schelling's insight wasn't really about places. It was about common knowledge: we converge when we can each reason our way to the same answer because we share the same sense of what stands out.

Distributed work quietly dismantles that shared sense. Your teammates are in different tools, different time zones, different tenures, different cultures. The "obvious" channel to a founder who's been here three years is invisible to the engineer who joined last week.

What's salient to you simply isn't salient to them — and neither of you can see the gap, because each of you assumes your obvious is everyone's obvious. That assumption has a name; it's the curse of knowledge, and it's the silent killer of focal points.

So the failure mode isn't that people are careless. It's that the salience landscape fractured. "Just use common sense, it's obvious where that goes" is advice that only works when the sense is genuinely common. On a distributed team, it usually isn't — which is why the most expensive coordination failures don't feel like failures in the moment. Each person did the obvious thing. The obvious things just didn't match, and you only find out two weeks and four duplicated tasks later.

You can build a Schelling point on purpose

Now the good news, and it's the most actionable thing Schelling ever implied: focal points are made. Grand Central became the answer through tradition and prominence — it was built up over time into the obvious choice. Salience can be engineered. A team that loses its natural focal points to distance can deliberately build new ones. A few moves that work:

Make one place unmistakably the place. For each kind of thing — decisions, in-flight work, the live discussion — there should be a single home so obvious that nobody has to think about it. The power isn't the specific tool you pick; it's that everyone knows it's the place, and knows that everyone else knows. That's the common-knowledge loop a Schelling point runs on. Half a great location plus universal certainty beats a perfect location nobody's sure about.

Default to the obvious, not the optimal. Schelling's deepest lesson is that the focal point isn't the best option — just the most guessable one. So when you set a convention, optimize for "a newcomer could guess this" over "this is clever." Times in one canonical zone. "Done" means merged, full stop. File names a stranger could predict. Cleverness fragments salience; predictability concentrates it.

Anchor recurring coordination to a fixed, shared moment. Grand Central was a where; "noon" was a when. Teams need temporal focal points too — a standing live working session that everyone knows is the moment things get decided. It becomes the noon-at-Grand-Central of your week: nobody has to negotiate when to converge, because the convergence point is already obvious. A tool that puts video, a shared canvas, and a running record of decisions in one place — like Coommit — turns that session into a single, unmistakable focal point, so people stop scattering across tabs trying to find where the real conversation is happening. The team meets at the booth, not in twelve different DMs.

Write the convention down so newcomers inherit the salience. A focal point built on tradition only works if the tradition is legible to people who weren't there when it formed. The new hire can't guess your obvious; they have to be handed it. A short, findable note on where things live and what words mean turns private salience into shared, confirmable understanding — the difference between a focal point that survives onboarding and one that resets every time someone joins.

The limit of going silent

A focal point is powerful, but it is not a substitute for talking, and pretending otherwise is its own failure mode. Two honest caveats.

First, the obvious default can be obviously wrong. Focal points are arbitrary by nature — they coordinate, but they don't optimize. Always defaulting to headquarters' time zone is a perfect Schelling point and a quietly unfair one. The fact that everyone converges on something doesn't make it good; it just makes it sticky. Engineer your defaults deliberately, and audit them, or you'll calcify whatever happened to be salient on day one.

Second, tacit coordination has a ceiling. Schelling's whole point was about the absence of communication — and even his strongest cases were recurring, low-novelty problems. For anything genuinely new, ambiguous, or high-stakes, no amount of shared salience saves you; you have to actually communicate. The right model isn't "replace conversation with focal points." It's the opposite: let focal points absorb the predictable 80% — the where-does-this-go, the what-does-this-word-mean — so you can spend your scarce, expensive synchronous time on the 20% that's actually ambiguous. That's the natural partner to commander's intent: give people one clear focal point and the why behind it, and they can coordinate through situations you never explicitly mapped.

The remarkable thing isn't the failures

Go back to New York one more time. The striking finding was never that strangers sometimes fail to meet. It's how often they succeed — total strangers, zero communication, landing on the same spot at the same hour, just by both reaching for the obvious. That latent ability to coordinate without talking is real, and your distributed team has it too. It just needs an obvious to reach for.

The default conditions of remote work erase the obvious — too many tools, too many zones, too many private versions of "common" sense. But a Schelling point can be built as deliberately as Grand Central was. Pick the place, default to guessable, anchor the moment, write it down. Do that, and your team stops guessing where to meet. They just show up at the booth.