I love all the amazing templates provided by the community in Miroverse!
One thing I’ve been thinking about that would make Miroverse even more awesome is the ability to create and share individual “components” that could be used in any board.
In my enterprise Miro account, I have a board called “Assets.” In this board, I add simple components I’ve created in Miro and share them with the rest of my organization (using the Save frame as template feature).
Two examples:
This is a profile card I made for my team members, to include in our onboarding docs. Since then, many different teams have used it to get to know each other better.
In a project I’m working with, we have introduced cell-based architecture – and we have of course created a visualization of our target architecture in Miro! For this visualization, I created these assets. It’s a basic empty cell with some component types, and an example cell (saved as two separate templates).
Imagine if we could create these kind of simple assets and publish them as components in Miroverse!
Love this idea,@Henrik Ståhl !
I wonder if@Kyle Chipman has anything to say on the topic since he authored an awesome article on creating a dynamic visual hierarchy in Miro :)
Fantastic idea. A granular sharing mechanism. I see this as allowing for two pathways for users:
I do see a challenge with organization / categorization, but welcome that as a bridge to cross when we need to.
Thanks for recommending the blog post@Anna Savina , it’s amazing! I really like the way you structure your work in Miro @Chrispurser , it’s very inspiring! Will definitely use your post as reference from now on.
yes@Henrik Ståhl ! Ever since I witnessed the gummy bear voting by @Rachel (and @Jonathan White ) at Distributed, I have been dreaming of components in Miroverse!
Upvoted!
and in case you want to see the gummies in action:
This definitely gets my vote. Similar to what has already been said, I have a "master board" that contains all my useful bits and pieces, some of which I've setup as templates for internal use by others. The possibilities are endless here.
Thanks for inviting me into the conversation@Anna Savina ! This is an invigorating thread.
@Henrik Ståhl I wanted to wait to respond til I had some interesting observations on the Cell-Based Architecture link you posted (only read the intro, was excellent), but this thread looks to be popping and it seemed more fun to jump in the conversation . Glad you liked the blog post.
@Henrik Ståhl
Damn, I ended up writing a wall of text. I think I just got excited by other people who wanted to have this conversation.
In an overarching sense, I still think scale is the necessary first step. Keeping a consistent starting point of scale, 48pt bold mid-weight stroke, for me, has proven terrifically useful over time. Allows for micro and macro definition, creates easier cross-board population, and helps establish multiple reasonable margins for essential frame sizes (A4 and 16:19, primarily).
Some interesting, general thoughts on this front I’ve had over the years:
...
...ah, that’s right, I did install the app a while back, but have repeatedly gotten stuck at the “Company Accounts are not supported” screen, and then additionally forget to check if that’s some integration setting on our back-end or corporate accounts straight-up aren’t supported by Miro. Uh, I will investigate with my Director of IT this week.
Wow,@Kyle Chipman thank you so much for such a nuanced response!
The scale mentioned in your blog post is a game changer for me. I was actually working on a new board yesterday and I adjusted it according to your recommendation (48p starting point) and it got sooo much better. Will never ever create a board again without setting proper scale.