Romo answered questions ahead of Super Bowl LIII in Atlanta. He will be on the CBS broadcast as an analyst.
The Super Bowl LIII media frenzy has begun in Atlanta, Georgia, and the Kansas City Chiefs are not a part of it.
That didn’t stop a reporter from asking CBS broadcaster and former Dallas Cowboys quarterback Tony Romo about causing Chiefs defensive coordinator Bob Sutton to lose his job. Romo correctly predicted much of what Tom Brady and the New England Patriots did in the AFC Title game against the Chiefs, especially toward the end of the game, leading some media members to believe he might have had something to do with Sutton’s firing.
Tony Romo got Bob Sutton fired. Romo was just doing his job, but he got him fired.
— Doug Gottlieb (@GottliebShow) January 22, 2019
Here’s the video, courtesy of Brooke Pryor of The Kansas City Star.
Tony Romo asked how he felt about essentially getting Bob Sutton fired after his see-into-the-future play-by-play in the AFC Championship pic.twitter.com/ikVhN4pCSD
— Brooke Pryor (@bepryor) January 29, 2019
“Yeah, I didn’t think your question to me was very good, so I’m just going to pass,” Romo said, via Pryor, as the crowd laughed. “Nah, I think what you find in the NFL, it goes much deeper. When any coach doesn’t have a job the next year, it’s not one game, it’s not one moment—it’s a collection. It’s like players. Evaluate it, like everybody. Coach (Bob) Sutton’s been incredible his whole career. You know, sometimes coaches make changes for different reasons. You’d have to ask coach (Andy) Reid that.”
Reid and the Chiefs fired Sutton on January 22 and hired his replacement in Steve Spagnuolo on January 24, but Reid has yet to be made available for a press conference.
Though Romo having something to do with Sutton’s firing is an interesting thought, he’s correct in saying there was more to it than his broadcast wizardry.
The Chiefs finished 31st in yards allowed per game (405.5) and 24th in points per game (26.3) in 2018. It was time.
from Arrowhead Pride - All Posts http://bit.ly/2G94MIa
No comments:
Post a Comment