Lately I’ve seen a lot of people saying Shane Greene shouldn’t be our closer, and with how his last two games have gone, I understand why. However, I personally completely disagree with this, and I decided I was going to look to the stats to see if there was anything backing my opinion.
I went into my research knowing that I have a bit of a bias towards Greene due to how much I have enjoyed him on the 619 podcast (This is a podcast Shane Greene and Nick Castellanos do together that just recently started. It is basically them just talking baseball and life, and I personally really enjoy listening to it. It has definitely helped break the barrier between player and fan for me and has made me feel personally connected to both Castellanos and Greene. You should check it out on Apple Podcasts.). However, I did think that I saw a pattern in how Greene performed based on when he came into the game. So I got up an Excel sheet and opened up Baseball Reference and got to work. Below are my findings, starting with Greene’s game logs sorted by what sort of an appearance they were.
*Note: D=Down (he came in when the Tigers were down a run or two), N=Normal (he came in during the 9th inning, but the Tigers were up by more than 3 runs so it wasn’t a save opportunity), SVO=Save Opportunity (he came in with the opportunity to get a save, whether he pitched a little in the 8th or not), and T=Tie (he came into a tied ballgame). Also, I used .33 and .67 for one third of an inning pitched and two thirds of an inning pitched instead of .1 and .2 just because it made calculations easier.
Date | Opponent | IP | ER | BB+H | SO | Type | Inning Entered | |
1-Apr (1) | DETvPIT | 1.00 | 0 | 3 | 1 | D | 9 | |
13-Apr | DETvNYY | 1.00 | 0 | 0 | 0 | D | 9 | |
28-Apr | DET@BAL | 1.00 | 0 | 2 | 2 | N | 9 | |
14-May | DETvCLE | 1.00 | 1 | 3 | 1 | N | 9 | |
30-May | DETvLAA | 1.00 | 0 | 0 | 1 | N | 9 | |
31-May | DETvLAA | 1.00 | 0 | 2 | 2 | N | 9 | |
7-Jun | DET@BOS | 1.00 | 0 | 1 | 0 | N | 9 | |
5-Apr | DET@CHW | 1.00 | 0 | 1 | 3 | SVO | 10 | |
8-Apr | DET@CHW | 1.00 | 0 | 0 | 1 | SVO | 9 | |
17-Apr | DETvBAL | 1.00 | 0 | 0 | 0 | SVO | 9 | |
18-Apr | DETvBAL | 1.00 | 1 | 1 | 2 | SVO | 9 | |
20-Apr (2) | DETvKCR | 1.00 | 1 | 4 | 2 | SVO | 9 | |
25-Apr (1) | DET@PIT | 1.00 | 0 | 0 | 0 | SVO | 9 | |
1-May | DETvTBR | 1.00 | 0 | 0 | 2 | SVO | 9 | |
5-May | DET@KCR | 1.00 | 0 | 2 | 3 | SVO | 9 | |
8-May | DET@TEX | 1.33 | 0 | 1 | 3 | SVO | 8 | |
12-May (1) | DETvSEA | 1.00 | 0 | 3 | 0 | SVO | 9 | |
15-May | DETvCLE | 1.00 | 0 | 0 | 0 | SVO | 9 | |
17-May | DET@SEA | 1.00 | 0 | 0 | 1 | SVO | 9 | |
20-May | DET@SEA | 1.00 | 2 | 2 | 0 | SVO | 9 | |
23-May | DET@MIN | 1.00 | 0 | 0 | 0 | SVO | 9 | |
25-May | DET@CHW | 1.00 | 0 | 1 | 1 | SVO | 9 | |
27-May | DETvCHW | 1.00 | 1 | 2 | 1 | SVO | 9 | |
1-Jun | DETvTOR | 1.00 | 0 | 1 | 1 | SVO | 9 | |
4-Jun (2) | DETvNYY | 1.00 | 0 | 1 | 3 | SVO | 9 | |
13-Jun | DETvMIN | 1.00 | 0 | 0 | 2 | SVO | 9 | |
14-Jun | DETvMIN | 1.00 | 0 | 1 | 2 | SVO | 9 | |
15-Jun | DET@CHW | 1.00 | 0 | 1 | 0 | SVO | 9 | |
16-Jun | DET@CHW | 1.00 | 0 | 0 | 2 | SVO | 9 | |
30-Mar | DETvPIT | 0.67 | 2 | 3 | 1 | T | 9 | |
20-Apr (1) | DETvKCR | 1.00 | 0 | 0 | 1 | T | 9 | |
30-Apr | DETvTBR | 0.33 | 3 | 3 | 0 | T | 9 | |
2-May | DETvTBR | 1.00 | 0 | 1 | 0 | T | 9 | |
13-May | DETvSEA | 1.00 | 0 | 0 | 2 | T | 9 | |
8-Jun | DETvCLE | 1.00 | 3 | 3 | 0 | T | 9 | |
9-Jun | DETvCLE | 1.00 | 0 | 0 | 0 | T | 9 | |
25-Jun | DETvOAK | 1.33 | 1 | 2 | 2 | T | 8 | |
26-Jun | DETvOAK | 0.33 | 2 | 3 | 0 | T | 9 | |
Stats | ERA | WHIP | SO/9 | Innings | BB+H | ER | SO | Appearances |
Down (D) | 0 | 1.50 | 4.5 | 2.00 | 3 | 0 | 1 | 2 |
Normal (N) | 1.8 | 1.60 | 10.8 | 5.00 | 8 | 1 | 6 | 5 |
Save Opportunity (SVO) | 2.01 | 0.94 | 11.69 | 22.33 | 21 | 5 | 29 | 22 |
Tie (T) | 12.91 | 1.96 | 7.04 | 7.67 | 15 | 11 | 6 | 9 |
Overall | 4.14 | 1.27 | 10.22 | 37.00 | 47 | 17 | 42 | 38 |
Digging into this data, you can see a very strange pattern. When Greene enters a game with a chance to earn a save, he generally pitches quite well. His ERA (2.01), WHIP (0.94), and SO/9 (11.69) are all amazing. In fact, if these were his overall numbers, we would consider him and elite, lockdown closer. However, these aren’t his overall numbers as his overall ERA is a large 4.14, so something must be holding back his stats.
Looking at his normal appearances and appearances when the Tigers are down, his WHIP is quite high (1.6 and 1.5), but the sample size is so small (7 appearances and 7IP) that it is hard to call that good evidence. He has also prevented runs from scoring even with the high amount of traffic on the bases. Until the sample size becomes larger, I do not this this data has much merit, even if the higher WHIP shows that Greene has his best stuff when he is closing tight games.
However, looking at Shane Greene’s appearances when games are tied, we see a whole different story. He has given up a remarkable 11 runs in 7.2 innings, along with allowing 15 hits and walks combined. On top of this, he has only struck out 6, giving him a SO/9 well below his overall SO/9 (7.04 to 10.22). In his 9 appearances when the game is tied, he has given up a run more times than he has not (5 to 4). Even though the sample size is small, I think the sheer drop off of his stats proves that tie games are Shane Greene’s kryptonite and the reason some fans view him as a bad closer. To further the point, Greene’s last two appearances were tie games, and he took the loss in both of them.
Overall, even though you generally want your best pitcher in the game in tie games, putting Shane Greene in tends to lead to bad things. In normal save opportunities, Shane Greene is stellar, but his overall stats are extremely inflated due to how poorly he performs in tie game situations. I was honestly surprised at how well the stats lined up with my hypothesis, and I think this proves that Shane Greene should be our closer. We just need to be careful when we use him.