Your current web browser is outdated. For best viewing experience, please consider upgrading to the latest version.

Contact

Send a question or comment using the form below. This message may be routed through support staff.

Email Article

ERROR
Main Error Mesage Here
More detailed message would go here to provide context for the user and how to proceed
ERROR
Main Error Mesage Here
More detailed message would go here to provide context for the user and how to proceed

Manhattan Institute

search
Close Nav

Aaron M. Renn

 

Aaron M. Renn

Aaron M. Renn

Contributing Editor, City Journal
Media Contact

212-599-7000


Expertise

Urban Policy
Economic Development
Infrastructure and Transportation
Rustbelt Cities

EDUCATION

B.S., Indiana University

Biography

Aaron M. Renn is a contributing editor of City Journal, and an economic development columnist for Governing magazine. He focuses on ways to help America’s cities thrive in an ever more complex, competitive, globalized, and diverse twenty-first century. During Renn’s 15-year career in management and technology consulting, he was a partner at Accenture and held several technology strategy roles and directed multimillion-dollar global technology implementations. He has contributed to The Guardian, Forbes.com, and numerous other publications. His perspectives on urban issues are regularly cited in the New York Times, Washington Post, Time, The Economist, Daily Telegraph, and other international media.

Renn holds a B.S. from Indiana University, where he coauthored an early social-networking platform in 1991. He has created several widely used open-source software packages, including the only program for recovering data from corrupted gzip backups. In 1998, Renn launched one of the nation’s first blogs, the Weekly Breakdown, to cover the Chicago Transit Authority.

 

Read More

FEATURED BOOK

City Journal

 

Publications

Sorry we were unable to find any results for “
Search suggestions
  • Make sure words are spelled correctly.
  • Try entering different keywords.
  • Try using more general keywords.
  • Try fewer keywords.
Loading
Saved!
Close