Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
engineering.telia.no
Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
1–10 of 70 posts
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#2> Recently, a decision was announced to decommission Miro as an official Telia tool. The replacement tools suggested was a combination of Microsoft Whiteboard, Microsoft Visio, Jira and Confluence.
I can't even imagine a worse replacement than that shudders. How typical that great bespoke tools are rejected in favor of whatever poor features/products available through existing product licenses.
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#3[deleted]
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#4Just 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.
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#5> Recently, a decision was announced to decommission Miro as an official Telia tool. The replacement tools suggested was a combination of Microsoft Whiteboard, Microsoft Visio, Jira and Confluence. I can't even imagine a worse replacement than that shudders . How typical that great bespoke tools are rejected in favor of whatever poor features/products available through existing product licenses.
Also, how many of the people doing the actual work at that company even want licenses to those tools in the first place?
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#6This reads like a really good review of Miro!
Either way, I don't see why the people doing the work should not be allowed to (collectively) choose their tools. That way you get both collaboration (because they picked one thing together) and the most appropriate tool for the work to be done.
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#7“ Employee experience and productivity should be equally important in these discussions as cost and security. And if you are making a decision about available tools on behalf of others, you need to spend time to understand the needs of the people you are deciding on behalf of, if you want to make a good decision.”
A - F*in - Men.
We recently dropped Miro for LucidSpark as we already had LucidChart. It’s so much worse, I hate using it. But on paper it does the same stuff, just implemented poorly. Example being, no anti aliasing on drawn lines. Wtf?!
Experience is king. Getting people to understand that when the mandate is save as much money as possible is the challenge.
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#8Just 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 already been a successful underground movement to use something other than Teams for video conferencing.))
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#9This reads like a really good review of Miro! Either way, I don't see why the people doing the work should not be allowed to (collectively) choose their tools. That way you get both collaboration (because they picked one thing together) and the most appropriate tool for the work to be done.
There's a high chance a company will have already paid a large subscription fee to Microsoft for Office 365, and so they don't want to pay yet another licence fee on top for a tool that's already included with that. The people making these financial decisions are usually not the users of said tool.
Re: Should you standardise tools in your company? Case of Miro vs. MS Whiteboard
#10This reads like a really good review of Miro! Either way, I don't see why the people doing the work should not be allowed to (collectively) choose their tools. That way you get both collaboration (because they picked one thing together) and the most appropriate tool for the work to be done.
> 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 and the other a different stack and there aren’t enough licenses for both.
And so on. It’s like having each team use its own code formatting rules or coding standard.