/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Legendary MLPS team behind Cisco's “spin-in” R&D strategy resigns in apparent disagreement with roles following recent reorganization

Move comes after last week's announcement of management changes involving three of the four executives  —  Four Cisco Systems Inc. executives …

Wall Street Journal Don Clark

Context & Ripple Effects

This resignation is the final act of a two-step demotion. In March, CEO Chuck Robbins broke Cisco's engineering unit into four teams — networking, cloud services and platforms, security, and applications and IoT — via an all-hands email on the four-team reorganization. Days ago, sources reported that three of the four executives behind Cisco's spin-in R&D strategy were shifted into advisory roles; today the whole MLPS team walks out instead.

The departures cap a year of leadership churn under Robbins, who took over from John Chambers with co-presidents Rob Lloyd and Gary Moore exiting and CTO Padmasree Warrior leaving shortly after. The MLPS team matters because the spin-in model was one of Cisco's signature R&D mechanisms — funding internal teams as startups, then reacquiring them.

First-order effects

  • Cisco loses the entire MLPS team outright rather than retaining them as advisors — the advisory-role compromise announced last week failed within days, leaving the spin-in pipeline without its architects.
  • Robbins' four-team engineering structure now stands unopposed internally; the executives who embodied the old model have removed themselves rather than accept reduced roles in it.

Second-order effects

  • The spin-in mechanism — which seeded ventures Cisco could later buy back — loses its internal sponsorship, raising the question of whether future Cisco acquisitions must come from outside rather than from homegrown spin-ins.
  • Departing networking talent has a proven landing spot at Arista Networks, where former Cisco insiders already turned customers into competitors — the same exodus dynamic that later cost Cisco key accounts per the Arista rivalry coverage.

Third-order effects

  • If the pattern holds, the Robbins era marks a structural break from the Chambers-era spin-in playbook toward a centralized, product-line-organized engineering org — trading entrepreneurial autonomy for integrated execution across networking, security, cloud, and IoT.
  • Repeated senior exits during a CEO transition can normalize departure as the response to reorganization, making retention of technical founders and architects a recurring governance problem for large acquirers that run internal venture models.

The trend: Cisco under Chuck Robbins is dismantling the Chambers-era spin-in R&D model in favor of a centralized four-team engineering organization, with veteran architect teams exiting rather than accepting advisory roles.