Are You a Good Developer or a Bad Developer?
The Los Angeles CityWatch’s recent article, Planning Ahead: Do Developers Wear Black Hats? seeks to uncover the reasons for developers’ frequently negative reputations. Residents’ views of developers often involve tiny horns and pitchforks because the former are concerned with the preservation of the existing community, and they don’t like to see change coming in the form of new development, regardless of whether or not the development is actually part of larger city planning.
But, as author Jon Perica points out, developers are often merely serving the request of another body, be it a mandate from city council to affect a change upon an evolving city, or an outdated zoning code. A developer may be required to create projects that are “consistent” with the existing zoning code, meaning, for example, that more single-family homes are built in low-density zones because those are the only allowable buildings.
However, the real problems stem from the fact that communities do not remain “consistent” but must constantly be adapted to fit with their changing economic and social needs. Developers most often get their black reputations from doing projects that are not consistent with the Community Plan, but Community Plans, in many cases, are significantly outdated. An outdated Community Plan can no longer be depended upon to match the market demands, so developments with variations on the Plan are often submitted and approved. But once some exceptions are, of neccessity, made, the door is open for developments that may be inappropriate for the changing face of the neighborhood.
The article also deliniates the qualities that characterize a sensitive developer. Good developers will:
- meet with the Neighborhood or Community Council far in advance to recieve comments, feedback, and community-oriented suggestions;
- view themselves as a member of the community, with responsibilities for creating new projects that harmonize with the existing framework;
- meet as many of the city planning regulations as possible, and present the fewest Zoning Code violations;
- consider the importance of aesthetics and “quality” features, such as design blend, landscaping, and security measures;
- share information about the planning process with the community, including ways in which residents can involve themselves or contact the developer;
- faithfully implement all the City regulations and conditions on an approved project, and oversee its early use to make certain that it functions as an asset and retains cleanliness.
Perhaps above all, Perica emphasizes the fact that developers will gain a repuation, for good or ill, that will eventually become common knowledge. Consequently, each project must be approached with the same sensitivity and consideration. “A good developer commits her or his reputation on every project they do,” Perica explains, “and the more they follow these guidelines for appropriate quality development, the better their development projects are and the better they will be perceived in the community.”
November 25th, 2006 at 9:23 am
Umm, you really need to read City as a Growth Machine: Toward a Political Economy of Place” by Harvey Molotch.
The average developer will “contribute” to social and community concerns to the extent that marginal returns are still revenue positive…
November 28th, 2006 at 12:42 pm
Thanks for the pointer! Of course, you’re quite right that there’s far more at work for developers than the issue of community contribution, but I think that Perica’s point was that ‘good’ developers are differentiated from ‘bad’ ones by their concern for the project’s community integration. The definition here has more to do with a developer’s public reputation as ‘good’ or ‘bad;’ I apologize if the title was misleading.