# Talking Numbers: The Significance of Statistical Significance

Standard

Statistical Significance. It’s so basic a concept that many modelers and statisticians don’t look for it in simpler analyses such as marketing campaign comparisons, population distributions and so forth. Nevertheless, statistical significance can make all the difference (pun fully intended) in whether results are jaw-dropping or trash-worthy. And when speaking with the business-side of the house, you’d better know which is which.

### Tip for Translation: Less Insignificant Info is More

First of all, check for significance. That could go without saying… but it doesn’t (see above). If the results are not significant then do not put them out there for the business to jump all over… which they will. If they are close to significant and you want to share them, add a caveat/footnote indicating that the results may be the result of random variation. Do not use technical terms here.

“Yeah, but my tests always appear significant because I have enough data that even tiny differences get picked up due to the sample sizes.”
Try bootstrapping smaller samples for comparison and see what happens. If you are still getting significant results, good on ya’. If not, maybe the results weren’t as significant to start with.

“But the business impact of this minuscule difference is huge so therefore it doesn’t matter if the result is significant.”
This is actually even more reason to validate your results. Presumably, if the resulting teeny difference would cause a major upheaval for the business, so too would a minor variation due to natural fluctuation. Use a significance level that aligns with the importance of finding a difference. For a super-important analysis, go with an alpha of .01 or even .001 rather than the usual .05.

### To Show or Not to Show Statistical Significance…

More often than not, business stakeholders only want to see results that are significant. They want to know how the analysis can be used to better effect. In general, that does not mean that you go around flaunting a p-value. Just state the results and how to use them and move on. On the other hand, it is usually informative and interesting to business users to see statistically insignificant results when it confirms or debunks a long-held hypothesis.

For example, let’s say that there is a “gut feel” that customers who buy diapers also buy beer. After doing some testing on purchase data, you find that there is no significant link between these two product categories. The business stakeholders (and holders of the gut feeling) would likely need to know that these two items are not correlated. It impacts store and display layouts for the future.

Got some great examples of significant results that really weren’t? Or times when instincts were proven right/wrong? I’d love to hear all about your adventures with statistical significance in the comments.

# Fostering Customer Community: A Tale of Two Experiences

Standard

What happens when you’ve positioned your business as a trusted, community member, but your customer community goes elsewhere when it’s time to make a purchase?

This is the question plaguing two businesses in my area. Both are retailers who organize events around hobbies. Both face competitive pressure locally and online. They fall on two sides of the same basic question: cash or community?

# Talking Numbers: Presenting Analytics

Standard

One of the most difficult parts of any analyst’s job is packaging and presenting analytics work for a business audience. It’s a matter of showing the “So What” rather than just the “What” of the data. As someone who not only does a lot of presenting, but also coaches others on how to improve their deliverables, I found myself in need of a consistent way to structure results that minimizes the technical or mathematical description and instead focuses on the business implications.

Here’s my framework, along with a handy acronym: FIRST

### Findings

You have to present the facts of the model or analysis. These are the numbers that came from all your hard work. Talk about the hypotheses tested, what fell out, what stayed in, results of tests, etc. Detail any rabbits you chased in the data (anomalies, unexpected results, iterations, etc). Include visualizations wherever able to succinctly illustrate what you saw. This section is of particular interest to other data scientists, model auditing teams, and the statistically-inclined.

### Insights

Now read into the numbers or the model and weave the story. Describe what you learned from the analysis or model and, especially, what it means to the business. Explain what the findings mean in a broader context.

### Recommendations

Document further analyses, follow-on projects, or deeper dives that you recommend pursuing. Also note any follow-up questions that your business stakeholders come up with based on the findings and insights. Build your own backlog of projects and then track them down. This is where you plan to tie up loose ends.

### Suggestions

Describe what you think the business should do, or how it should change, to make use of the insights or models. If there are specific processes that would benefit from incorporating a model or API, indicate how this might be done (do not show code – just say how it would revamp the process). How does this help the business make better decisions about their initiatives?

### Takeaways

This section details who is doing what coming out of this analysis. If there were specific expected actions to be taken based upon results, identify whom is needed to complete them. Any time frames necessary should also be outlined.

## Presenting Analytics in Documents

Putting FIRST into a document is pretty straightforward. Set up the project at the top, laying out the key questions, expected actions, and the planned analysis steps. Then include the FIRST sections with the majority of the content. Document as you go along so that you capture the findings roughly as they occur. This helps to ensure that you present all of the permutations of analysis performed.

## Presenting Analytics in Slides

Most of the time, when presenting analytics, we are called upon to use slides or a slide-like format for conveying information. Again, present the project overview and key questions. Then immediately put forward the key insights. Yes, this is out of order for FIRST. However, the next section is where FIRST comes into play. For each key insight, present the FIRST elements on a single slide.

An example might be that customers using discounts are more valuable over time. On a slide, show a graph comparing the spend patterns of customers with and without discounts. Provide a bullet point indicating that this is the key insight. Then outline additional steps for:

• analyzing types of discounts or time periods of discount as a recommended follow-on,
• using promotions to increase total basket size as a suggestion, and
• planning an upcoming promotion as a takeaway.

Wrap up with a summary of next steps so that there is a clear list of actions to be done.

What methods do you use today for presenting analytics? If you give FIRST a try, please leave comments about how it goes with your key stakeholders.

# Date Intervals in HiveQL

Standard

This picture is definitely not me. But as this is my first post regarding Hive, I felt the need to include a photo of a ridiculous beehive hairdo.

As is the case with many other Data Scientists, I am being pulled increasingly into the world of Hadoop and all the technologies associated with it. Lately this has meant trying to sort out how to do certain functions in HiveQL that I’ve grown familiar and comfortable with in various types of SQL.

Today’s conundrum was trying to determine if someone is at least 18 years old based on their birthday. Normally, I would use one of the following:

`date_of_birth <= current_date - interval('18 years') -- check for True condition OR extract(years from age(current_date,date_of_birth)) --check for >= 18`

There are a few functions that can be used here: DATE_ADD, DATE_SUB, MONTHS_BETWEEN, or ADD_MONTHS.

The DATE_ADD and DATE_SUB are roughly synonymous except that one adds days and the other subtracts them. I suppose that you could add a negative number of days though, if you wanted to just learn one of the two. That might look something like this:

`date_of_birth <= date_add(current_date,(-18*365))`

The number of days being added is calculated using 365 as a nice round number for dealing with years. However, it does not take into account that there could a few leap years in the mix. The DATE_ADD function does not allow decimals in the number of days to add so it cannot be used as -18*365.25 or something. This is not my preferred method. I like more precision.

Next up is the ADD_MONTHS function, which is sort of like using the interval except that you have to calculate the interval based on months rather than years.

`date_of_birth <= add_months(current_date,(-18*12))`

I prefer this method because it accounts for the leap year stuff by ignoring the actual number of days and just changing the months.

Similarly, the MONTHS_BETWEEN could be used along with division to get to the number of years.

`months_between(current_date,date_of_birth)/12.0 --check for >= 18`

# Inserting Multiple Rows into Netezza Table

Standard

This one has been irking me for quite a bit. If you have to insert multiple rows into a table from a list or something, you may be tempted to use the standard PostgreSQL method of…

```INSERT INTO TABLE_NAME VALUES
(1,2,3),
(4,5,6),
(7,8,9)
;```

Be warned – THIS WILL NOT WORK IN NETEZZA! Netezza does not allow for the insertion of multiple rows in one statement if you are using VALUES.

You have two options here: 1) create a file with your values and load it (see Loading Data into Netezza post) or 2) use individual INSERT INTO statements. With a small, simple set of records like the one above, the second method will do fine. It would look like this…

```INSERT INTO TABLE_NAME VALUES (1,2,3);
INSERT INTO TABLE_NAME VALUES (4,5,6);
INSERT INTO TABLE_NAME VALUES (7,8,9);```

If you have larger sets of data to insert or more complex row structures, consider using an external table.

Official documentation for IBM Netezza INSERT command.

Standard

Netezza is a super-fast platform for databases… once you have data on it. Somehow, getting the data to the server always seems like a bit of a hassle (admittedly, not as big a hassle as old school punchcards). If you’re using Netezza, you’re probably part of a large organization that may also have some hefty ETL tools that can do the transfer. But if you’re not personally part of the team that does ETL, yet still need to put data onto Netezza, you’ve got to find another way. The EXTERNAL TABLE functionality may just be the solution for you.

# Common Table Expressions versus Temp Tables in Netezza

Standard

This seems to be either a controversial or overly-technical topic: should you use WITH (a common table expression a.k.a. CTE) or a TEMP TABLE. Both can serve similar purposes but each has their own strengths and weaknesses in how they work with other aspects of your query or procedure.

So today we’ll take a look at both without going into crazy detail but covering at least the basics.

# Top 5 Reasons Why I Love Being a Data Scientist

Standard

According to GlassDoor, Data Scientists have the best work-life balance of all professions. Go us! And with thousands of Data Science positions out there in dozens of fields, it’s no wonder that we’re a growing group.

“What makes being a Data Scientist so great?”, you might ask. Well, lots of things. Here are the top 5 reasons why I love my job as a Data Scientist.

# Epic Epoch Time in Netezza and PostgreSQL

Standard

Epoch time is both a blessing and a curse. It is super-convenient for counting seconds (and doing calculations based on them) but can also be a pain to try to get into something readable as, or comparable to, a recognizable date. So today we’ll get into and out of epoch to show its flexibility without our brains having to be contortionists too.

# Seeking Small: Why Big Retailers Envy Mom & Pop

Standard

There are a few local stores I visit often – enough so that they know my name, preferences, boyfriend’s name, work/travel schedule, and even my pets. They call me on my cell phone when something new is available that they know I’ll love. They make sure I know in advance about events they’re holding. In return, I’m glad to pick up the phone when I see that they’re calling.

These are the experts in personalization and targeted messaging. They are the kings and queens of the customer relationship. And the big box retailers of the world are tremendously jealous of them.