What separates the developments that last

I bought into my first development at seventeen, while I was still at school. That was 1997. In the close to three decades since, I have delivered more subdivisions than I bother to count — residential estates, gated communities, townhouse projects, industrial and marine-industry subdivisions, commercial strata conversions in Sydney and on the Gold Coast — and I have watched a great many other people's projects from close range, the ones that worked and the ones that didn't.

If there is a single thing that long view teaches you, it is that the developments which last are quietly alike. They are rarely the boldest or the luckiest. They are the ones built on a handful of unglamorous disciplines, applied early and held to. Here are the four that matter most.

One: buy the asset, not the optimism

A development is largely decided on the day the site is bought. Land bought well forgives a great deal of trouble later; land bought on the assumption that nothing will go wrong punishes every ordinary setback as though it were a catastrophe. So I underwrite the downside first and let the upside look after itself.

The question I ask is not "how good can this be?" but "what happens if approvals take a year longer and costs come in above feasibility?" If the answer to that question is survivable, the project is worth doing. Price for the asset in front of you, not for the best version of the future, and most of the risk is behind you before the work even starts.

Two: treat the approval as the work, not a formality

A development consent is a process, not a moment, and the strongest projects respect that. The discipline is to keep your commitments matched to your certainty — spending first on the things that increase certainty, like diligence, planning and the right consultants, before the things that only pay off once certainty exists.

On one of my own projects the path to a usable approval ran through the Land and Environment Court. We navigated it, but I never assumed it would be quick or certain — and because the commitments were matched to that reality, the timeline was a fact to manage rather than a crisis to survive.

Three: design the capital into the project

Every development meets a surprise; the only questions are when and how large. The structures that hold are the ones with room in them — contingency, flexibility in the facility, a real relationship with the lender, something held back. With that room, an ordinary problem stays an ordinary problem.

I came to see financing not as something arranged at the end and forgotten, but as part of the design of the project — as much as the layout or the product. A development and its capital structure either fit each other or they do not. This is the lesson that eventually pulled me toward capital itself, and now informs how I structure it for others.

Four: keep the work to the few things that matter

Activity is not the same as progress. The work that actually carries a development is a short list: secure the site well, get the approval clean, structure the capital with room to breathe, and deliver the product the market actually wants. Protect that list — give it the budget and the attention — and most of the noise takes care of itself.

Where the success is really made

The romance of development — the render, the launch, the finished community — happens at the end, and it is the least of the work. The developments that last are made long before any of that, in the early, unglamorous decisions about price, certainty, structure and focus.

Thirty years in, that is the discipline I trust more than any other: get the quiet parts right, early, and the visible success tends to follow.