Why We Keep Using Miro, Even in MBSE Projects
If you’re working in Model-Based Systems Engineering (MBSE), there’s a good chance you’ve seen this pattern:
A team spends hours in a Miro workshop defining system structure, use cases, and functions — all with great energy and creativity.
Then… someone has to “translate it into Cameo.”
Feel free to replace Miro with any whiteboarding tool and Cameo with any SysML-based MBSE platform — the pattern is clear.
I’ve seen this many times. Even when a SysML model already exists, teams still prefer to brainstorm and collaborate on a flexible canvas like Miro. And honestly? I get it.
Why Miro Wins in Early Stages
Miro (or similar tools) gives teams:
🧠 Freedom: You can sketch ideas without worrying about stereotypes, diagram types, or validation errors.
🤝 Inclusivity: Stakeholders who don’t speak SysML can still contribute meaningfully.
⏱️ Speed: No tool complexity, no rigid modeling — just ideas flowing.
Meanwhile, tools like Cameo offer the opposite: structure, traceability, rigor. And we need that — but maybe not right away.
But There's a Cost
Eventually, someone has to convert all those sticky notes and arrows into formal model elements.
And that person is often left asking:
“What did they mean by this box?”
“Is this a use case or a system function?”
“Which requirement does this refer to?”
“What does this connection even mean? It doesn’t make sense…”
It’s time-consuming, mentally taxing, and often requires re-iteration with the team.
How We Can Do Better: 5 Ideas
Here are a few ways to streamline the flow from Miro to modeling:
Use a Lightweight Front-End to the Model
SysML v2 promises to bring the model to the center — not just the tool. Can we use more flexible or user-friendly interfaces that let us brainstorm directly into the model?
Designate a “Model Translator” Early
Involve a systems engineer during workshops to gently guide alignment (with the model in mind) and capture structure live — before it gets lost in abstraction.
Sync Fast
Keep the Miro-to-model handover within 24–48 hours — before ideas fade or lose context. Momentum matters.
Experiment with AI Assistance
We’re starting to explore tools that convert Miro exports or screenshots into SysML building blocks. It’s not perfect — but it’s promising.
(Optional) Use Modeling-Friendly Templates in Miro
Apply visual rules (e.g., color = element type, tags = requirements) so the whiteboard isn’t so far removed from the model.
Let’s Embrace a Hybrid Approach
MBSE doesn’t have to be rigid from the first idea. Early creativity and formal modeling should coexist, not compete.
If we treat Miro as the “thinking canvas” and Cameo as the “source of truth,” then we need better bridges between them — whether through technology or a shared way of working.
How Do You Handle This?
I’d love to hear how other teams are managing the informal-to-formal transition.
Do you have a method? A favorite tool? A workaround?
I’m genuinely interested in your experiences — let’s share and learn from each other.