In this episode of SHI’s Research Breakdown, we continue the conversation around the 2026 memory shortage with SHI Lead Field CTO Russ Cantwell and SHI Field CTO Steve Troxel. Drawing on Steve’s original research (featured in the February 20th edition of SHI’s Research Roundup), the discussion explores how supply constraints, AI-driven demand, and manufacturing dynamics are forcing IT leaders to rethink how they plan, design, and invest in infrastructure.

Rather than reacting to FUD (fear, uncertainty, and doubt), the conversation emphasizes scenario-based planning. Steve outlines how SHI's Strategic Technology Office models potential outcomes month-by-month to help organizations anticipate changes in availability, lead times, and pricing.

Russ expands the conversation by introducing a shift in mindset—designing infrastructure not just for uptime, but for availability over time. With supply disruptions now occurring more frequently, organizations may need to plan three to four years ahead and assume that at least one year of procurement could fail. This challenges traditional just-in-time models and forces a broader conversation around acceptable business risk and long-term capacity planning.

Finally, the discussion highlights a critical organizational shift: navigating supply constraints is not just an IT problem. CIOs, CFOs, and executive leadership must work together to balance cost optimization with resilience. As technology becomes inseparable from business performance, this moment represents an opportunity to strengthen cross-functional alignment and rethink how organizations prepare for disruption.

Discussed in this episode

The impact of the 2026 memory shortage on data center strategy
Scenario planning as a tool for navigating supply uncertainty
AI-driven demand and its effect on memory allocation and pricing
Designing infrastructure for multi-year availability, not just uptime
Rethinking just-in-time procurement models
Aligning CIO and CFO priorities around risk and investment
Treating IT as a business partner, not a service provider