When should data drive your UX design decisions?

There are many convincing reasons for not basing design decisions on intuition, somebody’s opinion or personal experience – it is against the core principles of user-centred design and can lead to many poor decisions (nobody reads users’ minds). When so many tools for collecting data are available, it is hardly worth the risk of getting it wrong, thus data-driven design is gaining more and more popularity these days.

Data can help you make better decisions

Even though there is a lack of a widely accepted definition or agreement on what “data-driven” means, in essence it is basing design decisions on actual data (qualitative and quantitative).

Nobody gets offended that others do not like his ideas.

Depending on the type and stage of the project, it could involve focus groups and usability tests to understand user’s needs, using analytics and A/B testing to see what performs best, as well as various tests and benchmarks – decisions at each stage of a project could be based on clear data.

There are some other benefits too, for example it could remove some tension within the design team – nobody gets offended that others do not like his ideas, the opinion of the highest person in the company’s hierarchy is not taken unquestionably – if the data shows that some idea is better than the others, it is better.

It is also easier to convince your clients that the new design is worthwhile – you can just show them the statistics instead of relying on highly subjective measures such as “more beautiful and contemporary” and sounding expert enough to make them believe you know what you are saying.

Data itself does not drive innovation

Even though these benefits are real and substantial, there is no such a thing as a magic bullet in design that is suitable for all situations and challenges, thus it is important not to get overexcited about data-driving everything.

Besides the risk of making a wrong analysis with wrong data and confusing correlation with causation (which could be avoided by letting only a qualified person do the analysis), there is a risk of becoming too data-focused and disregarding the fact that innovation and creativity come from a designer, not data.

Requiring a designer to back up even small design decisions with clear data will discourage thinking outside of the box, which is essential in creating a fascinating product.

Of course, this is not a problem with data-driven design, rather with it being used too religiously in a hope that following it will solve all the challenges and create what users really need and want.

Statistics never suggest anything innovative, neither do users – there is a famous quote by (reportedly) Henry Ford that summarises this idea well: “If I had asked people what they wanted, they would have said faster horses”. Data can inspire and inform, but it can never drive something innovative, it can make the product great, but more is needed to make it awesome.

As in all things, a balance needs to be found

For further reading