Why real-time co-authoring is the wrong model for spreadsheets.

Most teams turn off real-time co-authoring within a week of turning it on. There's a reason — and it's not what you think.

The pitch was always compelling. Both of you edit the same spreadsheet. You see your teammate's cursor moving. You watch cells update in real time. No more sending files back and forth. No more "which version is latest?" No more merge conflicts.

Google Sheets did it first. Excel followed. Every collaboration tool that touches structured data has some flavor of it now. And yet, when you talk to teams who actually use spreadsheets to run their work — sales pipelines, finance forecasts, board packs — you find something strange. Most of them have quietly turned real-time editing off.

The social problem, not the technical one

Real-time co-authoring solves a technical problem: multiple people can edit the same cells without conflicts. What it doesn't solve — and, arguably, actively makes worse — is a social problem.

When you're working on a forecast, you're thinking through scenarios. Some of those scenarios are wrong. Some are half-baked. Some you'll rework three times before you're comfortable showing them to anyone. The last thing you want is your CFO watching, in real time, as your Q4 pipeline number drops by $2M — before you've had a chance to explain why, or to check your math, or even to decide if that's the number you're going to commit to.

"I don't want my boss watching me think."

Every product designer who's talked to a finance team has heard some version of this line. And once you hear it, you can't unhear it. It's the whole reason real-time co-authoring keeps getting turned off — even when everybody agrees, in principle, that collaboration would be nice.

What people actually want: private, then shared

Watch how spreadsheet-driven teams actually work, once you strip away the tool they're forced to use. The pattern is remarkably consistent:

1. Each person works privately on their part.
2. They iterate, revise, and sometimes throw it away.
3. When they're ready — and only then — they share.
4. They usually attach some kind of reason: "moved Acme to Q4 because they pushed their vendor decision."
5. The whole team refreshes to see the aligned view.

Nobody wants to watch each other type. What they want is a clean handoff at the moment when the thinking is done. It's not because they're hiding anything. It's because work-in-progress needs privacy to happen at all.

The Submit and Refresh loop

This is what Symphony is built around. Every user has their own copy of the worksheet — private, editable, invisible to anyone else. When they're ready, they Submit. That Submit becomes a transaction: a single, atomic change with a reason attached, a timestamp, a user identity. Everyone else Refreshes when they want the latest state.

It sounds simple because it is simple. It's how humans naturally work. Real-time co-authoring took the file-sharing paradigm and made it faster; Symphony steps back further and asks what the actual social contract of collaboration should look like.

What you gain

A few things happen when you shift from real-time to Submit-and-Refresh:

• People do more, better thinking. Nobody's watching, so nobody's performing. You try things, revise, decide.
• Every change has a reason. Because you attach one at Submit time. Six weeks from now, when someone asks why the forecast dropped, the answer is right there.
• Merging is a moment, not a mess. When two people Submit changes to the same area, Symphony surfaces the conflict at Refresh time — with context, with reasons — and a human decides. This is what conflict resolution should always have been.
• The audit trail is honest. Every transaction, every reason, every user, every timestamp. Not because we're paranoid — because that's the material from which real understanding is built.

What you don't lose

People sometimes worry that shifting away from real-time means slowing down. It doesn't. Refresh is instant. Submit is instant. If you and I both make changes in the same minute, we both see each other's updates the next time we Refresh — which is likely to be seconds later, not days.

What you lose is the illusion of always-fresh state. What you gain is reliable state — state that people have stood behind, given reasons for, and committed to sharing. That's the state you can actually build on.

The quieter path forward

Not every team needs this. If you're on a shared shopping list or a lightweight editorial calendar, real-time co-authoring is probably fine. The stakes are low and everyone's happy to watch each other type.

But for the spreadsheets that actually matter — the ones running your business — the pattern that works is older, quieter, and more human than the flashy real-time cursor. It's just: think privately, share deliberately, remember everything.

That's the pattern Symphony is built for.