Is Developer Experience (as related to the culture DevOps facet I suppose?) off-topic here?
Would the strategy/methodology to qualify the level of Developer Experience significantly differ from strategies/methodologies known in the User Experience domain, applied to a given DevOps tool's UI?
How to formalize Developer Experience qualification strategy/methodology in DevOps toolsets where core asset is interaction with a tool's API?
To the second point, I may pay attention to situations where developer community discussing more or less their UX-related feeling, hope these examples are common: "this call is ugly".. "I am not comfortable with this interface".. "I don't like tool X"..
Specific problem: DX is a new field; working assumption is that good DX could make engineers happy as we know it from good UX. But it is not clear how to proceed (or if it comes out that such questions on DevOps are off topic the assumption is wrong and DX is rather a 'bad meme'.