Who wants to play?
Overhead roles:
Anything not tied to revenue.
DEI: definitely
Most VPs and above: yep.
StRaTegY: for sure
Other suggestions?
13 replies (most recent on top)
Mind your own business, Punk. Your legacy sales force is shoveling the coals, delivering results, so that you can sit on your a-s and be a CE some day
Half of VMware sales could be replaced by dedicated pre sales architects and post sales Customer Success people at half the cost.
VMware pays far too many people on every deal.
Sales management is busy scheming to save their empires. Splitting into regional management instead of keeping the leaner global managers means VMware has to support 4 teams of sales management middle when one central team could have carried the pipeline paperwork.
Such a waste of resources that could be better spent in customer acquisition or customer success.
We had a whole DEI team? How many people? I just thought it was the usual suspects harping on the social cause du jour.
@1ywa+1lrOdqcN Is spot on
For a company that can only innovate by acquisition, acquisitions are managed terribly. Pure incompetence.
Hiring that Dei team was an absolute pi-s take
All of HR is sh!te. Corporate cavities.
M&A teams - brings in companies, lays-off who they can, puts new SKUs on our price books for these products.
No wait, KEEPS the original companies' price books and support policies, KEEPS the original web site and billing systems in place while also having SKUs on VMware books, takes years sometimes to migrate them to our systems. All causing a serious amount of duplication, cycles wasted, $$ wasted, and often serious confusion to Field and Partners. And, many of these products tank anyway.
Csms
Internal marketing
Sebu
Most of HR
Ssms
DEI.
The DEI team.
The DEI program managers.
DEI
"I think the functions are mostly needed, here and any business."
Why is DEI needed?
If you're taking the line of 'not tied to revenue', that is also a significant amount of R&D. Architects, full-stack devs, and those extra 1-2 people per team that gives them the flexibility to handle issues without breaking deadlines. PMs and Devs working on features that are slated for 2025 and beyond are just wasting space and writing the same documentation over and over until it's time for their feature to be implemented.
It's easy to dunk on outside teams. When looking internally, many people don't realize that they may not be as important as they think they are.
If you took some of these functions away, core would complain that they’re overwhelmed with work. Spread too thin.
I think the functions are mostly needed, here and any business. The problem with vmw is that the operating model is excessive and lacks modern capabilities which makes it exceedingly ineffective.
That marketing department I worked with in my role. Half a dozen people including VP creating internal only collateral ...