>> a clear statement of the importance of the team's overall success, not their personal triumphs This doesn’t jive with my experience of devs i can see fittin

>> a clear statement of the importance of the team's overall success, not their personal triumphs This doesn’t jive with my experience of devs i can see fitting with the OP’s description. Talk of team success just isn’t on their wavelength, you may as well talk about the weather. It’s a different value system, it values heroism, it values cleverness, it does not value useful business outcomes like maintainability or cost of ownership. For keeping them on track, they can sometimes respond to automated controls better than to people telling them what to do. A linter in the CI pipeline will usually cause them to follow a style where another person could simply never convince them to make the same change. But everyone’s different and so even this is not guaranteed.