04-22-2019, 11:56 PMztevans Wrote:

04-22-2019, 11:49 PMBDonini Wrote: I still don't understand all the outrage in this thread. It's like JNH said here, it's still the GM's responsibility.


If my manager at work is responsible for a task and they hand that task off to me, I'm being paid to do that task but it doesn't clear my manager of his responsibility. If I mess up, I'll be held accountable but so will my manager as the task was their responsibility in the first place. Yes, there was a pick tracker and he didn't do his job properly but if a GM also has the responsibility to track his own picks then he's also partially at fault.

Imo there's no right or wrong option in this situation, HO could've justifiably given COL compensation for the pick just like they could justifiably deny COL of compensation for the pick.

I guess my biggest issue is that there's a well-established precedent for this exact scenario.  When a pick gets double-traded, the offending team loses an extra pick and the "receiving" team still gets the pick.  This precedent dates back several scenes and came back up very recently.

To go away from that precedent suddenly now because "it's the other team's fault too" ignores that in every other instance we've applied this result, the other team could have spotted the error as well.  Furthermore, HO seems to be leaning a bit on "Well, we've changed pick trackers since then" which, like, yeah, both teams have changed at least one GM since then.  That's only evidence of how badly the ball was dropped by all parties.  So making an exception to the precedent on this one occasion because "It's sorta Colorado's fault too" is really dangerous, imo.

I feel that the situations are different enough for the Halifax/Detroit situation to not be considered precedence though. Halifax isn't responsible for keeping track of Detroit's picks so they couldn't know that Detroit didn't have the pick if the tracker wasn't updated. Colorado acquired the pick in question so had they kept track of their picks they would have caught the error when the draft thread went up.