And a diagram (in such a 4GL) does not help when it has hundreds of decision nodes and the end-user (read: a human being) visual system can only deal with at most 10 nodes.
It is also very amusing when the executives finally realize how unnecessarily complex their order processing chain is.
how do you solve the issue you point out? isn't using symbols to represent something machine-readable what a programming language already is?
I'd argue that our next big jump in productivity is likely to come when we are able to have a conversation with an AI about the desired function of a program and have the AI write it for us. Whether visual programming will be a part of this conversation remains to be seen.
http://catb.org/~esr/writings/unix-koans/gui-programmer.html
I'd be disappointed if our hypothetical AI was unable to grok simple diagrams or generate its own. If a conversation with this entity can still be called programming, I can definitely see it having a visual element.
The boost in productivity will come when we stop reinventing the wheel every few years.
Each new batch of programmers is so ignorant of the past that they spend all their time reinventing it (usually, badly) instead of making any real progress.
Heck, if, even two decades from now we have some form of AI that just barely understands _existing_ code so that it can have at least a simple discussion with the programmer, I would be very surprised.