IBM placed bets on highly speculative "moonshot" programs like IBM Watson (especially Watson Health) that failed, while simultaneously failing to effectively compete in the growing cloud-centric market. IBM could have been a realistic contender in the Enterprise against AWS, Google, and Microsoft cloud environments, but it instead opted for large-scale vendor lock-in style approaches.
IBM has stalled due to poor business decisions. But those decisions are a symptom of bureaucratic system of IBM and those who know how to navigate it.
You can't divorce the actions of a company from the people who constitute the company.
Well yea, most of their headcount is consultants now, right? Corporate America might not be a democracy but neither can executives change the culture by edict.
No more proprietary OS lock-ins; Windows even can run Linux in a subsystem now (WSL). VSCode is open source.
I’d say he’s been fairly successful in changing the corporate culture.
Time will tell if Azure is any worse or better than the other cloud providers wrt lock-in.
Blaming all the people that has been long in the company without individually evaluating their performane is bad and lazy management. To target people by age, as only older people can have been so long in the company, it's discrimination on a protected class.
Are you really justifying firing people indiscriminately based on age, or other proxy parameters like decades working for the company?
I've met many older (40+) excellent technical people at IBM and usually their situation was that they were afraid of change and became used to IBM insanities, but gradually they are taking the leap of faith and jumping ship (AWS is taking them by the bucket). The feedback I get from those who left is that they can't believe they put up with IBM's crazyness for so long, as the other companies seem so lean and rational in comparison.
One thing IBM still has a talent for is training tech professionals as I met some truly great ones there.
This seems the fate of every company. As a company grows, the stake for making a mistake becomes higher to some employees. So they install processes. They add red tapes. They slow down everything in the name of preventing disasters. In the meantime, a company can't innovate or grow all the time. Sometimes they get into a plateau. And behold, when there's no grow, those who are good at grabbing land will win, and they are the incumbents who do not care about or are not capable of innovation. The results? The company dies, its talents going to other companies, and a new generation of companies rises.
That's why it's so much important for people, at least for most, to chase growth. Growth begets real meaningful projects. Growth makes turf war less relevant (you can't get rid of it entirely). Growth sweeps most of the ugliness under the carpet until, well, the growth stops.
Apple may not be a bad company but it has survived out of pure luck.
That's a good way of putting it. There is this "managerial comfort zone" that goes straight up the org chart. I have observed managers evolve to optimize the environmental constraints, delivering the correct messaging, delays, and target zone realignments, just but knowing how to apply the correct templates. On the other side, this has caused top-down management to evolve to push back on these constraints, creating unreasonable landing-zones knowing they will not be hit. It is a crazy passive-aggressive arms race.
Maddening. It is these boondogglers who should be excised due to nepotism and failure to deliver, as well as their enabling upper management. However, the knives-out behavior of the early 90's has changed to "you pat my back..." as competition has vanished leading to monopolies who are free to stroke each other.
Sources: my experience at IBM, Intel, and Microsoft. Among other companies that weren't as large.
Being a "business operator" really has a value there and most of the leadership is made of old timers simply because of how they know how to navigate (and circumvent) all the millions of gates and layer-over-layer of non-value added processes.
Maybe if IBM worked to remove the "Old timers" from the leadership while, at the same time, bringing in older, experienced professionals, but without the vices that 15/20 years at IBM brings, it could be justified.