1. For culture difference: I have heard YouTube culture is quite different than their parent (Goog) before and after aquisition.
2. After Microsoft's acquisition LinkedIn, from various anecdotes, not only LinkedIn culture is maintained differently but employees salaries are different (salary difference not entirely due to LinkedIn presence in valley vs Seattle - when both LinkedIn's and Microsoft's office exist in a same country outside USA, the employees have different level of perks and monetary compensation).
After experiencing that I started to periodically write at amazons elevator whiteboards “Twitch is NOT Amazon” as little petty rebellion.
Thanks for this, it goes a long way toward explaining how Cisco has a software list and a written offer for GPL for their products, and Meraki has an unpublished email address ([email protected]) that they ignore for months on end.
I often wondered how Cisco, who was famously sued for GPL non-compliance after the Linksys acquisition, could repeat that blunder with Meraki.
Their handling of enterprise customers is what lost them our business to Atlassian (also ugh).
Post-Microsoft, the product has been championed by the right owners. Enterprise works great, and we happily came running back. It only took five years for them to make the necessary adjustments.
Microsoft did that.
Tech tends to suffer from employees getting bored and wanting to do cool stuff that is totally disconnected from the business.
It seems that thanks to its network effect and Microsoft's guidance, Github managed to retake the lead.
They paid an incredible amount of money for Slack because of what Slack is. In my opinion, it doesn't really matter that Slack ceased to exist (which I agree de jure it did) because de facto the Slack culture still exists as a minority now. If anything, the incentives at Salesforce should be to preserve Slack, not whittle it down, because they thought Slack was worth billions of dollars. Is Slack's technology really worth that much? Maybe, maybe not. Is Slack's customer base worth that much and do they have a big enough moat that they won't start evaporating? Maybe, maybe not. More likely the value at Slack was created by the sum of its parts together, including culture.
Maybe you can make the argument that Salesforce thinks they bought a company that was worth less than the sum of its parts and that they can unlock value by making changes, but the acquisition and "culture clash" imply to me a big corporation throwing money at something they don't really understand.
As an analogy, it's like house-flipping - the acquirer needs to have a very good "eye" for potential, and then needs to put in significant work to realize that potential. As I understand, this is the model that Danaher follows with their acquisitions, but they're only able to do this because of that unique set of skills they possess internally, which sounds to me not that qualitatively different from regular synergy.
* To prevent a competitor buying it
* Because a competitor already bundles something similar and you don't
IE, as a stop loss, rather than better growth prospects.
Many acquisitions work that way.
The total number of sales of their product plummeted, but the acquiring company didn't care, all they cared about was a that a large enough fraction of the people currently using the standalone version or on of their competitors platforms switched to their platform to get to keep using those features.
I've been really surprised at how naive senior people in our parent company are on this front. Many have spent their whole careers at this one company, so they have very limited understanding of anything that doesn't align to what their company does.
Combine this lack of experience with a big dollop of hubris (they work for BigCo!) and it's easy to imagine a well-intentioned executive destroying the value of the acquired team and product.
Which is kind of wierd since the culture as reflective of a company’s emergent collective decisions are what makes the product of a company succeed. If an acquirer isn’t buying the culture, they may as well stay a customer unless they think their own culture can make a product that supplants the acquired one’s and retain the customers.
And it’s usually not explicit that the acquired companies culture is ‘removed’ - rather top down decisions that don’t make sense for them (due to culture differences) end up being applied, and end up mangling things and forcing prior strong culture people to leave.
There are multiple groups of people (old owners, new owners, sellers-employees, buyers-employees, customers), multiple assets (physical, intellectual, human, customer-base, code etc)
To ascribe failure to and acquisition I think means taking the viewpoint of they buyer - did the get what the wanted, or not? Not the viewpoint of employees or customers.
"A cottager and his wife had a Hen that laid a golden egg every day. They supposed that the Hen must contain a great lump of gold in its inside, and in order to get the gold they killed [her]. Having done so, they found to their surprise that the Hen differed in no respect from their other hens. The foolish pair, thus hoping to become rich all at once, deprived themselves of the gain of which they were assured day by day."
https://en.wikipedia.org/wiki/The_Goose_that_Laid_the_Golden...
What you said might be true for the majority of acquisitions at that scale, but it is by no means a strict rule.
A tree can be chopped down in an afternoon.
All it takes is for the next CEO to decide to undo this and it's undone.
It’s a fundamental change in dynamic.
If you want to boost numbers this quarter and don't care too much about intangibles, the incentives really push towards gutting the acquisition.
A CEO of an independent company has different incentives to a CEO of an acquirer.
The culture of Microsoft has gone through radical changes between gates, balmer and nadella.
But a culture isn't _only_ a reflection of the leadership, it's all the interconnections of people and organizations within the whole company.
A leader can come in and make changes, and often these changes first have to break everything that's there already; without care what replaces the broken structures is just chaos; by default that chaos is the governing culture without more inputs and work from leadership.
These changes are most pronounced when 2 large organizations become one because both cultures have inertia (whole foods / amazon, slack / salesforce, etc). But yes, of course when CEOs change there's change to the corporate culture, but because there's only the force from the CEO's changes not entire cultures bashing into entire other cultures, the changes tend to be more gradual.
I am not an MBA or sociologist or really anyone with a worthwhile opinion, I've just been around the block and have the stories to tell or retell...
Leadership, however, has changed.
(Extreme example, there are many others. Carly Fiorina's demolition of HP comes to mind.)
I always assumed Microsoft is to blame, but apparently not!
The point of OP is not that the Borg will assimilate you from day one. Inertia, operational convenience and upper management laziness can delay the implementation of the hegemonic culture - why mess with a division that works? The point was that there should be zero expectation of changing the corporation's culture to match yours, they paid 27 billion so that you no longer have an independent voice on the market and be forced listen to them.
Because of how corporations operate, with strong internal diffusion of management and operational practices, the assimilation will happen, it's just a matter of speed. The old company has ceased to exist.
Culture will fade, politics will kick in, etc
Linkedin was because everyone needed to have a “social” strategy back then and apart from maybe Dynamics, there’s no real synergy (I don’t like that word) between LinkedIn and Microsoft’s other businesses.
The GitHub acquisition was part of their plan to start repairing their fractured relationship with developers - almost a PR tool.
In both cases tight integration with the rest of the organisation makes less sense than Salesforce buying Slack - which is something that could be tied directly into Salesforce’s core business.
Buying Slack was Salesforce's way of getting back into that market.
1: https://techcrunch.com/2010/09/07/salesforce-takes-chatter-m...
I won’t be surprised if soon you can spin your backend on Azure in 2 clicks from VSCode because your code is on GitHub. Stuff like that. Maybe it won’t be advertise on the GitHub directly. But for sure it will be there available in 2 click on the Azure and VSCode.
How does that work? I imagine they don’t all pile into one server. Do you just have zero organic connection to 99% of your colleagues?
They aren't really your colleagues in the sense you're thinking.
Companies that big get broken up into departments or business units that function pretty close to separate businesses (until you get to the top of them, then it merges back a bit). Those are your colleagues, and most of the people you interact with.
(and of course yes, there can also be big general-purpose channels with a lower signal-to-noise ratio)
When I was at IBM, they had...uh...a lot of them.
And if you insist on not changing, you are better off to change the job entirely.
I've worked at places that acquired companies, and aspects of the acquired companies' culture persisted and sometimes spread beyond their group.
I'm pretty sure it could be sold, thus it exists. Or used to exist and could exist again?
hmm, there seems to be some misunderstanding. simplifying, there are two types of acquisitions: holding and integration. for holding a company getting acquired remains quite independent. for integration the company getting acquired is integrated into the parent. how this integration happens is up to both participants. sometimes both companies have to change, other times one company imposes their culture over the other. but from what i’ve see, IT companies (especially american) definitely prefer deep integration into the parent. in other fields (and nations) holding is more popular.
Trying to force two organic entities to merge into your vision. You have a very small chance of that working out. So small that, as an investor, I don't trust it will benefit me.
It is very profitable from the engineers perspective to keep insisting you work for Slack as long as possible though. If you just immediately roll over you’ll lose your old culture and benefits immediately.
> And all those promises about Slack being independent and autonomous? Well sure, that was the plan
Do you think you and I know this pattern but the executives of Salesforce and Slack don't? It wasn't the plan, it was lies; they knew what was going to happen.
For example, a holding company can buy your company and do ... absolutely nothing, just treating it as an investment. This happens a lot too. Off the top of my head, AMC was once owned by Wanda Group based out of Dalian, Liaoning, China. Yet I'm sure that nobody who worked for AMC could tell, or even knew this was the case.
They bought the company and tech. The company built the tech the way it did because of the people, and the people found the best way they operate. If salesforce wanted to have a salesforce built product they would have done that, but they bought slack. who’s to say if slack would be successful if the people are forced to act like salesforce?
And then I’m stuck with both “Salesforce” and “Slack” emails, and have to use “Salesforce” and “Slack” Slack channels.
And all those promises about Slack being independent and autonomous? Well sure, that was the plan, but now Slack is a part of Salesforce and Salesforce makes decisions that make sense for Salesforce, not Slack. So no, you don't get your own sales team, and no, you don't get your own customer support team. You're part of Salesforce now, it doesn't make sense. Oh and no, you aren't going to get the benefits you were getting at Slack, you don't work at Slack, you work at Salesforce, and hey! Some of those benefits may genuinely be better. Those HR reps that sorted all your perks at Slack? They're working in a Salesforce HR department now (if they weren't fired) and they're working to give you the Salesforce benefits.
It's a tough message but when someone buys the company you work for, you no longer work at the old company, you work at the new company, no matter what anyone says.