What Apple’s org structure should look like

Rogifan

macrumors Core
Original poster
Nov 14, 2011
20,666
22,381


This is what I think Apple’s org should look like.

Software Engineering would oversee all of Apple’s core OS’es along with all pro apps

Cloud services (overseen by new hire) should include: iCloud, Siri, Maps, AL/ML; development should be iterative and constant (not tied to OS releases)

Content (Cue) would be Apple Music & TV and build out of original content business; located in LA

Prod Dev/App Store would include product liaison between hardware/software/design for all hardware products responsible for features and pricing; oversee App Store and developer relations

Basically removing cloud and pro apps from Cue and Siri from Federighi. Move Cue to LA and have him focus 100% on content services. Move Siri out from under Federighi. He’s got enough on his plate overseeing all the core operating systems. Also Siri should be it’s own platform and not tied to the OS. Siri should he updated on a regular basis not just when new OS updates are release.

Agree/disagree?
 

Rogifan

macrumors Core
Original poster
Nov 14, 2011
20,666
22,381
Why is "design" separate from hardware engineering? Why not split the silos by form factor or OS (really the same thing)?
Because design isn’t just hardware and has always had its own leader. Even if you think Apple should be organized by product instead of function I would argue things like design, marketing, finance, etc. should be shared across all products. Still I think Apple is fine being mostly organized functionally but they need a new org for cloud services. And Eddy’s hodgepodge org needs to be focused. What does Apple Music and original TV programming have to do with cloud services and iWork?
 

bbnck

macrumors 6502a
Mar 19, 2009
565
303
Software Engineering would oversee all of Apple’s core OS’es along with all pro apps
Unless Apple software comes out of thin air... wouldn't you say software engineering already oversees Apple's operating systems and pro apps?
 

ApfelKuchen

macrumors 68040
Aug 28, 2012
3,147
1,808
Between the coasts
Ummm... Retail stores? Tech support? Why a separation between Hardware Engineering and Hardware Technologies, but no Software Technologies to go along with Software Engineering (seems to be tucked into Cloud, but not entirely)?

Overall, it's not clear what you're trying to accomplish, other than taking some stuff off of Craig's and Eddie's plates and changing the upgrade/development cycle for cloud services. I don't see a compelling need to do any of that, but apparently you do. I'm interested in a more thorough explanation of your reasoning.

The basic problem with any alignment/realignment is that Apple produces integrated software/hardware/cloud products. The key to success is not the separation/allocation of duties, but the coordination and integration of all the various development threads. There are some who believe Tim has too many direct-reports already. Adding more may not be such a good idea.