[Aloisius]

> Require ownership all the way to prod and beyond, no matter the role. (Turns out people tend to really like that.)

Depends on what you mean.

Individual ownership over code/feature/module/etc would seem to run counter to the article - it's just another fiefdom.

Collective ownership? Sure.

[T-Winsnes]

I think the right balance here is to have ownership of the outcome rather than the thing. E.g. you have ownership of making sure the feature you’re working on makes it to production and works properly

With that ownership comes there responsibility and accountability of making sure it happens. The level of responsibility and autonomy that comes with that is what I’ve found people react positively to

[Aeolun]

Ownership to ‘make sure it happens’ is entirely different from being able to ‘make’ it happen. The first is absolutely toxic.