Dirt to Data: Data Centers and AI Infrastructure

Suhail Tayyeb argues water infrastructure debates are driven by narrative context and visibility, not just raw data.

16 min Listen to the original Episode page
InfrastructureWaterPermittingPublic NarrativeDue DiligenceAI Data Centers

Summary

Suhail Tayyeb argues that infrastructure debates are driven by narrative rather than raw data, noting that the same water consumption figure can be perceived differently depending on the denominator used for comparison. He introduces the VWPP framework, linking visibility—such as visible cooling plumes—to public reaction and permitting friction. Tayyeb emphasizes that silence allows opposition groups to define the context, making it harder for developers to correct misconceptions later. He advises disclosing credible ranges and assumptions early to identify narrative vulnerabilities. The discussion highlights that water risk is contextual, varying by region, drought conditions, and local politics, requiring a holistic view of site-specific constraints.

Key takeaways

  1. 1
    A large number in a water water-rich rich region may create little concern. A much smaller number in a water constrained region may become politically explosive.

    Suhail Tayyeb · 2:16

  2. 2
    Visibility and narrative are linked: visible physical effects (e.g., plumes) create immediate public questions that abstract data cannot answer, often leading to negative assumptions if unexplained.

    Suhail Tayyeb · 4:03

  3. 3
    Silence from a developer does not leave a narrative void; it allows opposition groups to fill the information vacuum with their own framing, which is difficult to correct later.

    Suhail Tayyeb · 5:22

Episode sections

  1. 0:25 – 2:44

    The Power of Context in Water Debates

    Suhail Tayyeb argues that infrastructure debates are driven by narrative rather than raw data. He explains that the same water consumption figure can be perceived as manageable or enormous depending on the denominator used for comparison, such as total system capacity versus household equivalents.

  2. 2:44 – 5:03

    Visibility and the VWPP Framework

    The speaker introduces the VWPP framework (Visibility, Water narrative, Permitting friction, Public reaction timing). He links visibility—what neighbors see and hear—to the water narrative, noting that visible effects like cooling plumes create tangible concerns that spreadsheets cannot address.

  3. 5:03 – 7:14

    Narrative Control and Early Disclosure

    Tayyeb emphasizes that the entity that explains the issue first controls the narrative. He warns that silence allows opposition groups to define the context, making it significantly harder for developers to correct misconceptions later in the permitting process.

  4. 7:14 – 11:16

    Contextualizing Water Use and Trade-offs

    The discussion highlights that water risk is contextual, varying by region, drought conditions, and local politics. Tayyeb notes that cooling strategies involve trade-offs between water and electricity use, requiring a holistic view of site-specific constraints rather than generic technology comparisons.

  5. 11:16 – 16:12

    Due Diligence and Narrative Vulnerabilities

    The speaker advises developers to conduct due diligence by anticipating how skeptics will interpret their data. He suggests disclosing credible ranges, assumptions, and drought responses early to identify narrative vulnerabilities before they become political obstacles.

Claims worth verifying

The speaker uses the VWPP framework to examine where thermal and water decisions can create fragility in a data center project.

Unidentified speaker (UNKNOWN) ·2:44

How to verify: Verify by checking the 'Dirt to Data' website (fromdirttodata.com) or the speaker's LinkedIn profile for the definition and components of the VWPP framework. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.

A proposed data center may be compared against the total capacity of the local water system, representing a small percentage, or against household equivalents, making it seem enormous.

Suhail Tayyeb ·1:25

How to verify: This is a conceptual example provided by the speaker; verify by reviewing standard public comment documents or environmental impact statements for data centers that use these different comparison methodologies. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.

VWPP stands for visibility, water narrative, permitting friction, and public reaction timing.

Unidentified speaker (UNKNOWN) ·2:44

How to verify: Verify by checking the 'Dirt to Data' website or the speaker's published materials for the acronym definition. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.

Water can be withdrawn from a system, used in a process, and returned, whereas other water may be consumed through evaporation and not returned to the local system.

Suhail Tayyeb ·6:42

How to verify: Verify by consulting technical definitions from the USGS (United States Geological Survey) or EPA (Environmental Protection Agency) regarding water withdrawal vs. consumption. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.

Cooling choices involve trade-offs where reducing direct water use may increase electricity consumption or change capital costs.

Unidentified speaker (UNKNOWN) ·10:17

How to verify: Verify by reviewing technical specifications for data center cooling technologies (e.g., evaporative cooling vs. air cooling) from manufacturers or industry reports like those from Uptime Institute or Gartner. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.

The speaker references a framework called VWPP to examine where thermal and water decisions can create fragility in a data center project.

Unidentified speaker (UNKNOWN) ·2:44

How to verify: Verify by checking the 'Dirt to Data' website or the speaker's LinkedIn profile for the definition and components of the VWPP framework. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.

Do your own research

  • Verify local water withdrawal vs. consumption definitions for specific data center projects in drought-prone regions.
  • Review public permitting filings for cooling plume visibility complaints in recent data center approvals.
  • Check local utility capacity reports to contextualize absolute water usage numbers against total system capacity.
  • Identify opposition group narratives in local news archives to assess potential narrative vulnerabilities.
  • Analyze trade-offs between water consumption and electricity use for proposed cooling technologies in specific regions.
  • Review state-level water allocation policies to understand fairness and legitimacy concerns raised by residents.
  • Compare developer disclosures of drought response plans against actual historical drought data in the project area.
  • Assess the ratio of industrial water allocation to household conservation mandates in the project's jurisdiction.
Full transcriptexpand

0:25Suhail Tayyeb: Welcome to Dirt to Data. I'm Suhil Tayyib, and in this episode, I want to talk about a mistake we often make when discussing data centers and water. We assume that if we can produce the correct number, the number will settle the debate. How much water will the facility use? Give people the answer, show them the engineering, compared with available supply, and the issue should be resolved. Except that is not how infrastructure debates. usually work. Two people can look at exactly the same water number and come away with completely different conclusions. One sees a manageable industrial use, the other sees an enormous new consumer competing with homes, farms, and businesses for a limited resource. Neither reaction begins with the spreadsheet. It begins with the story people believe the number is telling them. That is why the water story can matter as much as the water number. Suppose a proposed data center is expected to consume a certain amount of water each year. The developer may compare that number with the total capacity of the local water system. Against that denominator, the project may represent a relatively small percentage. Someone opposing Closing the project may use a different comparison. They might convert the same number into equivalent consumption. of thousands of households. Suddenly, the number feels enormous. Nothing about the engineering

1:44changed, nothing about the water consumption changed, the denominator changed, and the denominator changed the story. This is one reason infrastructure debates can become frustrating. People think they're disagreeing about facts Acts when they may actually be disagreeing about context.

2:00Unidentified speaker (UNKNOWN): This

2:01Suhail Tayyeb: is true far beyond data centers. If I tell you a project will create 500 jobs, is that a lot? You cannot answer until you know something about the local labor market. If I tell you a project will consume 50 megawatts, is that a lot?

2:16Unidentified speaker (UNKNOWN): You

2:16Suhail Tayyeb: need to know something about the electrical system. Water is the same. A large number in a water water-rich rich region may create little concern. A much smaller number in a water constrained region may become politically explosive. So when someone tells you how much water a data center uses, the next question should not simply be, is that number high? The better question is, high relative to what? That is where the narrative begins.

2:44Unidentified speaker (UNKNOWN): In

2:44Suhail Tayyeb: the last episode, I introduced VWPP, the framework I use to examine where thermal and water decisions. can create fragility in a data center project. VWPP stands for visibility, water narrative, permitting friction, and public reaction timing. Today, we're going deeper into the first two because they are closely connected. Visibility asks what neighbors and the surrounding community can actually see, hear, and notice about the cooling system. Water narrative asks how the project project's water use gets described and understood publicly. Put those together and something important happens. What people can observe affects which explanation they're willing to believe. Imagine you live near a large data center. You've heard that the facility uses water for cooling. Then one cold morning you drive past and see a large white plume rising above the site. If nobody has explained, the cooling system to you, what do you think you're looking at? Maybe you assume it's pollution. Maybe you assume the facility is consuming enormous quantities of water. Maybe you wonder what chemicals are being released. Maybe you take a photograph. The photograph appears on a neighborhood Facebook group. Now imagine the caption. Look at what this data center is pumping into our community. The image may be showing ordinary water vapor, but by the time the

4:03technical explanation arrives, the visual has already created a story. That is why visibility and water narrative belong together. This creates a difficult communication problem. The engineer may have excellent data, the facility may be operating exactly as designed. Water consumption may be within the projections presented during approval. But residents have something powerful too. They have their eyes. If they can see a plume, hear cooling equipment, or watch water infrastructure being built, those physical observations make the project tangible. A spreadsheet is abstract. A plume is not. That doesn't make the public interpretation correct, but it tells you something important about how people process infrastructure. Visible effects create questions. If the developer doesn't does not answer those questions early, people will answer them for themselves. This is one of the most important ideas in water narrative. Who explains the issue first? Suppose a developer says very little about water during the early stages of the project because the engineering team is still refining the design. Months later, an opposition group publishes a graphic comparing the facility's projected water consumption. with thousands of homes. Now the developer responds, we need to provide some context. That is a much harder communication

5:22position. You're no longer explaining, you are correcting. And correcting an established narrative is much more difficult than establishing an understandable one in the first place. This does not mean rushing out in complete numbers. It means recognizing that silence does not leave. the narrative empty. Someone else may fill it. I want to make an important distinction here. When I say water narrative, I'm not talking about spin. If the project consumes a significant amount of water, say so. If the community faces water constraints, acknowledge them. If the cooling strategy creates a real trade-off, explain it. The objective is not to make a large number sound small. The objective is to make the number meaningful. Where does the water come from? How much is withdrawn? How much is consumed? Is potable water being used? Can reclaimed water be used instead? Does demand change seasonally? What happens during drought conditions? How does the project compare with available supply? Why was this cooling strategy selected? Those questions

6:22create context. Context is not spin. Context is how. people understand numbers. Water discussions also become confusing because different numbers may describe different things. Withdrawal is not necessarily the same as consumption. Water can be withdrawn from a system used in a process and returned. Other water may be consumed through evaporation and not immediately returned Return to the same local system. Those distinctions matter, but imagine presenting them at a contentious price. public hearing for the first time. You now have engineers explaining terminology while residents are trying to decide whether their community has enough water. That is not an ideal environment for education. This is why the water story should be understandable before the debate becomes adversarial. The public should not need a degree in mechanical engineering to understand what the project is proposing.

7:13Unidentified speaker (UNKNOWN): Now

7:14Suhail Tayyeb: imagine the same. data center in two different places. The first community has abundant water supply and modest growth. The second has experienced drought restrictions, rapid population growth, and political fights over future water availability. Same data center, same cooling system, same water number, completely different development risk. That is why I resist generic statements about whether data centers use too much. water. Too much relative to what? Available supply? Peak demand? Other industrial users? Agriculture? Future population growth? Drought conditions? The answer is contextual. The engineering may travel. The water politics usually do not. There's another layer that developers sometimes underestimate. A community may accept that enough water technically exists and still object to the allocation. That is a fairness question. Suppose residents have been told to conserve water. Maybe landscaping restrictions have been introduced. Perhaps farmers are facing limits. Then a large new industrial user arrives. The engineering analysis may show adequate supply, but the public question becomes different. Why are we being asked to conserve while this project receives water?

8:27That question cannot be answered only with system capacity. It requires explaining priorities, economic benefits, infrastructure investments, conservation measures, and the actual effect on other users. This is why resource debates often move from engineering to legitimacy. People are not only asking whether the system can supply the water, they're asking whether the allocation feels fair.

8:51Unidentified speaker (UNKNOWN): Now

8:51Suhail Tayyeb: bring visibility back into the picture. Imagine residents have been asked to limit outdoor water use during a dry period. Then they drive past a data center and see a large visible plume. What conclusion might they draw? The plume may not tell them anything useful about the facility's total water consumption, but visually it can become a symbol. That symbol may become more powerful than the engineering report. This is why a technically harmless visual effect can still have development consequences. It becomes evidence in a larger narrative. The issue is no longer simply what the cooling system is doing. It is what people believe the cooling system represents.

9:30Unidentified speaker (UNKNOWN): You

9:30Suhail Tayyeb: will often see water use translated into household equivalents. Equivalence. That can be useful. People understand household consumption better than gallons per day. but comparisons also need care. A household equivalent comparison may make an industrial user easier to understand while ignoring differences in economic output, seasonal demand, source water, return flows, or infrastructure investment. The same is true in the opposite direction. Comparing a data center with the entire regional water system may make a meaningful local impact look trivial. Neither denominator is automatically correct. The useful comparison is the one that helps people understand the actual pressure the project creates on the relevant system. That requires more than finding the most favorable statistic.

10:17Unidentified speaker (UNKNOWN): There

10:17Suhail Tayyeb: is another reason the story becomes complicated. Cooling choices involve trade-offs. A developer may reduce direct water use by choosing a different cooling strategy. Excellent. But perhaps that system consumes more electricity. Now you have changed the power equation. Maybe the project operates differently during extreme temperatures. Perhaps the capital cost changes. Maybe another cooling approach offers better efficiency but uses more water. This is why I include thermal and water together in pacts. packs. You cannot always optimize one variable independently. The real cool question is whether the overall system fits the site, the workload, and the local context. That is a much more difficult question than simply asking which technology uses the least water. One reason water controversies grow is uncertainty. People hear that a data center is coming. They know these facilities can be large. They hear conflicting claims about water consumption. They search online and find examples. from completely different climates using completely different cooling systems. Then those examples get applied to the local project. The information vacuum fills quickly. Clear disclosure can help. What cooling system is proposed? What is the expected water requirement? What are the assumptions? What happens during drought? What alternatives were considered? What could cause the

11:36number to change? A credible range with clearance. clear assumptions can sometimes be more useful than a precise number that creates false confidence. Instead of asking only how much water does the project use, I would add another question. How will someone who is skeptical of the project describe that number? That is not a cynical exercise. It's good due diligence. If the project uses reclaimed water, will people know that? If the annual number sounds enormous but peak daily demand is the real system constraint, which number matters? If water use is seasonal, has that been explained? If visible plume has nothing to do with pollution, does the community understand what it is seeing? If the project can reduce consumption during drought, is that part of the operating plan? You want to identify the obvious narrative vulnerabilities before they become political vulnerabilities.

12:25Unidentified speaker (UNKNOWN): Good

12:25Suhail Tayyeb: infrastructure communication. should not require everyone to support the project. People can understand the facts and still disagree about the trade-offs. That is legitimate. The goal is to make sure they're disagreeing about the actual project. If residents believe the facility uses 10 times more water than it does, that is a problem. If the developer understates a genuine resource constraint, that is also a problem. The best outcome is shared understanding of the facts. followed by an honest debate about whether the trade-off makes sense. That is a much healthier development process.

12:57Unidentified speaker (UNKNOWN): This

12:58Suhail Tayyeb: is a central lesson of the water narrative. Numbers do not arrive in public debates without interpretation. Someone chooses the denominator, someone chooses the comparison, someone explains what the number means, someone connects it to a larger story about growth, scarcity, fairness, jobs, taxes, influence. infrastructure, or the environment, and people interpret that story through what they can see around them. That is why visibility matters. The technical facts are the foundation, but facts still need context.

13:27Unidentified speaker (UNKNOWN): If

13:28Suhail Tayyeb: I were evaluating the thermal and water strategy for a project, I would want to understand the engineering first. How much water? From what source? Under what operating conditions? What happens during extreme heat? What happens during drought? Then I would step outside the engineering room. What will the neighbors see? What will they hear? What comparisons are likely to be made? What has the community already experienced with water? Who is likely to explain the project publicly? And when will that explanation happen? Those questions are part of development diligence, because if you wait until the public hearing to discover the water narrative, you may already be too late.

14:03Unidentified speaker (UNKNOWN): If

14:03Suhail Tayyeb: there's one idea I want you to remember from this episode, it is that the water number does not explain itself. A technically accurate number can still be misunderstood. A visible plume can become a symbol for something it does not actually represent. A perfectly manageable water requirement in one community can become unacceptable acceptable in another. And silence from the developer does not mean there will be no narrative. It usually means someone else gets to write it. That is why the water story matters as much as the water number. Not because the facts are unimportant, because facts need context before they can become understanding. Thanks for listening to Dirt2Data. If you found this episode useful, subscribe and share it with someone interested in real estate, State infrastructure, energy, or artificial intelligence. I'm Suhail Tayyib and I'll see you in the next episode.

This page was produced automatically: the audio was transcribed with nvidia/parakeet-tdt-0.6b-v3+sortformer-v2.1 and interpreted by Qwen3.6-35B-A3B-UD-IQ3_S.gguf. Transcription and interpretation can contain errors; always confirm against the original episode. Nothing here is investment advice.
All insights