We know most management everywhere is incompetent at best, but creating a new top level post about it almost every day shows you can't grasp the failure created by everyone else. The bugs that have been eating your development budget alive weren't created by managers in meetings, nor were they created by deadwood. IT can't configure Cisco network gear. Marketing lives under the delusion that any given feature will only be purchased by the market in a single week and if you don't complete an 18 month program before that week only a few weeks away Cisco won't sell anything ever again. There is a reality disconnect at every level.
6 replies (most recent on top)
Run the business, let the managers do their jobs without the social engineering.
Cisco has been unable to develop software for at least 30 years, long before the intercontinental links were fast enough to fully support development on other continents and an eternity before DEI. Management hasn't been able to manage during that entire time.
csco pretty much su-ks at engineering so don't think that they figured this out any more than figuring out how to write decent code.
You must have rewritten all four routing and switching operating systems from scratch in the past few years because the code was a giant bug riddled, insecure cut and pasted mess. Static analysis used to pump out an encyclopedia of problems on any given branch. The bugs that are escaping into conservative releases should be an embarrassment to you all.
What would Fran's political commissars do if they weren't driving progressive agendas into broken Cisco organizations?
Oh, I know, maybe they could help those organizations run more smoothly instead of creating completely made-up lists of the oppressed and the oppressors.
Maybe let the managers cut based on performance and not have to scale the diversity garbage in. I figure 3% of the uselessness could be cut if that wasn't in play. It shouldn't matter what color you are or if you identify as a newt - HR and the political bias at csco is past pathetic. Run the business, let the managers do their jobs without the social engineering. csco pretty much su-ks at engineering so don't think that they figured this out any more than figuring out how to write decent code.
Agreed too many communists here
LC the Queen Bee will never survive without her favourite worker bees. She needs to feel like she is the centre of attraction. Cut too many worker bees and she’ll feel “exposed”. Far safer to cut the worthless management layer fat. Get rid of the drones.
This is all a remnant of Chambers' strategy of flooding the market with overlapping products to squeeze out any competition and to maximize Cisco's market share. He wasn't concerned in the least when Cisco acquired multiple companies with the same products because, for a time, Cisco was supply constrained versus demand constrained. Because of that, there was no planning/oversight across product lines. In fact, Chambers encouraged internal competition between product teams.
Unfortunately, once Cisco started experiencing demand constraints, no one in senior leadership decided to create cross-product planning/oversight. It's why there wasn't really any actual product management at Cisco. The people called product managers were incented to shove as many features as possible into their specific product regardless of whether customers would ever use those features or whether it creates complete overlap with other products in Cisco's portfolio. This led to massive over investment in many product lines, too many operating systems with diverse implementation of the same feature, and a lack of investment in new technology spaces that may have led to future growth.