Should the Chiefs Sign Chris Chambers?

Steve SwearenginContributor INovember 3, 2009

PITTSBURGH - JANUARY 11:  Chris Chambers #89 of the San Diego Chargers  warms up against the Pittsburgh Steelers during their AFC Divisional Playoff Game on January 11, 2009 at Heinz Field in Pittsburgh, Pennsylvania. STeelers won 35-24.  (Photo by Chris Graythen/Getty Images)
Chris Graythen/Getty Images

One of the San Diego Chargers' key receivers over the past year and a half has been released by the team the day after the team beat the Raiders 24-16.

Chris Chambers made a very important catch in that game that helped the team secure the victory.

However, after 31 games played with the Chargers, they let him go, oddly after the trade deadline had already passed.

Norv Turner suggested a few reasons for the release of one of their key receivers was primarily due to the emergence of Malcolm Floyd. Another reason stated was that the team needed to make roster room to sign another linebacker, stemming from an injury to Tim Dobbins in the Raiders' game.

It has also been rumored in the media that part of the reason for the release is due to ongoing personal problems that Chambers is dealing with. There have not been any specific personal problems identified to cause the rift with the team up to this point.

It should be noted that prior to Sunday's game Chambers was demoted in favor of Floyd.

The question remains: Should the Chiefs sign Chris Chambers?

The Chiefs have been playing musical chairs all season trying to find a reliable receiver to complement Dwayne Bowe. It seems that no matter who Todd Haley plugs into the slot, they never perform up to Haley's high standards.

Haley made a career out of his work with Anquan Boldin and Larry Fitzgerald—an offense in which he transformed two up-and-coming receivers into two elite receivers who carried Kurt Warner into last year's Super Bowl. 

Haley has no doubt been spoiled in the past with his receivers, but since joining the Chiefs he has been victim of downsizing. I think Haley looks at receivers much like how I do reality TV: I know it's going to be bad, but you just have to create different levels of "bad."

Obviously, blame for the Chiefs' slow start shouldn't end with the receivers. The blame for the Chiefs' 1-6 start should be spread evenly across the entire organization. From the coaching staff to the offensive and defensive line, from poor execution to lack of overall talent, everyone is to blame. 

As fans we all know the Chiefs are rebuilding and will continue to do so for at least another year. The goal over the next few seasons should be to bring in as much talent as humanly possible.

That brings us back to the original question: Should the Chiefs sign Chris Chambers?

Here are a handful of reasons why the Chiefs should consider signing him:

1. He is more talented than all of our receivers with the exception of Dwayne Bowe.

2. He can help spread the field with his speed.

3. He is a better option than Bobby Wade.

4. The revenge factor—he will have his chance twice a year (one more time this year) to get back at the team that released him.

5. Chiefs need someone to fill the "slot." He could be just the answer.

On the flip side of that coin, here a few reasons the Chiefs should avoid signing Chambers:

1. He is 31 years old. The Chiefs don't need to bring in any more "veteran" receivers. They need to rebuild with young talent.

2. Chambers has been in the league for nine-and-a-half seasons and has only one season over 1,000 yards. Underachiever.

3. Character issues. He has already been rumored to have been released somewhat due to "personal reasons." He was also arrested in 2007 for a DWI.

4. His best season was in 2005 with the Dolphins. Since then his production has dropped every season.

Possibly, the biggest concern for signing Chambers is that whatever team does pick him up on waivers will have to pro-rate his base salary of $4.5 million due to him this season. The Chiefs would have to pay him $2.4 million and then could risk losing him in the offseason as an unrestricted free agent.

Personally, I don't think the Chiefs should sign him off of waivers. However, that's just an opinion from a lowly Chiefs bloggers...what do you think?


Check out more of my work at , or if you already have a blog and want to earn additional ad revenue, check out . Thanks for reading!