1) What is the purpose of the product/platform/work? Typically when speaking of software generally there is only one correct answer: automation. If the stakeholder cannot answer this question in 2 words or less nothing else matters, because this the foundation from everything else derives.
2) How does the stakeholder define product quality? Do they measure any of that? If there are not written goals AND measures its probably all bullshit.
3) How directly are incentives tied to the defined product quality goals? If I have to count the hops using two hands there are no product quality goals.
4) What is the target audience of the product quality goals? In theory the primary audience should that which is the primary driver of revenue, but in reality it is typically that which is of greatest comfort to people analyzing requirements. This is where things get toxic. This is what makes me want to abandon software as a profession.
5) Incentives are not necessarily compensation.
With this list in mind the typical goal of a corporate software developer is to complete some tasks, get paid, and retain employment. Product quality is completely irrelevant up to and including some tolerance for terminal failure.
