Model Storming

Agile Modeling Sessions

Model storming is impromptu, just-in-time modeling. Two or three people grab a whiteboard and hash out a design question that just came up.

It’s the opposite of a formal modeling session. No meeting invite, no agenda, no documentation afterward. Someone has a question (“How should this component talk to that service?”), they pull in a teammate, and they sketch it out in 5-15 minutes. Done.

Why model storming is powerful:

• Immediate — the question gets answered when it matters, not three days later in a scheduled meeting
• Collaborative — two brains are better than one, especially when the problem is ambiguous
• Low overhead — no preparation, no follow-up, no ceremony
• Just-in-time — you model exactly what you need, exactly when you need it

When to model storm:

• You’re about to implement something and realize you’re not sure about the approach
• Two people have different mental models of how something should work
• You’re stuck and need a visual thinking aid
• You want to quickly validate an idea before investing in code

The typical model storming session:

1. Someone says “Hey, can you look at this with me for a minute?”
2. They go to a whiteboard or grab a piece of paper
3. They sketch, discuss, debate, iterate
4. They reach understanding (or identify what they still need to learn)
5. They go back to their desks and implement

No artifacts needed. The value was in the conversation and the shared understanding it created.

Model storming is the agile modeling equivalent of pair programming — lightweight, collaborative, and embedded in the daily flow of work.

Related: Agile Modeling Session, Look-Ahead Modeling