>
In collaborative design formats like Process Modelling and Software Design, many possible alternatives can easily overwhelm the team.
Collaborative contribution can quickly turn into a standoff. One modeler may try to take the lead, while others raise objections or reminders. But when many alternative branches open, it is virtually impossible to solve all of them at once.
In design formats, we are collaboratively solving a puzzle, and we need some discipline to do so.
Prioritise having a visible baseline over visualising every possible branch of the exploration. You'll need something visible to start with.
Move on a straight line, supported by Speaking out loud , trying to reach a final state as soon as possible. Your trajectory may be simplistic, but it will serve as a clear starting point for further refinements.
At the same time, you're not supposed to forget about the complexity of possible alternatives and corner cases: we are just postponing it. Hot Spots can be used as a placeholder for the complexity we are deferring to a later discussion.
Also, remember that this complexity is not deferred indefinitely: we need to complete a scenario that makes the key stakeholder happy, and then we'll come back and pick the most interesting hot spot to explore. Or we can quickly ramp up with Raise the bar , after establishing a safe baseline flow.
Establish some working agreements - like providing only quiet feedback, or having Time-boxed leadership - to avoid swamping in complexity.
There is no way you are going to solve all the puzzles at the same time. But one after another, you can become unstoppable.
Completing the baseline flow should provide some safety net to your modelling party. But remember that there is not a single path to a final solution.
Sometimes incremental steps are all you need, but in some scenarios, you may want to revisit the foundation and start from a new baseline, especially after realizing that you are in a dead-end alley.