181–190 of 247 posts
If they offered it a la carte I would be a lot more interested. Our company is just getting over Microsoft hegemony. I'll never be part of getting back into that by buying Microsoft services that are intertwined.
But, seriously, this is likely more like Microsoft Groove (originally from Groove Networks) brought to the web. This idea has been around for a very long time.
Earlier quoted context omitted.
They are copying Apple [1]. It's supposed to demonstrate strength, since most competitors try to pretend that the competition doesn't exist. To me it always came off as really dumb and self-important in the most cringing of ways. [1] http://www.historyvshollywood.com/reelfaces/jobs-apple-welco...
Off topic note here: Apple forecasts a "logarithmic leap". I have never heard that term. Logarithmic growth is sub linear and doesn't seem like something akin to a leap. Usually you would go with "exponential". Just seemed like odd wording.
It's symbolic of the typical winner-take-all markets in the IT sphere, unlike the term exponential, which is constantly misused and inaccurate in most cases (except, perhaps, for Moore's law on a limited time interval)
-1 for no shame when coping the design.
This is exactly why Slack is not a defensible product. 1) The UI/interaction/UX can (and obviously will) be replicated, which has been slack's biggest value proposition. 2) There's no "stickiness" for companies. None of the data in chat is really a "system of record" and the switching costs are minimal. 3rd party bots/integrations are the only thing that really make it sticky for companies. 3) The IP isn't really all…
What do you mean, not defensible? As in, it shouldn't exist, or there's no way it can be profitable long-term? I think it's a great product experience, but as you say, without adding more value, it can be replicated by Zulip/Rocket.Chat/Mattermost/Cisco Spark/Microsoft Team/ you name it.
Earlier quoted context omitted.
Then you have to provision hardware to run it and someone to set it up and admin it. And deal with backups and data retention, etc. Healthcare IT teams tend to run ridiculously lean. There's a much stronger business case for paying a few bucks per user/month than take up expensive and generally highly limited sysadmin time rolling your own.
[IANAL] Chat's may or may not be deemed business records by a prudent attorney and therefore it may be possible to not retain them for reasons similar to those under which computer logs are not maintained. That might make complying with non-realtime HIPAA requirements simpler. Relative to IT requirements, the trend is toward much higher ratios of machines to IT staff due to virtualization and orchestration. I suspect…
Whether or not Slack has the better product or not, Microsoft will blow past them in terms of paying customers. Slack has 1.25 million paying customers as of now. Microsoft announced it signed a 400,000-employee comppany on launch day. They can easily sign Coca Cola, Macy's, McDonalds and Unilever in a matter of months, which could bring them at most 10 million paying customers. Microsoft has the power of existing cu…
To put it another way, look at something like SharePoint. Microsoft will happily tell you it has a ton of users. They might tell you that it's quite profitable. But SharePoint is a just a terrible piece of shit that everyone hates but IT departments drag everyone to it kicking and screaming.
So subscriptions will get purchased, contracts signed. Microsoft will make money. But will they take mindshare? Maybe Slack won't be able to differentiate enough. Time will tell but today employees actually want Slack.
This is exactly why Slack is not a defensible product. 1) The UI/interaction/UX can (and obviously will) be replicated, which has been slack's biggest value proposition. 2) There's no "stickiness" for companies. None of the data in chat is really a "system of record" and the switching costs are minimal. 3rd party bots/integrations are the only thing that really make it sticky for companies. 3) The IP isn't really all…
That's not true where I work. Slack's history is full of valuable information that we use all the time.
As somebody working in the healthcare industry, this is the killer feature for me: >Q. What level of security and compliance does Microsoft Teams support? >A. Microsoft Teams is expected to be Office 365 Tier C compliant at launch. This broad set of global compliance and data protection requirements includes ISO 27001, ISO 27018, EUMC, SOC 1 Type I & II, SOC 2 Type I and II, HIPAA and FERPA. Microsoft Teams also enfo…