My goals in this talk:
A key performance indicator (KPI) is a performance measurement of how well an organization is doing at achieving a specific goal.
KPIs typically follow a pattern:
In the data warehousing world, we have the notion of a grain. The grain of a fact (or measurement) is the maximum level of specificity for that measurement. We usually define grain in terms of dimensions, explanatory information which helps provide relevant context to the fact.
Ex: what is the grain for orders at a grocery store?
Once we know the grain of our measure, we know we can't dig any deeper (without making certain potentially-scary assumptions). We can, however, aggregate results and move up in our grain.
We also cannot move "orthogonal" to an existing grain. If we collect order data by customer and date, we cannot later aggregate this data by "missing" features like store location or register number.
We can, however, aggregate if there is a mapping function from our initial grain to the new grain, such as from customer to customer's favorite color.
We can aggregate any number, but some aggregations don't make sense. There are three levels of additivity:
A fact is a record in a dataset which tells us about something which has happened. A measure is some computation or explanation about the fact. A KPI is a measure which ties back to business need.
From here on out, it's all KPIs all the time! We will cover four main bases of KPI:
Review the code repository for bonus KPIs as well!
Over the course of this talk, we introduced the concept of key performance indicators (KPIs). We showed how to calculate a series of KPIs for a retail company using a variety of functions and capabilities in T-SQL, as well as a powerful calendar table.
To learn more, go here:
https://csmore.info/on/business
And for help, contact me:
feasel@catallaxyservices.com | @feaselkl
Catallaxy Services consulting:
https://CSmore.info/on/contact