I’m all in for diagrams in discussing software! When there is no whiteboard, I literally draw in the air to explain my point. However, doing real, orthodox UML

I’m all in for diagrams in discussing software! When there is no whiteboard, I literally draw in the air to explain my point. However, doing real, orthodox UML/BPMN requires everyone to understand the official notation, the difference e.g. between an „association“ and a „message flow“ (and then the differences between UML 1.4 and 2.0) etc. Do people really work in environments where all stakeholders have that kind of knowledge? Big corps I could imagine, probably where heavy machinery is involved. Aside from those „we build a cruise ship“ megaprojects I have the impression that people say UML and mean the much more approachable „squares connected by diamonds and labeled arrows“-diagrams. Wondering how no-code tools like this handle those discrepancies between the super-detailed specs and the real world diagrams