Excel is where the numbers live. But the moment two people need to work on the same numbers, the tools Excel gives you — co-authoring, shared drives, emailed files — start working against you. Here are the five ways it breaks, and what each one costs a team.
None of these are user error. They're consequences of one design decision: Excel treats the file as the unit of sharing, and it treats every keystroke as final. Everything below follows from that.
1. Every keystroke is live — to everyone
Turn on co-authoring in Excel (or share a workbook on OneDrive or SharePoint) and there is no draft state. The moment you type a number, your colleague sees it. A placeholder you meant to come back to. A what-if you were testing. A typo with an extra zero.
The cost isn't embarrassment — it's decisions. Someone opens the sheet at 3:40, sees your half-finished forecast, and takes it into a meeting at 4:00. By the time you've fixed it, the number has already been quoted. Most teams learn this the hard way and quietly turn co-authoring off within a few weeks, which sends them straight back to emailing files.
What good looks like: a private space where you can think, revise and abandon — and a deliberate moment where you say "this is ready." That's what Submit is.
2. Share a workbook, share everything in it
You want Finance to see the budget tab. Excel's answer is: share the workbook. Now Finance also sees the Notes tab, the Scratch tab, the tab where you're modelling headcount cuts, and the one where you kept the vendor pricing you promised not to circulate.
The workarounds are all bad. Splitting into separate files means the numbers drift apart. Hiding tabs is a click away from un-hiding. Password-protecting sheets breaks formulas and annoys everyone. So teams either over-share and hope, or under-share and end up with six versions of the same table.
What good looks like: the worksheet — not the workbook — as the unit you share. You Invite someone to one tab. The rest of your workbook stays yours.
3. Version history captures keystrokes, not decisions
Auto-save sounds like insurance. In practice it produces six hundred versions of a file, each a few keystrokes apart, with no way to tell which one held the number you agreed on in Tuesday's meeting. "Excel version history" is a list of timestamps. It isn't a record of what changed, or why, or who decided.
When something goes wrong — a formula overwritten, a row deleted, a figure that used to be 1.2M and is now 12M — you're left scrolling through snapshots, opening each one, comparing by eye. The realistic outcome is that nobody looks, and the history exists only to make people feel better.
What good looks like: history as a list of intentional changes, each with an author, a time and a reason. That's what the Changes command shows, for any cell, row or worksheet.
4. Three workbooks. One story. No easy way in.
Sales has a pipeline file. Marketing has a leads file. Finance has the forecast. The board wants one page that pulls from all three. Your choices are copy-and-paste (stale by tomorrow), external links between files (broken the first time someone renames a folder), or Power Query (a project, not a workflow).
The deeper problem is that each source keeps changing. Whatever you assemble is a snapshot, and the people who own the sources have no idea you took it. Next week you do it all again.
What good looks like: the same worksheet living in more than one workbook at once — not a copy, not a link — so the summary updates when the sources do. That's xCopy and xPaste.
5. Compare version 3 to version 1? Good luck.
You made three passes at the budget over three weeks. Now someone asks what changed between the first and the third — and why. Excel offers you two files open side by side and your own eyes. There's no diff. There's no "show me the cells that moved." There's certainly no "and here's the reason each one moved."
So the question goes unanswered, or gets answered from memory, or gets answered wrong. Over a quarter, a team makes hundreds of decisions this way — with no reliable way to reconstruct how any of them were reached.
What good looks like: every revision comparable to every other, with the reason attached at the moment the change was made. Not reconstructed later. Recorded then.
What Symphony does differently
Symphony is an Excel add-in that changes the unit of sharing from the file to the worksheet, and the unit of history from the keystroke to the decision. Your edits stay private until you Submit. Teammates pull them in when they Refresh. Every Submit records who, what, when and why. Worksheets can live in multiple workbooks and stay in sync.
It doesn't replace Excel and it doesn't ask you to move your data somewhere else. It fixes the five things above, and leaves everything else alone.
Read about the six commands →
Watch the story unfold →
See how it compares to the alternatives →