A better experience

The North Star for data teams is to build better data experiences.

So, what is a data experience?

Let's think about it from different perspectives within an organization.

Ask the CEO…

if the executive reports are refreshed as often as they would like. Does she have to wait one hour or 30 days to see key trends and KPIs?

Ask your Data Analyst or Business Analyst…

how many different source systems do they export data from to build the reports leadership asks of them.

Ask the marketing team…

what information about their customer base would make their job easier. Sit in any leadership meeting long enough and you will hear "We don't know that information" or "We don't have that data".

Ask the CFO…

if their financial forecasts are based on hourly, daily, weekly, or monthly trends. Aggregated data is powerful, but only aggregated data is crippling.

Ask the Operations Manager…

if his team managing inventory has access to all the data they need to order and stock effectively.

Ask your Application Dev Manager…

if the databases used by the applications are a performance bottleneck or if they create a great user experience.

Data experiences are (at least) about:

• Delayed data

• Disparate data

• Absent data

• Aggregated data

• Accessible data

• Responsive data

Keep going down the list in your company. Talk with anyone in any org. They all have data experiences. Some great. Some terrible. Many are exceedingly average because few people care to ask.

I'm glad you're here,

Sawyer