Product Leadership in Climate Tech: Building Impact in Regulated, Capital-Intensive Systems

In my early career, I was involved in a product that guided market participants in making daily decisions within U.S. electricity markets. One day, a customer reached out not because the product had malfunctioned, but because its performance slightly deviated from expectations during an uncommon market scenario. Although the product's outcomes were technically accurate, the customer was hesitant to proceed.

This incident left a lasting impression. In energy systems, while correctness is essential, it is not enough. If users do not trust a product enough to rely on it in critical situations, the product has failed its primary purpose. This lesson remains pertinent today. Climate technology is no longer a niche market; it is transitioning into core infrastructure.

U.S. electricity demand is rising again, with the IEA projecting a 2% annual growth rate from 2025 to 2027, significantly higher than previous expectations. Globally, data center electricity consumption is expected to more than double by 2030, equivalent to Japan's current annual electricity usage. Meanwhile, the physical systems supporting the energy transition remain slow, constrained, and heavily regulated.

By the end of 2024, nearly 2,300 GW of generation and storage capacity was in the U.S. interconnection queues, as reported by Lawrence Berkeley National Lab (Figure 1). This indicates substantial progress, but also highlights the challenges in converting climate commitments into practical outcomes. Product management advice often presumes a setting where experimentation is inexpensive, feedback is immediate, and users can easily switch applications with little consequence.

However, this approach does not apply to climate and energy technology. Feedback cycles in energy systems can last months or even years. Experiments carry tangible financial and operational risks. The customers are utilities, grid operators, regulators, and asset owners: entities that prioritize stability, predictability, and trust over innovation.

When a product decision goes awry, the repercussions extend beyond user dissatisfaction or experiment failure; they can encompass regulatory risks, revenue loss, or reliability issues that impact entire regions. Having spent over a decade in power markets, energy analytics, and climate research, I have discovered that product leadership in climate technology necessitates a distinct perspective.

The basic principles of product management remain applicable; however, they must be tailored to environments that are regulated, capital-intensive, and intricately linked to physical infrastructure. This article shares the insights I have gained while developing and expanding products in this domain. These lessons apply whether you are already in climate technology or contemplating a shift into it.

Shipping Features vs. Shipping Trust In the realm of consumer software, product success is frequently gauged by engagement metrics and adoption rates. In the energy and climate sectors, the criteria differ. A product's success hinges on customers' trust in its reliability during high-stake decisions. For instance, a battery operator deciding to bid into ERCOT during scarcity, a utility planner assessing transmission limitations, a commercial team determining pricing for long-term service agreements based on availability guarantees, or an industrial customer contemplating investments in on-site generation or storage.

Trust determines whether a product becomes an integral part of daily operations or remains a secondary consideration. This trust is cultivated gradually. It stems from consistent behavior, transparent assumptions, and a clear comprehension of the system the product operates within. Customers notice when a tool functions reliably in edge cases, such as market fluctuations, outages, or rule changes, and recall its performance when it fails to do so.

The landscape is becoming increasingly complex. U.S. utility-scale battery storage has experienced rapid growth, with the EIA reporting a 66% increase in battery capacity in 2024, followed by another record 15 GW addition in 2025, with plans for another 24 GW by 2026. In ERCOT specifically, EIA anticipates battery capacity to expand from around 15 GW in 2025 to 37 GW by the end of 2027.

This expansion presents opportunities but also raises the bar for product reliability. As software becomes a more integral part of dispatch, market participation, warranty enforcement, service guarantees, and outage response, customers require a deeper understanding of not just what a tool recommends, but the rationale behind it.

This implies that the most successful climate-tech products do not necessarily offer the most features but excel by: being predictable under edge cases, transparent about assumptions, explicit about uncertainty, and auditable when rules change. Trust accumulates over time. Once a product becomes a part of a customer's operational routine, it becomes challenging to replace.

Conversely, one significant failure during a critical event can set back adoption by months or years. Failing to Define Problems Effectively A frequent error made by product managers entering climate technology is prematurely jumping to solutions. In regulated environments, solutions are rarely open-ended. Market rules, physical constraints, and compliance requirements determine the solution space long before any engineering begins.

This makes problem definition the most valuable and often overlooked aspect of product work. Customers typically describe symptoms rather than root causes. They may request better reporting when the actual challenge is understanding risk exposure. They might seek automation when the underlying issue is uncertainty about rule interpretation in edge cases.

Accepting requests without critical examination can lead to feature accumulation without significant impact. Successful climate tech product managers slow down the conversation just enough to ask more insightful questions. What decision is the customer actually trying to make? What are they afraid of getting wrong? What constraints are shaping their behavior?

By reframing problems around decisions and outcomes, product managers can create space for engineering teams to deliver meaningful solutions.