As usual Bastiaan is correct. A process should be well laid out and legible, and as with traditional coding, if the developer has produced spaghetti that nobody can read (or test or implement or run or support or maintain) then the developer has done a bad job. The Design Authority approving the design and the Lead Developer who approved the execution of the design are also at fault.
BP XML is not intended to be readable, it's merely a vehicle for storing a definition. An even if it could be out into another view, if the original is a mess then any other view will be too.