What It Takes to Assemble a Site

The mechanism is documented. What it asks of the person doing it is not.

How development capacity moves between parcels is a technical subject and I have written about it at length elsewhere. This page is about something else: what assembling a site requires of the developer, which is almost entirely unlike the mechanism and considerably harder to teach.

The defining feature is that the work is done in a fixed order and cannot be restarted. Each step changes the conditions of every step after it. There is no version where you gather the pieces in parallel and combine them at the end, which is what people imagine when they hear the word, and the difference between the imagined version and the real one is where projects are lost.

The second feature is asymmetry of information, which runs against you. You know what the pieces are worth together. Everyone else knows what their individual piece is worth alone. You cannot correct that asymmetry by explaining it, because explaining it is the same act as destroying the advantage it gives you. So the developer works with a set of facts they cannot share and an interest they cannot fully state, for a long time.

That produces the third feature, which is patience of a particular kind. Not waiting, which is passive, but holding a position while its value is uncertain and while the cost of holding accrues. This is where I think temperament matters more than analysis. The analysis is usually stable. What varies is whether the person can sit with an unresolved position for years without either forcing it or abandoning it.

The fourth is that it is sequenced under uncertainty about the sequence itself. You often cannot know which order is correct until partway through, because what is available depends on what has already happened. So you make ordering decisions that are irreversible, on incomplete information, knowing that a better order probably existed and that you will not be able to identify it afterward.

My arguable position is that assemblage rewards patience far more than cleverness, and that the industry believes the opposite. Assembled sites get narrated as feats of ingenuity because ingenuity makes a better story, and because the person telling it was there for the clever part and has forgotten the four years of nothing happening. The developers I have watched do this well were not noticeably more inventive than their peers. They were more willing to wait, and better at not needing to look busy while waiting.

Somebody with more transactional experience than me would say that is romantic, that speed and structuring create most of the value, and that patience is what you call it afterward when it worked. I take the point. I have seen patience be indistinguishable from paralysis, and only the outcome separated them.

The honest limit is that this stage has a failure mode with no good answer. You can do everything correctly and still end with a set of pieces that do not combine, because one party's willingness was never yours to control. That outcome looks identical to incompetence from outside, and it is not always distinguishable from inside either.

None of this is work a developer does alone. A land use lawyer establishes what may combine, a surveyor establishes what physically exists, and both belong in before the first approach rather than after it.