Are You Still Managing Your Projects on Spreadsheets?
It's Monday, 9:02. The team is on the call, the tracker is on the screen, and the first thing anyone says is: "That's not right, the Henderson row. We shipped that Thursday."
So someone edits the cell. Then someone else points out that the launch date in column F moved last week and nobody updated the dependent rows. Ten minutes in, you haven't discussed a single decision. You've been proofreading a spreadsheet, live, with eight of your most expensive people watching.
If that scene made you wince, this article is about your company. Not because anyone did anything wrong but because of what quietly happens when a team keeps managing projects in spreadsheets long after the work has outgrown them.
Why every company ends up here (and why it was the right call)
Let's be honest about how the tracker was born, because it almost certainly wasn't a mistake.
Somebody probably a founder, an ops lead, or the most organised person in the room needed to see all the work in one place. They opened Excel or Google Sheets because it was free, it was flexible, and everyone already knew how to use it. No procurement, no onboarding, no "new tool" eye-rolls. One afternoon of building, and suddenly the business had a single view of everything in flight.
That decision was correct. At five people and a dozen projects, a spreadsheet is a genuinely good coordination layer. It bends to exactly how you work. It costs nothing. It ships instantly.
And spreadsheets remain unbeatable at what they were built for: calculation. Budgets, forecasts, pricing models, capacity maths that's grid territory, and nothing touches it. The trouble starts in a narrower place than most tool debates admit: a grid of cells is superb at computing numbers and poor at coordinating people. Deadlines, handoffs, ownership, status those aren't calculations. They're conversations with structure. And a cell can't hold a conversation.
The tool got outgrown. The person who built it didn't fail, they succeeded so well that the whole company moved in.
Here's what it costs once that happens. Six things, each of which you'll recognise or you won't and if you recognise four or more, keep reading to the self-test.
Hidden cost #1: One person became the system
Every long-lived tracker has a true owner. One person who knows why row 48 is amber, which tabs are dead, and what the colour coding actually means. When anyone needs to know the state of anything, they don't check the spreadsheet they ask her.
That's the tell: the spreadsheet isn't the source of truth. She is. The file is just her notes.
The cost is concentration risk. When she's on holiday, status goes dark. When she's in back-to-back meetings, updates queue behind her calendar. And if she ever resigns, the company's operational memory walks out with her. We've seen more than one business run end-to-end through a single hand-maintained master sheet a "One Pager" that only one or two senior people could safely touch. Replacing it is one of the most common projects we're brought in for, and it's never really a tooling project. It's a key-person-risk project.
Hidden cost #2: Status is typed, not true
A spreadsheet doesn't know anything. It only says what someone last remembered to paste into it. "In progress" might mean actively being worked on this morning or abandoned three weeks ago by someone who forgot the tracker exists.
This is the gap your Monday meeting exists to close. The tracker says one thing; reality says another; the meeting reconciles the two. Which means your status data is only accurate for about an hour a week immediately after the meeting that corrected it and decays from there.
The cost is decision risk. Every plan built on the tracker between meetings is built on stale data. The MD who glances at it on Wednesday is reading last Monday's world.
Hidden cost #3: The meeting tax
Because a cell can't notify anyone, humans have to do the notifying. The spreadsheet only answers when opened it can't remind, assign, or escalate. So the team compensates with meetings, check-ins, and "quick syncs" whose real agenda is: tell each other what the tracker should have said.
This is where the macro numbers stop being abstract. Asana's Anatomy of Work research found that around 60% of people's time goes to "work about work" chasing status, searching for information, sitting in coordination meetings and that managers spend 62% of their day on work coordination rather than the work itself. A spreadsheet-run operation doesn't cause all of that, but it institutionalises it: coordination that a system could do automatically becomes a standing item in expensive people's calendars.
Count your recurring status meetings, multiply by attendees, and price it. That's the tax.
Hidden cost #4: Version chaos
You know the filename: `Tracker_FINAL_v7_REALLYFINAL.xlsx`. Or its cloud-era cousin: one shared Sheet where, sometime last Tuesday, someone sorted a filtered range and quietly scrambled three weeks of updates and nobody noticed until the client asked why their project had someone else's dates.
The cost here is rework and embarrassment. Two people make decisions off two different versions of the truth. A quote goes out based on a row that was overwritten. The time spent untangling which version is real per Anatomy of Work, people spend about 10% of their day on work that's already been done, over 200 hours per person per year is pure waste, and version-tangled trackers are one of the places duplicate work breeds fastest.
Hidden cost #5: No memory of who changed what, or why
A deadline in the tracker moved from March to May. Who moved it? When? Was it agreed with the client, or did someone nudge it while tidying up? The spreadsheet can't tell you. The reasoning lives in an email thread, a Slack message, or someone's recollection if it lives anywhere at all.
Version history technically exists, but nobody reads a cell-by-cell diff to reconstruct a decision. In practice, the audit trail is gone. The cost is accountability risk: when something slips, you can't learn from it, because you can't see how it happened. The same mistakes repeat, politely and anonymously.
Hidden cost #6: Maintaining it became a senior job
Add up the hours your most senior operators spend feeding the tracker: chasing updates, re-pasting status, reformatting tabs, rebuilding the summary view before the leadership meeting. At many companies it's half a day a week of exactly the people whose judgement you hired, spent on clerical upkeep.
And the grid's only growth move makes it worse: it scales by adding tabs, and every new tab is a new place for work to hide and a new surface to maintain. The tracker becomes a project of its own one with a headcount, no deliverable, and no end date.
The tipping point: a six-statement self-test
How many of these are true of your tracker today?
1. If one specific person left tomorrow, nobody could confidently maintain it.
2. At least one recurring meeting exists mainly to correct or update it.
3. In the last quarter, two people have acted on different versions of it.
4. A missed deadline has gone unnoticed because no reminder ever fired.
5. You cannot reliably see who changed a given cell, or why.
6. Someone senior spends two or more hours a week maintaining it.
Zero to one: your spreadsheet is still doing its job, carry on.
Two to three: you're paying the tax, and it's rising with headcount.
Four or more: the tracker isn't managing your projects; your people are managing the tracker. (If you're now weighing the alternatives, we've written a direct comparison at (/asana-vs-excel).)
What the other side looks like
Picture the same team, same Monday, after the work moved into a real work management platform.
Nobody corrects a tracker, because there isn't one to correct. Status is a by-product of work happening: when a task is finished, it's marked done by the person who did it, the moment they did it and every dependent piece of work knows. Due dates remind people themselves. Handoffs notify the next owner instead of waiting for someone to spot them. The chasing that used to fill the meeting simply doesn't exist, so the meeting shrinks to what it was always meant to be: decisions.
This isn't hypothetical. One marketing agency we worked with went from zero reporting to live portfolio dashboards in under a month, their MD now runs Monday standups off a single Asana screen. Another client's ops team cut weekly admin by 12+ hours within six weeks, mostly by letting automation rules do the reminding and routing that humans had been doing by hand.
And the gap is still widening. A spreadsheet will never flag its own risks; Asana now can, Asana Dash finds overdue and at-risk work and generates status updates itself, which is a category of help no grid will ever offer.
The honest caveat
Switching tools fixes nothing by itself. If you lift a chaotic tracker into new software without deciding how work should actually flow, who owns what, what the stages are, what "done" means you get the same chaos with a nicer interface, and within two months someone quietly reopens the spreadsheet. That's why half-hearted migrations lose to Excel every time: the sheet is familiar, and familiarity beats an unstructured tool. The structure and the habits have to move with the work, we've laid out how to do that properly in Moving from Excel to Asana: don’t migrate everything
Take our Spreadsheet Scorecard, in a few minutes it shows you where your setup leaks time, where it puts work at risk, and what to fix first. As a certified Asana Solutions Partner, we turn fragile trackers into systems that run themselves.
Comments