UE PROCESS: Explain Behaviors with eye-catching design?

This always confuses me.

Recently, we are working remotely with our SH team to come up with UI customization proposal on Android 4 smart phone.

Our boss has his own opinion on the button layout, but we are trying to convincing him that there are some potential problems regarding either the ease of navigation or the flexibility to extend the functionality.

Mr boss asked  us to use EXAMPLES to give him a clearer idea of our concerns, which is totally understandable.

BUT, as i've expected... B asked us to present these examples in FULLY DESIGNED MOCKUP, which means the GUI team needs to work on the visuals.

In my opinion, we should never jump from the structure\ task flow to the visual design process directly, especially when the discussion is focused on "BEHAVIOR."

WHY?

According to my experience, if u come up with a very beautiful design, people tend to overlook the interface logic.

The best practice is to discuss this kind of stuff with task flows and simple wire frames.

1. Thus we dont have to put too many efforts on the look and feel in early stage.
2. There are fewer risks your boss choose a solution based on "it just looks right "