Data-Inspired vs. Data-Informed vs. Data-Driven Design


Q: What is Data-Driven Design?

Dear Reader,

That term "data-driven design" is thrown around a lot. Let's tackle it.

Last week, I asked some design friends what data-driven design meant. Here's what they told me:

Data-driven design means data science and A/B Tests.
Data-driven design means qualitative data drives projects.
Data-driven design is a buzzword used by managers to feel objective

It's true. I have seen "data-driven" projects cherry-pick data because the CEO or HiPPO (highest-paid person's opinion) didn't like the outcome.

But I've also worked with some brilliant data scientists who embody the term "data-driven" and have very high standards of rigor for data.

How should designers use data to make decisions?

There are 3 ways.

Note: "data" = both qualitative + quantitative data and focuses on customer data, both declarative and behavioral.

Data-Inspired Design

"Customer data is a source of inspiration, but intuitions make decisions."

Data is "insightful" to you, but it can come from anywhere and be cherry-picked. You prioritize a big-picture, future view. Trends, declarative data, and insights drive your team.

Example: Designers interview users periodically, and this declarative data indirectly lead them to simplify their app's information architecture. Later, the product manager noticed a drop in the numbers simultaneously as the feature launched. They suspect the customers' opinions they talked to don't match the customer base as a whole. In the end, they don't change the feature because they all agree that the change was an improvement. After all, the senior designer says that it's a best practice, and she's an expert in information architecture.

The Designer's Role:

  • Gather inputs and stay up-to-date on customer trends
  • Design based on intuition using any research or analytics data you can gather
  • Measure your work through outputs and company goals

Decision-Making: Experience makes decisions even over data

#Strategy #Insights #Inspiration

Data-Informed Design

"Customer data helps you evaluate your design decisions."

Customer data is "pulled" by experts or gathered through usability tests to measure projects. Big-picture goals, quantitative KPIs, and qualitative feedback drive the team.

Example: You create and launch a feature based on your team's quarterly OKRs that they hope will increase the adoption of their app. After releasing the feature, your team notices a significant drop in adoption on the analytics dashboard the same day as the release. You do some usability tests to figure out where the issue is. You don't find a problem, but you decide to change a few things that users bring up in the interview.

The Designer's Role:

  • Use research, testing, and analytics to adapt designs to the customer.
  • Design based on past research/intuition but evaluate your work through usability and analytics.
  • Measure your work indirectly through a variety of data points on customer outcomes using analytics and team KPIs

Decision-Making: Experience makes decisions unless customer data informs us that we're wrong.

#Analytics #Usability #Evaluation

Data-Driven Design

"Customer data shows you what to design next."

Design methods are seen as a valuable way to generate data. Design data de-risks ideas and enhances decision-making for the whole team. Behavioral data from experiments drive the team. Customer data is the start and end of projects because it's how you determine what to build.

Example: The last experiment you designed was a test of a new feature you want to build. You set up a Landing Page Test to see if users would give you their email address for the new feature. They didn't respond like you guessed...but in the experiment retro, your team looks at the heat map you added on Hotjar. You notice that every user that gave an email address hovered on the newsletter form at the bottom. You decide to design an experiment to remove all other forms from the page. It passes the test! So you design a prototype to test usability now that you tested the desirability.

The Designer's Role:

  • Design experiments that will generate customer data and enhance decision-making for the whole team.
  • Design based on learning from recent experiments and set up evaluation criteria before designing anything.
  • Measure your work directly through behavioral and data and de-risk ideas in lo-fi concept tests and hi-fi A/B tests.

Decision-Making: Experiments make decisions even over experience

#Experimentation #ConceptTesting #Innovation

Upcoming Live Courses


COURSE: Defining UX Strategy
Learn to design a winning strategy that aligns design with business.
Self-paced seats available・Next live cohort starts in autumn 2026
Buy a Seat


COURSE: Facilitating Workshops
Learn to turn meetings into momentum and clear decisions.
Next cohort: March 23–April 30, 2026
Buy a Seat
Only 1 coaching seat left!


Don't dishearten if you don't like where you land in this framework. Your role, team, and budget affect what you can do with data.

Build the skills to work with whatever customer data you can get hold of...qualitative and quantitative.

Until next week, get inspired, informed, or driven about data!

Jeff Humble
Designer & Co-Founder
The Fountain Institute

P.S. This Saturday, I'm giving a FREE webinar on concept tests and data-driven prototyping: Get a masterclass in designing with data→

Huge thanks goes to Adithya Jayan (AJ), Maximilian Schmidt, Maximilian's data scientist colleague, Mahdis Atabaki, Jean-Luc Momprivé, Damian Martone, Gonzalo Sanchidrian, Mohit Kishore, Gabe Ali, and Paolo Gambardella for giving their time to provide feedback on this framework.

The Fountain Institute

The Fountain Institute is an independent online school that teaches advanced UX & product skills.

Read more from The Fountain Institute
A collage-style image showing two identical women in long dresses near a revolving door, one entering and one stepping away, with abstract starburst shapes behind them.

Why Decisions Feel So Hard Right Nows By Hannah Baker Dear Reader, Over the last few months, I’ve been talking with design and product leaders across very different organizations, large companies, smaller teams, fast-moving environments, and slower ones. And I keep hearing the same thing. Their teams are being asked to make decisions faster than ever, and yet, deciding feels heavier than it used to. Not slower, exactly. Just harder. At first, people often explain this in familiar ways: too...

IBM Watson AI Failure

When Speed Stops Being the Bottleneck by Jeff Humble Dear Reader, Quick question: What happens when the thing that used to take 12 weeks now takes 4 days? I've been watching this play out across the industry, and it's wild. Lots of companies aren't sharing their new speeds, but a few are: Code and Theory (an agency that works with Microsoft and Amazon) is building dashboards in 40 minutes that used to take a week. They report cutting time-to-prototype by 75%. Coinbase reports a 2-5x increase...

Missed a few newsletters last year? Start here. By Hannah Baker Dear Reader, Before we jump into new ideas for the year ahead, we wanted to pause for a moment. If your inbox was anything like ours last year, there’s a good chance you missed a few newsletters. So instead of sending another new idea right away, we put together a curated catch-up, a handful of pieces from 2025 that capture the questions we kept returning to. If you only read a few things from us last year, these are a good place...