The Tech That Connects Us

The episode has useful technical moments - the lateral-movement risk of SD WAN interconnections, the 'islands' framing for future branch architecture, and the SASE vs SSE distinction - but they are buried under an extended career autobiography, generic leadership platitudes, a quickfire personal-interests round, and a diversity anecdote. Substantive density per minute is low.

“the fact that you can get into a network and then jump onto an interconnection, whether that's MPLS or SD wan, means you have lateral movement, means you can move around uh, the enterprise and um, that's a problem”

“we keep pouring investment into, into security and what are we getting?”

The self-aware 'right the wrongs of my career' framing and the 'building islands instead of interconnected networks' concept are genuinely fresh angles from a practitioner. However, most of the rest - zero trust evangelism, servant leadership, DevOps silos collapsing - is thoroughly recycled industry consensus.

“I've spent my career building these artifacts of of trust. And to me, that was completely wrong. I should have gone a different way”

“I think the future about branch connectivity is not going to be about interconnections between a branch and a location. It's going to be about building islands”

Spiegel has genuine practitioner credibility - he was effectively customer zero for an SD WAN startup and oversaw a real infrastructure transformation at Columbia Sportswear at measurable scale. His current field CTO role is vendor-side evangelism rather than operating at scale, which limits the ceiling.

“became basically customer number one for them. Um and had really a lot of input into the product”

“we went from a full rack of equipment down to about three devices. So um, pretty dramatic change”

The Columbia Sportswear era supplies real numbers - store count growth from 7 to 150, rack reduction to 3 devices, 10x Internet vs MPLS cost differential - but the strategic security content is almost entirely abstract, with no customer data, breach statistics, or measurable outcomes from the current vendor role.

“when I started there they had maybe seven retail um, stores. Uh, and over the 2000 and tens that grew from seven to 70 and then 70 to 150”

“the cost per megabit of an Internet line versus an MPLS line, it's significant 10x”

The hosts are recruiters, not security operators, and it shows: questions are uniformly broad and generic, there is zero pushback on any claim, and a substantial portion of the episode is devoted to personal-interest softballs entirely irrelevant to a B2B audience. No interesting thread is ever pulled.

“What does leadership mean in the digital age?”

“How will automation and DevOps continue to drive change in cloud environments?”