# Structure Network Operations Around Teams, Not Heroes

DevFeed: [Structure Network Operations Around Teams, Not Heroes](<https://devfeed.tech/articles/worth-reading-leading-intelligent-networks-11408.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/06/worth-reading-heroes-teams/>)

Published: 2026-06-16T06:06:00Z

Content type: opinion

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Networks](<https://devfeed.tech/topics/networks.md>), [Network](<https://devfeed.tech/topics/network.md>), [Automation](<https://devfeed.tech/topics/automation.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [automation](<https://devfeed.tech/tags/automation.md>), [network](<https://devfeed.tech/tags/network.md>), [network-automation](<https://devfeed.tech/tags/network-automation.md>), [networks](<https://devfeed.tech/tags/networks.md>), [operations](<https://devfeed.tech/tags/operations.md>), [teams](<https://devfeed.tech/tags/teams.md>), [worth-reading](<https://devfeed.tech/tags/worth-reading.md>)

## AI overview

An article argues that network operations should be structured around teams rather than individual heroes, suggesting that hero-dependent cultures can make network automation harder to deploy.

## Source excerpt

Chris Grundemann wrote an interesting article arguing that you should structure your network operations around teams, not heroes. Even if you feel you're perfectly OK with your network being held together by exhausted heroes (and duct tape), it could be a bit harder to deploy network automation in an always-busy hero culture. However, the choice, as they say, is yours.