In agriculture, everyone likes to talk about the weather because it’s a safe topic. Weather is convenient — it’s beyond our control, and there’s always something to complain about. But in our work with clients, it quickly became clear that weather isn’t the cause of problems. It’s the moment when problems show themselves.
As long as a farm operates on a small scale, many things “somehow hold together.” A few dozen hectares, a handful of machines, a few people. Decisions are made over morning coffee. Everyone does a bit of everything. If something breaks down, you can still fix it manually. The problem starts when the scale grows. Fields are acquired gradually, often without a single clear turning point. “In the meantime,” the farm grows to several hundred or even several thousand hectares. There are more and more machines. More operators. And the way the farm is managed… stays exactly the same. The same habits. The same methods that used to work. Except now… somehow they don’t.
It was in exactly this context while working with our client from the food industry, a company whose entire value starts in the field — that a sentence was said which set the direction for the whole project:
“We still operate as if we were a small farm.”
That sentence pinpointed the problem with precision. On a small farm, everyone knows and does everything. On a large one, you need specialization: someone plans, someone operates the machine, someone is responsible for reporting and preparing the work. You need meeting rhythms, a clear flow of information, and visualization —because with dozens of machines, improvisation quickly turns into exhausting chaos. On a small farm, a tractor and a few machines are enough. On a large one, you must consciously manage the machinery fleet: servicing, rental, costs, availability, and reliability.
And here a key perspective appears. When you look at agriculture through “Lean glasses,” the similarities to industry are striking. There are people. There are machines. There is a place where value is created. The difference is the scale of space. In a factory, machines move in centimeters and meters. In agriculture — in kilometers. The rest of the mechanisms are similar: planning, standards, reliability, flow, eliminating waste. Except that in the field, mistakes cost more and learning takes longer. Because one season is one experiment. And there’s no way to “try again” — yes, there will be another chance… in a year.
When Bartosz Wnuk, a consultant at 4Results Growth&Excellence, started this project, the goal was clearly defined: to check whether — and how — Lean thinking can be realistically applied to agriculture and large-scale farm management.
In this story, we build a broader narrative around the “triangle” of operator – machine – field. Three elements that, in large-scale agriculture, cannot be considered separately — because only their interdependence and cooperation determine the outcome of the whole system. Each corner of this triangle has its own specificity:
A machine, by itself, does not create value. It is a tool that enables value — provided it is reliable, available when needed, and matched to the type of work. The operator is not a “labor cost,” but the key — the only conscious, thinking element of this system. They see the field, make hundreds of micro-decisions, and are the first to notice irregularities. The field, in turn, is where value is actually created. A priceless resource that produces yield.
Around each corner of this triangle there are supporting areas. Maintenance supports the machine by ensuring reliability and readiness. Competency development supports the operator, giving them tools, knowledge, and confidence. And management ties these elements together and coordinates their work as one whole.
The field: where value is created
Moving to the project itself, it was clear to us that we couldn’t start anywhere else but the field. Fields — often geographically dispersed — cover huge areas, but that doesn’t change the fact that they can and should be treated as a deliberately designed workplace. Exactly like a production line in a factory. With one difference: instead of meters, we have kilometers; instead of a hall — changing conditions; and instead of constant lighting — often work after dark.
That’s why the first step was to ask a very concrete question: when an operator enters the field, do they have the conditions to work confidently, quickly, accurately, and safely — even at night and during short weather windows?
That question immediately revealed the scale of losses that result from lack of preparation. So we began to treat the field as a visual workplace — an environment designed for both the human and the machine.
The first layer was physical: a field map with marked risk elements. Poles, wells, muddy areas, depressions in the terrain, critical entrances, water intake points. Everything named, marked, and organized so the operator wouldn’t have to rely on memory or the experience of one specific person. Information was meant to be available systemically — not “in someone’s head.” It quickly turned out, however, that this still wasn’t enough.
More and more work happens after dark — not only harvests, but also spraying, where the time of day determines the effectiveness of the treatment. Night stopped being an exception. That forced another layer of thinking: what does this value-creating workplace look like at night? The answer brought simple but extremely effective solutions: reflective markers in key points of the field, visible from a long distance in the headlights. Thanks to this, the operator can “read the field” before entering a critical area. Of course, supported by GPS and onboard systems — but this visual anchoring in the terrain reduced decision fatigue.
The next layer concerned movement in the field — designing the optimal driving path. When a sprayer has a working width of around thirty meters — like a mid-size passenger plane — every unnecessary turn generates loss: fuel, time, and concentration. The field stopped being treated as a surface to simply “drive around.” It began to be treated like a route that can and should be designed.
In parallel, we tackled what in Lean determines results — though it rarely looks impressive: off-season preparation. Picking stones. Trimming branches. Hardening access roads. Repairing roads for heavy machinery and transport. Organizing water intake points. These are actions whose value becomes visible only when a critical moment arrives.
This is exactly where decisions about eliminating bottlenecks appeared. Example: water throughput. If the water supply cannot deliver the required volume quickly, and the sprayer needs tens of thousands of liters, the problem lies in the system. The solution turned out to be an intermediate tank and a high-capacity pump — fast filling when every minute matters, and calm replenishment in the background when pressure is low.
The same applied to the logistics of fertilizers and crop protection products. Instead of last-minute deliveries, the thinking shifted to intermediate storage points and operational readiness. Material prepared 2–3 days in advance, in a location that shortens travel time and minimizes the risk of losing a weather window.
The whole picture was completed by another layer of the field map — precision agriculture. Measurements of nutrient content in dozens or hundreds of points across the field, data transferred into systems and used for variable-rate fertilization. This helped reduce over-fertilization, but above all, it enabled a deliberate search for the optimal point between cost and effect.
The machine: reliability instead of improvisation
Once the field began to be treated as a designed workplace, it quickly became clear that this was only one part of the puzzle. Even the best-prepared field won’t protect the system when the machine becomes the bottleneck. And in agriculture, neglected machines break down at exactly the worst possible time: in the middle of a short weather window, at night, during a critical operation.
In conversations with the client’s team, the same narrative kept returning: a breakdown as a “random event” — something beyond our influence. The problem is that at the scale of several or several dozen thousand hectares, this narrative stops being true. One failure of a key machine triggers a chain reaction: downtime, frantic decisions, plan changes, pressure on operators, and losses that cannot be recovered within the season.
That’s why the second corner of the triangle became the machine treated as a system element. The starting question was: do we truly know what condition our machines are in before they enter the field?
This question opened a completely different approach to maintenance. Instead of reacting after the fact, we started building routines of autonomous maintenance. Simple, repeatable actions: daily cleaning, washing after returning from the field, basic checks, lubrication, quick detection of looseness and leaks. Collaboration between operators and maintenance. In parallel, inspections, repairs, and schedules became part of seasonal preparation. In agriculture, the cost of machine downtime at the wrong moment is incomparably higher than the cost of planned service — especially when one machine supports hundreds or thousands of hectares.
We also found that “maintaining the machine” alone is still not enough. What became critical was response time to a field failure. Hence decisions about mobile service teams and how to prepare them. What should a “workshop on wheels” look like? How to arrange tools so time isn’t wasted searching? How to apply 5S logic in a service vehicle working in the field?
At one point, a very practical question was asked: if we know which parts wear out most often, why should the operator wait for them? That led to the concept of critical parts assigned to each machine — prepared in advance, available immediately, without calls or driving around. A basic set of components that, if necessary, the operator can replace themselves, with clear instructions. During harvest season, machine uptime becomes an absolutely priceless resource.
At the same time, the connection between machine and operator became very clear. We began to look at the operator’s cab as a visual workstation: is visibility sufficient, are controls arranged logically, is everything needed where it should be? In practice, this also meant improving the cab for specific use — through the lens of the person who often spends many hours a day inside.
Another crucial topic was machine effectiveness depending on field characteristics. The same machine can be highly efficient on a large, straight, flat field — and completely different on a small, irregular one with difficult access, turns, or slope. The nominal performance exists only on paper; in reality, effectiveness always depends on the context in which the machine operates.
So instead of comparing results, we began designing realistic performance standards tied directly to the field’s difficulty class. For the client, this meant defining several field categories and assigning expected machine efficiency to each. This made it possible to measure plan execution — and to analyze deviations meaningfully: was the cause weather, a breakdown, logistics, or the way work was done?
Visualizing this data allowed the team to pursue clear targets instead of explaining failures. Efficiency stopped being subjective and became part of conscious system management.
This also brought in fuel consumption as an element of shared learning. When is it worth working shallower because the cost–effect ratio is better? When does deeper cultivation truly make sense? How to separate the impact of weather from operational decisions? Those conversations started only when the data was embedded in the context of field, machine, and work method.
The operator: the person who sees the most
The third corner of the triangle is the operator. And it was here that the change turned out to be the deepest — because it touched the way we think about people.
In modern agriculture, an operator is increasingly a young person who navigates GPS systems, onboard computers, maps, apps, and data with ease. They drive smoothly, understand technology, and can read the field. But at the same time, they are someone who no longer wants to work in constant firefighting mode or 12+ hour shifts. A real tension emerged: rising operational requirements on one hand, and generational change with completely different expectations toward work on the other.
The first thing that was clearly visible was significant differences in operators’ competencies and experience. Some operated only basic equipment; others could smoothly switch between different types of machines, respond to changing conditions, and support less experienced colleagues. Instead of treating this as “just the way it is,” a key question was asked: do we consciously manage operators’ competencies? Do we support their development and help them become the best version of themselves?
That’s how work with competency matrices began — showing who can operate which equipment, under what conditions, and with what level of independence. The client distinguished three levels: an operator for basic machines, a multi-machine operator (for several types of equipment), and a lead operator — someone able to safely and effectively run almost any machine on the farm.
This opened the door to real interchangeability, crucial for shift and night work—and to planned skill development. External training began to be supplemented by learning in practice: joint exercises in the field, testing machine settings before real chemicals or material were used.
In parallel, operator work standards were organized:
“How to prepare the machine before leaving”
“How to hand it over after the shift”
“How to pass information about equipment condition, field status, and potential issues”
In manufacturing, a shift handover standard is everyday reality. In agriculture, it often functioned “by feel.” And “feel” doesn’t scale well.
The thinking about operator performance also changed. It stopped being about “who drives faster.” Because at a certain point, higher speed means higher losses — for example, good grain thrown out behind the combine. The concept of optimal speed and work quality emerged, clearly defined for a given machine and type of harvest.
Along with all this, the operator’s role began to change. From a “driver,” a conscious process observer started to emerge — someone who, moving through the field, sees differences in growth, anomalies, warning signals, and reports them before they turn into real loss. But this could work only because the system stopped punishing problem reporting and started treating it as valuable information.
That triggered a change on the management side. The field manager stopped being the person who “knows everything, is everywhere, and makes every decision.” They became a system coordinator: preparing work in advance, supporting critical situations, developing people, and ensuring decisions are made earlier.
What comes out of this?
This project showed one thing very clearly: the field, the machine, and the operator cannot be managed separately. Each can function “fine” on its own, and yet the whole system will generate losses if there is no coherence. Only when we started designing them as one whole did real, tangible results appear.
The first change was faster response in critical moments. Short weather windows stopped being a chaotic race against time. With a prepared field, predictable machine availability, and better coordination of operators’ work, decisions were made earlier and more smoothly.
The second change was a clear reduction in improvisation, which had previously been treated as a “natural, unavoidable part of agriculture.” Fewer nervous plan changes, less firefighting, fewer situations where several small issues accumulated into one operational crisis — less waste of resources because “we don’t know what to do now.”
The third change concerned machine utilization. And here an important discovery appeared: the myth of “a difficult field” often covered up the real system bottleneck — inefficient organization of machine work. When machines began working on prepared fields, in planned sequences, with clearly defined expectations and fewer organizational stoppages, their effectiveness increased naturally.
The fourth — perhaps the most important — change concerned people. The quality of operators’ work improved noticeably: less pressure, more sense of control, greater responsibility for the whole process. Operators stopped being mere “task executors.” They became conscious participants in the system. Hidden talents began to surface.
People who previously did one type of work turned out to be capable of much broader action — taking on other roles, supporting the team in critical moments. At first, there was resistance. Naturally. But once trust appeared, it turned out that even relatively simple Lean tools, implemented consistently and with purpose, activate people’s thinking. Indeed — an operator driving through the field observes and asks: why does it grow differently here? is something happening here? That attention is priceless — but only if the organization wants to listen.
This connects to another element: a culture of safety and respect. When the “hard shell” cracks, it turns out operators — like all employees — also want to work safely, get home at a normal hour, and have an influence on their working environment. The machine cab becomes their workplace, often a place where they spend a significant part of their life. Order, standards, and responsibility for handovers stop being minor details. They become an expression of culture.
Appreciation, conversation, and the presence of owners or managers during the season’s critical moments build something that cannot be decreed by procedure. If you reach for the Shingo philosophy, it is easy to see that most of its principles have very concrete counterparts in the field: respect for people, skill development, solving problems at the source, learning from mistakes.
Finally, management stopped being about chasing the season. It became about preparing for its variability. The weather didn’t become kinder. Weather windows didn’t get longer. But the system was ready to use them better.
At this point, a thought worth saying out loud appears: the field stops being “nature” and becomes a project. And a project requires preparation, standards, visualization, and consistency — exactly like in a production plant.
What did we get out of this case? Three conclusions that stick.
First: weather is real, but it stops being an alibi. When the system is prepared, weather is just a variable — and the system responds efficiently to its changes.
Second: you win fastest not by “more power,” but by fewer decisions made on the fly. Field visualization and readiness logistics do the heavy lifting.
Third: when you treat the operator as a thinking human being, hidden talents start to surface. People notice things, report anomalies, understand consequences. And that’s priceless — because the operator is your eyes in the field.
And do you know what else was truly breakthrough in this project?
That moment when the team understood that by inviting a consultant, they wouldn’t get “city theory.” That we didn’t arrive with ready-made answers and a presentation — but with questions and a willingness to enter the same reality.
At one point, after a full day of work, someone said:
“Now clean the combine.”
A few minutes later, I had an air lance in my hands and was cleaning the combine — dust, grain residue, and dirt absolutely everywhere. And right then, the last barrier between us disappeared.
— says Bartosz Wnuk, consultant at 4Results Growth&Excellence
That is why more and more companies invite us to redesign their way of working before the next season. Because the cost of one wrong decision can be much higher than the cost of a well-designed system.
We’ll end with a question that closes this case — and at the same time opens space for further conversation: in your organization, do the field, the machine, and the operator form one coherent, deliberately designed system? Or do they still function side by side — meeting only when the season is already in full swing?