| ▲ | georgemcbay 3 hours ago | |||||||||||||||||||||||||||||||
> My favorite bit about this is how none of the execs want to take ownership of the change, but instead trying to put someone else in the hot seat and/or start a Committee. And with the exception of John Martin's reply (which recognizes that there are deeper problems they should think about, but seems resigned to the fact that that won't happen) the focus is pretty much entirely: "let's fix the exact issues Bill Gates ran into trying to download this one product we produce" (out of many hundreds/thousands) rather than "let's fix the root causes that caused us to arrive in this place to begin with". I haven't worked at any companies as large and siloed as Microsoft, but I'd assume this is pretty common for them, at least if they don't have a Steve Jobs-like tyrant who both has all the power and is singularly product focused. | ||||||||||||||||||||||||||||||||
| ▲ | Twirrim 3 hours ago | parent | next [-] | |||||||||||||||||||||||||||||||
There was nothing surprising in that email chain at all, looking at it as someone with lots of experience in large companies. In a twisted kind of way, the replies were reasonable and logical. They're not dumb, they can see it was crap. No one org can actually own this fix, so in that kind of situation it realistically requires someone like Bill to choose someone to drive it, and demand updates to ensure that everyone gets aligned. Telling his execs, especially in a company so notoriously political and "empire" oriented as it was, isn't going to work. I actually liked that in Amazon, Jeff Bezos used to send out the infamous "question mark" emails on such a regular basis that they built an exec commitee specifically for the purposes of driving direct action on problems. Didn't matter where you were, or what you were working on, if that question mark email came you dropped everything to work on it. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||
| ▲ | vjvjvjvjghv 3 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||
It's very common. From a certain level up, execs rarely use the products they are responsible for. It's all about strategy, committees, meetings, plans and reports. For them the product is just an abstract thing. When I rented a Buick car, I thought to myself that there is no way any decision maker ever tried the car and thought that this is ok. I think one of the strengths of Apple during the Jobs days was that Jobs actually sometimes seemed to use the products himself and gave feedback. When I look at the blatant bugs MacOS and iOS had in the last years, I also think that the current Apple big shots never use their stuff or they would have noticed. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||
| ▲ | noir_lord 2 hours ago | parent | prev [-] | |||||||||||||||||||||||||||||||
> I haven't worked at any companies as large and siloed as Microsoft, but I'd assume this is pretty common for them. Doesn't need to be that large, I worked for a company that ~4500 employees with about 1000 at HQ, that entire email chain looks exactly like what would ensue every time someone at the C-level flagged an issue. I suspect the reason is much the same, no one wants to be in the hot seat to fix a problem they have no faith they can fix so everyone plays hot potato with the flaming sack of shit until it bursts and lands on someone. > Fish begins to stink at the head, not the tail. (13th Century Persian Proverb) | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||