Slashdot Mirror


How Steve Jobs Solved the Innovator's Dilemma

hype7 writes "With yesterday's release of the Steve Jobs biography, a raft of interesting information has come to light — including Jobs' favorite books. There's one book there listed as 'profoundly moving' to Jobs — The Innovator's Dilemma by innovation professor Clayton Christensen. The book explains how in the pursuit of profit, good managers leave their companies open to disruption. There's an interesting article over at the Harvard Business Review that explains how disruption works, and how Jobs managed to solve the dilemma by focusing Apple on products rather than profit."

5 of 424 comments (clear)

  1. But can he solve the First Post dilemma? by Anonymous Coward · · Score: 3, Funny

    He can't because he's dead.

  2. Re:How long... by Dunbal · · Score: 5, Funny

    If Christianity is any metric to measure this by, we're going to be hearing about Steve Jobs for at least the next 2100 years...

    --
    Seven puppies were harmed during the making of this post.
  3. Re:MBAs Prevent Disruption by bmo · · Score: 2, Funny

    Mod parent funny.

    --
    BMO

  4. Re:How long... by Anonymous Coward · · Score: 3, Funny

    I wanted to wait until his next biography to find out if Zombie_Jobs rises again.

    ...it's been more than three days.

    We need to wait 75 years for someone to promulgate a resurrection + subsequent disappearance/ascension myth. Maybe a little longer, given current lifespans. Preferably, the promulgator will be someone with admin access to archive.org in order to "tweak"/"harmonize" historical accounts. The promulgator can also publish three different accounts under different pseudonyms to give the appearance of corroboration of the "historical" account.

    4 bonus internets if the promulgator can integrate parthenogenesis somehow producing a male Jobschrist.

  5. Re:Nice if you can do it by BasilBrush · · Score: 4, Funny

    With that, he walked over to my desk, found the power cord to my Apple II, and gave it a sharp tug, pulling it out of the socket, causing my machine to lose power and the code I was working on to vanish. He unplugged my monitor and put it on top of the computer, and then picked both of them up and started walking away. "Come with me. I'm going to take you to your new desk."

    Now I understand why OSX has got so good at not losing unsaved user data when unexpected power loses happen. ;-)