Kansas City Chiefs: Enough With the Tony Romo Rumors

Jan 4, 2015; Arlington, TX, USA; Dallas Cowboys quarterback Tony Romo (9) reacts during the game against the Detroit Lions in the NFC Wild Card Playoff Game at AT&T Stadium. Mandatory Credit: Kevin Jairaj-USA TODAY Sports
Jan 4, 2015; Arlington, TX, USA; Dallas Cowboys quarterback Tony Romo (9) reacts during the game against the Detroit Lions in the NFC Wild Card Playoff Game at AT&T Stadium. Mandatory Credit: Kevin Jairaj-USA TODAY Sports /
facebooktwitterreddit

The Kansas City Chiefs are likely looking to move on from quarterback Alex Smith in the coming years, but Tony Romo is not the answer. Let’s stop with the “Bring Romo to KC” conversations.

The KC Chiefs are in a good spot right now. They’re 7-2 and leading the AFC West and look to be playoff bound for the second straight season.

Looking towards the future, however, it’s evident that Alex Smith might not be in the team’s future plans. He looked downright awful against the Carolina Panthers last weekend and has never been the type of guy to “light it up” on the field. His recent concussion might signal the end of Smith’s time in Kansas City.

The guy that Mike Florio of Pro Football Talk has suggested to replace Smith though makes absolutely no sense. That guy, by the way, is Dallas Cowboys now backup quarterback Tony Romo.

Romo isn’t a guy who’s going to come in and lead this team to the promise land.

Romo was out for most of the 2015 season and then got injured again during preseason this year. His backup, rookie Dak Prescott, came in and dominated under center for the Cowboys to the tune of an 8-1 record, and Romo recently had to accept the fact that this wasn’t his team anymore.

As football fans, we all know the drill.

When a “prominent” football player runs his course with one team, the rumors about which team he’ll wind up with next start to surface and spread like wildfire.

If you ask me, which none of you did, but you’re going to hear my opinion anyway, I want nothing to do with Tony Romo becoming a member of the Kansas City Chiefs.

Romo is one hit away from his entire career being over with (which I’m surprised he’s not already contemplating that, to be honest). He’s always been injury prone and that’s not a good thing for a quarterback that’s going to be 37 years old next season.

More from KC Kingdom

Alex Smith will be 33 next season and has shown he knows how to win with this team. He’s also won in the playoffs recently and isn’t injury prone.

Romo is older than Smith, has been bad in the playoffs, and is injury prone. He chokes under pressure and that’s not the type of quarterback that the KC Chiefs need to sign for next year.

If the Chiefs decide to move on from Smith next season, then so be it, but Tony Romo is not the solution. Let division rival Denver or a team like the Jets take a chance on Romo. He’s not needed in Kansas City.

As far as the KC Chiefs quarterback situation goes though, here’s how I think it should break down. The Chiefs draft a quarterback in one of the earlier rounds this year, let him sit behind Smith in 2017, and then let the new guy take the reigns in 2018.

That seems so easy in theory, but we’ve seen how bad the Chiefs are at developing quarterbacks. I believe this is the year in which John Dorsey and the Kansas City Chiefs finally draft a quarterback and try and develop him into the future franchise starter.

Next: Five Worst Starting Quarterbacks for the Chiefs

With the defense they have this season, the Chiefs are Super Bowl contenders, and likely will be next year too assuming they don’t lose too much talent (Eric Berry, Dontari Poe, etc). Maybe Smith isn’t the best quarterback in the world, but he’s still playing smart football and isn’t costing this team games.

Romo isn’t a guy who’s going to come in and lead this team to the promise land. He’s an overrated and old quarterback who the Chiefs should want no part of.

Pass.