A project timeline is a schedule reduced to its key dates: the phases, milestones, and deadlines of a project laid out along a time axis so anyone can see where it is and what comes next. It is the communication view of a plan. A Gantt chart shows every task, its owner, and what it waits on; a timeline shows the handful of dates the sponsor, the affected departments, and the crew need to know. Most improvement projects need both: the Gantt chart for the team running it, the timeline for everyone else.
Timeline, Gantt chart, or board?
| Project timeline | Gantt chart | Kanban board | |
|---|---|---|---|
| Shows | Phases and milestones against dates | Every task as a bar, with owners and dependencies | What stage each task is in right now |
| Level of detail | 5 to 15 items | 20 to 200 rows | One card per task, no dates |
| Audience | Sponsor, stakeholders, the plant | The project team | The people doing the work, daily |
| Answers | When does it start, when are the big dates, when is it done? | What is on the critical path and who is late? | What am I working on and what is blocked? |
| Maintained | When a milestone moves | Weekly, daily during an event | Continuously |
A board is not a timeline; it has no time axis. It is covered under kanban. The timeline and the Gantt chart are the same plan at two zoom levels, and the timeline should be derivable from the Gantt chart by hiding the task rows.
Kinds of timeline that are useful in a plant
Milestone timeline
A single line with dated markers: charter approved, materials in, event week, 30-day audit. The format for the sponsor update and the notice on the project board. Fits on one line of a slide or one strip of paper on the wall.
Phase timeline
The same thing with the phases drawn as blocks (plan, prepare, implement, sustain) and the milestones at the boundaries. Shows duration as well as dates, which makes overlaps visible. The right format for a rollout that moves through several areas, drawn as one row per area so the sequence and the gaps between them are obvious.
The improvement program calendar
A twelve-month timeline of every planned event, rollout, and audit across the plant, one row per area or per project. This is the timeline that matters most in a Lean program and the one most plants do not have. It is where resource conflicts show up (two events in the same week pulling the same maintenance tech), where the follow-up window after each event is reserved before the next one starts, and where the leveling happens so improvement work arrives at a steady pace instead of in bursts before an audit. Posted in the continuous improvement office or on the main board, updated monthly.
Building a timeline
- Fix the scope first. The timeline is a promise about dates, and the dates are only as good as the scope behind them. The charter's problem statement, deliverable, and out-of-scope list come before any date; see scope creep for what happens otherwise.
- Break the project into phases. Three to six. For most improvement projects: plan, prepare, implement, sustain. Each phase ends at a milestone that is a verifiable event, not a date.
- Set the milestones. Approval points, deliveries, the event or install dates, training complete, the follow-up audit. A milestone is something someone can confirm happened: "layout approved by safety," not "week 2." Eight or fewer for a project of a few months.
- Estimate durations from the task level. If a Gantt chart exists, the phase durations come from it. If not, estimate the main tasks in each phase, add them with realistic overlap, and remember that the owners also have regular jobs. See resource management on using actuals from past projects.
- Place the fixed dates and work backward. Some dates are given: the customer audit, the plant shutdown week, the weekend the aisle can be closed. Put those in first, then schedule the phases around them. The weekend closure, not the start date, is usually what drives a floor marking timeline.
- Check it against the program calendar. Does it collide with another event, a peak production period, or someone's vacation? Move it now, not in week three.
- Post it and keep it current. On the project board at the area, on the sponsor's one-page update, and on the program calendar. When a milestone moves, every copy moves the same day, with a note on why.
Example: a three-area 5S rollout
One cell per month, with the sustain phase of each overlapping the next cell's preparation. Illustrative dates.
| Area | Jan | Feb | Mar | Apr | May | Jun |
|---|---|---|---|---|---|---|
| Cell 1 (pilot) | Plan ◆ Charter 1/12 | Prepare ◆ Event wk of 2/9 | Sustain ◆ 30-day audit 3/11 | ◆ Standard signed off 4/1 | ||
| Cell 2 | Plan ◆ Charter 3/16 | Prepare ◆ Event wk of 4/13 | Sustain ◆ 30-day audit 5/13 | ◆ Standard signed off 6/1 | ||
| Cell 3 | Plan ◆ Charter 5/18 | Prepare ◆ Event wk of 6/15 | ||||
| Fixed dates | ◆ Customer audit 4/22 | ◆ Shutdown wk of 6/29 |
What this shows that a task list does not: the Cell 2 event lands a week before the customer audit, which is either a problem (the area is torn up during the audit) or an advantage (the area is freshly marked and labeled), and that decision needs to be made in January. The Cell 3 event runs into the shutdown week; either the event moves up or the follow-up audit moves into July. And each cell's sustain phase overlaps the next cell's planning, so the pilot team is available to coach, which is the point of the sequencing.
Keeping a timeline honest
- Milestones are events, not dates. "Materials delivered" can be verified; "end of week 3" cannot. If a milestone is reached late, the timeline shows it; if it is defined as a date, the date just passes.
- When a date moves, say why. A timeline that shifts silently stops being trusted. A one-line note at the milestone ("mirror backordered, install moved to 3/14") keeps it credible.
- Do not add tasks to it. The moment a timeline grows task rows it becomes a bad Gantt chart. Keep the detail in the Gantt chart or the board and the timeline at milestone level.
- Protect the fixed dates. Everything else can move; the aisle closure weekend, the audit, and the shutdown cannot. Build in buffer before those, not after.
- Reserve the sustain phase. Every event timeline includes the 30-day follow-up as a milestone with an owner. Timelines that end at the event report-out produce events whose gains fade.
Tools
A milestone timeline is a row of a spreadsheet, a line on a whiteboard, or a strip of masking tape on the project board with sticky-note markers. The program calendar is a spreadsheet with one row per project and one column per week or month. Project management software adds the ability to roll a Gantt chart up to a milestone view automatically and to share it across sites, which is worth having once several projects share people; for a single plant's improvement program, the paper copy at the gemba is what gets looked at and the spreadsheet is the record.
Frequently asked questions
What is the difference between a project timeline and a Gantt chart?
A Gantt chart shows every task as a bar with its duration, owner, and dependencies. A project timeline shows only the phases and milestones. The timeline is the Gantt chart with the task rows hidden, made for communicating rather than managing.
What is a milestone?
A verifiable event that marks the end of a phase or a key decision point: charter approved, materials delivered, event complete, audit passed. A milestone has zero duration and a definite yes-or-no completion.
How many milestones should a timeline have?
Few enough to read at a glance. Five to eight for a project of a few months; one or two per month for a year-long rollout. If it needs more, the detail belongs in a Gantt chart.
Is a Kanban board a project timeline?
No. A board shows what stage each task is in, with no time axis. It is the right tool for running day-to-day work, not for showing when the project will be done.
Do I need project management software?
Not for a plant improvement program. A spreadsheet and a wall are enough. Software is worth it when several sites share people or the project count outgrows what one person can hold in their head.
Related tools
The timeline is the top layer of the project plan. The task layer is the Gantt chart; the daily layer is a kanban board. The plan it belongs to also includes resource management, stakeholder engagement, cost-benefit analysis, and scope control. The projects most often timelined this way are on the kaizen and 5S pages.