We have a set of principles that guide how we write and what we publish. None of this is complicated, but it matters enough to state plainly.

Plain Language, Always

If a concept can be explained in ordinary English, we explain it in ordinary English. Urban planning and environmental science are full of useful ideas buried under layers of specialized vocabulary. Terms like "green infrastructure," "bioretention," and "multimodal connectivity" describe real things, but they create barriers when used carelessly. We use technical language when precision requires it and define it when we do.

This is not about dumbing things down. It is about respecting the reader's time and intelligence. A retired schoolteacher on a parks commission and a landscape architect should both be able to follow what we write.

Real Examples Over Abstractions

We try to ground every claim in something specific. When we write about urban heat, we talk about measured temperature differences between tree-covered streets and exposed parking lots. When we discuss trail networks, we reference places like the 606 in Chicago or the park connector system in Singapore. When we talk about waterfront access, we look at places where it works and places where it does not, and we try to explain why.

General statements have their place, but they should be supported. "Green space improves wellbeing" is a starting point, not an argument.

Evidence Over Opinion

We try to distinguish between what the evidence shows and what we think about it. When research from sources like the Nature Conservancy or the EPA supports a point, we say so. When a question is genuinely unsettled, we say that too. We would rather be honest about uncertainty than sound confident about something we cannot back up.

Independence

The Urban Imperative does not accept advertising, sponsored content, or funding from organizations we write about. We have no institutional affiliations. Nobody reviews our articles before publication except our own editorial process. If we ever make a factual error, we correct it publicly and promptly.

Specifics Over Generalities

It is easy to write vague, encouraging sentences about sustainability and community. We try not to. If a framework like the SITES rating system or the Trust for Public Land's 10-minute walk standard is relevant, we name it and explain what it actually measures. If a city has done something well, we describe what they did, not just that it was "innovative."

Tone

We aim for the tone of a well-informed friend who happens to know a lot about urban ecology and public infrastructure. Not preachy, not academic, not bureaucratic. We think these topics are important, and we think most people would agree if the writing did not get in the way.

Questions about our approach are welcome through the contact page.