So, to those that scream about Brad Stevens and his timeouts, tonight with around 9:00 left on the clock Milwaukee was starting a run and instead of calling a timeout, Stevens saved it because the TV timeout was coming up.
Some were complaining about this as they usually do. But it's a good thing he saved it because he needed one with 8.9 seconds remaining so took his last timeout. He told JT go make it happen with confidence and Tatum hits his shot.
You can't constantly call timeouts early in the game because you'll need them late. You especially don't do it if a TV timeout is coming up quickly.
Uh, except the fact that it likely would have not been that close at that point had Brad effectively used the timeouts earlier, thus obviating the need for the extra timeout anyways. This is revisionist history. The fact that we won *despite* the bad judgment made at that time does not make it any less bad of a call. If we would have better managed that run and not let them get momentum in that way it's likely that there's more distance between us in the final minutes.
Defend him all you want, but that's a consistent weak spot of Brad's that *regularly* loses us games because we're not always lucky enough for Tatum to bank in a last-second three and Giannis to miss a go-ahead free throw for us to win it.
Massively clutching at straws here, lol
I mean, it's not though. If anything this argument about the usefulness of the timeout given what happened tonight is.
Nick's position is based on the supposition that if we had used the timeout the game would've gone *exactly* as it did tonight when we didn't use the timeout originally, which in itself is unrealistic based on pure probability and causality.
An effective use of the timeout to manage the Bucks' run there very well could've changed the flow and course of the game, leading to a larger lead and less close game down the stretch. That's the entire argument I'm making. You call the timeout to stop the run, settle your guys down, and then set something up to try and get your guys going again.
Sure, maybe it wouldn't have worked out, but it's illogical to posit that the game would've occurred the exact way it did with or without the timeout there. That's just poor logic.
Or you're just giving TNT ad revenue in between getting your ass kicked.
Why is your assumption that a timeout will definitely - or even probably - end a run? Is there any statistical evidence that supports that idea? I've seen timeouts 'stop' runs, but I've also seen occasions when teams called a timeout just to keep on getting pasted when play resumed.
A quick google search didn't turn up much except for a D'Antoni quote that said timeouts aren't necessarily effective run-stoppers, but I didn't find anything concrete either way.
Good question. I've done a bit of research on this before, but it's something I'm interested and continuously reading about. The statistical and economical evidence is mixed on this, and it's further complicated by some other deeper statistical/economical questions and conflicts within the game that impact upon this question.
The most difficult one in particular is whether there is such a thing as "momentum" or a "hot streak" in sports like this, particularly basketball. One side says that, no, there is no such a thing as "momentum" or a "hot streak"; rather, these are just statistical anomalies of chance with several shots, defensive stops, plays, etc. just happening by chance to occur in a positive direction for the team in a short amount of time. The other side (which I am in agreement with) argues that there is such a thing as "momentum" and "hot streaks", which are likely psychological phenomena leading to increased performance that serve as catalysts for the "momentum" and "hot streaks".
Naturally, the former group is generally on the side that things like timeouts are not effective at stopping "runs", because these are really just statistical anomalies that will revert back to normalcy on their own without any conscious efforts by the opposition. The latter group is generally on the side that things like timeouts can be effective to stop "runs", as the runs are primarily based on other psychological, emotional, or other factors rather than just statistical anomalies.
That's a really basic and rough interpretation (lol), but that's one part of the issue that makes this a difficult thing to truly assess. So I do admit that some of this is based upon basketball philosophy, and I - along with many other coaches in the league and people on here - hold a different philosophy when it comes to this issue. But I've seen Brad blow enough games with this decision to forego timeouts in these scenarios that I'm firmly entrenched in this camp. (The same goes for the timeout prior to a game-winning or game-tying end of game offensive scenario. I'm all for the timeout in that scenario, especially with someone as good at drawing up ATO plays as Brad. Yet Brad holds the "let them play" philosophy and prioritizes the iso play and not letting the defense set over drawing up an efficient, set play. I find this very aggravating lol)