The work I do in it feels effortlessly lightweight. And a sign of work being lightweight is when throwing it away feels like progress. Miro has the right mix of primitives that support thinking in action.
I can effectively provide enough latitude in it to enable breakthroughs, i.e., to enable my future self and others to work within rough, schematic constraints while leaving the specifics open according to the realities of the project.
Figma feels right once affordances are wired up to code and we are ready to add the finishing touches. This is a different intent than what it was designed for and how it is often used. I see Figma not as the ideal pre-development tool, but as a good fit for in-development work.
Also, Miro’s action space is the perfect general framework to easily build various ways of working conventions. It ensures communication is spatial (on the work where the work is) and thinking artifacts are contextually maintained on its substrate. I can easily replace Google Docs and Slides (and the like), most of Sheets, and most, if not all, project management tools while supporting visual reasoning along the way.