Я уже писал раньше, что клево, когда у компании есть набор лаконично сформированных принципов. Например тут про дзен GitHub или про дзен Python.

А вот тут про принципы Heroku: https://gist.github.com/adamwiggins/5687294

PDF на будущее, если вдруг ссылка перестанет работать.

Цитата из этих принципов. Как раз про DRI:

“Every product, feature, software component, web page, business deal, blog post, and so on should have a single owner. Many people may collaborate on it, but the owner is “the buck stops here” and makes the final call on what happens with the owned thing.

…

The owner can and should collect feedback from others, but feedback is just that: input that the owner might or might not choose to incorporate into their work. If something doesn’t have an owner, no one should be working on it or trying to make decisions about it. Before those things can happen, it has to be owned.

…

Ownership can’t be given, only taken. Ownership can’t be declared, only demonstrated. Ownership begins with whoever creates the thing first. Later the owner may hand it off to someone else. If an item gets dropped for some reason (for example, the current owner switching teams or leaving the company), it’s fair game for anyone else to pick up.”

И еще

The status quo is never good enough.

…

Be blunt, honest, and truthful. Constructive criticism is the best kind. Avoid keeping quiet with your criticism about someone or something for the sake of politeness. Don’t say something about someone to a third party that you wouldn’t say to their face.

…

Nothing is real until it’s being used by a real user. This doesn’t mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

(цитировать можно многое - отличные принципы)