I'd argue folks in ethics roles shouldn't be responsible for actually creating the systems, processes, and practices required to put those concepts into practice. That's what engineering, product, and people leadership are for.
AI ethics is first and foremost about setting policy and advising on how those systems should be constructed.
This is because ethics isn't some separable function. It threads through everything an organization does. You can't just treat it as another department/function/unit if you want any hope of actually making it work.
> I'd argue folks in ethics roles shouldn't be responsible for actually creating the systems, processes, and practices required to put those concepts into practice. That's what engineering, product, and people leadership are for.
I agree with you, but then we have HR for a reason.
Haven't we seen from history that handing down policy from your ivory tower is a disservice to all involved? Or do we think out of touch politicians accurately represent the interests if their constituents?
Another example you might be familiar with is enterprise architects. When you spend all of your time in theory you lose sight of practical implications. Of course, since you only had the idea, when it doesn't go to your ideal it can always be blamed on the implementers.
I am not in the AI ethics field, but I've watched multiple tech-adjacent disciplines that say "that's what engineering and product are for" get subsumed by engineering and product, who don't really care for a group that sees themselves above implementation. Based on history alone, that's what I expect to happen whether you agree with that or not, and I suspect this tension is driving at least part of the role of AI ethics at companies trying to turn profit.