Speaking as a former resident deep in Cue's org, I believe this is common knowledge internally, but there isn't alignment on how to address it. Even at the IC level, most people I spoke with are aware of Apple's shortcomings in services. Services are not the favored child at Apple. iOS and hardware are, because of revenue. Services ICs know that, and it hits morale directly; I saw (and felt) this. There are attempts to fix it, too, but those manifest as reorganizations. I was subjected to four in a year and a half.

You hear pains from teams like Maps, who were moved from iOS to services during my tenure, and who immediately ran into serious organizational problems, dried up budgets, and so on. The gettin' is good in iOSville, and once you leave iOS, it's a whole 'nother Apple. There's a common story about the origin of Maps at Apple where Maps was basically given a blank check, and they're still mopping up some of that excess to this day. That doesn't happen in services.

Meanwhile, organizationally, Siri is kind of outside the typical services structure for various legacy reasons and they're off iterating like all getout and having a blast without the encumberance of the services organization. Every time I met with Siri I always came away with questions like, in this organizational climate, how on earth are they getting so much done?

Apple needs a serious Microsoftism on services. If you would have told me five years ago that Microsoft under Nadella would completely reverse course and embrace the living hell out of services while Apple meandered in the "let's buy companies to implement our services strategy" grasslands, I'd have said the opposite is more likely, yet here we are.