We are currently working on the very first iteration of our healthcare application. The goal for this iteration is to provide some basic means of navigation and a dashboard-like screen.

I was responsible for the navigation part. It should consist of a list of patients to select from, a menu-like panel to invoke use cases and some other rather minor things. A rather great deal of work has to be done to develop a basic underlying application framework. That doesn't leave much time to tweak the user interface and create nice-looking navigation parts.

My co-worker's task is to create a screen that shows some summary information including a chart to display some health data.
Today he showed me a first draft of the screen. It showed a very pretty chart. With animated lines and gradient colors. A typical WPF chart.

It looked very cool. But I didn't think it was a good idea to include such modern control as part of the first iteration. While all other parts of the app look pretty basic and simple, the chart will draw much of the test users' attention.

But that is not what I want to achieve with the first and very basic iteration drop. The primary aim should be to get as many meaningful feedback as possible. But I'm afraid the test users will get distracted and won't deliver as much support as would be possible.
Don't get me wrong here. This is unconscious behavior. The chart control will catch every tester's eyes. This is not what I want to achieve.

So our strategy is to include a simpler version of the chart first and upgrade its appearance along with all other user interface parts. This way we can make sure that the testers don't focus too much on only one part.