Recommended Posts

Found this great article on CNNSI about sports teams and choking. Thought I'd share it with you all:

We need to get something straight about choking, which is merely the most misunderstood concept in all of sports. It has become a catch-all term, applied to any player or team who: A) blows a huge lead; B) fails in a crucial moment; or C) loses an important game more than once. Whenever someone falls into any of those three categories, we turn into that annoying Rob Schneider character from Saturday Night Live. The New York Yankees give away a 3-0 lead in the ALCS? Chokesters. Scott Norwood misses a last-second, game-winning field goal in the Super Bowl? The choke-man. Phil Mickelson comes up short in major after major? Choke-o-rama.

But not everyone who fails when we expect them to succeed is a choker. In fact, most of them aren't. The Yankees are the latest team to have the tag slapped on them unfairly, a result of their unprecedented collapse against the Boston Red Sox in the ALCS. There are any number of words that accurately describe the Yanks' failure -- "humiliating" comes to mind -- but "choking" is not one of them. A choker is a player or team who loses because the pressure of the moment adversely affects their performance. There is no way that could logically be said of the Yankees. They have thrived under pressure so often that it's absurd to think that they suddenly crumbled because of the magnitude of the moment.

Yankee closer Mariano Rivera, nearly infallible in the postseason for close to a decade now, didn't blow two saves against the Sox because he suddenly turned weak in the knees. Teammates like Derek Jeter, Bernie Williams, and Jorge Posada should likewise be immune from accusations of choking. They've succeeded in the clutch so many times that when they fail, it makes no sense to suggest that they suddenly developed a case of nerves.

Among elite athletes, choking is a rare but usually unmistakable occurrence. The purest example I've seen first-hand came in the 2000 NBA playoffs, when the Portland Trail Blazers squandered a huge fourth-quarter lead in the seventh game of their series against the Los Angeles Lakers. It wasn't that the Blazers lost, it was how they lost. As their lead dwindled and the L.A. crowd grew louder, the Blazers looked scared. Suddenly they couldn't make the easiest shots, shots they had been making all game, all series, all season. I remember Portland's Rasheed Wallace continually looking up at the scoreboard clock as if he was praying that time would run out before the Lakers could catch them. The Blazers were overwhelmed not so much by the Lakers but by the intensity of the circumstances. That's choking.

Choking is a mostly mental phenomenon that affects physical performance. Just so we're clear, a few examples:

Remember the panicked look on Chris Webber's face when he called for a timeout that Michigan didn't have in the NCAA championship game? That was a choke.

Bill Buckner's boot in the 1986 World Series? A physical mistake at the worst possible time, but not a choke.

The heavily favored Lakers losing four straight to the Detroit Pistons in the NBA Finals last season? Massive collapse, yes. Choke, no.

Golfer Jean Van de Velde, blowing the 1999 British Open with terrible shots and even worse decisions for a triple bogey on the final hole? Paging Dr. Heimlich.

Sometimes accusations of choking can do a disservice to the winner as well as the loser. Suggesting that the Yankees choked, for instance, diminishes the accomplishment of the Red Sox. The Sox were simply the better team for the last four games of the series, just as they appear to be the better team in the World Series against the Cardinals. With a 2-0 lead, it appears that the Red Sox are finally going to bring a World Series title to New England. You can feel their fans' excitement. You can sense the anticipation building. But a friendly word of caution to the Red Sox nation, who surely know this better than anyone:

The circumstances are perfect for a choke.

CNNSI

Link to comment
https://www.neowin.net/forum/topic/236329-thought-the-yankees-choked/
Share on other sites

ahhh denial is a good thing :p

584813678[/snapback]

It's not denial. They lost and it was a pretty embarassing situation. However, they didn't choke, they just went into a slump. There is a difference. Boston earned their spot, without a doubt, but this guy is right, the Yanks didn't choke.

It's not denial. They lost and it was a pretty embarassing situation. However, they didn't choke, they just went into a slump. There is a difference. Boston earned their spot, without a doubt, but this guy is right, the Yanks didn't choke.

584813708[/snapback]

Thank you, for being one of the few intelligent people here.

The article's absolutely right. Choking is balking under the pressure and doing something stupid.

If you want a great example of a 'choke', just watch Bill Buckner trying to get the last out of the '86 World Series. He was literally two feet away from breaking the Bambino's Curse and winning it all when he choked and missed the ball that was rolling right up to him.

/flame on!

They choked, 4 straight loses when up by 3 with 1 to win is choking, no matter what the actual definition from dictionary.com says :p

584814642[/snapback]

That's an absurd statement.

I'm defining you as 'X', regardless of what 'X' actually means!

Uh, no.

The Yankees blew 4 straight in one of the biggest losses in history, but it wasn't a choke, which happens in an instant. They just plain lost it.

Yankees choked many times during the Sox's comeback run. I didn't see all the games but the announcer in game 7 said that many times, they had the chance to end the series and they failed to do so. Maybe its not choking because of pressure, but over confidence or under estimating the oponent. Either way, they paid the ultimate price for it, choking or not.

And the Lakers didn't lose 4 straights to the pistons, they won the 2nd game on Kobe's buzzer beater that sent the game to overtime which they won. And then lost the next 3 games.

Edited by mayamaniac

It's an opinion... one that I disagree with. You can't simple label some of those things choking and others not. The Yankess may thrive on pressure, but that doesn't mean that they couldn't have choked. Not saying they did or didn't, but I just find the reasoning stupid.

Well guess what. I'm going to have to say that the Yankees have just redefined the meaning of 'choke'

If it was the greatest comeback in baseball history, then it must also be the greatest failure. To be up 3 games and then blow it all away is not excusable. The new definition is to inexcusibly blow an incredible advantage or lead when it matters the most

  • 3 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Nvidia 576.80 WHQL graphics driver fixes 5090 FE on idle, adds new games, and more by Taras Buria Nvidia has released a new graphics driver with support for new games and a long list of various fixes. If you have a compatible graphics card, you can download driver 576.80 WHQL. It adds optimizations and day-0 support for FBC: Firebreak, DLSS 4 and multi-frame generation for REMATCH, and path tracing support for DOOM: The Dark Ages. Fixed gaming bugs in driver 576.80 include the following: Dune: Awakening: stability issues EA Sports FC 25: stability issues Dragons Dogma 2: displays shadow flicker Clair Obscur: Expedition 33: stability issues Enshrouded: crashes after launching game Monster Hunter World: stability issues when playing in DX12 mode Gray Zone Warfare: stability issues Marvel Rivals: stability issues Ghost of Tsushima Directors Cut: Flickering/corruption around light sources GTA V Enhanced: stability issues Honor of Kings: World: stability issues Forza Horizon 5: stability issues Indiana Jones and The Great Circle: Image corruption And here is the list of general bugs that have been fixed: GeForce RTX 5090 FE acoustic improvements for idle and low loads Changing a setting in the NVIDIA Control Panel -> Manage 3D Settings may trigger shader disk cache rebuild Twinmotion: Bugcheck when attempting to launch Adobe Substance 3D Painter: showing viewport corruption after baking BlackmagicDesign: UI overlay in Fusion page is not displayed correctly Video playback in a web browser may show brief red/green flash corruption Videos captured with NVIDIA App may appear washed out after editing with the Windows Photos app Certain DisplayPort 1.4 monitors may display random black screen flicker when connected to DisplayPort 2.1 graphics card In addition to the new driver, Nvidia released a new version of the Nvidia app, which now supports DLSS 4 override options under Driver Settings > Graphics for supported titles. With today's release, DLSS override is available for 46 new games, such as DCS World, F1 25, Frostpunk 2, Avowed, and more. The full list of new games is available here. Also, the Nvidia app now has optimal settings for Dune: Awakening, F1 25, FBC: Firebreak, and REMATCH. You can download the driver Nvidia 576.80 WHQL from the official website or the Nvidia app. Full release notes are available here (PDF).
    • And you can guarantee they're going to sell a phone that is full of non-U.S. made parts assembled by non-U.S. labor. Agent Orange wants iPhones built in the U.S. despite the cost but won't care about his own product if it can be made cheaper in Asia.
    • Sorry, no - Data protection is solely the responsibility of the user. If you value the data, you have multiple copies. Microsoft/Dropbox/Apple/Box etc will all have similar ToS - it's still your data and you're still responsible for your DR planning. Sure there may be an issue with access or the provider going bust or a catastrophic failure of infra the datacentre end, and that's a problem (potentially very large and SLA invoking problem) but if that scenario means you loose all your data that's on you at the end of the day. I'm a huge fan of OneDrive with KFM and FOD, it's brilliant and I use it all the time both personally and professionally, but in both cases OneDrive is not the only place the data is stored and nor should it (or any cloud service) ever be.
  • Recent Achievements

    • Experienced
      dismuter went up a rank
      Experienced
    • One Month Later
      mevinyavin earned a badge
      One Month Later
    • Week One Done
      rozermack875 earned a badge
      Week One Done
    • Week One Done
      oneworldtechnologies earned a badge
      Week One Done
    • Veteran
      matthiew went up a rank
      Veteran
  • Popular Contributors

    1. 1
      +primortal
      703
    2. 2
      ATLien_0
      271
    3. 3
      Michael Scrip
      213
    4. 4
      +FloatingFatMan
      186
    5. 5
      Steven P.
      143
  • Tell a friend

    Love Neowin? Tell a friend!