Mobile Analytics Design And The Consistency Principle

people-smiling-at-phones.jpg

When designing mobile analytics solutions, the “consistency principle” is the most powerful tool to effectively deliver a mobile user experience. Developing components that are both consistent and repeatable greatly accelerates the “mobile learning curve,” leading to higher user adoption.

We apply the consistency principle at two levels:

  • The macro level occurs at-the-project or engagement level and covers all resources or artifacts that are used to deliver and support implementation of mobile assets (like user guides, communication, online stores, and support).
  • The micro level deals with the design of each individual mobile analytics asset (like a report or dashboard).

Here are three key design fundamentals of the consistency principle.

Teach once, use many times

Each design component on a mobile analytics asset, whether it involves a specific functionality or the use of a specific color/text, has to be developed and applied in a consistent manner throughout the same target mobile user interface (UI). Expanding this concept to the macro level, the application of the consistency principle will affect the entire portfolio or a specific set of reports. It will include every aspect of the delivery infrastructure, ranging from how mobile assets are accessed to how they’re downloaded or consumed.

By using a consistent design, we teach the user all they need to learn to consume the mobile analytics asset at the first touch point. By re-using the same elements (buttons, links, swipes) and in the same context (use of colors or text), we have a chance to accelerate the learning curve. This approach significantly improves the “mobile analytics user efficiency” because the user will be able to use many times what they’re taught at the beginning.

Simplicity begets consistency

In mobile analytics design or implementation, I often observe that project teams hesitate to keep things simple. Don’t be afraid to simplify your design elements at every chance. Remember to simplify to the point that it makes sense both for the end user and for your back-end operations.

Many times, simplicity can provide the prerequisites to a consistent design because it compels us to use fewer parts, an approach that will force us to think creatively and methodically. Taking this simplicity approach is more beneficial than following the urge to build the most intricate solution possible.

Think for a moment about how this plays out in our everyday lives. How many of the features available on a TV, PC, or smartphone does an average user actually get around to using? Do most regular users even have time or a desire to explore all the other available features?

Don’t design what you can’t explain

As simple as this might sound, this is one rule that, if it’s broken, can be the most costly mobile design infection because it can destroy trust.— a cornerstone of any business transaction or engagement, especially in the integration of business and technology.

This deficiency can surface anywhere in our design because it’s easily overlooked or taken for granted. It can be as basic as the location of a button on the screen (for example, placement near the close button results in frequent accidental exits) or the incorrect use of a color to highlight a specific text or number (for example, red for negative numbers on one page and positive numbers on another page).

In more serious cases, it may involve major differences for the same functionality that may be completely superfluous.

Bottom line

Business users are always pressed for time, and businesses are continuously concerned about productivity. If the goal of mobile analytics is to enable faster, better-informed decisions, there’s nothing that can help you get there that’s more powerful than applying the simplicity principle consistently to business and technology.

Stay tuned for my next blog in the Mobile Analytics Design series.

You may also like the Mobile BI Strategy series on IT Peer Network.

Connect with me on Twitter @KaanTurnali, LinkedIn and here on the IT Peer Network.

A version of this post was originally published on turnali.com and also appeared on the SAP Analytics Blog.