What is farm management?

Farm management is the work of running a farm as a business, and the discipline has organized itself around functions since Henri Fayol named them in 1916. The shorthand for it today names four. Planning decides what to produce, at what scale, and with what resources. Organizing arranges who does what, and with which machine. Directing puts the crew to work, day after day. Controlling checks whether what happened matches what was decided, and acts on the difference. The four together are management. No one of them alone is.

This page walks through all four, one at a time, and then shows what Rurivia does inside each of them. All four functions are the company's territory, not one of them in place of the other three. What the company brings that is different is not a function, it is a discipline: closing the loop, which comes further down, marked as a position.

Where the definition comes from

Henri Fayol wrote the definition the field still uses, in a paper published in French in 1916. His sentence is short enough to quote whole:

To manage is to forecast and plan, to organize, to command, to co-ordinate and to control.

Henri Fayol, Administration industrielle et générale, 1916, translated by Constance Storrs, 1949

Five verbs in Fayol, and current textbooks consolidate them into planning, organizing, leading and controlling, with commanding and coordinating folded into leading. The lists vary in number, between four and five, but none of them loses a function along the way. Planning, organizing, directing and controlling appear in every one.

Fayol's own title carries a wrinkle worth knowing, because it explains why management and administration get used for the same work. The French book is called Administration. Its first English translation, in 1930, kept that word and came out as Industrial and General Administration. The 1949 translation that became standard changed it to General and Industrial Management. Same book, same author, two different words on the cover, decided by translators nineteen years apart.

Oliver Sheldon had already tried to separate the two words in 1923, and his split is the one most people are reaching for when they use both:

Administration is the function in industry concerned in the determination of the corporate policy, the co-ordination of finance, production and distribution, the settlement of the compass of the organization, and the ultimate control of the executive. Management proper is the function in industry concerned in the execution of policy, within the limits set up by administration.

Oliver Sheldon, The Philosophy of Management, 1923

Farm management as a taught subject starts in the same period. George Warren began teaching it at Cornell in 1907, and the textbook he published in 1913 sold over 90,000 copies and set the standard for teaching farm management for much of the ensuing two decades. What Warren taught was broad, and the field stayed broad: choosing enterprises, sizing the operation, arranging rotations, financing it, carrying the risk. The definition the FAO adopts is deliberately wide: the process by which resources and situations are manipulated over time by the manager, with less than full information, in pursuit of goals, a definition first proposed by Dillon in 1980 and adopted by the FAO.

Planning sets the direction before the season starts

Planning is the function that chooses, before the result is known, what the farm will do: which enterprise to run, at what scale, in what rotation, with what money, and carrying what risk. It is the oldest one on Fayol's list and the one George Warren was already teaching: choosing among competing uses of the same land, the same labor and the same capital, which never stretch to cover everything. A plan is a choice among alternatives, made and written down while the outcome is still open.

In practice, planning takes the shape of concrete things: the crop plan, the cycle's budget, the decision to lease or buy, the investment plan, the succession plan. Each one fixes an intended result, and that intended result is the standard everything that comes later gets compared against. That is why planning comes first. You can organize, direct and check an operation nobody decided the direction of, but you cannot tell whether it got there.

Organizing arranges the resources and the people

Organizing is arranging the resources and the people so the plan can happen. Who answers for which front, which machine goes to which field, how the work divides between the permanent crew and the seasonal one, who decides what when the owner is not on the farm. Fayol treated it as the second function, and Max Weber added the part a family farm most needs to hear: authority sits in the role, not in the person. Whoever holds the role answers for it, and the role outlasts the person who held it.

On a farm, organizing is what separates an operation that depends on one person's head from one that survives that person's absence. An org chart, even a simple one, a description of who does what, a rule of who signs off on what: these are the organizing function put on paper. The small operation organizes informally and the large one formalizes it, but both organize.

Directing puts the crew to work, day after day

Directing is putting people to work and keeping them aligned to the plan, day after day. Fayol called it commanding and coordinating, and today's textbooks fold both into leading. It is the function that happens in the morning, in the talk before the crew heads out, and through the day, when the plan meets what the field actually presents. Mary Parker Follett summed the function up in a line the discipline has never bettered: management is the art of getting things done through people.

Researchers who watched managers at work, Henry Mintzberg onward, found that the real day of someone directing is fragmented, verbal and interrupted, not the orderly command of the manuals. Anyone who runs a farm recognizes the description. Directing well is not giving more orders. It is making sure the crew knows what the goal is and what to do when the plan does not fit the day.

Controlling checks what happened and acts on the difference

Controlling, in Fayol's definition, is making sure everything happens according to what was decided, and acting when it does not. It is not a report and it is not a scorecard. It is the function that compares what was supposed to happen against what did. Robert Anthony, who founded the study of this as a field in its own right at Harvard in 1965, defined it as the process by which managers assure that resources are obtained and used effectively and efficiently in the accomplishment of the organization's objectives. Notice what the definition requires before anything can be checked at all: objectives stated in advance, which is exactly what the planning function delivers. A number with nothing to compare it against is not control. It is a record.

Current textbooks break that comparison into four steps: establish standards, measure performance, compare performance to standards, and take corrective action. Put into the vocabulary of a farm rather than a factory, they look like this:

This is where the most repeated and most mistaken sentence in management lives. "If you can't measure it, you can't manage it" is credited to Peter Drucker, who never said it: the institute that holds his archive published the correction itself. Deming, the other name it gets pinned on, was arguing the opposite, and his institute treats the line as a myth. The phrasing everyone repeats traces back to a 2008 newspaper column, and it has a second half almost nobody quotes: what gets measured gets managed, even when measuring it is pointless, and even when doing so harms the organization's purpose. This matters because the truncated version is what sells dashboards. If measuring were managing, a screen full of numbers would be a finished product. Under the actual definition, that screen is the middle of the road: someone still has to compare and act.

Closing the loop, in any of the four

Here the company's position begins, and it is marked as a position. All four functions are the company's territory. What it brings that is different is not one of them, it is a discipline that holds for all four: for whatever a function produces, declare the intended result, record what actually happened, find the gap while there is still time to act, and close it out with a named owner and a due date. It is the loop almost no farm and almost no software closes, and it is not only in controlling that it is left open. It is left open in the plan nobody revisits, in the org chart that went stale, in the check that flagged the variance and stopped there.

The loop is old and it was not invented here. Shewhart described it for industrial quality in the 1930s, and Deming carried it into management practice. From the farm side, research reached nearly the same shape: watching working farmers, Öhlmér, Olson and Brehmer described the farmer's decision as a phased process and found that farmers prefer to head off and correct early rather than evaluate after harvest. The 1961 study by Johnson and colleagues, which that work revisits, had already read six decision steps in the farmer: problem definition, observation, analysis, decision, action, and responsibility bearing.

Two independent routes to the same loop are a better argument for it than either one alone. And the preference for correcting early is a design requirement, not a curiosity: a variance that surfaces only at the end of the cycle has missed the window in which anyone could have acted, and the farmer who ignores the end-of-season report is behaving rationally.

The common impression is that setting the first standard is a big project the farm will get to when there is time. Most of the time it is not: much of the standard is already written, dated, and not by the farm. The machine's manual sets the service interval in hours, the label sets the rate and the pre-harvest interval, the permit sets the day it expires. Setting the standard, to begin with, is less about writing than about gathering what already exists and putting it next to what happened. And a claim is worth more when a counterparty's document backs it, an invoice, a permit, a service record, than when it rests on memory alone. What the company does not promise is that the bank, the buyer or the inspector will accept the result: acceptance is their decision, and a company that promises acceptance is promising what it does not control.

The six axes a farm gets managed along

The four functions say how management works. The six axes say what about. Any decision on a farm falls into one of them, and that is how this library is organized.

Planning is where the farm decides its direction: goals, budget, mission, risk analysis, succession. It is the axis every other one comes out of, because it is where the intended result gets chosen.

Production is the field work and the machines: the window for each operation, the rate, the sequence, fleet maintenance, the soil. It is where most of a farm's technical knowledge already lives.

People is the crew: hiring, training, organizing who does what, directing the day to day, and the legal and safety obligations that come with having people at work. It is the axis with the heaviest documentary weight and the heaviest privacy duties.

Marketing is turning production into revenue: when and how to sell, contracts, the cooperative, the farm's own pricing policy. Checking whether you followed your own rule is the company's ground. Telling you when to sell is advice about the price of an asset, and this company does not give it.

Finance is the money: cost by enterprise, cash flow, debt, tax, what a cycle left behind. It is the axis that says whether the rest was worth it.

Sustainability is the license to operate today and tomorrow: soil conservation, environmental permits, traceable origin, packaging disposal. Increasingly it is also what a buyer requires before closing a deal.

What farm management is not

Two different exclusions get confused with each other, and they are not the same kind of thing. One is about subject matter and is permanent: it is not farm management. The other is false: it is farm management, it is Rurivia's territory, and the shorthand definition sometimes leaves it out by mistake.

The left column is a statement about the field and it does not change. The right column is also farm management, and someone reading the shorthand sometimes excludes it by mistake. Worth being precise about the left one, though, because the shorthand invites a misreading. The exclusion is technical production, not agronomy as a discipline and not agronomists as readers. Farm administration is taught inside agronomy programs, and a large share of the people managing farms trained as agronomists.

One more thing this page does not do, and it is a promise the company refuses to make. Rurivia does not promise better yield, a better price, or a percentage of cost saved. Rain and the market decide part of the result and neither one answers the phone, and a company that charges for outcomes it does not control is charging for weather. The manifesto makes that argument at length.

And one exclusion that is not on the list, because it is a misreading rather than a limit: the size of the operation. Management is not what a farm starts needing once it grows. Where the room for error is narrow the requirement is larger, not smaller, because the mistake a big operation absorbs into the year's result a small one absorbs nowhere. What changes with size is the shape of the instrument, not the need for it.

Where to start, depending on what you already have

If nothing is written down anywhere, start with planning: what you would decide today, if someone asked. The planning axis takes that on one decision at a time, and none of it asks you to buy anything.

If the plan exists but nobody is quite sure who answers for what, the place to start is organizing: putting on paper who does what. And if the standard is already on the shelf, in the manual, the label, the permit folder, the place to start is comparing what was done against it. The finance axis opens with the fuel invoice against the hour meter, a check that runs on records the farm already keeps.

If you would rather read first, the library is organized along the six axes above, and every technical claim in it points to a document you can open yourself. Each piece carries its sources, what it covers, what it deliberately leaves out, and the date it was last checked against them.

If you would rather run one number first, the calculators do the arithmetic for you, in the browser, and nothing you type into them leaves your device. Each one is paired with the article that explains the method behind it.

Closing the loop in one domain, once, is something most operations never do in any domain. Worth noticing how narrow that first win is, and how little of it depends on buying anything.