The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/AI & Data/AI for HR Weekly Podcast, brought to you by Barry Phillips
AI for HR Weekly Podcast, brought to you by Barry Phillips artwork

Data Centres, Water, and the Danger of Big Scary Numbers in the Workplace

AI for HR Weekly Podcast, brought to you by Barry Phillips · 2026-06-25 · 6 min

0:00--:--

Key moments - from our scoring

Substance score

39 / 100

Five dimensions, 20 points each

Insight Density10 / 20
Originality10 / 20
Guest Caliber3 / 20
Specificity & Evidence11 / 20
Conversational Craft5 / 20

Barry Phillips tackles a pervasive workplace problem: how organisations and employees misuse statistics to drive fear around AI and sustainability. Using the Amazon Indiana data centre's 300 million gallons annual water consumption as his primary case study, Phillips demonstrates how raw numbers lack meaning without context. He reveals that this figure represents roughly five hours of U.S. golf course irrigation annually - a comparison that reframes the narrative entirely. The episode also benchmarks data centre water use against California almond farming, which consumes several times more water. Phillips argues that HR departments must develop "context literacy" in their workforce: the ability to interrogate big numbers by asking what they're compared against, over what period, and which definitions apply. He identifies three HR responsibilities - training employees on realistic AI impacts, maintaining organisational trust through honest communication, and building critical thinking skills - that determine whether workplaces can separate evidence from panic. This episode serves operations leaders, HR professionals, and anyone communicating about technology adoption and sustainability claims. The practical takeaway: when discussing AI or digital transformation, ask not just "can we use this?" but "what are we comparing it with?" and "what don't we know?"

Key takeaways

  • →Amazon's Indiana data centre's 300 million gallons annual water use equals roughly five hours of US golf course irrigation, not the monster consumption headlines suggest.
  • →HR should train employees to ask three critical questions about AI sustainability claims: what is the real environmental impact, what are valid comparisons, and what do we not yet know.
  • →Context literacy - the ability to interrogate numbers by comparing them across different periods, scales, and use types - is a critical workplace skill for the AI era.
  • →Employees are increasingly skeptical of corporate sustainability statements and deserve evidence-based communication rather than either doomsaying or dismissal about AI's environmental impact.
  • →Organizations need 'calmer minds' that can separate risk from rumor, requiring leaders to challenge bad comparisons and cultures where evidence beats outrage.

In this episode

  1. 1Data Centre Water Consumption: The Big Scary Number Problem
  2. 2Contextualizing Water Use: Golf Courses, Almonds, and Scale
  3. 3HR's Role in AI Ethics and Employee Training
  4. 4Building Context Literacy in the Workplace
  5. 5Three Better Questions for Sustainable Digital Transformation

Topics in this episode

Digital transformationData centre water consumptionAmazon Indiana data centreGolf course irrigationCalifornia almond farmingContext literacyAI sustainabilityCorporate transparencyMisinformation in infographicsWorkplace trust and ethics

Questions this episode answers

How much water does the Amazon data centre campus in Indiana use annually?

Around 300 million gallons per year, which Phillips contextualizes as equivalent to approximately five hours of U.S. golf course irrigation annually.

How much water do U.S. golf courses use each year compared to data centres?

U.S. golf facilities use approximately 500 billion gallons annually (1.4-1.5 billion gallons daily), which is significantly more than direct data centre consumption.

What is context literacy and why does HR need to develop it?

Context literacy is the ability to hear a big number and ask critical questions like "compared with what?" and "over what period?" - skills that help employees distinguish between insight and panic when evaluating AI and sustainability claims.

What three questions should organisations ask when discussing AI and sustainability instead of just 'can we use this tool'?

Ask: what is the real environmental impact, what are we comparing it with, and are we being honest enough to admit what we do not yet know.

Why should HR be concerned about how employees are trained to view AI's environmental impact?

If employees are told AI destroys the planet or has no impact at all, they either avoid useful tools for wrong reasons or accept misinformation - neither supports good decision-making about technology adoption.

What our scoring noted

Our reviewer’s read on each dimension, with quotes from the episode.

Insight Density

10 / 20

The episode offers a handful of genuinely useful reframes - 'context literacy' as distinct from AI literacy, and the golf-course/almond comparisons to calibrate data-centre water use - but at six minutes it is necessarily thin and the core message (big numbers need context) is not deeply developed. A meaningful chunk of the runtime is rhetorical flourish rather than transferable insight.

A number on its own is not a fact. It's a fact-looking object.
Context literacy. The ability to hear a big number and ask: compared with what? Over what period? Local or national? Water withdrawn or water consumed?

Originality

10 / 20

Coining 'context literacy' as a workplace skill distinct from digital or AI literacy is a tidy and moderately fresh reframe, and the golf-course fire-hose metaphor is a vivid illustration. However, the underlying argument - 'compare big numbers to other big numbers before panicking' - is a well-worn media-literacy lesson rather than a genuinely novel idea.

Not just digital literacy. Not just AI literacy. Context literacy.
the data centre is presented as a thirsty monster, while the golf courses are quietly out the back drinking from a fire hose

Guest Caliber

3 / 20

There is no guest at all - this is a solo monologue by the host. The transcript provides no evidence of the host's own practitioner credentials or seniority, which severely limits this dimension regardless of the content quality.

Hello Humans! And welcome to the weekly podcast that aims to address an important AI issue relevant to HR in five minutes or less.

Specificity & Evidence

11 / 20

The episode does better than most short-form content by naming the Amazon Indiana campus and citing specific figures (300 million gallons, 16,000 US golf courses, 500 billion gallons per year), and converts them into a memorable 'five hours' comparison. However, no sources are cited, and the California almond claim is explicitly hedged as vague, limiting evidentiary weight.

There are around 16,000 golf courses in the United States. U.S. golf facilities use in the region of 500 billion gallons of water a year. That works out at about 1.4 to 1.5 billion gallons every single day.
almond farming in California appears to require several times more water than direct U.S. data-centre consumption

Conversational Craft

5 / 20

This is an uninterrupted solo monologue; there is no interview, no follow-up questioning, and no productive disagreement possible. The host poses rhetorical questions but answers them himself, so there is no craft to evaluate in terms of pushing back on claims or drawing out depth from another speaker.

You might be thinking, 'What has this got to do with HR?' Quite a lot, actually.
So here's a practical workplace idea. The next time your organisation discusses AI, sustainability or digital transformation, don't just ask, 'Can we use this tool?' Ask three better questions.

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Most-used words

water13data8number5centres4workplace4context4questions4centre4gallons4golf4technology4literacy4five3local3almond3sustainability3

Full transcript

6 min

Transcribed and scored by The B2B Podcast Index.

Hello Humans! And welcome to the weekly podcast that aims to address an important AI issue relevant to HR in five minutes or less. Today I want to talk about water, data centres, and one of the great workplace diseases of our time: the big scary number with no context. You’ve probably seen headlines saying data centres are “guzzling” water.

And yes, data centres use water. Some use a lot of it, especially where water is used for cooling. That matters. Local communities are right to ask hard questions.

But here’s the problem. A number on its own is not a fact. It’s a fact-looking object. Rather like a dodgy CV, it may contain elements of truth, but it still needs checking.

Take the new Amazon data centre campus in Indiana. One figure doing the rounds is that it could use around 300 million gallons of water a year. That sounds enormous. And in one sense, it is enormous.

Most of us don’t pop to the kitchen tap and casually draw 300 million gallons before breakfast. But scale matters. There are around 16,000 golf courses in the United States. U.

S. golf facilities use in the region of 500 billion gallons of water a year. That works out at about 1.4 to 1.

5 billion gallons every single day. So, if we take the Amazon figure at face value, its annual water use is not more than a day of American golf-course irrigation. It is closer to five hours. Five hours.

In other words, the data centre is presented as a thirsty monster, while the golf courses are quietly out the back drinking from a fire hose. And almonds? California almond production is another useful comparison. Estimates vary, but almond farming in California appears to require several times more water than direct U.

S. data-centre consumption. Again, that does not mean almonds are evil. I’m not here to cancel almond croissants.

That would be a dark day for civilisation. The point is simpler. When we talk about sustainability, AI and technology, we need proportion. We need context.

We need grown-up thinking. And that is where HR comes in. You might be thinking, “What has this got to do with HR?” Quite a lot, actually.

First, HR is often responsible for how organisations train people to use AI. If employees are being told “AI is destroying the planet every time you write an email”, they may avoid useful tools for the wrong reasons. Equally, if they are told “AI has no environmental impact at all”, they are being sold fairy dust in a data-centre-branded bottle. Neither is good enough.

Second, HR has a role in organisational trust. Employees are increasingly sceptical of corporate statements on sustainability, technology and ethics. And frankly, they should be. Some statements deserve scepticism.

But scepticism is not cynicism. Cynicism says, “Everything is rubbish.” Scepticism says, “Show me the evidence.” That is a workplace skill.

Third, HR should be helping employees build what I’d call “context literacy”. Not just digital literacy. Not just AI literacy. Context literacy.

The ability to hear a big number and ask: compared with what? Over what period? Local or national? Water withdrawn or water consumed?

Drinking water or reclaimed water? Direct use only, or including electricity generation? Those questions are not pedantic. They are the difference between insight and panic.

So here’s a practical workplace idea. The next time your organisation discusses AI, sustainability or digital transformation, don’t just ask, “Can we use this tool?” Ask three better questions. What is the real environmental impact?

What are we comparing it with? And are we being honest enough to admit what we do not yet know? Because the future of work will not be shaped only by technology. It will be shaped by whether people can think clearly about technology.

In the AI age, organisations will not just need faster systems. They will need calmer minds. People who can pause before sharing the scary statistic. Leaders who can separate risk from rumour.

Cultures where evidence beats outrage. Because misinformation does not always arrive wearing a tin-foil hat. Sometimes it arrives in a smart infographic, with a dramatic headline and a number big enough to frighten the finance director. So yes, let’s challenge data centres.

Let’s demand transparency. Let’s ask hard questions about water, power and local impact. But let’s also challenge bad comparisons. The real workplace skill of the next decade may not be knowing all the answers.

It may be knowing when a big number is trying to mug your judgement in broad daylight.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

  • Episode #26 - Founder-Led Scale in a PE-Backed World w/ Chuck CantonThe LAB: Value Creation in Private Equity · on Digital transformation81 / 100
  • E08: Ilya Kravtsov - Serial Entrepreneurship & AI BankingTrue Founder Stories · on Digital transformation78 / 100
  • ERP134 - Navigating Rapid Change in the MSP ChannelEvolved Radio · on Digital transformation77 / 100
  • Why do most construction strategies fail (and how to fix them)?The Power of Construction · on Digital transformation77 / 100
  • Ep. 61 | Rethinking ROI: Balancing Innovation and Stability in Business The Resolution Room · on Digital transformation75 / 100
  • Why leaders need to create space for thinkingThe Digital Lighthouse · on Digital transformation75 / 100

More from AI for HR Weekly Podcast, brought to you by Barry Phillips

All episodes →
  • Hello, Can I Speak to a Human, Please?51 / 100
  • The Top Five GenAI Tools for HR57 / 100
  • The Forthcoming AI Token Crisis - What’s HR got to do with it?40 / 100
  • Is Your Organisation AI Aware or AI Feral?37 / 100
  • The Ghost in the Machine…. and Who Owns It74 / 100
Explore the best B2B AI & Data podcasts →
All AI for HR Weekly Podcast, brought to you by Barry Phillips episodes →