What Apple’s org structure should look like

Discussion in 'Apple, Inc and Tech Industry' started by Rogifan, Apr 8, 2018.

  1. Rogifan macrumors Core

    Rogifan

    Joined:
    Nov 14, 2011
    #1
    [​IMG]

    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?
     
  2. AidenShaw macrumors P6

    AidenShaw

    Joined:
    Feb 8, 2003
    Location:
    The Peninsula
    #2
    Why is "design" separate from hardware engineering? Why not split the silos by form factor or OS (really the same thing)?
     
  3. Rogifan thread starter macrumors Core

    Rogifan

    Joined:
    Nov 14, 2011
    #3
    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?
     
  4. bbnck macrumors 6502a

    Joined:
    Mar 19, 2009
    #4
    Unless Apple software comes out of thin air... wouldn't you say software engineering already oversees Apple's operating systems and pro apps?
     
  5. ApfelKuchen macrumors 68030

    Joined:
    Aug 28, 2012
    Location:
    Between the coasts
    #5
    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.
     

Share This Page