5 ms·

Curious why it is so hard to find an owner to the issue. Gates' experience started with the web UI, then I'd expect that the team who owns the microsoft.com or

Curious why it is so hard to find an owner to the issue. Gates' experience started with the web UI, then I'd expect that the team who owns the microsoft.com or owns the experience. To them there are only two types of bottlenecks: their web pages (usability, JavaScript performance, ways to get backend data, and etc), and their immediate dependencies. So, they drive improvement on both types of the bottlenecks, and the owners of the immediate dependencies recursively handle their own. For instance, the web team will identify that calling the catalog API has a P99 latency of 5 seconds and the network is fine, then they ask the catalog API to improve the API latency. If the catalog team does not do the obvious, the team's manager gets punished. Of course, I'm being naive here, as I've seen too many companies fail to achieve such basic ownership. So, curious what I have missed. Of if the ownership is not a clean DAG, well, it goes back to Gates, as he was responsible for both the org charts and the company culture.

Telaneo 8d ago
It wouldn't surprise me that what seems like whole things from the outside are split up even further on the inside of Microsoft. There's probably no single person responsible for microsoft.com (nor was there at the time). Instead the front page is one team, Windows Update (at the time) was yet another team, and sales another, and then there are 5 other teams doing other things, and no single individual or group is responsible for the whole thing. They've all got permission to push things to the website and change whatever just from time immemorial, and not through any defined authority, since that authority doesn't actually exist. You can still see symptoms of this today. MS will (or at least would) spin up new domains rather than just update microsoft.com, or create newthing.microsoft.com, since both of those require talking to whomever is responsible for the main domain. Even if that person exists, knowing who they are in an org like MS is already a big ask when it's organised the way it is. Meanwhile, buying a new domain likely takes less than an hour, even if you include billing and such.

Telaneo 8d ago

It wouldn't surprise me that what seems like whole things from the outside are split up even further on the inside of Microsoft. There's probably no single person responsible for microsoft.com (nor was there at the time). Instead the front page is one team, Windows Update (at the time) was yet another team, and sales another, and then there are 5 other teams doing other things, and no single individual or group is responsible for the whole thing. They've all got permission to push things to the website and change whatever just from time immemorial, and not through any defined authority, since that authority doesn't actually exist. You can still see symptoms of this today. MS will (or at least would) spin up new domains rather than just update microsoft.com, or create newthing.microsoft.com, since both of those require talking to whomever is responsible for the main domain. Even if that person exists, knowing who they are in an org like MS is already a big ask when it's organised the way it is. Meanwhile, buying a new domain likely takes less than an hour, even if you include billing and such.