Explore Yellowfin now with our sample datasetGet Started
The unique features of Yellowfin Canvas ensure complete and pixel perfect design capability. This is particularly useful when planning and designing the layout of dashboards to ensure that the data displayed is easily viewed and understood by the end user so they can establish the insights they need to make effective, data-led decisions.
By understanding the end-user, it is vitally important that the right dashboard type is designed to align with the end-user needs and analytic capability. This is discussed in more detail here.
For example, there is no point in creating an operational style dashboard with detailed reports and charts for a senior manager who may only be needing top-level KPI style numbers. The opposite of course applies when delivering a dashboard to someone that has very detailed and operational needs. A KPI dashboard with limited detail will prove to be a frustrating experience for someone with more in-the-moment needs. As well as they may be designed, the wrong dashboard for the wrong use case will nearly always result in a low ongoing adoption by the intended audience.
As a very simple rule, it’s best to line things up. This does not necessarily mean all components of a dashboard need to be the same size but, where possible, try creating visual alignment between multiple components. This will again lower the effort required for the user to visually navigate through the dashboard. Use alignment to help contribute to hierarchy knowing that the human eye tends to start top left and move towards the bottom right. Consider visually aligning chart headers, charts, blocks of text as shown in the example below. A considered, structured alignment will also look and feel cleaner and help convey an overall sense of simplicity.
Yellowfin Canvas allows elements to go anywhere on a page and therefore enables pre-defined grids to be broken. On very rare occasions, it may help to break the grid in order to make certain information pop. This could work well on ensuring the component is first seen or not missed by the end users and could include KPI dials or an automation widget as shown in the example below. In this case, small changes in data are presented as Signals and these need to be seen. For this reason, the Signals ‘breaks the grid’ and pops into the foreground.