Tag: energy

  • The Return of Industrial Time

    The Return of Industrial Time

    For the last two decades, a lot of management culture has learned to think in software time.

    Build. Test. Release. Measure. Iterate.

    That operating logic changed how companies build products, how teams organize work, and how boards talk about speed. It made experimentation respectable in places that used to reward only long planning cycles.

    My read on this: that lesson is still useful, but it is no longer enough.

    A growing part of the strategic agenda is not moving on software time. Electricity grids, energy systems, ports, factories, semiconductor supply chains, defense production, railway capacity, industrial permitting, and resilient sourcing all run on a different clock.

    They require capital before certainty arrives. They depend on permits, suppliers, safety, skills, land, regulation, maintenance discipline, and long-term demand signals. They take years to build and decades to amortize.

    This is the return of industrial time.

    The interesting leadership problem is not choosing between speed and patience. It is knowing which clock a decision belongs to.

    The software clock changed executive expectations

    Software gave leaders a powerful idea: speed can reduce risk.

    If a team can release a small version quickly, observe real behavior, and adjust, it does not need to pretend that every answer is known upfront. That logic has shaped far more than product development. It influenced strategy processes, innovation portfolios, transformation programs, and investor communication.

    The software clock is visible in how companies now talk about pilots, minimum viable products, agile delivery, platform thinking, data loops, and continuous improvement.

    I think that mindset still has enormous value. Faster feedback improves capital allocation. Faster decision loops reduce internal friction. Better data can reveal what customers, suppliers, and employees are actually doing, not only what the organization hopes they are doing.

    But the software clock also creates a temptation: the belief that every important problem can be de-risked through rapid iteration.

    That belief breaks down when the strategic problem is physical.

    You cannot A/B test a power grid in the same way you test a landing page. You cannot scale a defense-industrial base with the same reversibility as a software feature. You cannot rebuild semiconductor resilience quarter by quarter. You cannot fix underinvestment in infrastructure with a sprint review.

    Industrial systems can and should become more digital, more transparent, and more adaptive. But their underlying constraints remain material. Increasingly, they come with a price tag and a lead time that no roadmap can compress.

    Industrial time is slower because reality is harder

    Power grid control room overlooking high-voltage transmission lines at sunrise
    Industrial time is slow because physical capacity, permits and infrastructure cannot be compressed into software cycles.

    Industrial time is not slow because managers are old-fashioned. It is slow because the work sits inside physical, financial, and institutional constraints.

    Three numbers make the point.

    Grids. The International Energy Agency has warned that grids risk becoming the weak link in the energy transition unless investment accelerates. Its grid report says annual grid investment needs to double to more than USD 600 billion by 2030, and new transmission lines routinely take 5 to 15 years to plan, permit, and complete. IEA Executive Director Fatih Birol put it bluntly: "We must invest in grids today or face gridlock tomorrow." In the United States, the Department of Energy's National Transmission Needs Study estimates the country must more than double regional transmission capacity by 2035. That is not a communications problem. It is a capacity problem.

    Europe's investment gap. Mario Draghi's report on European competitiveness matters because it turns a familiar policy debate into an industrial-time problem. Its headline figure – roughly EUR 750-800 billion of additional investment per year – is not just a financing number. It is a statement about the scale of energy, defense, deep tech, infrastructure, and productivity capacity Europe would have to build. The report's core message is that Europe needs a different growth trajectory, not just better language around competitiveness. That lands as a management signal as much as a policy one.

    Semiconductors. A chip ecosystem is not one factory. It is design capability, advanced tools, specialty chemicals, materials, packaging, testing, energy, talent, customers, and export-control exposure. The CHIPS Act logic itself reflects this: the United States put USD 52.7 billion behind domestic semiconductor manufacturing and research because capacity is a multi-year industrial problem. TSMC's Arizona build-out, which began as a USD 12 billion project and later expanded, is now reported as a USD 165 billion U.S. investment. In mid-2026, TSMC CEO C.C. Wei told shareholders it would be "a long time before we can meet customer demand".

    Advanced semiconductor fabrication campus with clean industrial equipment, logistics docks and power infrastructure
    Semiconductor capacity is an ecosystem of tools, materials, energy, talent and long ramp-up times.

    The same pattern appears in defense. Europe can announce higher defense ambitions quickly, but ammunition output, supplier depth, testing capacity, skilled labor, and common procurement cannot be improvised. NATO's Jens Stoltenberg described the need to "shift from the slow pace of peacetime, to the high-tempo production demanded by conflict". That is industrial time in one sentence.

    The binding constraint is no longer the speed of the interface. It is the speed at which physical capacity, capital, skills, and permits can be brought into being.

    What this looks like inside companies

    The point becomes clearer when you look at company cases.

    Ford's electric-vehicle build-out is one example. A product with heavy software content still depends on battery plants, cell production, equipment orders, supply chains, trained workers, and industrial ramp-up. Ford described BlueOval City as part of its more-than-USD-30-billion EV investment through 2025. That is not a quarterly optimization exercise. It is a multi-year industrial bet.

    Orsted is another. The company took an impairment of roughly USD 4 billion in 2023 and cancelled its Ocean Wind 1 and 2 projects in New Jersey after supply-chain inflation, higher interest rates, and permitting delays made fixed-price contracts uneconomic. CEO Mads Nipper pointed to "significant adverse developments" in the supply chain and said the company was "extremely disappointed" to cease the projects. The deeper point is that industrial-time projects front-load commitment, then absorb the variance of a multi-year supply chain.

    Boeing shows a different version of the same issue. After the January 2024 737 MAX door-plug blowout, the FAA blocked Boeing from expanding 737 MAX production until quality systems were fixed. Demand was not the bottleneck. Industrial integrity was.

    And TSMC's Arizona expansion shows why industrial capability cannot simply be copied from one geography to another. The company has had to manage cost and timeline pressure in the United States, with reporting around TSMC's Arizona build-out pointing to substantially higher U.S. construction costs than in Taiwan. A fab is not just a building. It is an ecosystem.

    These are not failures of intelligence. They are encounters with a clock that does not negotiate.

    The harder management problem: two clocks, one company

    I do not think the answer is to become slower.

    The harder task is integration.

    A company that only thinks in industrial time becomes too slow. It over-plans, protects legacy processes, and treats every decision as irreversible. It may preserve reliability, but it loses learning velocity.

    A company that only thinks in software time becomes careless. It mistakes optionality for strategy. It launches too many pilots, underestimates physical dependencies, and treats capital-intensive systems as if they can be refactored later without cost.

    The way I see it, modern leadership needs both disciplines.

    Digital speed matters where reversibility is high and learning is valuable: customer insight, forecasting, demand sensing, workflow automation, internal transparency, scenario modeling, and decision support.

    Industrial patience matters where reversibility is low and execution risk compounds: plants, grids, logistics nodes, critical suppliers, regulatory approvals, safety systems, and long-lived assets.

    The mistake is applying the wrong rhythm to the wrong problem.

    Capital allocation becomes the test

    Executive strategy room with industrial infrastructure model, digital dashboard, hourglass and analog clock
    The real management test is whether capital, skills and capacity line up before the next shock arrives.

    Industrial time turns strategy into a capital-allocation test.

    It is easy to endorse resilience in a board presentation. It is harder to fund redundant capacity, dual sourcing, inventory buffers, grid connections, cybersecurity hardening, supplier development, and workforce training before the next disruption makes the need obvious.

    The same is true at national scale. The Draghi investment gap and the IEA grid investment number describe the same uncomfortable truth: agreement does not build capacity. Capacity follows from committed capital, credible timelines, aligned incentives, and operational ownership.

    The question I would be asking myself is simple:

    Where are we pretending that a strategic dependency is only an operating cost?

    If energy availability can constrain growth, it is strategic. If a supplier bottleneck can stop production, it is strategic. If a missing skill base can delay execution for years, it is strategic. If regulatory approval, grid access, or logistics capacity determines market entry, it is strategic.

    Industrial time makes these dependencies visible.

    It also changes the meaning of efficiency. In software time, efficiency often means reducing waste, shortening cycles, and automating repetitive work. In industrial time, efficiency also means keeping enough capacity, redundancy, and competence to survive stress.

    A system optimized only for the normal case can be financially elegant and strategically fragile.

    Andreas's view

    My read on this: the next advantage is temporal discipline.

    The companies that do this well will not become nostalgic industrial planners. They will still use digital tools aggressively. They will use better forecasting, better data, better scenario models, and faster feedback loops to make long-cycle decisions less political and less blind.

    But they will also recognize that some commitments have to be made before certainty arrives.

    I don't think the next decade rewards organizations that simply move fast. It rewards organizations that know when speed is a learning tool and when early commitment is the real advantage.

    Three things I'm watching:

    • Whether Europe can turn the Draghi diagnosis into actual capacity: energy, defense, capital markets, compute, and industrial execution.
    • Whether AI infrastructure pushes grid access, power contracts, cooling, chips, and data-center permitting into the center of corporate strategy.
    • Whether companies start treating suppliers, energy, skills, and resilience as strategic assets rather than procurement line items.

    The telling indicator will be whether management teams can hold both clocks in their head at the same time.

    Move fast where learning is cheap. Commit early where capacity will be scarce. Use data to shorten decision cycles, but respect the physics of assets, infrastructure, and institutions.

    The world is becoming more digital and more industrial at the same time.

    That is the leadership rhythm I think matters now.

    Sources

    https://commission.europa.eu/topics/competitiveness/draghi-report_en

    https://www.iea.org/reports/electricity-grids-and-secure-energy-transitions

    https://www.iea.org/news/lack-of-ambition-and-attention-risks-making-electricity-grids-the-weak-link-in-clean-energy-transitions

    https://www.energy.gov/oe/national-transmission-needs-study

    https://www.semiconductors.org/chips/

    https://pr.tsmc.com/english/news/3210

    https://www.cnbc.com/2025/03/03/tsmc-to-announce-100-billion-investment-in-us-chip-plants.html

    https://www.tomshardware.com/tech-industry/semiconductors/tsmc-ceo-c-c-wei-says-it-will-be-a-long-time-before-we-can-meet-customer-demand-tells-shareholders-that-he-will-keep-prices-stable-refrain-from-implementing-price-hikes

    https://9to5mac.com/2023/08/04/us-made-tsmc-chips/

    https://corporate.ford.com/articles/electrification/blue-oval-city/www/

    https://www.cnbc.com/2023/11/01/orsted-axes-two-new-jersey-wind-projects-takes-4-billion-writedown.html

    https://www.faa.gov/newsroom/faa-halts-boeing-max-production-expansion-improve-quality-control-also-lays-out-extensive

    https://www.nato.int/en/news-and-events/events/transcripts/2024/02/15/press-conference

    • European Commission: The Draghi report on the future of European competitiveness
    • International Energy Agency: Electricity Grids and Secure Energy Transitions
    • International Energy Agency: "Invest in grids today or face gridlock tomorrow"
    • US Department of Energy: National Transmission Needs Study
    • Semiconductor Industry Association: CHIPS Act overview
    • TSMC: U.S. investment expanded to USD 165 billion
    • CNBC: TSMC total U.S. investment reported at USD 165 billion
    • Tom's Hardware: TSMC CEO C.C. Wei on customer demand
    • 9to5Mac / NYT summary: TSMC Arizona construction-cost premium
    • Ford: BlueOval City and EV investment
    • CNBC: Orsted offshore wind impairment and cancellations
    • FAA: Boeing 737 MAX production expansion halted
    • NATO: Defense industrial production remarks
  • AI’s next bottleneck may not be intelligence. It may be Earth.

    AI’s next bottleneck may not be intelligence. It may be Earth.

    For the last two years, the AI debate has been mostly about intelligence.

    Which model is ahead? How fast are capabilities improving? Will agents replace tasks, jobs, or whole workflows? Can Europe regulate the technology fast enough?

    All valid questions.

    But the next constraint may be less abstract. It may be physical.

    Power. Grid capacity. Land. Cooling. Permits. Transmission lines. Water. Construction time. Capital allocation.

    The AI race is turning into a gigawatt race. And if the space-data-center discussion is any signal, the next frontier may not just be cloud regions. It may be orbit.

    My read: the executive conversation has to move from "Which AI model should we use?" to "What physical infrastructure does our AI strategy depend on?"

    The scale shift

    Chart showing typical data center power use from 5-10 MW to 100 MW and 1 GW
    The scale jump matters: 10 MW is a facility, 100 MW is industrial infrastructure, and 1 GW becomes a regional energy strategy.

    A modern hyperscale data center is not a large office building with servers. It is an industrial energy asset.

    The International Energy Agency says average data centers draw around 5-10 megawatts. Large hyperscale facilities increasingly require 100 megawatts or more. That number sounds technical, so translate it.

    One megawatt running continuously for a year equals 8.76 gigawatt-hours. A 100 MW data center therefore consumes 876 GWh per year, or 0.876 TWh. At 90% utilization, still roughly 0.8 TWh per year. The IEA compares this to the annual electricity demand of about 350,000 to 400,000 electric cars.

    A 1 GW AI campus is ten 100 MW hyperscale data centers. Running continuously, it consumes 8.76 TWh per year.

    For comparison, Germany's annual electricity consumption is roughly 500 TWh. The EU is around 2,700 TWh. The US is around 4,000 TWh. So one 1 GW AI campus would be small at continental scale – about 0.3% of EU electricity consumption or 0.2% of US consumption – but huge at local grid scale.

    That local point matters.

    Put a 1 GW load in the wrong county, with weak transmission and slow permitting, and it is not "0.2% of America." It is a grid emergency, a political fight, and a capital allocation problem.

    Now consider the language around terawatts. Elon Musk's recent "Terafab" discussion was about chip manufacturing, not a conventional data center, but the vocabulary matters. AI infrastructure ambition is moving from mega to giga to tera. A theoretical 1 TW compute or manufacturing footprint running continuously would consume 8,760 TWh per year. That is more electricity than the US and EU combined.

    That does not mean a 1 TW data center is around the corner. It means the ambition curve is now colliding with the energy system.

    The current footprint

    The IEA estimates global data center electricity consumption at 240-340 TWh in 2022, excluding crypto mining. That was around 1-1.3% of global final electricity demand.

    In large economies such as the United States, China and the European Union, data centers already account for around 2-4% of total electricity consumption. That is the average.

    The local reality is more extreme.

    The IEA notes that data centers have already surpassed 10% of electricity consumption in at least five US states. In Ireland, data centers account for more than 20% of electricity consumption. Denmark projects data center electricity use could rise sixfold by 2030 and approach 15% of national electricity consumption.

    This is the important distinction: globally, data centers are still a manageable share of electricity. Locally, they can become one of the dominant loads on the system.

    Goldman Sachs Research estimates data center power demand could grow 160% by 2030, with global data centers rising from roughly 1-2% of power consumption today to 3-4% by the end of the decade. It also estimates AI could add around 200 TWh per year of data center power demand between 2023 and 2030.

    Two hundred TWh is not abstract. It is close to the annual electricity consumption of a mid-sized industrial country. And it is only the AI-related increment in one forecast.

    The backlash is already here

    Chart comparing global data center electricity share with US, EU, Ireland and local grid impacts
    Global averages hide local pressure: data centers can reach double-digit shares of electricity demand in specific regions.

    This is no longer theoretical.

    In May, several local flashpoints showed the political side of the bottleneck. Seattle was weighing a pause on large data centers. Durham, North Carolina passed a 60-day moratorium on data-center development. A Texas county paused data-center construction in rural areas for a year. Utah approved a data-center project described as twice the size of Manhattan, triggering backlash. Tennessee was considering legislation that would let data centers self-power with limited regulation.

    Different places, same pattern.

    AI infrastructure is colliding with local politics. Communities are asking who gets the jobs, who pays for grid upgrades, who carries water risk, who absorbs noise and land-use impact, and who benefits from the compute.

    This is the part of the AI story many executives still underestimate. It is not enough to have GPUs. You need permission. You need interconnection. You need credible energy sourcing. You need community acceptance.

    The future of AI may be decided as much in planning boards and utility queues as in model labs.

    Why energy is now part of AI leadership

    Executive checklist for AI energy strategy and infrastructure planning
    AI energy strategy is now an executive checklist: economics, thresholds, model allocation, partnerships, and efficiency.

    For a long time, digital leaders could assume infrastructure would scale behind the scenes. Cloud abstracted away servers. SaaS abstracted away operations. Developers increasingly acted as if compute was infinite, elastic, and mostly someone else's problem.

    AI breaks that illusion.

    Training frontier models is energy-intensive. Inference at scale may matter even more because successful AI products are used continuously. Agents add another multiplier: they do not just answer one prompt. They plan, call tools, retry, search, generate, check, and act. A single user request can become dozens or hundreds of model calls behind the scenes.

    That makes energy not just an engineering issue but a leadership issue.

    If AI becomes a core production layer, power becomes part of product economics. Latency becomes part of geography. Energy procurement becomes part of risk management. Infrastructure partnerships become part of market entry. Sustainability claims become harder to defend if absolute consumption rises faster than efficiency improves.

    The better question is not whether AI uses "too much" energy.

    The better question is: are we using scarce energy for high-value intelligence, or are we wasting it on low-value automation theatre?

    The opportunity

    The upside is enormous.

    AI can help design better grids, forecast demand, optimize industrial processes, improve cooling, accelerate materials science, reduce waste, and make energy systems more flexible. The same technology that increases electricity demand can also improve how electricity is produced, routed, stored, and consumed.

    There is also a market opportunity.

    Companies that solve the infrastructure layer will not just be suppliers to AI. They will become strategic gatekeepers. Power developers, grid operators, data-center builders, cooling specialists, chip designers, construction firms, nuclear developers, storage providers, and energy software companies are moving closer to the center of the AI economy.

    This is especially relevant for Europe.

    Europe often frames AI competitiveness around regulation, foundation models, sovereignty, and talent. All matter. But infrastructure sovereignty may become just as important. If compute depends on power availability, grid speed, and data-center capacity, then AI sovereignty is partly electricity sovereignty.

    A European AI strategy without an energy strategy is incomplete.

    The space question

    Conceptual space-based AI data center with solar arrays orbiting above Earth
    Space-based data centers are not a near-term replacement for terrestrial infrastructure. They are a signal that the AI compute curve is pushing beyond the grid.

    The more provocative version of this debate is space.

    A few years ago, data centers in orbit sounded like science fiction. Now Bloomberg is writing about how to build them. McKinsey has made the case for space-based data centers. University researchers are exploring the idea because AI energy demand is rising. Google and SpaceX have been linked in recent coverage to the broader possibility of AI data centers in space.

    The attraction is obvious: continuous solar power, less terrestrial land pressure, potentially easier cooling through radiative systems, and the strategic appeal of moving part of the compute layer off Earth.

    The problems are just as obvious: launch cost, maintenance, radiation, latency, orbital debris, security, regulation, and basic economics.

    But the fact that serious people are asking the question matters. Space data centers are not a near-term replacement for terrestrial infrastructure. They are a signal. The AI compute curve is steep enough that people are looking beyond the grid.

    When a technology forces executives to ask whether the data center belongs in orbit, something fundamental has changed.

    What leaders should do now

    The call to action is practical.

    First: put energy into the AI business case. Every serious AI initiative should have a compute and energy view, not just a model and vendor view. If the project scales 10x or 100x, what happens to cost, latency, emissions, and capacity?

    Second: use real thresholds. A 10 MW workload is a large facility. A 100 MW workload is industrial infrastructure. A 1 GW workload is a regional energy strategy. Treat them differently.

    Third: separate high-value intelligence from low-value automation. Not every workflow deserves heavy AI. Use frontier models where judgment, ambiguity, and leverage justify the cost. Use smaller models, retrieval, caching, rules, and process redesign where they are enough.

    Fourth: make infrastructure a board-level topic. If AI is strategic, then power supply, data-center capacity, cloud concentration, and sustainability are strategic. CIOs, CTOs, CFOs, COOs, and sustainability leaders need one shared view.

    Fifth: build partnerships beyond software. The AI stack now reaches into energy markets, utilities, real estate, cooling, semiconductors, construction, public policy, and eventually maybe space.

    The leadership shift

    The first AI leadership question was: "What can this technology do?"

    The second was: "How does it change work?"

    The third is now emerging: "What does it require from the physical world?"

    This is where the debate becomes more serious.

    AI is not just a software wave. It is a capital investment wave, an energy demand wave, and an infrastructure coordination problem. The limiting factor may not be imagination. It may be megawatts.

    Executives should not panic about that. But they should stop treating it as somebody else's problem.

    Models matter.

    But electricity decides where the models can run. And if the curve continues, the strategic question may become even stranger:

    How much intelligence can Earth afford to host?

    Sources and further reading