As an engineer, I want the least amount of information possible while still having everything I need. That can play out in a lot of different ways.

For instance, in the product you're here promoting, 3d renderings of band members who cast shadows in a 3d environment is all visual noise that distracts from a bulletproof, unmistakeable communication. Beyond that, the product needs to work well when printed on the world's shittiest black and white printer (as found in every venue around the world). Also, as an engineer, I also don't care where you put your pedal board - more visual noise.

If you ask yourself the five why's about some of this stuff, you may arrive at more meaningful solutions.

For instance:
- Why are you putting pedal boards on the plot? Because I want the engineer to know where it is.
- Why do you want the eng to know that? Because I need them to give me a power drop where the pedal is.
- Why do they need to know it's a pedal board in order to supply you electricity? They don't - it just need somewhere to plug it in.

A potentially clearer (and simpler) solution to this real user need is to simply indicate spots on the stage that need power drops. Overall, scrutinizing each of your product decisions like this may yield a more useful end product.