Tuesday, March 10, 2009

Handling Those Situations Part 1

At our first clinic this year Garret quoted Jim Evans saying, "95% of this game can call itself". There will be games that you are in the field and really don't make many calls. You still have to work your butt off by busting to the correct position and work hard. You may signal safe, foul, or outs but nothing close. This is normal, this is baseball. However there will be games that you constantly are calling those bang-bang plays or ruling on weird situations (the other 5 %). Those games will drain you, so be prepared. We are there to do a job and that is to call that game. It can be fun and it can be a bit rough at times. You will learn this with experience. There will be days that nobody says a word and days where half to everyone may hate you. That is part of the job. There will be times a coach tests you to see your limits to see how much he can get away with. There also will be times a coach goes off for little reason or very good reason. Ejections happen. They should not happen often, but they happen. So I wanted to give a simple post about handling situations. This should be new to all of the rookies and may serve as a refresher to the vets.

Simply, Don't take it! That does not mean you have to be a red A@# and go looking for trouble. What that means is that you should be approachable by coaches and able to discuss situations with them, yet not taking remarks and inappropriate actions from them. There is a balance. You will learn this with proper training and experience. Always ask your peers and veterans, "did I handle this right?" That is what this is all about.


Steps to Handling those Situations

Step 1 Ignore
a. Ignore what they say. Example: "Come on Blue be consistent, that ball was up. That is
terrible!"
b. Ignoring someone who wants attention will frustrate them.

Step 2 Acknowledgment
a. Take a look at the coach
b. It can be verbal, "I hear you Mike!"
c. Acknowledge that you heard them, do not move toward them, and you may possibly give
them the stop sign with your hand

Step 3 Warn
a. Step out from your position
b. Verbal, "Coach this is your warning"
c. At that moment write down your warning on your line up card
d. He has now had a verbal and physical warning
e. Be prepared to act on your warning

Step 4 Restrict/Eject
a. The coach has been warned
b. In Fed rules coaches may be restricted to the dugout instead of being ejected. Verbal:
"Coach, you are restricted to the dugout for the remainder of the game."
c. Be prepared for an ejection. Typically coaches do not like to be restricted and feel they may as
well be ejected.
d. If there is an argument with a call you can use this verbal mechanic, "Coach, if you do not immediately go back (or stop complaining from the dugout) you will leave the game."
e. Give a strong, yet not over the top, ejection mechanic and prepare for the fallout :)

Tomorrow we can continue with this in Part Deux. We will possibly discuss what to do during the arguments and after the ejections regarding partner help.

3 comments:

  1. GREAT job, Ricky. This blog will be invaluable for all of us. Can't wait for the interaction.

    Paul Yarbrough

    ReplyDelete
  2. One of the things suggested to me by a veteran umpire (and it was something I'd already been making an effort to do) is to call each head coach by their first name instead of just "Coach". This can help keep things on friendly terms and sort of even the playing field. We're the umpires and they're the coaches, but just because we're out there doing different jobs, we're still equal--they're not superior to us, nor are we to them.

    ReplyDelete
  3. Steve I completly agree. I always call the coach by his first name. Matter a fact I write it on the outside of the line up cards before I fold them up following the plate talk as a reminder. I called him coach in the examples to avoid confusion. So yes I encourage us to learn their names. If they don't address you by your name simply remind them. "hey Mike just call me Ricky". As for not being superior to them...well we may disagree. That may not always be the case :)

    ReplyDelete