How to present a timeline in slides

To present a timeline in slides, decide first what kind of timeline you have. A handful of dated events belongs on a milestone rail, stages that follow each other belong in phases, and work that overlaps belongs on a Gantt chart. Then label each point with the outcome that is true when it is reached, not the activity underway, keep dates and grid lines to the minimum the audience needs, and make the single most important date the most visible thing on the slide.

Pick the kind of timeline first

Most cluttered timeline slides are the wrong kind of timeline. A plan with overlapping workstreams forced onto a single rail needs crossing arrows and footnotes; a history of seven events forced into a Gantt grid is mostly empty cells.

The table below this article lists five kinds with a finished deck that uses each. The deciding question is whether things overlap. If each point is one event, use a rail or a list. If stages run one after another, use phases. If several pieces of work run at the same time, use a Gantt.

The project kickoff deck example on this site shows the Gantt case. An invented distribution business is replacing four warehouse systems with one platform by March 2027, and slide five is the plan to the first go live: six tasks across five months, from discovery and process design through data cleanup, build, site training and cutover rehearsals to go live and hypercare at the first site. Site training alone spans two of the five months and runs into the go live month. A rail could not show that.

Dates or phases

Use dates when the audience will act on them or hold you to them. Use phases when sequence matters more than the calendar.

The kickoff deck does both, on different slides. Its Gantt uses month columns rather than dates, which suits a plan the room is about to approve. Its decisions slide names one exact date the room must approve: 6 February as the cutover weekend. Putting that date on the Gantt as well as the decision slide would make it one label among many; putting it in a decision makes it the thing people remember.

The product launch deck on this site uses phases without dates: three acts over eight weeks, seed, announce and shelf, with one announcement day in week four. That fits an internal launch plan, where the teams need to know what comes before what, and the exact dates live in a separate checklist slide.

Investor timelines are a special case. Sequoia’s advice on presenting to investors is to keep financials simple and show on a timeline how you would spend the money, such as headcount, to achieve specific milestones. That is phases tied to money, not a delivery schedule.

What to label

Label each point with what is true when it is reached. Kingsway go live is better than development continues. Seven operators trained is better than training phase. An outcome label lets the audience check the plan later; an activity label cannot be checked.

The company profile presentation example, for an invented chilled meals manufacturer, compresses seventeen years into seven dated steps: one kitchen and six staff in 2009, the first supermarket listing of four lines in 2012, a hospital food service contract in 2015, its first BRCGS AA food safety grade in 2018, and a second site doubling capacity in 2021. Each step is a year and a fact. Nothing on the slide says grew or expanded without saying by how much.

Edward Tufte’s notes on project charts make two labelling points worth copying. Avoid mysterious acronyms and all capitals, which make every label harder to read, and annotate with substance rather than leaving bars bare. On a slide, substance means one short outcome per point, not a paragraph.

Gantt or milestones

A Gantt chart, as the reference site on the method describes it, shows activities against time: what each is, when it starts and ends, how long it lasts, where activities overlap, and the start and end of the whole project. The first version was devised by the Polish engineer Karol Adamiecki in the mid 1890s, and Henry Gantt’s version followed about fifteen years later.

Use a Gantt when the audience needs to see overlap and duration: a steering group approving resources, a team agreeing who is busy when. Use milestones when they need to see sequence and dates: an executive team, a customer, a board.

Tufte’s criticism of most Gantt charts is that the grid dominates. He describes charts where thin data sits in heavy grid prisons, so the administrative structure becomes the main visual statement instead of the tasks. On a slide, that means faint or no grid lines, bars coloured by workstream rather than by task, and no more rows than the audience can read. Group related tasks with a shared colour so the chart reads as three workstreams, not twelve bars.

Show plans against reality

A timeline for a finished project should show planned and actual together. Tufte recommends showing actual dates of completed work alongside projected dates. The lessons learned deck example is the closing review of the same invented warehouse rollout: it puts planned against actual on slide two, 20 weeks planned and 26 taken at 12 per cent over budget, then walks the timeline of what happened.

The same idea works in a live project. A forecast marker beside the original date, with the gap labelled in days, tells the story faster than a paragraph about slippage.

For proposals, a dated list of next steps does a similar job looking forward. The pricing proposal deck example runs five dated steps from a site survey on 5 November to service starting on 1 April, and the board decision on 14 January is the step the whole proposal is aiming at.

Common mistakes

• Every date on one slide. Show the dates decisions depend on; move the rest to an appendix.
• Activities as labels. Design phase tells nobody when anything is done.
• Heavy grids. The grid is scaffolding, not content.
• Arrows everywhere. If a timeline needs many arrows, it is probably a Gantt or a flowchart.
• Equal spacing that lies. A rail that spaces 2009 and 2012 the same distance as 2021 and 2022 implies an even pace; say so in the labels if the gaps differ.
• No today marker. On a live plan, show where the project is now.

For charts of numbers over time rather than events, the post on presenting data in slides covers choosing between lines, bars and waterfalls. The question page on deliverables explains the difference between a deliverable and a milestone, which is the difference between the two kinds of label.

Build it

The builder has 18 timeline templates, and the page on timeline slides shows the layout families and how many points each holds. For overlapping work there is a Gantt element. Each task has a name, a start and an end, and an optional group and description; tasks have no dependency links, so no arrows are drawn between bars. Task caps are set by layout: 6 on the phase rollup over five months, 8 on the quarterly roadmap, 10 on the sprint plan and 12 on the swim lane roadmap, and a Gantt added from the element library holds 12 tasks across four columns by default.

The guide to adding charts, maps and diagrams to slides covers adding a Gantt timeline. In an editable PowerPoint export the Gantt artwork stays a picture, but its labels become native text boxes you can still edit.