James Dickey

What we talked about

The industry has to make its own case

James Dickey believes data center developers cannot leave the public conversation to elected officials. In this Making Names interview, the JD Key Consulting founder argues that companies need to explain their projects, answer questions and make the case for what they would bring to a community. His perspective is openly pro-development, shaped by work at the intersection of business and local government. The conversation is less about the technology inside a server building than the work outside it: understanding public concerns, explaining trade-offs and building a credible case for a project.

A familiar argument about something new

Dickey places the debate over data centers alongside earlier disputes about railroads, nuclear power and hydraulic fracturing. He sees those examples as warnings about the long-term cost of rejecting development. These are the comparisons he uses to frame the issue, rather than proof that every new project deserves approval. His broader question is how Texas should approach infrastructure that may shape its future economy. He argues for evaluating the opportunity as well as the concern, and for keeping a sense of scale when discussing land, electricity and water.

Nuclear energy opened the door

Dickey says his recent work in data centers grew out of efforts around nuclear energy. Looking for customers for future generation brought him into conversations with operators that needed substantial power. Those discussions highlighted a timing problem: interest in future nuclear capacity does not remove the need to serve demand sooner. He also reminds listeners that data centers predate the current interest in artificial intelligence. For him, separating the building, the power infrastructure and the uses of computing is part of making the discussion more understandable.

Local benefits need a local explanation

When Dickey discusses the opportunity for rural Texas, he focuses on the potential for a broader tax base, local services and infrastructure investment. He describes arrangements in which developers contribute to water projects as examples of what he wants communities to consider. Those interview examples are not a guarantee that every facility will produce the same result. His point is that a proposal should be explained in terms people can evaluate locally. A developer’s expectation that a project will be welcomed is not a substitute for showing residents what is being proposed.

Listen before choosing the message

Dickey closes by describing how his firm approaches projects that have met resistance. The work includes speaking with officials, learning what they are hearing and talking with constituents about the issue. He wants supporters to be heard alongside opponents, rather than assuming the most frequent speakers represent everyone. He also directs listeners to Hyperscale News for coverage of power, water and policy in the data center sector. The lesson running through the interview is that technical and financial arguments still need a public conversation, and the people proposing a project have a responsibility to take part.