The History of the Gantt Chart

By Victor Hoang · Updated Oct 23, 2026

Picture a munitions plant in 1917. A typed table cannot show anyone whether the plant is on time. Wallace Clark's book says that gap is what pushed the engineer Henry Gantt to develop a way of charting that compared performance with promises.

The Gantt chart is named for Henry Laurence Gantt, an American engineer who built his charts in factories between about 1890 and 1919. The name, though, comes from a 1922 book by his colleague Wallace Clark. The bar chart most people use today is a later, simpler descendant. The through-line is a steady build with a long dilution in the middle. A chart made to compare promises with performance became the default way to draw a schedule.

In that plant, orders that had been counted in hundreds were suddenly counted in millions. This article follows that chart from its precursors to the desktop, and separates three things that are often blurred: who drew the first bar chart, who drew Gantt's chart, and who gave the name to the chart you know. For the concept itself, see what a Gantt chart is. For the wider field, see the history of project management.

Timeline at a Glance

Dates here separate invention from publication. Where sources disagree, the row says which date it uses.

The Time Charts (1765-1896)

Lines on a page learn to stand for time

Start in 1765 with a two-by-three-foot paper scroll covered in pastel stripes. The National Endowment for the Humanities describes Joseph Priestley's Chart of Biography as roughly 2,000 names of poets, artists and statesmen, sorted into six columns and placed along a horizontal line marked in ten-year steps. Priestley tied years to distance on the page, so a name drawn twice as far away had lived about twice as many years earlier. He wanted a reader to see how lives related to one another without the help of arithmetic or even words. A companion, A New Chart of History, followed in 1769.

Project historian Patrick Weaver traces the modern bar chart to this work and to William Playfair, whose 1786 atlas carried 43 time-series plots and a histogram. Weaver finds no evidence of bar charts before 1765, and says bar charts were developed about 100 years before Gantt. That is the first thing to keep straight: the idea of a bar standing for a span of time is much older than the man whose name is on it. Weaver's separate study of the origins of bar charting traces the supporting ideas of graphing back through the Middle Ages to ancient Greece. The work being scheduled is older still: builders ran ancient megaprojects with logbooks and labor gangs long before anyone drew a bar.

Then came the first scheduling chart in the strict sense. In 1896 the Polish engineer Karol Adamiecki developed what he called the harmonogram. By Weaver's description, it used scaled paper strips, one per activity, with each activity's predecessors listed above it and placed to its left, which makes it a distinct forerunner of the network methods that came roughly 60 years later. Adamiecki worked independently of Gantt. Weaver also reports that by 1912 a bar chart was in routine use on a mountain railway in Bavaria, which suggests Gantt could hardly have been unaware of the form.

What this means for teams today: a schedule picture is not one invention. It is a layered idea, and the part you call by one man's name may be the third or fourth layer.

Gantt's Machine Shop (1890-1916)

A Taylor associate charts what was promised and what was done

Now move to a machine shop around 1900. On the wall is a sheet where each machine is a row and each day a box, and a clerk fills in the quantity a worker actually produced against the quantity the plan called for. This is where Gantt worked. Weaver describes him as an American mechanical engineer who was part of Frederick Taylor's circle, and who first described a version of his charts in a paper printed in the ASME Transactions in 1903, alongside Taylor's Shop Management. The two papers were meant to be read as one production planning and control system. In that paper he says his charts date from 1890 onward, and Weaver names A Graphical Daily Balance in Manufacture (1903) among his earliest publications. For how Taylor's system itself developed, see the history of scientific management.

James Wilson's peer-reviewed centenary paper places the 1903 paper at the center of Taylor's system, because charts were needed to plan the workload of men and machines. Weaver adds a caveat from the same line of research: the "graphical" daily balance was really tabular, since no graph was used in its first form. In 1916 Gantt collected his ideas in Work, Wages and Profits, and Weaver notes that its first charts were record-keeping cards and bonus charts, filled in at the end of each day. The point of those early charts, as Geraldi and Lechter conclude from reading the originals, was to monitor and reduce idle time and to make each worker's output visible.

That is not the chart on your screen. Weaver stresses that Gantt's charts were retrospective and diagnostic, built for batch production and factory throughput, and he argues that Gantt "sought to eliminate" one-off jobs that could not be batched. Geraldi and Lechter, who set out hoping to find early traces of project thinking, report that they found Gantt developed his methods for repetitive routine operations, in all three of his books.

What this means for teams today: the oldest use of the chart was a way to hold promises up against results. If your chart shows only the plan, it is missing the half Gantt cared about.

The Ordnance Years (1917-1919)

A war turns a factory tool into a national one

Imagine a Shipping Board office in 1917 with a wall map bristling with pins and flags, one for each vessel. Clark's book records that the flag-and-pin system could not follow even coastwise ships, and its most serious flaw was that it took no account of time: a flag in a port said nothing about how long the steamer had been there. Card records were tried next and buried the facts in files. At that point, the book says, Gantt was called in, and he worked out ship movement charts that showed what each vessel was doing day by day.

The same preface tells the army side. In 1917, after inspecting factories where Gantt's methods had been installed, General William Crozier, then Chief of Ordnance, retained Gantt as a production consultant, first at the Frankford Arsenal and then, right after the declaration of war, in the Ordnance Department in Washington. Orders had jumped from hundreds to millions, and typed tables could not convey what such numbers meant. During 1918 the charts were used in arsenals, in naval aircraft production, and in the Emergency Fleet and the Shipping Board. Clark describes the Gantt progress chart's defining feature this way: "Work planned and work done are shown in the same space".

The war also exposed the chart's weak point. Weaver reports that after the war Crozier moved on and the Ordnance charts were quietly dropped by officials who preferred to describe what they had done rather than compare it with what could have been done. Gantt returned to private consulting. His book Organizing for Work appeared in 1919, and he died on November 23, 1919. Clark adds that Gantt never tried to patent or copyright his charts and gave samples to anyone who asked.

What this means for teams today: a visible gap between promise and performance is only useful if someone is willing to read it. Weaver's account of the dropped charts is a warning, not a footnote.

Clark Carries the Chart (1919-1930s)

A disciple gives the chart its name and its passport

Wallace Clark was the man who made the chart travel. According to the University of Exeter's biography, Clark (1880-1948) first learned scientific management in night classes, worked for Gantt's consulting firm from 1915 to 1920, including assignments for Remington and the U.S. Shipping Board, and in 1920 left to found his own firm. The book, with appendices by Walter Polakov and Frank Trabold, carries a title page dated 1922. Weaver gives 1923 for the book, and the name "Gantt chart" can be traced to its title. Weaver adds that Gantt himself always named his charts for their purpose, which is why the label belongs to Clark.

The book's boldest sentence is a verdict: the Gantt chart, because it presents facts in their relation to time, is the most notable contribution to the art of management made in this generation. Clark's preface describes uses well beyond munitions, including automobile painting shops, printing plants, textile mills and power plants.

The spread across borders came through Clark's firm. Exeter's biography reports that the book sold widely and was translated into twelve languages. The firm opened offices in Paris and London and later in Warsaw, Athens, Berlin, Prague and Geneva. Clark advised the Polish government on industrial modernisation in 1927, and the biography notes that Lyndall Urwick credited him with helping to lay the foundations of the European productivity revolution. A British edition from Pitman was issued in 1946, with a 1938 copyright according to the Lehigh University Library. Weaver also lists the American Society of Mechanical Engineers' Gantt Medal, established in 1929, as a sign of how fast Gantt's standing grew after his death.

What this means for teams today: ideas travel on books, consultants and a good label. The name stuck because someone wrote the manual, not because the original drawing was the best.

The Name Drift (1930s-1950s)

Any bar chart on a time scale becomes a Gantt chart

This is the dip in the story. Picture a 1940s production-control textbook with a neat horizontal-bar schedule on a page. Weaver says that by the 1930s American managers had dropped most of the sophistication of a true Gantt chart and started calling any time-scaled chart a Gantt chart, and that scholars in the 1950s and 1960s then accepted the name as a synonym for bar chart. Other names existed too. Geraldi and Lechter's review finds the earliest illustration of a project-based Gantt chart in Koepke's 1941 book, still close to Gantt's second version, and says the modern form first appears in Muther's 1944 book, where it is called a schedule chart. Its only real difference from Gantt's second version is that the older one also recorded the reasons for deviation.

That is a precise way to describe what was lost. Gantt's second version of the chart carried codes for why work slipped, such as W for waiting for set-up, M for lack of material, and H for lack of help. The same peer-reviewed review reports on a 1951 experiment cited by MacNeice in which 300 management students faced a complex production planning task: when asked to solve it intuitively only 1 percent could, and when given a Gantt chart all of them produced a solution within 15 minutes. The chart was powerful, but the version that spread dropped the diagnostic half.

What this means for teams today: a label can outlive the idea it was invented for. When a tool has "Gantt" in its menu, ask which Gantt it means.

Networks and Desktops (1957-present)

Dependency logic arrives, and then the personal computer

The chart's next test came from networks. In 1957 to 1959 the critical path method and PERT were built to handle what bars could not, and today you can read about them in the critical path method and the PERT chart. The expectation was that the new tools would push the bar chart aside. According to Geraldi and Lechter, the opposite happened: the network tools did not supersede the Gantt chart, its use increased, and the tools were used in combination, with the outcome displayed as a Gantt chart. They date the surge of interest in project use to the mid-1960s, and cite Wilson for the point that personal-computer packages later revived the chart. Weaver observes that the planned-versus-actual information on Gantt's charts resembles what earned value management formalized later.

Then came the desktop. The Microsoft Project Users Group dates the first release of the product, version 1, to 1984. It says Microsoft bought all rights in 1985 and released later versions for DOS, and it describes version 3.0 in 1990 as a significant upgrade that ran on Windows 3.0. Geraldi and Lechter note that popular tools such as MS Project and Primavera use the Gantt chart as the central platform for planning and managing schedules. A 2008 survey they cite of 750 project managers ranked it fourth out of 70 tools and techniques.

The newest layer is critique. Geraldi and Lechter argue that the chart carries six principles from scientific management: it is time-focused, objective, deterministic, analytic, accountable and sequential. They say those principles are not valid for all projects and that the chart can encourage a false sense of certainty. They do not call for dropping it; they ask for a contextual and reflective use. They also say processes that loop, such as software work with testing cycles, cannot be adequately represented in a Gantt chart, because it is not known beforehand how often a loop will repeat. That helps explain why teams guided by the Agile Manifesto tend to use the chart at program level and not for each iteration. A study they cite, by Yakura, found the chart useful as a boundary object because it makes time concrete and negotiable across groups.

What this means for teams today: put work that needs a decomposed scope behind a work breakdown structure and use the chart for sequence and deadlines. Keep loops, discovery and uncertainty somewhere else.

Key People

Key Facts

• Priestley's 1765 chart placed about 2,000 names on a scale where distance stood for years.
• Gantt first described his charts in the 1903 ASME Transactions, saying they dated from 1890.
• Clark's book carries a title page dated 1922, and Exeter's biography says it was translated into twelve languages.
• Gantt died on November 23, 1919, before the name "Gantt chart" appeared.
• The Microsoft Project Users Group dates Microsoft Project version 1 to 1984.
• A 2012 review finds that CPM and PERT did not displace the Gantt chart; use increased.

The Pattern Behind the History

This is our synthesis, not published research. Five points repeat in the chart's history:

• The picture comes first. Priestley and Playfair drew time before anyone scheduled with it.
• The purpose migrates. A tool for judging promises against output became a tool for drawing plans.
• The name outlives the design. Clark's title and the 1930s habit of calling any bar chart a Gantt chart left the label attached to something simpler.
• Rivals get absorbed. CPM and PERT added logic, and the chart stayed as the view of their results.
• Software freezes the form. Once the desktop made one layout easy, that layout became the default for every kind of project.

What It Teaches Teams Today

• Show plan next to actual. Gantt's original idea was the gap between the two, so track both.
• Record why work slipped. His codes for waiting, material and help are a cheap way to find a recurring cause.
• Know which Gantt you are using. A forward-drawn schedule and a production record answer different questions.
• Match the tool to the uncertainty. Geraldi and Lechter's test is a good start: is the work time-driven, describable, routine, divisible and sequential? If not, lean on something else.
• Trace your own tools. The chart's story, like the project management timeline and who invented project management, shows how a method's meaning drifts once it spreads. For the broader arc, see the evolution of project management methodologies.