In almost every organisation we work with, the same scene plays out. The project management tool is in place, schedules are kept in it, more or less. And when someone asks who will be available next month, a team lead opens an Excel file: team members in rows, weeks in columns, colours to flag overruns.
For a long time we saw that file as a lack of discipline. That was a mistake. It says something important about how workload is really managed, and about what tools fail to do.
What the file says about the organisation
In a previous article, we described resource management as the blind spot of project management: deadlines get planned without checking that the means will be there. The spreadsheet is the tangible trace of that blind spot. It exists because the workload question found no place anywhere else.
First, it shows that workload is not limited to projects. Support, urgent requests, recurring activities, the colleague on loan to another department: all of it weighs on capacity, and none of it exists in the tool's resource pool. The team lead knows it, so they write it down wherever they can.
Second, it shows a need for discretion. A cautious assumption written in a shared tool quickly becomes a commitment. In a personal file, it stays an assumption.
What it costs, without anyone putting a figure on it
The file has one major flaw: it knows nothing about the schedules. When a phase slips by three weeks, it does not know. It is right on the day it is built, then it drifts. Every serious trade-off therefore means rebuilding it, often in a hurry.
It also isolates. Two team leads never compare their files, and the project manager never sees what their schedule sets off for others. Management wanting an overall view has to request the files, piece them together, and discover along the way that everyone has their own conventions.
Finally, it depends on one person. When they change jobs, the knowledge of the workload leaves with them.
The real cost is not the time spent filling in the file. It is the delay between the moment an overload becomes predictable and the moment someone sees it.
Henry's perspective: make the file unnecessary rather than banning it
The Henry team devoted an article to this question: Why resource planning always ends up in a spreadsheet. Its argument matches what we see in our assignments: the spreadsheet does not win because teams resist tools, but because it is the only place where project workload and everything else can finally meet.
That leads to a conclusion that changes how the subject should be approached. Banning the file achieves nothing: it will come back through the side door. What is needed is a tool that offers the same flexibility (every useful row, the level of detail you choose, assumptions that are not commitments) while staying connected to the schedules. At that point, the file no longer has a reason to exist.
On the same blog, the article Committing to deadlines without knowing whether the teams can hold them shows what that disconnect costs at the very moment a date is promised.
Where to start
- List the existing workload files instead of ignoring them: they reveal what teams actually need.
- Note what they contain that the tool cannot represent: non-project activities, shared resources, part-time work.
- Connect workload to the main phases of the schedules, even roughly, at monthly level if need be. An approximate but accurate view is better than a precise but wrong one.
- Decide who arbitrates when workload exceeds capacity. Without an arbiter, the best view in the world only serves to observe.
The spreadsheet is not the enemy. It is a signal. Read properly, it shows exactly what needs to be built to do without it.