I deleted it.

[SamIAm]

I deleted my thread concerning game management due to the fact that it had no real answer and it was point-less.

[mplagrow]

Originally Posted by SamIAm

I deleted my thread concerning game management due to the fact that it had no real answer and it was point-less.

. . .so you added another post that has no real answer and is pointless to replace it. Thanks.

[Dan_ref]

Let's take this opportunity to discuss game management.

IMO the "game management" concept is completely over-thought. Comes from a combination of what camps are teaching and an uncertainty on some official's part about just how much sh1t they are willing to take and retain their own self-respect.

[Jurassic Referee]

Originally Posted by Dan_ref

Let's take this opportunity to discuss game management.

IMO the "game management" concept is completely over-thought. Comes from a combination of what camps are teaching and an uncertainty on some official's part about just how much sh1t they are willing to take and retain their own self-respect.

Agree. It becomes an excuse for not making calls.

[M&M Guy]

Originally Posted by Dan_ref

Let's take this opportunity to discuss game management.

IMO the "game management" concept is completely over-thought. Comes from a combination of what camps are teaching and an uncertainty on some official's part about just how much sh1t they are willing to take and retain their own self-respect.

Good point.

It seems like I haven't heard this term as much in camp recently. I wonder if there are others that have come to the same conclusion as you: game management = don't blow the whistle.

Maybe because it's so close to dinner, but I would equate game management to seasoning on a steak. Sometimes you need a little, sometimes you don't need any. Either way, you still need to blow the whistle, or use a knife and fork. (On the steak, Dan, not the players and coaches...)

[WhistlesAndStripes]

Originally Posted by M&M Guy

Good point.

It seems like I haven't heard this term as much in camp recently. I wonder if there are others that have come to the same conclusion as you: game management = don't blow the whistle.

Maybe because it's so close to dinner, but I would equate game management to seasoning on a steak. Sometimes you need a little, sometimes you don't need any. Either way, you still need to blow the whistle, or use a knife and fork. (On the steak, Dan, not the players and coaches...)

I think the fork could be likened to an ejection, as in, "Stick a fork in him, cause he's done!!"

[mick]

Originally Posted by Jurassic Referee

Agree. It becomes an excuse for not making calls.

Agree. Too, it becomes an excuse for making weak calls.

[SamIAm]

Originally Posted by mplagrow

. . .so you added another post that has no real answer and is pointless to replace it. Thanks.

It is considered poor manners around here to delete a thread. I made an effort to explain to prevent any nefarious suppositions.
Pointless or not, Mr. Pot, you posted in both of them.

[zebraman]

Originally Posted by Dan_ref

Let's take this opportunity to discuss game management.

IMO the "game management" concept is completely over-thought. Comes from a combination of what camps are teaching and an uncertainty on some official's part about just how much sh1t they are willing to take and retain their own self-respect.

Interesting discussion. I have always thought of game management as everything that does not involve blowing the whistle for fouls and violations.

Managing the coaching box. Managing the clock. Managing a frustrated player before it becomes a situation. Things like that. Things that I was not very good at during my first 5 years of officiating.

[M&M Guy]

Originally Posted by zebraman

Interesting discussion. I have always thought of game management as everything that does not involve blowing the whistle for fouls and violations.

Managing the coaching box. Managing the clock. Managing a frustrated player before it becomes a situation. Things like that. Things that I was not very good at during my first 5 years of officiating.

You're right in that regard. It's just that there seems to be a feeling that it also is an excuse to not blow the whistle.

"Coach called me a a$$hole only twice; I got him calmed down so I wouldn't have to stick him for calling me that the third time."

"I saw you knock that shooter down; please don't do it again or I may have to call a foul."

Game management?

I agree that there are real game mangement situations. Maybe you see a player looking frustrated after missing a couple of shots because a defender is playing great defense; if you can get next to him and quietly remind him to not lose his cool, you might prevent something bad from happening later. I also have told the story about team from the School for the Deaf - the team played hard all game, but was down by 30 - 40 late. One of their players had a FT, clearly stepped over the line before it went in, but I chose not to see it. I was commended after the game for not calling it by both an evaluator and the winning coach. I don't make a habit of not calling violations, but this one certainly falls into the "game management" category. I still don't know exactly where that line is; I guess that's why officiating is an art.

[mplagrow]

Originally Posted by SamIAm

It is considered poor manners around here to delete a thread. I made an effort to explain to prevent any nefarious suppositions.
Pointless or not, Mr. Pot, you posted in both of them.

I get bored. Mr. Pot?

[SamIAm]

Originally Posted by mplagrow

I get bored. Mr. Pot?

As in, "the pot calling the kettle black".

[stmaryrams]

Originally Posted by zebraman

Interesting discussion. I have always thought of game management as everything that does not involve blowing the whistle for fouls and violations.

Managing the coaching box. Managing the clock. Managing a frustrated player before it becomes a situation. Things like that. Things that I was not very good at during my first 5 years of officiating.

I'm with you z. In your manage the clock aspect, Knowing a team will likely take a timeout. Knowing how much time is on the clock on a restart.

Counting to 5 and 5 (not just 10). Those things that keep you from blowing the whistle because they are corrected before they are a problem.

[mplagrow]

Originally Posted by SamIAm

As in, "the pot calling the kettle black".

OK, I see.