Standing Water Is a Pond You Haven’t Dug Yet

Walk a property with its owner and there is usually one feature they apologize for. A wet corner that swallows a mower every April. A bank too steep to mow, too poor to plant. A hedgerow of thorns nobody wants to touch. The apology is the tell. Before anything has been designed, the land has already been judged wrong, and the job has already been framed as correcting it.

It is rarely wrong. It is expensive to argue with, which is a different thing.

Read the water before you move it

South-central Pennsylvania gets a little over forty inches of rain a year. Where it ends up has less to do with the total than with slope: water moves while the ground falls away and stops when the ground flattens. What gets called a drainage problem is usually just the place where it stops. A saturated flat, holding for weeks each spring, in a spot the topography has been pointing at for a very long time.

The conventional answer is to move it along. Perforated pipe, a stone trench, a swale cut to daylight, and a bill. It works. It also exports the only free input the site produces, and it exports it fastest in the exact season the rest of the year depends on.

Water that stands is water that has already been delivered, stored, and paid for. The question is not how to get rid of it. The question is what it is worth if you keep it.

Three questions before the shovel

The same three, in this order. They cost nothing and they cut most projects in half.

One: what is it actually doing? Not what it looks like. Watch it in a real rain, or read the evidence after one. Sediment fans tell you speed. Rush and sedge tell you duration. A rust-colored seep line on a cut bank tells you where the water table meets the surface, and it will tell you the same thing every year.

Two: what is it trying to become? Standing water wants to be storage. A steep eroding bank wants to be terraced or held by roots. A thorn thicket wants to be an edge, and edge is where the yield lives. Every problem on a site is a system running without a job assigned to it.

Three: what does it cost to stop fighting it? This is the honest one. Sometimes the answer is a pond. Sometimes it is accepting that a tractor will never park there, and planting willow and elderberry instead. Both are designs. Only one of them has a contractor invoice attached.

The move it usually becomes

For a wet low spot, the design that answers it is often some version of the same one, and it is old enough to be unglamorous: put the water feature at the low point, and use the spoil from digging it to raise a planting bench beside it.

Two problems solve each other. The excavation has to put its material somewhere, and the ground next to a wet spot wants to be higher. What you get is storage where the site was already collecting, and drained rooting depth immediately uphill of it, out of the same afternoon’s work. Same water, same acre, same rainfall. The only thing that changed is which direction you decided it was going.

That is not a clever trick. It is what a site like that is already asking for, written down.

The reframe is the whole practice

Bill Mollison put it in four words, and permaculture people have been quoting them ever since: the problem is the solution. It gets read as optimism. It is closer to accounting.

A problem is an unassigned resource. Excess water is storage with no vessel. A pest is a niche with no predator. A waste stream is fertility in the wrong place, at the wrong time, in the wrong form, and you only have to change one of those three for it to stop being waste. The design work is not invention. It is noticing what the site already produces for free and building the thing that catches it.

So before you price the pipe: go stand in the wet corner during a rain. It is the cheapest consulting anyone will ever get, and it is generally right.