Tuesday, June 30, 2009

Explanation on Roster Moves

My last two blog posts have received comments along these lines: "No offense to Ramon Ramirez, but he was only batting .211. Why was he moved up?"

This is a good question, and one that would be better answered by the Diamondbacks, since they are the ones that made the move. However, I can tell you that promotions aren't always about who has the best numbers.

Looking at the Silver Hawks roster, we see 25 players. So why wasn't the guy with the best stats promoted? Let's start trimming off guys:

First off, Visalia needed a position player, so that eliminates the 13 pitchers, and leaves us with 12 players that could be promoted.

Secondly, they needed an infielder, so that trims off six more (two catchers and four outfielders), leaving us with six players that could be promoted.

Thirdly, they needed a corner infielder, so that trims off Navarro, Elmore, and Estevez, leaving us with:

1) Ramon Ramirez
2) Justin Parker
3) Nelson Gomez

Of those three, Parker has the best numbers, but he is just coming back from an injury and has played in just two games in the last three weeks. Are you really going to promote a guy who has been hurt, and force him to play against tougher competition as he's trying to get better?

So now between Gomez and Ramirez, while Gomez has slightly better numbers, Ramirez is older, has been in the system longer, and is better suited for a move to the next level. Gomez is just starting to figure out his hitting here in the Midwest League, and a move right now could mess him up.

Ramirez is a veteran player who can move up, fill the role needed (even if it's as a backup), and not miss a beat. Again, no offense meant here to Ramon Ramirez, but a promotion is very rarely given to the best player on the team. Age has a lot to do with it. Experience has a lot to do with it. And the biggest key of all is who can fill the open role at the next level.

And another important thing to remember is that you wouldn't promote a left-handed specialist reliever to fill a starting role at the next level, right? So you also wouldnt' promote a starting third baseman to fill a backup role. You want to keep guys in their same roles all the way through the system for the most part.

Hopefully this helps.

6 comments:

  1. Thank you Owen, I was having a hard time understanding the move, but with you explaining it, it makes sense. I was going over possible moves last night with someone, and that wasn't one we saw coming. Do you think they might be trimming the outfielders as we now have 5? And also, once Dan S. is off the DL, is it possible all the promotions could be sent back?

    ReplyDelete
  2. Ok. Thanks again!
    I guess this is just the start of more changes to come since the draft just happened, and the lower leagues have started the seasons.

    ReplyDelete
  3. I'd say as people get healthy, you'll see some shuffling again. Whether it be players moving back the other direction or guys getting released, that remains to be seen. I'd be shocked if we saw Duffy come back down. I think Ramirez has a chance to come back at some point, but I don't know that for a fact.

    ReplyDelete
  4. Just a few notes, Ramon played 3rd base last year, this year he has played 1st base.

    Despite his batting average, he is hitting better this year compared to last.

    of course, there will always be questionable moves up and down as well as questionable releases that don't always seem to make sense.

    Dave

    ReplyDelete
  5. Facts
    Gomez is 8th moths younger than Ramirez, when you highlight this I was thinking in a bigger difference.
    I’ll said in the post was miss the error committed by each one of the sort list, ok let me tell you
    G E E/G
    Parker 48 17 .35
    Gomez 58 13 .22
    Ramirez 40 5 .125

    ReplyDelete
  6. Yes, Gomez is only 8 months younger, but Ramirez has been in the organization since 2004. Gomez has been in the organization since 2008. That's a huge difference. Maybe I should have said Ramirez is "more experienced" rather than "older".

    ReplyDelete