# Gantt chart

> A timeline view in which each task is a horizontal bar running from its start date to its end date.

## What it means

Bars on a timeline from start to end dates; where it came from ; when it helps (fixed dates, dependencies) and when a Kanban board suits better; how to make one from any list with two date columns.

## A practical example

Research runs Monday–Wednesday and drafting begins Thursday; the bars make the sequence and overlap visible.

## Put it into practice

- Name the concrete situation before applying the label. Gantt chart is useful only when it changes a choice, boundary or next action.
- Make the state visible: write the owner, time, source or stopping condition down instead of relying on memory.
- Review what happened. Keep the part that reduced ambiguity and change the part that added ceremony without helping the work.

## How it relates to Plexii

any Table switches to a Gantt view when it has two Date columns, without changing the rows (/help/table-views); tasks have start and due dates (/help/widget-tasks-planning).
