Miro is great for collaborative activities, less for actual design

We use miro for most, if not all, of our internal products during discovery and build phases. During discovery phases, it helps facilitate collaborative sessions about understanding the product, putting together ways of working and a wide variety of other sessions. There aren't many other collaborative tools out there that handle the scope like miro does, and it's our product of choice when it comes to these sorts of collaborative sessions. During the build phase, it serves as a very useful tool for archiving the discovery type sessions, in which we can refer back to the massive board we've populated, and also as a tool to facilitate retrospective sessions and dashboards for sharing during standups and whatnot. It helps the team keep track of where we are and where we've been. Paired with Confluence, we have everything we need to share knowledge and refer back to previous information.

We use miro for the entire early phase of new projects. The boards store all of the key information we uncover through workshops and other discovery activities. We use the board for initial planning workshops, in which we plan what we aiming to do, product vision and other key product ceremonies, all working together remotely, or in person. It helps us keep track of what we've done so far, and also actively engage in the current activity using the tools provided