Why We Keep Using Miro, Even in MBSE Projects

Here's a scene that plays out in many Model-Based Systems Engineering projects: a team runs a creative workshop on Miro or a similar whiteboarding tool to sketch out system structures and functions — and then faces the labor-intensive task of translating those informal designs into a formal tool like Cameo or another SysML platform.

I've watched this pattern repeat itself. Even when a formal model already exists, teams still prefer a collaborative, flexible canvas. There are good reasons why:

• Creative freedom — people can think without worrying about technical constraints.
• Inclusivity — non-technical stakeholders can participate easily.
• Speed — ideas flow without the overhead of tool complexity.

But there's a significant drawback: eventual conversion requires manual interpretation. Someone has to decipher ambiguous sketches, clarify what each element actually is, trace connections back to requirements, and often iterate again with the original team. It's cognitively demanding and time-consuming.

To close that gap, here are five strategies worth considering:

• Brainstorm inside the model. Use lighter interfaces that let you sketch directly within the formal modeling environment.
• Embed a systems engineer in the workshop to guide alignment and capture structure as it emerges.
• Keep the handover window short (24–48 hours) to preserve context and momentum before details fade.
• Explore AI-assisted conversion tools to help bridge sketch to model.
• Apply modeling-compatible visual conventions within the whiteboard itself, so the translation is less ambiguous later.

The goal isn't to make informal creativity and formal rigor compete — it's to make them coexist. Effective MBSE needs stronger bridges, technological or procedural, connecting exploratory thinking to authoritative models.