New York Yankees pitcher Devin Williams

...

Zach Pressnell

By Zach Pressnell

Contributing Sports Writer

0

Share

Newsweek is a Trust Project member

See more of our trusted coverage when you search.Prefer Newsweek on Googleto see more of our trusted coverage when you search.


The New York Yankees swung a blockbuster trade for Milwaukee Brewers closer Devin Williams during the offseason, but the regular season hasn't been kind to the righty.

Williams is 0-2 with one blown save in five attempts, but he's allowed 10 earned runs in eight innings. He's getting hit, and they're not jammed shots. The righty is getting hit considerably hard right now.

Yankees manager Aaron Boone recently announced he had removed Williams from the closer role for right now, presumably replacing him with Luke Weaver.

Read More on MLB

New York Yankees pitcher Devin Williams

...

"This is a guy who's in the prime of his career," Boone said. "He's just going through it, and it happens. I tell our players all the time, you make a career at this long enough, and you're going to face some challenging moments. You're going to face some adversity along the way.

"The good news for Devin is, he has everything to get through this and come out better from the other side. That's my expectation. Right now, it's best for everyone to pull him out of that role and try to start building some good rhythm, confidence and momentum. I fully expect him to be a central figure for us moving forward."

Adjusting to being in the Bronx is a tough thing to do. The good thing about it is the fact that Williams is incredibly talented. Weaver can handle the closer role right now while Williams works out the kinks in a lower-leverage role.

This is a great decision by Boone, and it should pay dividends down the stretch of the season. There's a chance the Yankees pursue a trade for another high-leverage arm this season, too.

More MLB: Guardians Manager Makes Shocking Emmanuel Clase, Cade Smith Announcement

View 0 Comments

Request Reprint & Licensing

Submit Correction

View Editorial & AI Guidelines