IBM, Smart Cities, and the Art of Saving a Group Project

A graduate capstone project for a Strategy and Negotiation course, completed in late 2023. The concept was strong. The team dynamics were not. I'll leave it at that

Every graduate program has at least one group project that teaches you more about managing people than about the actual subject matter. This was one of mine.

The assignment was a strategic analysis and forward-looking recommendation for a major corporation. Our team chose IBM — a company that has spent the better part of a decade quietly losing revenue while sitting on a century of institutional knowledge, some of the most sophisticated AI infrastructure in the industry, and a consulting arm with relationships that most competitors would trade significant market share to acquire. The problem was not that IBM lacked assets. The problem was that it had stopped knowing what to do with them.

The argument we built — or rather, the argument I & one other person built and then carried across the finish line — was that IBM's most credible path forward ran directly through smart cities. The numbers made the case almost too easily: $41 trillion projected in US city government infrastructure investment over the next twenty years, 43 megacities globally expected by 2030, and 45% of government organizations having entered the pandemic entirely unprepared for the disruptions it brought. IBM already had the pieces — hybrid cloud storage, AI through Watson, consulting relationships with governments, semiconductor expertise, and a 2009 Smarter Cities campaign that had generated $3 billion in revenue in its first year alone before being quietly deprioritized. The strategic play was not to invent something new. It was to recognize what IBM had already started and commit to it seriously.

The overlap between IBM's existing competencies and smart city requirements was almost diagrammatically clean: AI integration, cloud and data management, digital civil infrastructure planning, transportation efficiency, financial integration, sustainability. The company had the infrastructure for all of it. What it lacked was the strategic will to pivot away from legacy revenue streams that were declining and toward a market that was genuinely expanding.

The roadblocks were real — public-private partnership complexity, data privacy and security concerns, the sheer cost of overhauling existing municipal infrastructure, resistance from local governments protective of incumbent vendors. None of these were insurmountable, and the mitigation strategies were straightforward: pilot deployments, startup collaborations specializing in smart city features, leveraging IBM's existing Smart Planet white papers as implementation frameworks, and developing regional government relationships built on proven consulting track records.

What I find most interesting about this project in retrospect is how directly it connects to work I had been doing across multiple disciplines for years. The HighEcology concept from VIS 162 — repurposing highway infrastructure for sustainable urban living. The GIS walkability analysis asking who the city is actually built for. The San Diego 2072 final project mapping climate-responsive urban design at the county scale. The IBM smart cities argument was the business strategy version of the same question I keep returning to: what does it actually take to build cities that work for the people in them, and for the planet they sit on?

The project got strong reviews. The presentation went well. I'll spare the details of how that outcome was achieved given the circumstances, except to say that "strategy and negotiation" turned out to be an apt course title in more ways than one.