Where the Idea of Productivity Came From

Turn this article into takeaways for your work.

Each assistant summarizes the article only for you and suggests best practices for your work.

A temple needed to know how much barley had gone out. A monastery needed its hours kept. A French court needed to know why harvests were failing. A factory owner needed to know who was fast.

The problem a society faced in each period shaped what "more output" was taken to mean. People tracked grain, hours and labor for more than five thousand years before anyone had a word for what they were tracking. The concept of productivity, output set against the effort that produced it, took shape in eighteenth-century Europe. The Physiocrats and then Adam Smith asked where a nation's wealth really came from. Merriam-Webster dates the first known use of the word itself to 1808. It became a number managers and governments watched only in the twentieth century.

That gap between practice and idea is the story here. This article follows the concept and the word, not a year-by-year chronology. For the dated sequence, see the productivity timeline, and for how the idea got turned into statistics, see the history of productivity measurement. The full eight-era overview sits in the history of productivity.

Timeline at a Glance

Year Milestone Why It Mattered
c. 3300 BCE Earliest tablets in southern Mesopotamia record economic information in pictographs and numerals Output and stores become things a society writes down
c. 3100-2900 BCE A Sumerian tablet most likely documents grain distributed by a large temple The ledger becomes an administrative habit
Old Kingdom, Khufu's 26th year Merer's logbook records a crew hauling limestone to the pyramid A work crew's days are scheduled and written down
Reign of Amenhotep III A calcite water clock from Karnak carries hour marks by season and month Time is divided into units a clock can show
Sixth century CE The Rule of St Benedict sets fixed hours for prayer, labor and reading A daily schedule becomes written law for a community
Mid-1700s French Physiocrats treat farming as the sole source of a country's wealth Economists start asking what makes output grow
1776 Adam Smith publishes The Wealth of Nations Division of labor explains rising output; labor is sorted into productive and unproductive
1808 First known use of "productivity" The word exists, though few people use it for decades
1817 Ricardo's Principles of Political Economy puts distribution at the center The question shifts from how much to who gets it
1898 BLS releases "Hand and Machine Labor" on 60 manufacturing industries Output per worker becomes a public question about jobs
1911 Taylor's Principles of Scientific Management ties prosperity to productivity The term moves from economics into management
1940 Congress authorizes BLS to run continuing productivity studies A government starts watching the number
1959 BLS publishes labor productivity for the total private economy, covering 1909-58 Productivity becomes a national scoreboard
1999 Drucker argues knowledge-worker productivity is management's next task The concept stretches to work with no clear unit
April 2023 An NBER paper studies 5,179 support agents using an AI assistant The idea is applied to work done with machine help

Ledgers and Hours (c. 3300 BCE-1700s)

People count and schedule work long before they name it

Picture a scribe in southern Mesopotamia pressing numerals into wet clay to record what a temple had handed out. The Metropolitan Museum explains that the earliest tablets, probably around 3300 BCE, recorded economic information with pictographs and numerals, and that a later Sumerian tablet from around 3100 to 2900 BCE most likely documents grain distributed by a large temple. Nothing in those tablets compares output to effort. They count. But counting is the precondition for every productivity idea that follows: you cannot ask what a crew produced until someone writes down what it produced.

Egypt shows the next step, which is scheduling effort. The Diary of Merer, found at Wadi al-Jarf, is dated to the 26th year of Khufu's reign and describes Merer and his crew moving limestone blocks from the Tura quarries to the Khufu pyramid. A crew leader was running a recorded schedule for a defined job, and nobody was calling it management.

Time itself had to be divided before it could be budgeted. A calcite vessel from Karnak, made in the reign of Amenhotep III, is an outflow water clock whose interior carries twelve columns of hour marks, each labeled by season and month. Marking hours by season and month is not our clock, but it is the same instinct: turn the passing of time into units a person can read off a device.

The clearest early rulebook for a working day comes from a monastery. The Rule of St Benedict, attributed to the Abbot of Monte Cassino in the sixth century, sets seven day Offices plus a night one, and declares that "Idleness is the enemy of the soul." From Easter to October, the monks leave Prime and labor until about the fourth hour, read from the fourth to the sixth, rest after the midday meal, and work again until Vespers. The schedule is built around time, not output. A monk is "productive" if he keeps the hours.

These were precursors, not the concept. Drucker made the point bluntly in 1999: it was axiomatic throughout history that workers could produce more only by working harder or longer. Societies measured stores and scheduled hours. Almost nobody asked how to get more from the same hour.

What it means for teams today: a ledger tells you what happened and a schedule tells you when. Neither tells you whether the work was worth doing. If your team's idea of productivity is "everyone follows the calendar," you are running a Benedictine system, which is a fine thing to know about yourself.

The Net Product (mid-1700s-1776)

French thinkers ask where a nation's wealth comes from

By the middle of the eighteenth century, a group of French writers wanted a theory of wealth, and they found it in the soil. Adam Smith later summarized their view: agriculture is the sole source of the revenue and wealth of every country. These are the Physiocrats, and Smith singled out Quesnay, a physician, as a prominent voice.

Their scheme divided society into three classes. Landowners held the land, cultivators received the name "productive class," and, in Smith's words, artificers, manufacturers and merchants were given the "humiliating appellation" of the barren or unproductive class. The logic was that farming yields a surplus beyond its costs while a craftsman only transforms materials someone else grew.

Smith thought they were wrong about manufacturing and said so at length. His account also explains the setting: French policy had favored the industry of the towns over that of the country, and agriculture had been left depressed. The Physiocrats bent the rod the other way, in his phrase.

Still, they did something that mattered for the history of the concept. They treated wealth as something produced, with sources that could be identified and compared. "Productive" became a label with real stakes, a sorting of workers into those who add to national wealth and those who do not. That sorting problem did not go away.

What it means for teams today: every organization still sorts its work into "productive" and "overhead," and the sorting is usually as crude as the Physiocrats'. Support, compliance and coordination often get labeled unproductive because their output is harder to see, which is a reason to define output carefully before you cut anything.

The Word Arrives (1776-1817)

Smith redraws productive labor, and the word itself appears

In 1776, a Scottish moral philosopher published a book that opened with a pin factory. Adam Smith's Wealth of Nations argues that the greatest improvements in the "productive powers of labour" came from the division of labour. The book's opening chapters ask why one worker making whole pins produces so little and ten specialized workers produce so much, and the answer is arrangement, not harder effort. For a deeper look at the pin example, our evolution of productivity article covers the same ground from the economics side.

Smith also redefined the Physiocrats' sorting in Book II. Labor that adds to the value of the thing it works on he called productive, and labor whose services perish in the instant of their performance he called unproductive. He put menial servants in that second group, along with the sovereign, the army and the navy. He added that such labor "has its value" and deserves its reward, so the label described what a service leaves behind, not whether it matters. The definition is narrow by modern standards, since it leaves out most service work, but the move was lasting: productivity became a property of work that you could reason about.

David Ricardo, writing in 1817, changed the question. His Preface calls the laws governing how a nation's produce is divided among landowners, capitalists and laborers the "principal problem in Political Economy". For Smith, the puzzle was how output grows. For Ricardo, it was who ends up with it. Both questions remain in every argument about whether productivity gains reach wages.

The word arrived in between. Merriam-Webster lists the first known use of "productivity" in 1808, and defines it first as the quality or state of being productive. The word began as a general quality of any productive thing, a field or a mine or a worker, and it took more than a century to become the economist's ratio of output to input. Drucker, writing in 1999, observed that the term itself is barely fifty years old in its modern sense, and argued that productivity as a measurable property of a worker "did not exist" in nineteenth-century economics. Both can be true: the word existed from 1808, while the idea of treating a worker's output per hour as a thing to improve was still missing.

What it means for teams today: Smith's pins are a lesson about design. Before asking people to produce more, ask how the work is arranged. And watch Ricardo's question: if your team's output rises and nobody can say who captured the gain, the next round of effort will be harder to get.

The Measured Worker (1898-1970s)

Governments and managers turn output per hour into a number

In 1898, the U.S. Bureau of Labor Statistics released a study of 60 manufacturing industries called "Hand and Machine Labor", prompted by congressional concern that machines were displacing human labor. It documented the labor saved by mechanization across the last half of the nineteenth century. Notice the framing. Productivity entered government record as a worry about jobs, not as a goal.

Inside factories, the concept got a manager's version. Frederick Winslow Taylor's 1911 book, The Principles of Scientific Management, argues that "maximum prosperity can exist only as the result of maximum productivity." It was a bold statement, and it moved the word from economists' pages onto the shop floor. Taylor wrote about the men and machines of an establishment turning out the largest possible output. Drucker later called him the first person to work as a manual worker and then study manual work, and credited the decade after Taylor with the start of a rise in manual-worker productivity of about 3% a year, compounded. Our scientific management article covers the method and its critics, and who is the father of modern management sorts out the rival claims.

By the 1920s, BLS reports that productivity was an issue in labor-management relations because it bore on wage adjustments. During the Depression, concern grew over the effects of productivity and technological change on employment, and in 1935 BLS applied to the Works Progress Administration for funds to study productivity in 50 industries. In 1940, Congress authorized BLS to begin continuing studies. During the war, the program turned to the most efficient use of scarce labor, with studies of synthetic rubber and shipbuilding. In 1959, BLS published labor productivity for the total private economy covering 1909 to 1958.

The new problem was that "output per hour" fit a factory and fit a government statistician, but it fit a clerk poorly and an engineer worse. The number came easily for work you could count.

What it means for teams today: a productivity number is a decision about what counts. Anything easy to count will get managed first, and the rest will quietly lose attention.

The Self-Managed Worker (1980s-2010s)

Productivity moves from the factory into the individual

In 1999, Peter Drucker wrote that the most important contribution management needed to make in the twenty-first century was to increase the productivity of knowledge work and knowledge workers. He credited management's twentieth-century achievement to a fifty-fold increase in the productivity of the manual worker in manufacturing.

His list of six factors reads like a rewrite of the concept. The first is a question: "What is the task?" In manual work, he wrote, the task is always given, and the question is how to do it. In knowledge work, the task has to be defined. He added that knowledge workers have to manage themselves and need autonomy. Productivity had stopped being a property of a process that a supervisor could measure. It was now something each person had to own.

The popular books followed that shift. Stephen Covey's The 7 Habits of Highly Effective People (1989) argued for putting important work ahead of urgent work, an idea we cover in the Eisenhower matrix, and David Allen's Getting Things Done (2001) gave workers a way to get commitments out of their heads, which is the subject of getting things done. The unit of analysis had moved from the nation to the plant to the individual's attention.

The new problem was that personal systems cannot fix shared causes. A perfect to-do list does not remove a pointless meeting, which is the argument in why personal productivity fails.

What it means for teams today: ask Drucker's question out loud. If a team cannot say what the task is, the problem is clarity, not speed, and no app will fix it.

The Machine Collaborator (2020s-present)

Software drafts the work, and the definition stretches again

The newest chapter tests the concept's oldest assumption: that effort is human. In an April 2023 NBER paper, Erik Brynjolfsson, Danielle Li and Lindsey Raymond studied 5,179 customer support agents after an AI assistant was introduced. Issues resolved per hour rose 14% on average and 34% for novice and low-skilled workers, with minimal impact on experienced workers.

The study is useful partly because it measures the old quantity, output per hour, in a new setting. But it also reopens the question the Physiocrats and Smith each answered differently. When a tool drafts the first version, what is the worker's output, and what counts as the effort? The word has stretched before, from fields to factories to knowledge work, and each stretch exposed definitions that no longer fit.

What it means for teams today: define the output before you measure the assistant. A faster first draft is only a gain if the work around it can absorb it.

Key People

Name Role Contribution Year
Merer Egyptian crew leader Kept a logbook of limestone hauls to the Khufu pyramid Khufu's 26th year
Benedict of Nursia Abbot of Monte Cassino Wrote the Rule that fixed a community's hours of prayer, labor and reading 6th century CE
Francois Quesnay Physician and Physiocrat Physiocrat discussed by Smith, whose school treated farming as the source of a country's wealth Mid-1700s
Adam Smith Moral philosopher Tied rising output to division of labour and split labor into productive and unproductive 1776
David Ricardo Economist Named distribution the principal problem of political economy 1817
Frederick W. Taylor Engineer and consultant Linked prosperity to productivity inside the firm 1911
Peter Drucker Management writer Pushed the concept to knowledge work and self-management 1999
Erik Brynjolfsson, Danielle Li and Lindsey Raymond Economists Measured an AI assistant's effect on support agents 2023

Key Facts

Key Facts: Origins of the Idea of Productivity

The Pattern Behind the History

Here is our own synthesis, not published research. We call it Practice First, Name Later, and it has four parts.

  1. Practice precedes the name. Scribes, crew leaders and abbots managed output and time for millennia before the word existed.
  2. Counting comes before comparing. Societies recorded what was made long before anyone divided it by what was spent.
  3. Each definition answers its era's fear. The Physiocrats reacted to France's depressed agriculture, Smith wanted to explain growth, Ricardo worried about division, and the BLS worried about jobs.
  4. The input keeps changing. Land, then labor hours, then attention, now machine-assisted work.

What It Teaches Teams Today

Treat "productivity" as a definition your team has to write down, not a fact it can look up. Name the output, name the input, and notice which fear is steering the answer. A team that counts calls handled and a team that counts decisions made have chosen different definitions, whether or not they said so.

Check what your current schedule actually rewards. Benedict's monks were measured by keeping the hours, and many offices still are. Then ask Drucker's question about each recurring piece of work: what is the task? If the answer is unclear, clarity is the productivity problem to fix first.

The history also says to be wary of any single number. Taylor's output per hour fit the factory it came from, and the concept had to be stretched every time work changed. The next stretch is already here. For the eras after this origin story, the history of productivity picks up where this article ends. To see how the concept sits inside the broader story of organizations, read the history of management, and for a plain definition, start with what productivity is.

The concept is older than its name and younger than most of the work it describes. Knowing which parts of your own definition were inherited from a temple ledger, a monastic bell or a factory stopwatch is a good start toward writing a better one.

About the author

Victor Hoang

Victor Hoang

Co-Founder, Rework.com

Victor Hoang is Co-Founder and CMO of Rework. He spent 12+ years scaling B2B SaaS growth, building a lead engine that generated over 1 million leads and $10M+ in annual recurring revenue. Today he builds AI agents and MCP servers into Rework's products to empower customers across growth and operations. He writes about what actually works.