Australia is often described as “the driest inhabited continent”, yet the raw facts point to a different problem: we receive substantial rainfall per person, but we harvest only a tiny fraction of it. This article explains why water shortages persist, not just through technical limits like evaporation and runoff, but through the way our water institutions are organised. The key message is simple: better technology exists, but without “lean” systems and integrated leadership, it will stay stuck on the shelf.
Introduction: Plenty Of Water, Yet A “Crisis”
This is an extract from a talk titled “Solving the Water Crisis” (Part 1: the effect of organisational structure on water management), delivered by Colin Austin in March 2006. The central claim is deliberately provocative: Australia is not short of water in absolute terms. On average, the rainfall per person approaches a million litres per day. Compared with many countries, Australia has a high level of water availability per head. Yet we hear constant stories of water restrictions, towns facing severe cutbacks, reduced farmers’ entitlements, and the familiar headline phrase: “Australia, the driest inhabited continent”.
We like myths. We respond to slogans. But if the numbers suggest there is ample water, then the practical question is unavoidable: why does the lived experience feel like shortage? What is actually going on?
Why We Have Water Shortages
The simplest answer is that out of every 2,000 litres of rain, we only harvest about 1 litre in our system of catchments and dams. That sounds like a neat explanation, but simple answers rarely tell the full truth. If we are harvesting so little of what falls as rain, we need to understand the real reasons, not just repeat the headline ratio.
The talk frames the explanation at two levels. The first is technical. Australia has high evaporation across large areas, and over much of the continent evaporation exceeds rainfall. After only a few days of hot, drying conditions, the top layer of soil becomes dry. When small rain arrives, it is absorbed and disappears into that dry surface layer. There is no runoff. It takes either heavy rain, or a long enough period of follow-up rains, to wet the soil profile and create runoff that can be captured by dams.
That brings us to the practical limitation of our current approach: large dams. Large dams work best when you have high rainfall and terrain that suits big catchments and storage. As a result, our water capture is concentrated in mountainous, high rainfall areas. Catchment areas are a small percentage of the total land area, and even within catchments we mostly capture only the heavy and prolonged rains that generate runoff.
But much of Australia is relatively flat, and much of our rainfall arrives as small rains. These small rains do not generate runoff, yet they add up over time. In our current system, they are largely lost to evaporation and do “no useful work” for water supply, not because the water is absent, but because we fail to capture it.
Rainfall, Evaporation, And The Drought Illusion
The talk makes an important point about the fine balance between rainfall and evaporation. A small drop in rainfall (often paired with increased evaporation) can have a disproportionate effect on runoff and dam inflows. In a marginal dam system, a 10% reduction in rainfall might cut runoff by 20%. A further 10% reduction may cut runoff to 50%. Another 10% may mean no runoff at all. This is why dam-dependent systems can swing from “fine” to “crisis” quickly.
It also reframes what a drought really means. A drought is not necessarily “no rain”. It is a lack of useful rain in the sense of rainfall patterns that generate runoff: typically a heavy rain followed by enough follow-up rains to keep the soil wet and maintain runoff. In drought conditions, there may be adequate rainfall to supply needs, but because it arrives in small events and evaporative demand is high, it is not captured. The water falls, but the system fails to use it.
The talk is split into two parts. Part 2 is technical, focusing on technologies designed to make use of small rains. The claim is that there is no real debate about whether these technologies can work: many have been around for years, they are effective, and they can be remarkably cheap compared to the capital and operating costs of large recycling or desalination plants.
So Why Aren’t These Technologies Adopted?
This is where Part 1 turns away from hardware and into the uncomfortable territory of institutions. The argument is direct: the organisations responsible for water have not adopted the small-rain harvesting technologies. In some cases, when they have been aware of them, they have even been opposed. That suggests the barrier is not technical performance, but the way decisions are made, responsibilities are allocated, and incentives are structured.
To explain this, the talk uses a simple “John and Jane” story. A laundry tap is leaking. The technical answer is obvious: it needs a new washer. But that is not the real reason the tap is still leaking. John fixes taps quickly when he sees them. The problem is that John has been banned from the laundry because he does a terrible job with washing (pink underwear, shredded tissues, and so on). John never sees the laundry tap. Jane expects John to fix it because that is “his job”, but she never tells him it is leaking because, in her mind, he should already know. The problem is not the washer. The problem is the system.
This is how water management failures arise. Most people do their assigned job reasonably well. If something sits outside their job description, they assume someone else is taking care of it. The water world is full of “over the wall” behaviour: issues are passed to another department, another authority, another level of government, until nothing is done.
Water Delivery Is A Complex System
Water delivery is not managed by one clean chain of command. It involves federal, state, and local government. It involves water authorities that theoretically answer to state governments, but also hold the technical expertise that governments may lack, which makes control “nominal” rather than practical. It includes a spread of research bodies: CSIRO, government departments, CRCs, and universities, each pursuing specialities, often without a single integrating mechanism.
So where do we look for guidance on fixing system-level problems? The talk points to an unexpected teacher: the automotive industry, because it has gone through major shifts in how it designs and integrates systems.
From Hand Production To Lean Production
The talk references the book The Machine That Changed the World, which describes three generations of manufacturing. First was hand-built production. Second was what we loosely call mass production. Third is “lean” production. The claim is bold but clear: our water shortage problems are linked to the failure of the water sector to move from second-generation thinking to third-generation “lean” thinking.
Mass production was enabled by interchangeability: parts made accurately enough that any combination could be assembled without custom fitting. That, in turn, enabled reductionism: breaking a complex task into smaller tasks so specialists can become efficient at their piece. Reductionism is not “bad”; it is the basis of modern science and modern wealth. The talk notes it is not new, either. From Adam Smith’s pin factory to early civilisations, societies have used specialisation to advance.
The failure comes when the process is no longer appropriate to changed circumstances. Large projects like the Chaffey brothers’ irrigation systems, and later the Snowy Scheme, were impressive and suited to their time. But as the need grows to manage water as a multi-faceted asset (economic, environmental, community, long-term security), institutions struggle to adapt. In that struggle, simplification and omission creep in: complex tasks are simplified so they can be subdivided, key areas get missed, and new tasks emerge without organisational redesign to handle them.
Diverted Loyalties And The Cost Of Speaking Up
The talk highlights a deeper problem: diverted loyalties. In a reductionist organisation, people are embedded in sections, departments, and hierarchies. Their day-to-day loyalties are focused on satisfying the immediate needs of their group. Those needs may not align with the national interest, especially when the original objectives were defined by older legislation and older assumptions.
A water authority, for example, may see its job as delivering water as cheaply and effectively as possible. That may have been a sensible objective when the system was built around a narrow definition of supply. But as priorities evolve (environmental flows, sustainability, resilience, decentralised harvesting), the old objective may no longer match what Australia needs. Even so, it is rare for individuals to speak against their immediate group. The life of a whistleblower has never been comfortable.
Integration: The Missing Discipline
Reductionism only works when there is integration across the whole operation, what people often call leadership. The talk illustrates integration through history. The Roman Empire combined specialists with an integrated system capable of functioning as a whole, even incorporating soldiers from captured territories. The empire of Genghis Khan had enabling technologies, but its greater strength was integrating previously warring tribes into a unified force. Civilisations can collapse when they fail to operate as an integrated whole.
The practical point is that water management needs the same discipline: integration, not just a collection of efficient sub-units.
What Lean Thinking Really Changed
After World War II, Japanese engineers studied American auto manufacturing in Detroit. They were overawed by the scale: huge presses, dedicated tooling, long production runs. Japan could not match that scale. But the Japanese then noticed the massive infrastructure required to manage parts: large warehouses, armies of clerks, inspection systems that allowed substandard parts to accumulate, and defects that were discovered late, causing scrap and rework.
They redesigned the system, not just the components, creating lean production. They introduced ideas like “Just in Time” and process-based quality control. Inspection shifted from sorting good parts from bad parts, to keeping the process itself in control. The insight was fundamental: making every part of a system “efficient” does not automatically make the overall system efficient. Sometimes you even sacrifice local efficiency to improve total performance.
“Lean” Water: The Direct Analogy
The talk argues the water industry is in the same place Detroit once was. Many players operate in their lanes. Each component may be efficient. Yet the system as a whole fails to capture the obvious opportunity: harvesting the water we currently lose.
And there is a warning embedded in the analogy. The American auto industry ignored Japanese lean methods until imports ravaged its home market. It adopted lean only when crisis forced change. The water sector, the talk suggests, is going through a similar transition. The hope is we do not wait for an equivalent crisis before we move to lean water thinking.
Key Points From Part 1
- Adequate rainfall: Australia has substantial rainfall per person, but our dam-and-runoff model captures only about 1 litre in every 2,000 litres that fall.
- Evaporation drives the loss: High evaporation dries the soil, suppresses runoff, and turns small rains into “lost” rain under current harvesting methods.
- Technologies exist: Practical technologies can harvest small rains by catching and storing water locally, typically underground, protected from evaporation.
- Mega-project bias blocks adoption: Water institutions are culturally and structurally aligned to large dams, desalination, recycling, and other mega projects, not many small local systems.
- Threat to revenue streams: Local harvesting can be perceived as a threat to existing investments and the revenue that supports them.
- “Over the wall” fragmentation: Because local harvesting does not sit neatly in one departmental box, responsibility is often passed along until nothing happens.
- Weak private-sector incentive: If systems are cheap and components are locally available, there is less commercial incentive for a company to push adoption; the benefits flow mainly to the community.
So What Is The Solution?
It would be comforting to think the water bureaucracy will quickly absorb the lessons of lean production and restructure itself into an integrated, modern system. The talk acknowledges that this shift is already under way in some form, but argues that the time scale is too slow. The American car industry took decades to fully adapt to lean production. Australia cannot wait that long to start harvesting the water we currently lose.
So the talk proposes a faster path: a “fast track” model inspired by the personal computer revolution. IBM understood that a PC division embedded within existing bureaucracy would be smothered. Instead, it formed a small, independent, high-quality team with top management backing, a “ginger group” set free to make the new thing happen. It used open standards, and the result was one of the great success stories of modern technology adoption.
A Federal “Water Harvesting Group”
The talk argues the analogy to water is remarkable. Before the PC, computing was dominated by a few large organisations focused on grand schemes. The small end was left to hobbyists and small outfits. After the revolution, PCs dominated. In water, the current landscape is dominated by large institutions focused on grand scale projects, while the much greater potential of many smaller local harvesting projects is ignored.
The key question becomes: who can initiate the change? The talk’s answer is blunt: only the Federal Government has the capacity to lead the shift. Once started, existing resources can be integrated—research expertise (such as irrigation-focused CRCs), and local councils for trial projects.
Over time, local councils are likely to become major managers of local harvesting: promoting systems, providing technical advice, approving sites, and giving planning permission. But councils will need guidance, standards, and workable formats. The missing piece is a dedicated lead group to coordinate those elements into something that can scale.
The proposed “Water Harvesting Group” would act as pioneers and coordinators: refining and documenting technologies, setting standards, establishing demonstration projects, and pulling together the existing capabilities that already exist but are not integrated. The point is not that we lack knowledge. The point is that we lack the structure that makes knowledge deployable.
Download “Solving Australia’s Water Crisis” (Full PDF)
