In some projects the alarm does not come from the product but from a spreadsheet cell. A number does not add up, a forecast fails to match the actual result, or a row remains incomplete. The project manager urgently calls the person they believe can fix that cell. At the other end, however, is someone immersed in a real malfunction, worried about what is not working and the people who will bear the consequences. Asked to explain the number immediately, they cannot help thinking: “You are interrupting me about your spreadsheet while I am trying to save the product?”
Two maps of the same reality
The project manager watches deadlines, costs, commitments and progress. The person working on the product sees failures, unsuccessful attempts, waiting users and technical decisions that must be made. Neither perspective is useless. The problem begins when one map is mistaken for the whole territory: what does not add up in the spreadsheet automatically seems more urgent than what is happening in reality. The word “urgent” then means something different to the person speaking than to the person listening.
The spreadsheet is not the enemy
An inconsistent figure may be the first sign of a delay, an underestimated cost or a mistake that nobody had noticed. Always ignoring it would be irresponsible. But before calling someone urgently, we should understand what that number represents. Is a record missing? Has the information simply not been updated yet? Or has something happened that could change a decision today? A cell can point to a real problem; by itself, it does not prove that this is the most serious problem.
When the measure becomes the goal
The syndrome begins when the spreadsheet must look orderly even though the product does not. Explanations are demanded at once so a figure will finally be consistent, while the malfunction still needs attention. We risk ending up with a green cell and a defective product. Measurement should help us see more clearly and choose more wisely, not create the feeling that everything is under control because the table has been filled in.
The cost of an interruption
A phone call takes more than the minutes spent speaking. Someone investigating a malfunction has to stop, reconstruct the context for another person, answer, and then recover the thread of their own reasoning. Already under pressure, being summoned “urgently” over an unexplained figure can add frustration to worry. This does not mean that the technician owes no account of their work. It means that the time and concentration of people solving problems are also project resources.
Three questions before calling
Before turning a cell into an emergency, I would ask: what concrete consequence does this discrepancy have? What happens if the answer arrives in an hour rather than now? Is this really the person we need to interrupt? If the number reveals a serious risk, the call is justified, and the reason should be explained. If the aim is merely to complete a report, we can leave a clear request and agree on a time for the answer. Urgency should not be a tone of voice; it should be an assessment of consequences.
Keeping control also means protecting priorities
A good manager does more than collect figures. They help the team distinguish what can wait from what threatens the outcome, remove obstacles and make trade-offs visible. The person working on the product, too, must explain clearly what is happening instead of assuming that every administrative request is a waste of time. When both sides listen, the spreadsheet becomes what it should be: a tool that serves the work, not its master.
What I would like to leave my children
If one day you lead a project, do not mistake a precise table for a healthy product. Before demanding an immediate answer, try to understand the problem the other person is facing. And if you are the one interrupted, calmly explain which priority you are protecting. A number can help us see; it must not stop us from looking. A cell can be corrected. Time taken away from the right problem cannot always be recovered.
Papy