Maybe the non-engineers don't have much of a reference on what a better solution would look like.

Everytime an engineer tries to push slack on a consultant all they see is a new interface, shit loads of noise, gifs etc (cultural issue rather than tech stack obviously) and no real extra benefit vs the cost of learning something new when what you have today ticks all the boxes.

I also use both as I'm a partner on the engineering side of the business but also run a large consulting pod - I really don't care which one anyone uses. I don't personally see Slack being better 'enough' to justify the effort of switching for those that are already on teams.

Thankfully, teams has gif support as well.

It would be a dark day indeed if we'd have to stop spamming memes while at work

Because the rest of the business comes from Skype/Lync! Which was somehow an even larger atrocity.

Very true. I know a couple of people who like Teams, they work in healthcare and education. I think that mostly just speaks about the horrid quality of the software they usually have to face.

Each and every tech worker I know loathes Teams with passion. On the upside it's like a common enemy so there's a small team building aspect to using it.

Are you American? I tend to find tastes in tech differ across the pond. An American literally sent me a link to a google doc the other week - I couldn't believe anyone would send a final professional doc in anything other than Word - you can't even get proper section numbers without a poor plugin....

Every organisation in Poland I've worked at has used google docs and GSuite.

On the other hand, we're mostly using it for few page design doc, and have no idea what "final professional doc" or what "proper section numbers" are and why would anyone care.

I am referring to section 2.3.1 of the strategy doc.

But hard to point someone to the right place without decent numbering.