VMware Explore is ten weeks out and the content catalog hasn't dropped yet. June 23 is when that changes. Until then, every expectation in this industry is still uncontaminated by official messaging — and that's exactly the condition under which a useful wishlist gets written.
Once Broadcom publishes the keynote and the session lineup, our mental frame shifts. We start evaluating what was announced against what was promised. We stop asking what we actually need and start reacting to what we were given. So I'm writing this now, before the slide decks arrive, while the questions still come from the field rather than from the press release.
The keynote will tell us where Broadcom wants to take the platform. I'll be watching to see how close that is to where practitioners actually need it to go.
Here's what I'm watching for — component by component — going into VMware Explore 2026.
The power is there. Nobody serious disputes that NSX's distributed firewall is capable — micro-segmentation at the hypervisor layer, east-west traffic control without a bump in the wire, policy enforcement that travels with the workload. The capability story is solid. The day-two operational complexity is where we lose people. Security teams who didn't grow up in a software-defined networking world look at the policy model and flinch. I want to see Broadcom lean into simplification without sacrificing depth — better guardrails for teams coming from traditional firewall backgrounds, cleaner audit trails, and an operational runbook story that doesn't require a three-day training engagement to hand off.
What I'm watching for: Any session titled around NSX operational simplicity or day-two management. That's the signal the product team has heard the feedback from the field.
vSAN Express Storage Architecture adoption has been slower than the performance numbers would suggest it should be — particularly in mid-market environments. The ESA story is genuinely compelling if you're building net-new on Gen11 hardware with NVMe. If you're running a mixed fleet with legacy OSA nodes and a team of two, the migration conversation gets complicated fast. The performance differentiation is already proven. What I want to see is a clearer operational differentiation story — specifically, what does the day-to-day management experience look like for a team that isn't running a dedicated storage engineering function? That's most of the market.
What I'm watching for: ESA operational sessions aimed at mid-market or mixed-fleet environments. Right now the content skews toward greenfield enterprise deployments.
Aria Operations is impressive when you use all of it. Most shops don't. The observability stack has matured significantly — capacity analytics, cost management, workload optimization — but the adoption curve is steep enough that a lot of organizations are still running on dashboards they built in 2019 and haven't touched since. I want to see what the entry point looks like for teams who are just getting started: what's the minimum viable configuration that delivers real operational value, and how do you get from zero to useful without a six-month implementation engagement? The product is capable. The on-ramp needs work.
What I'm watching for: Aria adoption sessions, quick-start content, and anything framed around teams migrating from third-party monitoring. That framing is where the real audience is.
That's the whole ask. SDDC Manager has gotten considerably better as the central orchestration layer for VCF lifecycle operations — bundle management, cluster expansion, certificate lifecycle, upgrade orchestration. The bones are good. The surface area still requires more manual intervention than it should for routine operations. Patch day in a VCF environment should feel closer to a pipeline trigger than a checklist. I want to see continued investment in the automation surface — API coverage, integration hooks for external orchestration tools, and fewer steps between "I need to do X" and X being done.
What I'm watching for: SDDC Manager automation sessions and anything touching VCF API surface area expansion. This is where the platform earns or loses the argument against manual sprawl.
Multi-workload domain configurations are where VCF gets genuinely complex — stretched clusters, cross-domain networking, workload mobility across domains with different transport zone configurations. The architecture is powerful and the use cases are real. The documentation and session content hasn't always kept pace with the complexity of what customers are actually building. My home lab runs a nested VCF environment specifically to pressure-test these configurations before they touch production. I want to see sessions that go deep on the edge cases — not the clean reference architecture, but the real-world topologies with existing network constraints, mixed hardware generations, and operational teams who didn't start greenfield.
What I'm watching for: Multi-workload domain and stretched cluster deep dives. Any session that uses the word "brownfield" is getting added to my schedule immediately.
The setup for September
I'll be revisiting each of these five areas after the keynote and session catalog drop on June 23 — and again after the event in September. The post-event debrief writes itself: did Broadcom deliver on what practitioners actually needed, or did the announcements land somewhere adjacent to the real problems? That comparison is the most honest product review you can write about a platform release.
The nested lab I've been running at home on VMware Workstation has given me a cleaner picture of where the friction points actually live than any whitepaper has. That's the vantage point I'm bringing into Las Vegas. Four days of immersion, hands-on labs, and Hub conversations with the engineers who built these features — and then we'll see how close the wishlist was to the roadmap.
Catalog drops June 23. I'll have session picks posted the same day.
RG
Robert Greenlee
Systems Engineer · Sacramento, CA · robertgreenlee.com