Just wait for the migration from Slack to MS Teams, makes me wanna stop working all together. Also, MS recently launched their Notion clone, so all Notion users in MS shops better prepare to migrate to a much worse alternative.
I briefly led an underground incentive to use something other than Teams among the engineers at a previous employer. It gathered quite a bit of steam even though none of the alternatives proposed were great. Tells you what people think of Teams! (It petered out when my priorities shifted, though, so I guess that tells you how much bandwidth people actually have for caring about their instant messaging. (There had alr…
Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
21–30 of 70 posts
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#22Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#23Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#24Earlier quoted context omitted.
> Either way, I don't see why the people doing the work should not be allowed to (collectively) choose their tools. Because in a big company you’ll find some things are documented in a combination of jira and confluence while another are in big figma boards and nobody knows where to look (my gf’s company has exactly this problem). Also in a big company you want to have two teams collaborate but one uses one tool set…
I don’t understand. Would it be sensible to require people using Figma to instead use Jira? Two tools with completely orthogonal use cases. It sounds like you’re describing a different problem.
(You probably wouldn't choose either for that from the beginning, but you start using Jira for issue tracking/feature planning, of Figma for feature design, and end up with them holding a lasting record of how the feature is intended to be.)
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#25It's super standardised, though.
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#26A bit of a strange post. How can you write so much about a decision to stop using a tool? And on the company blog? And threaten to quit at the end of the blog?
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#27It seems odd that a post on the official company blog is showcasing disliked IT policy. This reads like an airing of dirty laundry, and I’m kinda surprised it was allowed to be published. I understand the “we have food at home” IT policy of using software you’re already paying for. On the other hand, it’s clear that the author isn’t sure who made the call to ditch Miro and wants Miro reinstated. I wonder if this blog…
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#28Just wait for the migration from Slack to MS Teams, makes me wanna stop working all together. Also, MS recently launched their Notion clone, so all Notion users in MS shops better prepare to migrate to a much worse alternative.
I think MS Teams gets a bad rap that is doesn't deserve. I don't know if the experience has improved or something - maybe Teams used to be worse and people are reacting to how it used to be? I've also been using MS Loop a lot and it's pretty great actually. It's clearly still under development and missing a lot of features but leaving that aside, I don't think it's fair to dismiss it as a Notion clone. It's far simpl…
Loop - Super beta product with very few features compared to Notion. In particular, I've enabled it in our tenant and it has a showstopping bug for many users in which none of their work is saved. This bug exists from day 1 and still not fixed.
> MS 365 wins by being "just good enough" at _loads_ of things, and way cheaper than the competition.
Agreed!
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#29Just wait for the migration from Slack to MS Teams, makes me wanna stop working all together. Also, MS recently launched their Notion clone, so all Notion users in MS shops better prepare to migrate to a much worse alternative.
I think MS Teams gets a bad rap that is doesn't deserve. I don't know if the experience has improved or something - maybe Teams used to be worse and people are reacting to how it used to be? I've also been using MS Loop a lot and it's pretty great actually. It's clearly still under development and missing a lot of features but leaving that aside, I don't think it's fair to dismiss it as a Notion clone. It's far simpl…
Two problems with information are duplication (too many copies around, all of them slightly different) and finding where it is. MS Teams makes it easy to store duplicate data and hard to find it later: did you upload the data as a file in the "development" channel, or as a link in the "updates" wiki? Nobody knows, not even the search function. And with each new project manager creating five channels per project, two of which will actually see any activity...
I think MS Teams wants to be everything for everyone and succeeds at neither.
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#30If you want to go fast, go alone. If you want to go far, go together. If you want to pass an IT audit, good fucking luck to you. I have about 20 years of experience dealing with this ranging from mostly harmonious all the way to civil war. 100 employees and 130 different SaaS tools. Got buy in from senior management to reduce footprint to lower cost and increase security and compliance only to get pushback from every…
> Try convincing everyone that grammarly is a keystroke logger. Funny how it's not the opposite viewpoint that is scrutinized. Prove how it's not a keystroke logger, then Grammarly can be deployed. Until then, it's assumed to be malicious. That's how people treat for example ChatGPT as well.
And it isn't very risk-based. In most cases, the keylogger can be assumed to be entering via the OS, probably based on some NSA/GRU/Chinese MSS exploit being used for industrial espionage. Grammarly is a bit more niche.
It is a threat. One day it will be an acute one, perhaps. But the risks and opportunities favour recklessness.