Gantt in Excel vs Gantt online: what really changes
The Gantt chart is the most immediate way to show when activities start, how long they last and in what order they occur. The question that many Italian project managers ask themselves is not whether a Gantt is needed - it is almost always needed - but where to do it: in the spreadsheet they have already opened, or in a dedicated tool? The honest answer is "it depends", and in this article we try to understand what it depends on, without fans. Because the wrong choice isn't using Excel: it's using the wrong tool for the problem you really have.
How to make a Gantt in Excel
Let's start with the good news: to build a Gantt in Excel you don't need macros or additional components. Excel does not have a default Gantt chart type, but the same result is achieved with a stacked bar chart, as explained in theMicrosoft documentation. The steps are these:
- Prepare a table with three columns: activity, start date and duration.
- Select the data and insert a stacked bar chart.
- Make the first series — the start dates — invisible by setting the padding to "none": only the duration bars remain visible, positioned in the right place on the timeline.
- Reverse the order of the categories on the vertical axis, so the first task is at the top.
- Color system, grid and labels: the Gantt is ready.
There is also a second way, without graphs: conditional formatting on cells, coloring each cell in the row that falls between the start date and the end date. It's convenient for quick reading on the screen, but less suitable for projecting or inserting into a document. In both cases, if you prefer to start from a ready-made file, Microsoft offersFree Gantt templatesfor Excel, from the "Simple Gantt chart" to the "Gantt project planner".
All this takes little time the first time and even less the following times. For a simple plan to show in a meeting, this is more than enough.
The limits that are discovered later
The problem with the Gantt in Excel isn't building it: it's maintaining it as the project moves. And projects are always moving.
Dependencies don't exist
The graph is a representation of the data, not a model: if you move the end date of a task, the tasks that depend on it stay where they are. The logical link between activities lives in the head of whoever updates the file, not in the file. In a plan with dozens of tasks and cross-dependencies, each change becomes a manual hunt for everything that should move accordingly — and sooner or later something slips through the cracks.
The baseline is not there
Comparing the approved plan with the actual trend requires a second set of bars built and maintained by hand: every week, an update job that someone has to do and redo. It's the reason why thebaseline managementit is a chapter in itself in project control: without that comparison, the Gantt only shows the plan, never the gap between the plan and reality.
The update is not collaborative
The bar is an element of the chart: you can't ask a colleague to "tick" their activity and see the Gantt update. Every update comes from you, from the right file, from the right version: exactly the bottleneck that a shared plan should avoid.
The time scale is rigid
Weeks or months, you decide at the beginning; re-adapting the view — for example switching from week to month for a committee — is not a matter of a click, but of redoing the table or graph. The same goes for calendar changes, such as holidays that move the end of activities.
When Excel is enough, when not
The Gantt in Excel is enough when: there is only one project, with a few dozen activities; dependencies are few and simple; you are the only person who updates the plan; the Gantt is used to communicate a sequence, not to govern it.
You need a dedicated tool when: dependencies really matter and a delay needs to propagate itself; it is necessary to compare the plan and the final balance on a baseline; more people update the plan; the Gantt must enter into periodic reports without manual redoing.
In my opinion, the bottom line is this: as long as the Gantt is a drawing that you show to others, Excel is fine; when it becomes the tool with which you govern the project, drawing is no longer enough.
The honest comparison
| I wait | Gantt in Excel | Gantt in a dedicated tool |
|---|---|---|
| Creation | Fast, no additional costs | Requires initial setup |
| Addictions | Not managed | Connected: the delay propagates |
| Baselines | To be built by hand | Native plan-final comparison |
| Updates | Manuals, one person at a time | Shared: everyone updates their part |
| Reports | To be redone every lap | Generated from updated data |
| Cost | Zero: It is already installed | To be evaluated on a case-by-case basis |
Neither column wins outright: the question they answer changes. The Gantt in Excel answers "how do I explain it", the one in a dedicated tool answers "how do I control it". And they are two different jobs: explaining a sequence can be done once the project is finished, checking a plan is done every week.
The next step
If your case is the latter — dependencies that matter, baselines to compare, multiple people updating — it's worth seeing what a Gantt looks like in ControlRoom: afree guided demoIt's the quickest way to figure it out without installing anything. First, some useful reading: theGantt chart guide, which takes up the basic concepts, so you arrive at the demo with ideas already clear.