Ask boundary questions before you draw another diagram
A short field guide for analysts who open a whiteboard too early and lose the room to premature architecture.
Diagrams are useful once the room agrees what sits inside the system and what stays outside. Jumping to boxes and arrows often freezes a wrong boundary into something that looks authoritative.
Start with three questions: who is affected, what must stay true after the change, and which decisions are already locked. Write the answers where everyone can see them before any shape is drawn.
In Appcovecore cohorts we practise this sequence aloud. Teams leave with a habit: talk boundaries first, then choose the lightest notation that serves the next decision—not the prettiest canvas.