When you’re an exec in charge of a whole area, the buck stops with you and, to quote Steve Jobs - the reasons stop mattering.
As a user I don’t care about having “extraordinary insight into the development process”. All I know is you’re vice president of interface design and the interfaces are getting worse over time.
When I worked for someone else (now self-employed), some bugs were my fault. But with features and other intentional changes, the bosses had to sign off on them, and in some cases there were vigorous internal debates, but the bosses had the final say and could overrule objections.
No, he is saying that we should blame the person who has command responsibility. It is pretty well-established principle in jurisprudence actually.
The stockholders do not make design decisions but only elect the board of directors. The board of directors do not make design decisions but only elect the CEO. The former CEO Steve Jobs did make design decisions, but the current CEO Tim Cook appears not to make design decisions, delegating that to subordinates. Alan Dye is Vice President of Human Interface Design at Apple. He does make design decisions; indeed that's in his job title. Dye previously reported to Jeff Williams, COO, but Williams just retired, so it's unclear who Dye reports to now. In any case, Dye is likely the person at Apple who has the final say on design decisions.
There are tens of thousands of interface designers who would be able to make a better interface than what is Tahoe and iOS 26. One of them should have the job.
So if you hired a plumber to install a new faucet or whatever, and he totally fucks up (eg. floods your entire kitchen), you're saying we shouldn't blame him, we should blame... you, for hiring him in the first place?
>not the people who could have said no?
Going to the plumber example, you're saying that you should be hovering over him to catch any mistakes? Isn't the whole point of hiring a professional is that you don't have to worry about stuff like this? If you're able-bodied and are going to have to supervise the whole thing, why bother hiring someone?
If Mac as a whole is a disaster, then whoever is responsible of that needs to be fired.
If Mac hardware is a disaster, then whoever is responsible of that needs to be fired.
If Mac software is a disaster, then whoever is responsible of that needs to be fired.
If Mac software UI design is a disaster, then whoever is responsible of that needs to be fired.
And of course the people above are responsible as well. But in this case there's a very obvious project which has failed.