Brief 3 - Instrument Cluster - Final Designs

In-situ mockups help to assess the real world suitability of the design 

Minimal Mode

Eco Mode

 Sport Mode

 Standard Mode

Close-ups

Brief 3 - Instrument Cluster - Development of other display themes

Standard Variant

No outstanding decorative elements or distracting colours except for imminent nav instructions; neutral appearance with expected information. 

Low Power Mode 

Utilising a thinner typeface and blue decorative elements to incite calm and create a more elegant appearance. Hierarchy of information shifts to battery/energy related info

Sport Mode 

Utilising a heavier weight, italicised typeface to incite speed and movement, with red decorative elements inspiring activity and aggression. Hierarchy switches to speed, energy use and range remaining as priorities. This is for the racetrack. 

Allowing users to switch display styles can allow for the driver to add more personality into their car, but can more importantly; in this case, provide three different designs for three different modes of operation, improving the user experience of each one. My COP project, which explored the use of colour in user interface design, was incredibly helpful in providing the knowledge of what colours to use to incite what emotions or responses.

Test sessions were carried out with the above designs, and any identifying elements were removed. When users were asked to explain how each one made them feel, or how it looked, the following were given:

Blue Version:
Calming, relaxing, encouraging, futuristic

Red Version:
Active, aggressive, sporty, quick, fast

Brief 3 - Instrument Cluster - Continued Visual Development

Experimental Alternative: 

A large-scale-element option, inspired by the instrument cluster of the Ford GT supercar, was explored but was deemed unsuitable for the target audience and usage scenario of the target car's user base. Though it would exciting in-use because of its rapidly updating and visually engaging appearance, the instrument cluster being developed is for a conceptual, future electric variant of the Range Rover Velar, and so must be rugged but luxurious, and technologically advanced; it would rarely, if ever be used for racing or other high speed activities. 


Continued Development of Informed Initial Idea

Automotive interfaces must be able to work in bright daylight and the dark of night. Usually this results in the development of a separate Dark and Light mode, but instrument clusters are forgiven somewhat because of their location and the techniques used to shield it from interfering light. Grey is a good compromise - it allows for the bright contrast of white for daytime, but is not too harsh on the eyes for night.  

This vehicle angle was chosen to best represent a fly-over view of the car, allowing for the same angle a low-flying aircraft would have if it was tailing the cars in that lane. This makes it easier to display any obstruction or cars in front of its own, without having to look directly through it.

In user testing, Navigation was listed alongside Speed, Transmission and Battery as the 4th most important feature in an instrument cluster. The blue colour gives Nav joint highest priority (alongside Speed) when an immediate response is required e.g. turning off etc., and the rounded edges provide a visual link to road signs, alluding to their purpose. 

The circular, decorative lines to the left and right of the road are reminiscent of the more traditional design of dial-based clusters, and also provide three areas of information hierarchy - left, centre, right. 

Brief 3 - Instrument Cluster - Feedback on Initial Concept

In order to inform the direction going forwards, a number of people were asked to identify what they thought was bad, and what they thought was good about the following three concepts:

Concept 1 
There was an overall agreement that although the simplicity of this concept was refreshing and relatively pleasing to the eye, it wasn't enough of an advantage to compromise necessary information, and that some more decorative elements would be appreciated. 

Concept 2 
The visual highlighting of elements on the vehicle was received positively, as was the minimalist notification toasts. The more decorative lines on this concept, reminiscent of the traditional dial-style rounded designs employed by the majority of automakers, were also well received. 

Concept 3 
The aesthetics of this concept were appreciated, but not in the context of a car with some level of manual driver control. 


Conclusion 
Incorporate more information, more decorative elements, but continue simplicity 

Brief 3 - Instrument Cluster - Initial Concept

Starting with an incredibly simple design allows for the basics to be worked out - what information is absolutely essential, and what way is best to display them. 

Then more decorative/hierarchical elements can be experimented with. These division lines create an interesting white-on-white aesthetic whilst also subliminally creating three areas for information; e.g. potentially the left section for driver info, middle for vehicle info, and right for media info. Categorising information helps it be more easily identifiable/locatable, and avoids cognitive overload. 

Colour is incredibly useful in interface design - here it makes clear to the user that they should focus on the wheels, and highlights that there's a problem there. Giving a visual example of the problem area is more useful that simply providing a written description both in terms of the rapidity in which the user understands what is wrong, and how easily they understand it (particularly with more complex faults). 

Brief 3 - Instrument Cluster - Vehicle Imagery (Collaboration)

Autodesk VRED Pro is a 3D visualisation and virtual prototyping software specifically for the automotive industry, and helps designers and marketers create product renderings, design reviews and prototypes. 

I collaborated with Keith Burden, Senior Interface Designer at Jaguar Land Rover for the creation of the vehicle imagery. Having previously worked at JLR as a design intern, I had easy access to Keith and after leaving was trusted to handle design files of vehicles that had already been seen by the public. The vehicle used for this project is an L560, or a Range Rover Velar; Land Rover's newest, most avant-garde SUV. 

Keith's full internal and external 3D model of the Velar was handed over to me, and using VRED I was able to rotate and translate the vehicle, its wheels, doors etc., to any desired position, then take imagery of it to be used in any applicable interface elements. Keith taught me how to operate the software, how to manoeuvre the model, and how to apply realistic virtual lighting effects and 3D backgrounds. 

The final imagery required for this project is relatively simple, however - rear view imagery with a drop shadow for semi-autonomous driver monitoring, lane assist etc., and a side profile for vehicle status, controls etc. 

Imagery: 

Side view - Useful for helping the user understand where faults on the vehicle are located, or see real time control alterations, ride height adjustments, open doors etc.  

Brief 3 - Instrument Cluster - Sketching

Experiments with various shapes and aspect ratios - traditional instrument clusters were bound by the need for circular dials, but this is no longer a limitation. 

A centrally located speedometer allows for as little eye movement as possible (short of using a HUD) when the driver is adjusting their vision from the road e.g. just downwards, whereas locating it to the left or right would mean a movement of down then left/down then right. In a car with human-operated driving, it is key that any interfaces are as distraction-free and easy to use as possible.