3 ms·
Maybe it is simply a terminology issue, but what you describe, I would call it responsibility rather than ownership. Ownership implies strong exclusivity. Agree
by axlee 6y ago
Maybe it is simply a terminology issue, but what you describe, I would call it responsibility rather than ownership. Ownership implies strong exclusivity. Agree with your post otherwise.
- hrpnk 6y agoI agree that responsibility is what we are actually looking for. The term 'ownership' is popular in product teams [1] and in engineering career frameworks [2]. In the second example, it's defined as "The rest of that story is about owning increasingly heavy responsibilities". Even github allows defining code ownership through the CODEOWNERS files. [1] https://svpg.com/autonomy-vs-ownership/ https://svpg.com/autonomy-vs-ownership/ [2] https://open.buffer.com/engineering-career-framework/ https://open.buffer.com/engineering-career-framework/