14 ms·
Leaked Slack all-hands meeting reveals a ‘strong culture clash’ with Salesforce
- Traubenfuchs 4y agohttps://archive.ph/vjgMy https://archive.ph/vjgMy
- defnotahuman 4y agoI was part of a small startup (about 50 employees) that was acquired by a big publicly-traded tech firm about 5 years ago, and boy was that experience interesting. Before moving to the new office, we were told that we were getting our own dedicated section of the building to ourselves so we could continue to collaborate freely and develop our product since our work was fairly niche and we had a very different tech stack from the rest of the org. We show up on day 1 and there's no dedicated space for us. We're moved a few times over the first few months, but it was clear that zero effort went into planning our arrival. About 6 months after the move-in, our customer support team is moved to be with the rest of the parent company customer support org (something they told us would never happen). A few months after that, they tried to take away our hybrid work perk (for years, we could work from home Tues, Wed, Fri and they promised to honor this after the acquisition), relenting only after being told the change would cause attrition. For two straight years, it was nothing but lies and broken promises. Alongside all of this, I saw an unfathomable amount of wasted effort, millions upon millions upon millions in engineering pay being lit on fire. They had a whole team dedicated to building a shitty front end component library that we all had to use to reskin our apps in order to achieve design consistency. We could've used a mature tool like MaterialUI but nooooooo, this hot mess of a component lib was our great gift to the open source community. My favorite part: we constantly ran into cases where the provided components didn't meet all of our UI behavior needs, but the development backlog for the UI team was 2 years so we had to fork the components and make our own changes, which other teams were doing as well. It was the worst of all worlds. It boggles my mind that companies can grow to be so big, so dysfunctional internally and yet still turn a profit or appease investors. It was the first time I felt like companies were getting too big.
- mathattack 4y agoIt boggles my mind that companies can grow to be so big, so dysfunctional internally and yet still turn a profit or appease investors. It was the first time I felt like companies were getting too big. The power of economies of scale…
- shapefrog 4y ago> yet still turn a profit or appease investors They are absolutely miles away from NOT turning a profit, and investors want them to make even more money. The ultimate "functional company" that has succeeded doesn't exist, in the survival of the fittest the dysfunctional companies have risen to the top. Perhaps the academic and armchair literature of what it takes to make it are not as accurate as they like to believe they are.
- pitched 4y agoThank you, this is a really interesting framing! What do you think the objective function might be that gets min/maxed by being dysfunctional? Something about minimizing the harm from poor decisions?
- granshaw 4y agoYes once you reach a certain size, predictability >>> everything else. This trickles down, and risk aversion becomes the name of the game even at the individual level
- zug_zug 4y agoThank you for this. Really illuminating to here raw stories unvarnished with a forgetful idealism.
- tjpnz 4y ago>They had a whole team dedicated to building a shitty front end component library that we all had to use to reskin our apps in order to achieve design consistency. I feel awful for the engineers who end up working on these efforts, it's heartbreaking and ultimately a wasted endeavour. Your small team can't keep up, people start working around you (even actively undermining you) and eventually that company edict forcing everyone to adopt said library is forgotten in the name of expediency. I've seen it so many times now to the point where it's become a farce.
- achow 4y agoTony Fadell in his book 'Build' gave insight of the culture clash when Google acquired Nest. Not only with Nest employee, but with himself as well - he decided to vote with his feet and quit Google. Excerpt from the (excellent) book: ..But as more Googlers joined our ranks and Nest employees started understanding what kinds of perks were typical at Google, there was a huge internal debate about what people were and weren’t getting. Why did Googlers get massages? Why did they get more buses so they could come in late and leave after lunch? Why did they get 20 percent time (Google’s famous promise to employees that they can devote a fifth of their time to other Google projects outside their regular jobs)? We want 20 percent time! I said it wasn’t happening. We needed 120 percent from everyone. We were still trying to build our platform and become a profitable business. Once we got there, we could talk about employees using Nest money to work on Google projects, get a free massage, and end their workday at 2:30 p.m. As you can imagine, my positions weren’t popular with the new employees. But there was no way I was going to let entitlement creep in when there was still so much left to do. I wasn’t going to parcel out more perks just because Google employees were used to them. The experience of being a Google employee is not normal. It’s not reality. .. And that’s why I left. Not just because Google was trying to sell Nest or because they wanted me to stop acting like a parent CEO, but as a warning to my team. I was under a gag order, so I couldn’t tell everyone that something was seriously wrong. But I could show them. ..if you’re a CEO or high-level executive and you can see the water level rising before everyone else, then it’s your responsibility to signal clear and present danger to your team. And there’s no clearer sign that something ain’t right than you walking out the door. You can’t assume acquisition will mean acculturation. That’s why Apple doesn’t really buy companies with large teams. They only acquire specific teams or technologies, usually very early in their life cycle when they’re pre-revenue. That way they can easily be absorbed and Apple never has to worry about culture. They can also skip the inevitable duplication of functions between existing teams like finance, legal, and sales, or the painful process of integrating one large team into another. https://www.amazon.com/Build-Unorthodox-Guide-Making-Things/dp/0063046067 https://www.amazon.com/Build-Unorthodox-Guide-Making-Things/...
- SilverBirch 4y agoFadell also just talked a bit about this on the "On with Kara Swisher" podcast : https://podcasts.apple.com/us/podcast/peering-into-the-future-with-tony-fadell/id1643307527?i=1000592603154 https://podcasts.apple.com/us/podcast/peering-into-the-futur... He says a similar thing, but the tone comes across quite different.
- SilverBirch 4y agoThere seems to be a certain consensual hallucination that happens with these acquisitions. The acquirer says "you're amazing, you do great work, we don't want to change a thing, you'll still be completely autonomous, we'll just help you accelerate". And there's a good reason for it, the employees came to work for Slack, not Salesforce and if they all quit then the acquisition will have been a waste. So Salesforce makes all the same promises, but at the end of the day there's reality. The second Salesforce bought Slack, Slack ceased to exist, and all the workers now work for Salesforce. There's no culture clash between Slack and Salesforce. There's a Slack culture that once existed, and now there's Salesforce culture the company those workers now work at. You can embrace it, you can be unhappy, and you can leave. But remember, you're at Salesforce now and those other 70,000 workers - they joined the Salesforce culture, not the Slack culture and they sure as hell didn't buy you because of your culture. 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.
- achow 4y agoThis is mostly true. However, there are acquisitions which managed to keep their unique identity and even different salaries (!) after getting acquired. 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 of LinkedIn, from various anecdotes, not only their previous culture is maintained but employees salaries are different as well (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).
- decafninja 4y agoA similar case is when a big conservative company creates an internal “innovation lab” that promises tech startup like culture. I’ve been in places like that, and it seems more often than not the big bureaucratic processes of the parent company inevitably leak into and then consume the “startup” group.
- ciropantera 4y agoYes, I've been in this situation too. What at a first glance might look like the best of both worlds - low bureaucracy and solid funding - turns out to be the worst of both worlds: all of the bureaucracy of the mother company plus the risk of the whole project getting the axe every quarter because it doesn't make any profits
- lamontcg 4y agoI've watched that happen at companies and seen the "startup" fling servers out in front of the firewall that got hacked in minutes due to default root passwords because part of the deal was completely bypassing all of the rigid bureaucratic internal IT controls.
- rchaud 4y agoA lot of these 'labs' just ended up as tenants for WeWork's most expensive properties. The 'innovation' had to have the highest possible visibility I guess.
- j-bos 4y agoI wonder if this has anything to do with the exfiltrated Slack source code. https://news.ycombinator.com/item?id=34257646 https://news.ycombinator.com/item?id=34257646
- capableweb 4y agoNo, the problem seems to be the disillusion by Slack leadership that somehow Salesforce would incorporate Slack culture rather than Slack culture slowly being morphed into Salesforce culture. > “The problem has been, there’s no incorporation of the Slack culture into the Salesforce culture,” Butterfield said, according to an audio recording of the meeting obtained by Fortune. “And unless there is some element of that, then it’s not integration in any sense. It’s just the elimination.” Not sure how anyone would think a acquisition would lead to the parent company starting to incorporate bought company's culture into their own, haven't seen that in the wild anywhere.
- supersync 4y agoWhat’s sobering is even a prescient leader like Butterfield was snowed despite that clear evidence. I tell everyone founder - acquisition is the death of everything you worked for. Acquisitions teams are sales teams with 0 follow on accountability, structure, or goals. They are quite literally there to tell you what you want to hear & get you to believe it’s true. With maybe the exception of Microsoft, it’s not.
- atdrummond 4y agoMcDonell-Douglas, despite being the acquired party, destroyed Boeing’s engineer-led culture and replaced it with an accountant-led one instead. A big reason why the unimaginative 737MAX was allowed to proceed and more innovative projects like the 797 floundered or were cancelled. Even the 787, which should have led to massive Boeing orderbooks due to its prescience, was hamstrung by battery issues right out of the gate.
- paxys 4y agoWhat's the relation between the two stories other than company name?
- Caitlynmeeks 4y agoHard to imagine something as loving and magical as Tiny Speck's game, Glitch, wound up getting pivoted into office productivity software acquired by a titanic mediocrity such as Salesforce. As a former Glitch player it just makes me think of drinking bureaucratic water.
- readthenotes1 4y agoOne change guru had an often unspoken rule: -Culture follows Process (Especially the budgeting process).
- maxbond 4y agoSeems to me it's reflexive, eg, process shapes culture and culture shapes process, but you if you buy a company you can't per say change the culture. Not like a light switch anyway. But you can do that to processes.
- readthenotes1 4y agoOnce you get processes in place, the only way to change the culture is to change the processes. By that time, usually have a HR department and it's game over...
- maxbond 4y agoYou can change culture by hiring people with a fresh outlook, talking to people about what the culture is and what it should be, setting expectations, etc. In short, you can change culture by participating in it. I was in a meeting once where my manager said, "We aren't working evenings anymore." The visible relief that ripped through the room was something to behold. There was never a policy of working evenings, and there wasn't a policy of not working evenings afterwards. But my manager was using their leadership to make positive change in the culture regardless. But things like that can't be quantified and so are only visible to people in the trenches. But culture isn't actually someone measurable; it exists in the space between people. An acquiring company is unlikely to be interested in such nuances. It takes time, it isn't guaranteed you'll get your way (indeed, you'll be asked to make concessions), and it's an ongoing process with no definite end where you can declare victory and check a box. When you try to change culture through dictates instead of discussion - you may never hear about it, but people will understand that that means you don't see them as people, but as living automata to be programmed through policy. You'll lose their trust. That said. I went of vacation just after that meeting. I came back from vacation to work on a deploy until after midnight. A regret I have was not speaking my mind, "guys, we said we weren't going to do this." (I probably did, but not vocally enough.) Not setting an explicit policy against working evenings was a mistake, because the problem wasn't just the expectation from others on the team that, if you're here I should be here too, but also that the rest of the organization didn't respect our boundaries, and would dictate timelines and such without consulting us, implicitly demanding that we work crazy hours. It is important to codify values as policy. But it should be organic and driven by the people who are involved and understand, not executives of an entirely different company who are trying to squeeze blood from a stone. This is inherently incompatible with using policy to change culture.
- sfdcthrowaway9 4y agoI started at SF In the last 15 months. I was frankly surprised how primitive Salesforce’s use of Slack was when I got there. Since then there’s been a ton of workflows created but the (Slack) culture is still a bit weird. i think the workspace itself was created around the time of acquisition. Some teams were using Slack, but it was piecemeal at best. Some of those workspaces got folded into the workspace. 1. Threads for everything everywhere, always. People are practically afraid to not use a thread, even in team channels. 2. Little to no #random culture. People are afraid to meme? Maybe if you find some of the weirder channels you see it 3. Terrible GUS integration. There was no GUS integration at all when I started. (GUS is Jira implemented on Salesforce). There’s all sorts of other things I could say about GUS, but the worse thing I suppose I could say about it is that I miss Jira. GUS bot, I think, is implemented with APEX, so it’s kind of like the SDK for Salesforce I think. Not sure if this is dogfooding or it was just what the team knew. From GUS, you can create some channels in GUS for an incident, for example, but I think that’s inverted compared to how Jira sort of can do things (i.e. you should be able to look at guess and find everywhere something was discussed, but it’s not posible) 4. No integrations for internal Github 5. One workspace. Not that terrible though. Slack employees are all homed in their workspace. 6. It’s impossible to write your own Slack app to connect to. More generally, it’s hard to just run informal internal tools at Salesforce. I think people used to do that now with Heroku, but that’s sort of deprecated and I think there’s network/security reasons why. There’s other things, but I can only guess on the Slack side they’d see some of these things and be annoyed For some reference, I’ve been on Slack for over 8 years and came from Hipchat. Edit: 7. Nobody uses Huddles, Google Meet is heavily used. I think slack use culture has improved a bit. I would say it’s still very strange to see the list of Slack apps installed to be so small. I understand it’s for security reasons. I’m mostly happy at Salesforce - and most work happens on Slack.
- autarch 4y ago> 1. Threads for everything everywhere, always. People are practically afraid to not use a thread, even in team channels. My new(ish) employer does this and I absolutely love it. Channels are not a constant stream of interleaved noise, and when I want to dive into a particular conversation it's incredibly easy to follow.
- Waterluvian 4y agoIs Salesforce one of those Atlassian companies that just buys stuff and welds it together into some monstrosity that technically solves every problem?
- hiyer 4y agoI don't know how it works from the culture pov, but Salesforce has a few products that can be used independently - mulesoft, tableau, heroku, and of course, slack.
- needcaffeine 4y agoIs the joke that every one of those is an acquisition?
- rwaksmunski 4y agoSalesforce is an Oracle/Java webapp from 1999 + a whole bunch of poorly integrated acquisitions. It's a miracle it works at all.
- thelittleone 4y agoI have never met a sales person that enjoyed the salesforce user experience. As with many of these enterprise apps, they are to shine for the people who sign the check, corporate finance. Nice reports, lots of governance, horrendous UX for the sales force. "Who cares.. they always whinge, just tell them they have to use it."
- SSLy 4y agowhat software do they enjoy?
- CSDude 4y agoBeen in an Atlassian acquistion from a smaller startup. AMA
- raincom 4y agoSalesforce bought slack for $27B. In the span of two years, its market cap came back to pre-pandemic levels. If slack stayed as in independent company, its worth would have been $9B. If Slack wants to impart its culture across Salesforce, it has to prove itself as a heavy profit generator.
- ojbyrne 4y agoIt’s been my experience that journalists often cherry pick questions from employee Q & A to generate a story. This seems to be a series of 3 related questions from one employee.
- wolverine876 4y agoAs these companies follow the trend of trashing employee-driven cultures, which highly value employee contributions (rather than 'bossism'), there must be a supply of highly talented people who want this culture and who a company that embraces it could attract. Many of these people may prioritize that over annual pay. And this culture has worked very well for SV - the most successful center of business in possibly generations.
- Uptrenda 4y agoI'd be curious what exactly the 'cultural clashes' are? You would expect a whole article about such a thing to ah... at least list some? Like, is it longer work hours? Less pay? No free lunch? Less or more 'family friendly'? More emphasis on the customer? IDK what because nothing was brought up...
- foepys 4y agoFrom my experience when a small company gets acquired it's often because people are no longer having the freedom they previously had. The last company I worked at was acquired by a 100x larger company and "do whatever you want" turned into "fill out 3 different forms for each feature, plus meet with at least 3 senior people every week where you have to defend your design decisions to people unfamiliar with your domain and requirements. Also, you cannot hire new people locally, instead you need to use the offshore team from now on who have zero domain knowledge and are often only junior devs without experience".
- bryanrasmussen 4y agoIn my experience the single biggest differences between company cultures tend to be caused by size and industry of the company (some industries have a great deal of regulation, others not). I don't know what the differences are between Slack and Salesforce's "cultures" from reading the article, does anyone here?
- hbarka 4y agoTableau is suffering the same fate. https://www.geekwire.com/2023/tumultuous-times-at-tableau-salesforce-cutbacks-impact-senior-leaders-and-longtime-employees/ https://www.geekwire.com/2023/tumultuous-times-at-tableau-sa... “You don't understand. I coulda had class. I coulda been a contender. I coulda been somebody…” — Terry ‘Tableau’ Malloy
- hrpnk 4y agoDoes anyone know any good books/blogs about Tech M&A that describe the deal structures and post merger integration strategies?
- Def_Os 4y agoSalesforce culture is actually pretty great. This is largely an apples-to-oranges comparison between a startup in hypergrowth and a giant in recession mode, IMO.