5 ms·
Just to be clear, he's not "leaving." He got fired. He got fired because after the map fiasco became apparent, he refused to send out an apology or sign his nam
by mukaiji 14y ago
Just to be clear, he's not "leaving." He got fired. He got fired because after the map fiasco became apparent, he refused to send out an apology or sign his name to the one Tim Cook sent. (internal knowledge)
- jusben1369 14y agoNot sure if that's true or not but there's probably more to it than just that correct?
- mukaiji 14y agoWell he wasn't very liked either.
- pooriaazimi 14y agoBy whom? The (upper) management, or his team?
- mukaiji 14y agoBoth.
- gsibble 14y agoApple Security is probably outside your house as I write this.
- wisty 14y ago(No internal knowledge) I'm surprised he got fired over maps. Mapping is hard - comparable to writing a search engine. Apple did as well as can be expected for a first attempt. They had some kind of problem with Google Maps, and wanted to build their own capability, which was never going to be easy. He might have been fired if he cheated, by creating a well curated Valley dataset to prove to the other execs what a great job he'd done. That would annoy people. I've heard rumors that he was seen as "better managing up than down" (impressing his boss, at the expense of results), and that doesn't strike me as something Tim Cook would like very much (both from his reported management style, and the number of stock options he has). I can see that being a last straw from Tim - "You screwed up, now own up to it. Or else."
- bonzoesc 14y ago> I'm surprised he got fired over maps. Mapping is hard - comparable to writing a search engine. Apple did as well as can be expected for a first attempt. The problem is that they released that first attempt. iPhone and iPad weren't their first attempts at phones and tablet computers, they were simply the first ones good enough to take to market.
- gfosco 14y agoMapping is very hard, and he shipped it before it was ready. That was a pretty bad event for them; caused lot of negativity from users. I'm not surprised.
- brianpan 14y agoThere are ways of dealing with hard problems- managing scope, managing expectations. I'm not too surprised he was fired for not executing. Remember Papermaster and the antenna? http://daringfireball.net/2010/08/papermaster_damn_antenna http://daringfireball.net/2010/08/papermaster_damn_antenna
- spinchange 14y agoWhile it hasn't seemed to have an appreciable affect on sales or the stock price, the shortcomings of the new Maps have been an embarrassing PR mess for Apple and a hit to its reputation for uncompromising quality that sets it so far apart from everyone else. It does not surprise that he's being fired for this or that his departure is going to be transitional since he's so intricately involved with so many central aspects and initiatives at the company. (also no internal knowledge)
- ok_craig 14y agoThis makes me wonder - who at Apple decided it was necessary to make their own maps app? It's easy to blame Forstall for a crappy product. But if someone else was responsible for mandating the change, assigning him the project, and pushing an impossible deadline, maybe it's more their fault.
- Apocryphon 14y agoIt was a decision that was forced by a number of factors. Google wouldn't agree to providing directions for turn-by-turn navigation, so Apple had to seek other solutions.
- travem 14y agoThe guy was an SVP, passing the buck isn't really an option at that level. It's about ownership.
- ok_craig 14y agoI understand. I'm just wondering if he put himself in that position or if someone else did.
- fatbird 14y agoScuttlebutt is that it was an executive-wide decision based on the coming renegotiation of their 5 year agreement with Google regarding Maps. Google has been letting iOS maps lag behind Android maps (e.g., Android has turn-by-turn navigation, iOS maps didn't), so Apple was understandably not excited about renewing that agreement, and leaving themselves very vulnerable to one of their biggest competitors. But they didn't have something comparable, so they pushed a weak maps app early to catch Google off-guard--and they did. Google didn't have an app ready in the app store to replace the one they lost in the OS. That's my synthesis of the analysis of a bunch of Apple watchers, so take it with a bowl of salt. But it makes sense to me.
- jklp 14y agoReminds me of this quote from Steve: "Jobs tells the VP that if the garbage in his office is not being emptied regularly for some reason, he would ask the janitor what the problem is. The janitor could reasonably respond by saying, "Well, the lock on the door was changed, and I couldn't get a key." It's an irritation for Jobs, but it's an understandable excuse for why the janitor couldn't do his job. As a janitor, he's allowed to have excuses. "When you're the janitor, reasons matter," Jobs tells newly minted VPs, according to Lashinsky. "Somewhere between the janitor and the CEO, reasons stop mattering," says Jobs, adding, that Rubicon is "crossed when you become a VP." http://www.businessinsider.com/steve-jobs-on-the-difference-between-a-vice-president-and-a-janitor-2011-5 http://www.businessinsider.com/steve-jobs-on-the-difference-...
- wilfra 14y agoThanks for confirming this. It seemed obvious that his back-to-back failures with Siri + Maps and the fact that lots of people inside Apple hated him were the reason for this, but it was impossible to know for certain without somebody inside taking a risk and saying that. Care to speculate on who would be next in line to be CEO now? That was presumably Forstall. Now it would be Cue or Ive or...?