1. Leader escalates issue to his team 2. The team scrambles to come up with a solution 3. No one wants to take ownership. #NotMyProblem 4. weeks or months are spent on 'developing a plan' 5. nothinghappens.jpg
So nothing got done.
So the temperature on the issue went up.
So management whose failure was their own could only think of engaging more managers and processes….
Never ended.
I work at small companies now, less money but I enjoy it more. I just fix things and everyone is happy.
It results in the equivalent of treating an infection with Tylenol rather than antibiotics. The exact symptom reported by a "Leader" will usually get fixed, but in a more of a "KPI hacking" rather than a fundamental fix to the problem. I have seen a "Leader" point to the staggering number of support tickets as a problem then have teams make it incredibility difficult to open a support ticket. The number of support tickets plummets and the first report to instruct their team to do so gets rewarded and all other teams follow suit. Have a leader point to complexity of the sign up process, and have teams "simplify" the signup process by just taking an email to create the account, then make the experience of doing anything post sign up a broken mess because you forgot to go into settings and filling up all the required details. Or have a leader complain about the install process like in this example, and have teams just bundle massive dependencies or make wide horrific modifications to the users machine to "simplify" the install process. Now suddenly installing a video editing software also modifies your default video player, your HDR or scaling settings, your audio device setup, and your keyboard layout (because why not?)
Large companies are why large companies are large (in IT/OT at least)
Standard psychology says they should be highly sensitive to status loss, but it almost seems the opposite.
Existing in a large org over the long term becomes a game of survival. It's very much similar to the "dark forest" or the Eye of Sauron. Your number one goal as an IC is to complete the tasks directly assigned to you by a supervisor and avoid at all costs any kind of "hey you" assignments that have zero upside and plenty of possibility for downside. It would be wonderful if we lived in a world where individual initiative mattered and was rewarded, but it doesn't. It becomes "why haven't you delivered XYZ", and the vague ephemeral reasoning of "well A, B and C for team D needed fixing" is not an excuse, and now you can't pay your mortgage anymore.
How much money does movie maker bring Microsoft? Now which executive would want to prioritize movie maker so much that they would directionally alter the company to fix this? Consider the issue that the execs had was fixing all the issues involved a huge number of teams.
Discredit to Bill here but I honestly think he was the only one who had the power to fix this. A Jobs-like figure is the only person with the organizational power and freedom to drive details like this to completion. Anyone else would end up in a power struggle
The only thing that can prevent it is a flat organization but one that has enough structure so an unofficial hierarchy can't form. And making that work is hard.
I’ve been in this situation in a small company as well. The owner wasn’t managing the company and there was no other manager. So the owner would express his frustration in an all hands meeting “I don’t like x” or “we’re going to do y from now on” but he would not assign the task to anyone, or give ownership. He would come up with some insane new goal but no plan, no equipment, and no one person who’s in charge of making sure the required resources, time and responsibility is assigned. So nothing would change, a month later there would be another meeting, with a middle aged man having a tantrum about why did no one do anything!? Why is no one listening to me?
You might be thinking it’s a good opportunity to accept some responsibility, it might get you a promotion or be a good learning opportunity. Yeah I tried that for a while, if you succeed, congratulations, you now have one new task for which you’re responsible for without any extra compensation or benefit. If you fail? Well guess who’s getting the blame..,
If you provided leadership in your case then I think it’s different
I think the thing that really made it horrible is like I said. The boss would say x needs to happen but would not think through the details, buy the equipment, allocate the time or human resources. Someone still had to work out how to do those things and who was going to do what.
In the end if there are enough incentives(usually money) people would work on those.
Agreed. Even at companies known for having a great culture and being "different from the rest", the Game of Thrones politics is still there - it's just more hidden and polite. I was a senior exec in the biggest BU at just such an F100 valley tech giant for >10 yrs (one level from the CEO). The company actually did have a nicer environment than its peers, no 360 reviews, no 'up or out' mandates, and a vibe genuinely a cut above.
While the net effect was more pleasant day to day and teams were insulated a few more levels down than most places, the brawling over headcount, budget and revenue attribution was simply practiced far more artfully. Sadly, I think it's just endemic to the breed of "large public corp" and while the best may be better, none are immune.
> Someone decided to trash the one part of Windows that was usable? The file system is no longer usable. The registry is not usable. This program listing was one sane place but now it is all crapped up.
This is so true, and not only under Windows. Install any modern program under any modern OS and have a look at the filesystem, it's a flaming mess. Nowadays the only solution "smart people" have found is to install a complete system, complete with libraries and frameworks, for each program.
I miss the days of simple executables.
One of my "santa's not real" moments of computing was realizing how much static and dynamic libraries fucking suck. This cannot be overstated, and is illustrated perfectly by the heroic efforts of software vendors to get away from them.
Okay, a few functions like fopen are fine - but even those are syscall wrappers IRL. But every OS seems to have concluded, that in the place of API calls, one should rather have streams of text (UNIX) or binary messages (Windows, also a bunch of Linux desktop stuff, like Wayland), or File I/O.
Basically a major motivation behind JIT langauges (C#/.NET certainly) was an effort to get away from dynamically linked libraries,
Even DOS didn't really have libraries, you had peripherals mapped to memory at certain addresses, and a set of interrupts, and that was it.
These single file Go and Rust programs read and write stdio and/or network, which is a reasonable solution to a lot of problems, but certainly not all of them, especially in the interactive space.
And linked libraries are interfaces mapped into memory at certain names. I think that's an awesome improvement.
Did I just dream up loading a mouse driver and MSCDEX in DOS?
Every day I drop 1k lines of Python code and replace with go. Will be fully go soon!
made me irate. It was very clear! Read the issues and be accountable for fixing them?
Sadly, even though most of these philosophies have been discredited over the long term (stack ranking can be fine if you do actually need to do layoffs, so long as you realized there are exceptions to the rule), other bad management practices have also taken over. We're now squarely in the depths of all the worst aspects of "product driven" development, where nebulous metrics are measured for success (such as the bad VSCode decision to append copilot in commit messages, which makes it look like copilot is more heavily used than it is).
When people compete internally on Microsoft, what are they competing on if everybody works in a different horizontal?
Instantly reminded me of this especially apt comic:
https://pbs.twimg.com/media/EyJfRwHWYAI0_yt?format=jpg
[1] Also available here: https://www.reddit.com/r/ProgrammerHumor/comments/6jw33z/int...
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.
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.
This is how learned helplessness looks like when you’re a high level executive.
Must be nice being so useless, yet getting paid so much.
Though I guess these people must have been good at politicking to rise so high.
This goes right back to the leadership failure on Bill's part. If your company is structurally incapable of producing good products (which Microsoft assuredly is and still was) then it's on you as the CEO to implement the correct structures.
That's literally the purpose of upper management: you create the conditions for success to happen.
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.
Or they do and they don't think it's worth their time and energy to get them fixed. I think they just don't care about their products, unlike Jobs.
The crazy thing is that it's more likely that most people in Apple are using their own products, versus any of the Android phone manufacturers or within Google, where it's likely a few of them would be using the Apple ecosystem instead.
Many of them are definitely dogfooding it, but it's possible that there are communication or empowerment issues.
But since a few years it goes up and down daily by 100 GB or more. Sometimes I have 350 GB, sometimes I have 100 GB. I think it has to do with Time Machine snapshots and purgeable space (whatever that means) but it's totally useless now. I can't tell for sure if I can copy 250 GB to my disk or not. It may fail now but work 2 hours later. How come nobody notices such a fundamental thing not working? Somehow the dogfooding doesn't seem to work. Or maybe the Apple people all have 8 TB disks so they don't care.
https://eclecticlight.co/2025/02/28/friday-magic-how-to-make...
Yeah, I wonder what's going on within the macOS division, but then again Liquid glAss is a thing.
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)
Once bad culture gets to your company, it doesn’t matter the size.
If the big boss is frustrated by the UX, they might send an angry email or even yell at you in person. If your division doesn't meet its sales projection for the quarter, you might get fired.
If BillG had wanted a company that made good user experiences, he'd have hired (and fired) for that. Sending a pissy email is what you do when you're annoyed but don't actually care enough to do anything about it.
They are arguing about not wanting to take ownership because they know the organizational structure is going to be an impediment. The problems Bill describes could not have been solved by Microsoft without a massive internal restructuring. We know this because Microsoft's UX is still abysmal.
Nobody wants to have the inevitable failure hung around their necks by "owning" something that depends on the cooperation and coordination of departments that don't report to them.
https://bonkersworld.net/img/2011-06-27_organizational_chart...
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.
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.
This feels like an email that should have been blasted to the entire company. Top-down, empower employees to think of a more unified experience. Then again, all of the external jokes about Microsoft indicate that every department is fighting for their lives against the others, so that kind of kumbaya togetherness was never going to happen.