Denny Medley-US PRESSWIRE

This coming football weekend the Chiefs will face the Steelers on Monday Night Football, and given the shape the Chiefs have been in, I expect it to be brutal. That being said, I don’t particularly care for the Pittsburgh Steelers.

But I do live in Pennsylvania and they are the “home” team, so I have to put up with their fans quite a bit. One of those (unfortunate) fans happens to be my wife. Not only is she a diehard Steelers fans, but every single one of my in-laws are: whoopee!!!

Normally when Kansas City goes head-to-head with Pittsburgh, my wife and I are glued to the TV, volleying taunts and insults back and forth, while I do the same with my brother-in-law through texts.

I am so gonna get slammed this year.

So much so that if the Chiefs are only able to win one more game for the rest of the season, I hope and pray that it’s this one. Of course, the Chiefs organization isn’t making an upset outcome look any likelier. It would’ve been nice to see Gibbs promoted earlier in the season. Would’ve been nicer, still, to see them keep their second-best CB on the team at least long enough to help hamper the pass-heavy Steelers offense.

History is a little bit on my side though. Since meeting my wife, the Chiefs and Steelers have only played twice before. One was last year where, though the Chiefs defense kept the score low enough, Palko* was just incompetent enough to allow the Steelers to win. This, obviously, isn’t in my favor. However, in 2009, a season in which the Chiefs wound up going 4-12, a season much the same as this one, one of the Chiefs’ four wins came against the Steelers in an OT victory so sweet that I can still taste it. As Succop lined up for the game-winning field goal, my wife attempted to flee the room. I say “attempted” because I was quick to bearhug her from behind and force her to watch her beloved (wretched) Steelers lose to a craptastic Kansas City team that was only 2-7 going into that game. It was, in a word, glorious.

*Or as my brother-in-law and I henceforth referred to him as: Brucie.

Palko knew he shouldn’t've eaten that popcorn

That was November 22^nd. We’re a little bit earlier this year. At this time in 2009 the Chiefs were 1-7 (sound familiar?). Hopefully the football gods will smile upon our Chiefs this coming Monday and give us (and especially me*) something to be happy about.

*Yes, I am being that self-centered.

To make things more interesting, my wife and I have the running bet that whenever our teams play one another the victor gets the bed all to themselves for that night, and the loser is relegated to the couch. Quite a suiting bet considering that by the end of the game we’ve spat so much crap at one another, and the victor is so heavily gloating and boastful, that we don’t want to be in the same room with another, let alone the same bed. The next day when the sore wounds have healed some, we determine the game’s MVP, also known as “Reason for Divorce” (what? I said when the wounds heal some).

What do you think, Addicts? Will a bad Chiefs team be able to beat the Steelers just as they did in 2009? Will my back be killing me on Tuesday? Do you have an odd/unique running bet you’d like to share in the comments? I’m all ears.

Until next time: (For the love of all that is holy) Go Chiefs!!!

The Kansas City Chiefs continued to break our hearts this past Sunday, getting trounced by the Tampa Bay Buccaneers. Rumors have surfaced about Pioli’s (and even Crennel’s) future with the team. Though this article was pre-planned by a couple weeks, it’s actually as good a time as any to look ahead to the 2013 offseason to see how the Chiefs’ cards fall as it concerns the roster and salary cap.

To kickoff, let’s start out by listing which players’ contracts are expiring at the end of this season.

A few names that I’m sure have popped out are Albert, Bowe & Dorsey, as they’ve been the most talked-about players whose contracts will be expiring (such talk dating back to at least April), with a lot of that talk being related to how high of a contract these players may demand. Two other names that pop out to me (though whose contracts should be exponentially cheaper) are Colquitt and Gafford. Not only should a punter’s and long-snapper’s value to a team not be underestimated, but they’re among the only players who have been consistently performing up to standard all season.

A lot of how we view what player personnel changes should be made relies on a general idea of how much a player would likely demand and how much money is likely available for the team to use on these players. It’s the latter portion of this speculation that I (and my Spotrac-obsessed hind parts) primarily hope to shed light on this week.

At last announcement, the Chiefs had approx. $14.5 million remaining in cap availability; though I’ve indicated in past that some of this money many be promised to players in the form of NLTBE incentives (and thereby wouldn’t show up until next season after the player has earned said incentive, we’ll assume for the sake of this exercise that either such NLTBEs were not set or, if they were set, weren’t met. So the Chiefs should have at least $14.5 million in cap space available next season by rollover alone, but how else is the team looking?

Running the numbers on next season’s non-FAs (read: guys that’ll still be on roster), I’ve discovered that the team currently is set to be allocating approximately $117 million towards cap hitting player expenses. It is likely that next year’s league defined cap will be in the same range as this year’s set cap which is $120.6 million. So, before factoring in rollover money, the Chiefs are only set to have about $3.6 million freed up to spend on FAs (regardless of whether they’re the Chiefs’ own or from other teams). That’s not counting the estimated $7 million dollars that will be required to spend on next season’s draft class. So, without the rollover, the Chiefs are in the hole $3.4 million.

Looks pretty bad at first glance, but let’s tack on the rollover money: that would put the Chiefs $11.1 million under cap after the rookie class is taken into consideration. Okay, now that doesn’t look as bad, but there are at least three big names up for FA and $11.1 million cap availability looks to be able to sign only one.

There appears to be a way around this, but it’s one that Pioli may not like as it involves two of “his” players:

1) Tyson Jackson, through “help” of a contract escalator, is set to be making $14.72 million in base salary next season and has also caused additional cap hits through bonuses amounting to $2.525 million. According to NFL.com’s Brian McIntyre (formerly of Mac’s Football Blog), Tyson Jackson’s 2013 base salary is only guaranteed for $3.22 million. So it looks like a certain someone should probably be cut. In doing so, the Chiefs would free up $11.5 million dollars in cap space (as indicated in a previous article, bonus money has a way of becoming dead money, so we’re looking at $14.72 million minus the guaranteed $3.22 million the Chiefs would be required to pay Jackson out of cap hitting funds). Now we’re up to $22.6 million in available cap space in 2013.

2) Matt Cassel. Though I’ve been unable to locate how much, if any, of Matt Cassel’s base salary for 2013 & 2014 is guaranteed, we’ll assume for this exercise that none of it is, and the only Chiefs obligation would come from bonuses. Cassel is currently set to cause a $9.825 million cap hit in 2013. Were he cut (and again assuming that none of the base salary is guaranteed), the Chiefs would be looking to spend $4.2 million in dead money, freeing up about $5.625 million in 2013. This would bring the available cap space to $28.225 million dollars (assuming a Jackson cut… and, at his ludicrous 2013 salary, why shouldn’t we want to see Jackson cut?).

Now, I realize I just threw out a bunch of numbers in sentence-form, which, if you’re anything like me, makes it a little harder to follow and reference. So to make the presentation of this information a little bit easier, I’ve devised the following table

“EOS” refers to the summation of the expected cap hit Entering the OffSeason (includes both players on roster, including Jackson and Cassel, and the rookie pool of approx. $7 mil). Current rollover is what it sounds like: money that may be expected to be rolled over and help alleviate the cap room. The $11.5 million in the “Jackson” column is what could be expected to be loosened up in cap space were TJax to be cut; same with the $5.625 million in the “Cassel” column.

So the question arises: how should this potential cap money be spent? To help facilitate this line of thinking I’ve developed the following hypothetical situations.

NOTE: One thing to remember in doing these hypotheticals is that, of the 18 positions open due to contracts expiring, seven will be filled through draft (at least as of now, and whose cap hit has already been accounted for in the figures) and two (the lowest priced ones) won’t count towards the cap (cap is determined by the highest 51 contracts of the 53-man roster come the regular season), so nine spots will need to be filled through re-signing the Chiefs FAs, or signing FAs from other teams, or signing UDFAs after the draft. These nine spots will cause a minimum cap hit of $3.51 million [determined as the minimum (rookie) contract of $390,000 X 9 spots].

Hypothetical Situation #1

For whatever reason (brain damage, maybe?), it’s decided to not cut Jackson or Cassel. After taking into account player cap and rookie cap there is approx. $124 million in cap obligations. The $14.5 million in rollover money brings this down to $109.5 million. Assuming a league set cap of $120.6 million, you have $11.1 million left to re-sign players. Who gets re-signed? What positions get targeted in the draft?

Hypothetical Situation #2

You’re slightly less brain-damaged and decide to cut Cassel and leave Jackson be. After taking into account player cap and rookie cap there is approx. $124 million in cap obligations. The $14.5 million in rollover money brings this down to $109.5 million. Cutting Cassel frees up an additional $5.625 million in cap space. Assuming a league set cap of $120.6 million, you have $16.725 million left to re-sign players. Who gets re-signed? What positions get targeted in the draft?

Hypothetical Situation #3

You’ve decided to cut Jackson, but leave Cassel on board for back-up purposes (he’s an expensive back-up, but provides a veteran presence/experience at the position, so you think the harm to the cap outweighs allowing a rookie squad plus Stanzi to run solo). After taking into account player cap and rookie cap there is approx. $124 million in cap obligations. The $14.5 million in rollover money brings this down to $109.5 million. Cutting Jackson frees up $11.5 million in cap space. Assuming a league set cap of $120.6 million, you have $22.6 million left to re-sign players. Who gets re-signed? What positions get targeted in the draft?

Hypothetical Situation #4

You’ve made the decision to cut both Jackson and Cassel. After taking into account player cap and rookie cap there is approx. $124 million in cap obligations. The $14.5 million in rollover money brings this down to $109.5 million. Cutting Jackson frees up $11.5 million in cap space. Cutting Cassel frees up an additional $5.625 million in cap space. Assuming a league set cap of $120.6 million, you have $28.225 million left to re-sign players. Who gets re-signed? What positions get targeted in the draft?

Bonus: Hindsight Hypothetical

Not knowing how this season would play out up to this point, you decide to sign all the players in FA that Pioli decided to sign, but you’ve decided to tweak the offseason slightly by also re-signing Carr. The terms of the agreement are the same terms the Cowboys offered him. For the sake of this hypothetical we’re assuming matching these terms would be enough for him to re-sign with the Chiefs, childhood dreams be damned. This season, Carr’s contract hits the cap by $3.2 million; in 2013, it hits the cap by $16.3 million. The rollover money is now $11.3 million (the current $14.5 million minus the $3.2 million cap hit). In adding Carr onto the 2013 roster, and taking rookie cap into account, the new 2013 cap obligations amount to $140.3 million. After deducting the new rollover amount ($11.3 mil), you’re down to $129 million in cap obligations. The league defined cap is still $120.6 mil; you have to come into compliance. Cutting Cassel wouldn’t be enough to come into compliance ($129 mil minus $5.625 mil is still greater than $120.6 mil), so your hand is forced in cutting Jackson to free up that $11.5 mil. Without additionally cutting Cassel (yet), the cap obligations decrease to $118.5 leaving only $2.1 million in available cap (not even enough to re-sign Colquitt). Now by cutting Cassel the available cap can be increased to $7.725. Who gets re-signed? What positions get targeted in the draft?

____________

Of the four, still possible, hypotheticals, I’d personally subscribe to Hypothetical Situation #4. Cutting Jackson seems to me to be a no-brainer (no way is he worth $17.245 million, and I’d rather tie up $5.745 mil in dead money in 2013 for the sake of having the remaining $11.5 million available to help with re-signing players or potentially dabbling in FA with other teams’ players). Though, with Quinn entering FA, cutting Cassel leaves the team without a QB on roster with regular season experience, I wouldn’t be opposed to seeing the Chiefs “double-tap” the QB position in the draft (ideally, Geno Smith in Round 1 and, if he or someone like him drops so far, someone like Collin Klein in Round 3 – keeping in mind that the loss of Carr will likely earn the Chiefs a compensatory Round 3 draft pick); it’d be a risk, what with both players having no NFL experience, but it’s a risk I’d like to see be taken. I know, it’s probably crazy to draft two QBs such as the ‘Skins did this past draft with RGIII and Kirk Cousins, and especially crazy given the team I’m suggesting do it (our beloved Chiefs) given the team’s history in this regard, but God help me, if Klein is available later, despite the Heisman hype, I’d love to see a QB with his fight and passion as the #2 keeping guys pumped on the sideline, and I’d trust someone like him to not do any worse than the Chiefs QBs this year were a situation to arise where he’d have to play. I’m sure it’s a pipe dream, but that’s part of what this exercise is about.

As for how I’d like to see the freed up $28.225 million spent: I’d prefer to see Bowe and Albert re-signed for certain. Given the average costs of WRs and LTs of similar quality, this could cost as little as $8 million in 2013 (akin to Carr’s deal with the ‘Boys where he accepted an incredibly low base salary in the 1^st year of the contract, given that he still received $10 million in signing bonus this season, and just allowed the team to prorate it over the course of five seasons at $2 million a season) or it could cost as high as $20 million (taking the average cap hits of comparable players’ contracts). I’ll assume the 2013 costs to be somewhere in between at $14.225 total for both players (2014’s projected cap hit based on active contracts is only $84.894378, so a deal structure closer to Carr’s wouldn’t be nearly as damaging that year).

So, in my scenario, I’m down to $14 million available. I’d definitely re-sign Colquitt and Gafford who, combined, would likely hit the cap by $3.5 million in 2013, leaving $10.5 million available.

Given that I’d be cutting one starting DE (Jackson) and letting the other walk in FA (Dorsey), I’d probably re-sign Pitoitua (whose re-signing I’m estimating to hit the 2013 cap by $1.5 million) and would gun for a DE in either Round 3 (compensatory Carr pick) or Round 4 in the draft.

Down to $9 million in cap space, I might also bring back Edgar Jones and Lilja (estimating a $2.7 million combined cap hit in 2013, $800,000 for Jones and $1.9 mil for Lilja). Jones has been a boost to ST this year and provides okay LB depth (and is one less position to be targeted in the draft) and Lilja would provide reliable back-up depth, if nothing more, and would help keep the OL more intact as they continue to gel together in this year’s new zone blocking system.

Two cap-hitting roster spots remain in this scenario and I’ll assume they’ll be filled by rookie UDFAs (for a cap hit of about $800,000) bringing the remaining money down to about $5.9 million, which I might let ride into 2014.

For the draft I’d target: QB, ILB (I’m letting both Belcher and Siler walk after all), DE & DB (in that order of importance).

As for my thoughts on the “Hindsight Hypothetical”: Carr really doesn’t look like he’d have been worth it. With only $7.725 mil remaining, which is really only about $4.225 mil after deducting the minimum $3.51 mil for nine open roster spots (which I mentioned in my “note” up there), a ton of useful players would need to be allowed to walk and maybe one of Bowe, Albert or Dorsey (at absolute best) could’ve been re-signed. At risk to be replaced through rookies (by drafting or signing as UDFA) would’ve been QB (Cassel would’ve had to been cut, which looks like an inevitability now, but had he returned to 2010 form would be deemed a problem, and Quinn probably couldn’t be re-signed even if you wanted to), both starting DEs and one of the back-up DEs, two out of three starting OL positions (Albert & Lilja), star WR (Bowe), starting ILB (Belcher) and his best back-up option (Siler), the punter, the long snapper, and two veteran S’s (Daniels and Elam; leaving only current rookie Tysyn Hartman and rookie IR player De’quan Menzie as backups). That would be cause for a massive rebuild (all those positions can’t be addressed in the draft, and not early enough in the draft to be hopeful about the players’ ability to replace the lost players with an equal or higher level) and would put the Chiefs in a much, much worse position than the team currently finds itself in. Not signing Winston, Boss or Routt would’ve cleared up about a maximum of $10 mil to be rolled over into next season, and cleared up active contract requirements in 2013 to the tune of about $18.2 mil for a total of $28.2 mil. These are much nicer figures for signing at least two of the big three in 2013, but doesn’t address the issue of what to do about RT this season (whichever choice being made decreasing the rollover amount), or the depth at TE this season (a “contingency plan” being a top concern considering Moeaki’s early injury in 2011), and the secondary depth would still be the same it is today (meaning it would still not be good enough). Maybe things could’ve worked out, but considering it would require leaving nearly $24.5 mil in available cap this year (for the intent purpose of rolling the money over to help during the 2013 season), the heat from fans and media for any underperformance while having greater cap space availability would be even hotter than it is now; not to mention the heat turning up if Moeaki fell to injury without preemptive back-up efforts being made, or BRich received an extension.

As for whether or not the Chiefs should make a play on Matt Flynn or another prospect to help turn around this season now: just keep in mind that the acquisition of such a player would decrease the available funds for rollover into 2013, and that if such player had a contract for more than just this 2012 season you’d have to increase the cap numbers for 2013, too . This would also affect the hypotheticals and how likely it’d be to re-sign who you deem to be key players next year*. Trading for a QB or picking up a QB from FA (McNabb?? Garrard??) might not be as harmful as re-signing Carr could’ve been. The re-signing of Carr would have not only decreased how much cap was left to rollover into 2013 by $3 mil, but also would have added the obligation of a $16.3 mil cap hit to next season which is what would’ve made it so potentially damaging. So, if you feel a QB now would be worth the cost, feel free to hypothesize in the Comments section, just be mindful that how money is spent in this season does have an effect on what personnel moves may be made next season.

*Assuming that all that changes hands are Flynn and draft picks. If someone like Bowe were traded for Flynn directly, or traded to MIA for picks, and picks traded to SEA for Flynn, then the loss of Bowe’s salary would make up for the addition of Flynn’s. In that case both Albert and Dorsey could be re-signed next year, if so chosen, what with Bowe out of the mix.

Let me hear your thoughts. Which hypothetical would you use? Who would you re-sign? What positions (and maybe even who, specifically) would you target in the draft? After seeing a more comprehensive look at the cap figures, do you think signing Carr would’ve been more trouble than it was worth? Are you still frustrated about this year’s available cap space, even after seeing situations in which it might be put to better use next year? Do you feel a different QB now would be worth the cost elsewhere?

Let me hear it all; I’m curious as to what options my fellow Addicts think would be possible in terms of player personnel moves intended to make the 2013 Chiefs a more competitive team. Despite being mostly realistic, I was admittedly a little pie-in-the-sky with my hopes of drafting both Geno and Klein; feel free to do similarly (but let’s try to not go too extreme into complete delusion, as euphoric as it might be, and keep it more in the realm of realism and where we think our Chiefs might be headed).

Sound off, Addicts!

It’s been a rough week for the Kansas City Chiefs and their fans. That is also probably the understatement of the week. Negative attitudes are at a high, and there are so many things at work that it’s difficult to sort things through and address things equally and/or fairly. But here’s my perspective on the varying issues, maybe you’ll agree, maybe you’ll disagree, but hopefully I can bring a few things to light which may have previously gone unconsidered. Some of what I say will be supported by facts, some by speculation in the absence of publicly available facts (such as Pioli’s “master plan”, assuming he has one), but the main intent is to present information or perspective that may not be currently represented (or is, at least, underrepresented). As some (if not most… if not all) of these views are likely to be unpopular or underrepresented, I’m prepared for a hailstorm of comments to the contrary. In the interests of perpetuating a well-reasoned, well-thought-out discourse, I kindly request such comments remain cordial.

Chiefs Ownership

Though owned by the Lamar Hunt family, through Hunt Sports Group, through Unity Hunt LLC, when one thinks of Kansas City Chiefs ownership, one thinks of the family-elected CEO and Chairman Clark Hunt. Simply saying the name “Clark Hunt” will send chills down a large number of Chiefs’ fans spines.

Clark Hunt has been associated with cheapness, caring more about the bottom dollar than team success/glory, and caring less about the Kansas City fanbase and community. That he lives in Dallas, TX is usually a shot taken by fans and media as indication of his lack of caring for the fanbase and community, and that cap availability numbers inaccurately represent how much a team is spending on its players have given him the label of being cheap.

I do not agree with a lot of the negativity surrounding Clark Hunt. For those of you who read my  article two weeks ago, you should know by now that the Kansas City Chiefs have not been cheap in their player spending, having amassed the highest paid team in the NFL this season according to salary cap figures. If you did not read that article, it may be more conducive to your fair assessment of Clark Hunt to do so now. The article provides insight into team spending for all NFL teams and how certain aspects of salary cap management function. To summarize the article for the sake of expedience, Clark Hunt isn’t being cheap on the player spending. This also feeds into how much Clark Hunt cares about the bottom dollar. Though I’m sure the Hunt family’s business interests in the Chiefs would keep them from wanting the organization to start functioning in the red, the same could be said of any business’s or organization’s owner(s) ever. Something can only be supported for so long when it’s not earning revenues equal to or greater than its expenses. That’s just basic economics.

In regards to his consideration for the fanbase and for the Kansas City community, more consideration is being given than the Hunt family has been commonly assessed. One of the chief complaints is that the on-the-field product is not equating to what a lot of Chiefs fans consider to be fair prices for stadium attendance. They don’t feel they’re getting the bang for their buck; a sentiment that is amplified in rough economic times where how one spends what money one has is greatly scrutinized by the spender. So, how does the Chiefs’ gameday experience stack up against the 31 NFL teams? Every year Team Marketing Report in Chicago, IL researches this very question. Here is a chart of the average ticket prices for a fan to attend a game at each of the NFL stadiums; it should be noted the cost and quantity of premium seating is not included in these averages:

The average NFL ticket price is reported as $78.38, well above what the average ticket price to Arrowhead costs. Even factoring out the five highest ticket prices (all above $100) the average ticket price for the 27 lowest price teams is $71.84, still firmly above the Arrowhead average. What may be of additional interest is that Team Marketing Report also tracks the percentage changes in ticket prices for each NFL team. TMR determined that the average NFL ticket price has increased by 2.5% compared to last season. Fifteen NFL teams saw no change in their ticket prices. Of the remaining seventeen teams nine increased ticket prices [the lowest being the Seahawks by 1%, the highest being the Bears by 9.2%], and six lowered ticket prices. The Kansas City Chiefs are not only counted among the six NFL teams that lowered ticket prices, but KC decided to decrease their prices by the second-most percentage* [2.6%]. As part of their report, TMR provided the NFL average cost dating back to the 2007 season; even going back that far, the current Chiefs’ pricing does not meet or exceed the league average.

*Only the Bengals decreased their ticket prices by a greater percentage[4.2%]; however TMR’s research showed that, of the six clubs that decided to decrease ticket prices, the Bengals were one of two clubs that decided to lower ticket prices following lower fan attendance during the 2011 season; the second team being the Bills.

TMR also researched the average premium ticket costs and the cost of beer, soft drinks, hot dogs, parking, programs and caps as part of their study. Their figures on beer and soft drinks are based on the smallest sizes available at each stadium, and their figures on caps are based on the least expensive, adult-size adjustable caps at each stadium. In these categories, the Kansas City Chiefs exceed the league average in only two of them: 1) Hot Dogs – in excess of 66 cents, and 2) Average Premium Ticket costs in excess of $26.30.

As part of their report TMR created a cost index comprised of the costs of four average-price tickets, two small beers, four small soft drinks, four regular-size hot dogs, parking for one car, two game programs and two of the least expensive, adult-size adjustable caps. The reported cost index for such a gameday experience for each team is as follows:

As can be seen, the Chiefs rank as the fourth cheapest team in terms of the cost index. TMR determined that the average NFL cost index has increased by 3.9% compared to last season. Only two NFL teams saw no change in their cost index. Of the remaining thirty teams twenty-six saw an increase in cost index [the lowest increase being the Cardinals by 0.3%, the highest being the Bears by 16.3%], and four saw decreases in their cost index. The Kansas City Chiefs are not only counted among the four NFL teams that lowered the overall cost of an average gameday experience, but KC decreased their prices by the second-most percentage [1.6%] with only the Jets showing a greater decrease [1.9%].

So though some, including The Arrowhead Adventurer, may not care for certain organization initiatives, such as the switch to paperless tickets (thereby depriving fans of the memento of ticket stubs), savings are being passed onto the fans by making such changes (I, for one, always tended to rip/disfigure ticket stubs from any events I’ve attended and, as a result, do not partake in that particular keepsake practice… as such, I’d personally prefer more efficient line movement).

Does this forgive the disparity between on-the-field product and the associated costs? Not incredibly. We’d still all like to see the Chiefs be more competitive and in championship contention; an increase in quality without an increase in cost. But at least you’ve been afforded the opportunity to see what other teams’ fans are paying out on gameday, and I think we can all agree that being a Jets fan has to suck considerably more by a quality to cost comparison.

As for the Hunt family living in Dallas, this is the way it’s always been. Lamar Hunt’s ability to finance a football team came from the wealth earned by his father, H.L. Hunt, in conjunction with Hunt Oil. Though Lamar Hunt’s branch of the Hunt family tree no longer holds a stake in Hunt Oil, there are many other business ventures they do own a stake in which are, for the most part, based in Dallas. In the early days, when the Dallas Cowboys (who at the time were much less successful than the Dallas Texans) started taking attention away from Lamar Hunt’s beloved football team, and he resigned to the fact that sentiment was not enough to continue functioning in Dallas when the previous three seasons found the organization in the red, he sought to move that team to a city that would give a damn. The speculated options at the time were for a move to be made to either Oakland or Kansas City. After what was described as a “cloak-and-dagger” affair,  Kansas City’s mayor and Hunt agreed to stage a season ticket run to determine if the new city would be devoted enough to the sport to garner the team with the attention Lamar felt it deserved. Obviously Kansas City met Lamar Hunt’s expectations as we know that he moved the team there; however, what may not be known is that Kansas City fell far short of the set season ticket goal (25,000 tickets) in that they only sold tickets in the 13,000-14,000 tickets by the given deadline. Lamar still felt that the city showed enough devotion and passion (despite not meeting the ticket sales threshold) that he decided to move the Texans to Kansas City.

Nowhere is it mentioned or even suggested that Lamar Hunt agreed to pull up his family’s stakes to move to Kansas City. A lot of tradition and business interests already existed in Dallas for that to have been part of the deal. That same family tradition continues to this day. The Chiefs are but a part of Hunt Sports Inc., and Hunt Sports Inc. is but a part of Unity Hunt LLC. To expect numerous businesses, and a family’s tradition, to be uprooted for the sake of one of those business ventures (though the Kansas City Chiefs are the most recognizable) is asking a lot, and probably too much

Does this mean that the Hunts and the Chiefs don’t care about Kansas City? Not in the least. By my count the Hunts through the Kansas City Chiefs have 15 steady community service programs devoted to helping various aspects of the Greater Kansas City Community. Players are encouraged to actively participate in giving back to the community. And new initiatives such as the Chiefs partnership with the University of Kansas Medical School are geared towards ultimately helping the Kansas City community as a whole. These are not the actions of an ownership that doesn’t care about its fans or its team’s city’s citizens. In fact, their devotion to the community is a large part of why I am of a fan of the organization and have remained a fan through the tougher years; they may not always win (or even be competitive) but the organization’s devotion to contribute beyond what the game dictates is, by my estimation, admirable and should not be diminished by how they play 16 days a year.

Also, when it was obvious things were not progressing under Carl Peterson and Herm Edwards, Clark Hunt made a move to obtain one of the most decorated executives in the football industry, and spared no expense to bring him in to help the franchise (something an owner that doesn’t care wouldn’t do), which brings us to:

Chiefs Management

I don’t know what to think about Pioli. On the one hand Kent Babb has painted a pretty bad picture of Pioli. On the other hand, Babb also neglected to look into team finances and painted the Hunts as cheap on players though they appear to be anything but*, and generated negativity on that front where negativity wasn’t due.

Aside: I’m still astounded by that one. I’m a legal assistant in Pennsylvania, devoting nearly 60 hours a week towards my day job with a wife and 2-year-old daughter also garnering my attention, and I was still able to do more thorough research on that front (cross-checking my findings across many independent sources with no team affiliation for slant) and reported this as part of my contribution to this website. It was Kent Babb’s day job to do such things for which I’m sure he got amply paid, and he couldn’t do that much??? I guess I’m saying I’ve re-read Babb’s articles with a grain of salt as I am not satisfied with his research abilities (or lack thereof).

In Michael Holley’s book “War Room”, it is indicated (and I’m paraphrasing here) that when Pioli arrived in Kansas City, the Chiefs staff and scouts were complacent and unmotivated, which (by that point in the book) were distinguished as work habits in conflict with Pioli’s own work ethic. Holley (in juxtaposition to Babb) painted Pioli as a hard worker who would sooner have his work product exceed his paycheck than his paycheck exceed his work product.

If that is his work ethic, and the incumbent staff did not put their hearts into their jobs and strive towards the goal of making the Chiefs organization a championship product, I can understand the turnover ratio. There are no salary cap concerns in the front office; severance packages maybe (and they could be pillaging Hunt’s pockets for all we know), but not a set number that the organization may not exceed in accounting terms. If these people were not earning their paychecks (admittedly by Pioli’s standards), then I can understand Pioli taking swift action in terminating them and bringing in new people. I can even understand him bringing in people he knew from his time with the Patriots (as he likely had previous knowledge of these individuals’ work ethics, knowledge and talents).

The desire to have people who work for you do their damnedest and take more pride in doing their work in excess of expectations rather than taking the mentality of “I’m doing just as much as I think my pay warrants” (such people usually overestimating how much pay they’ve ‘earned’ through the work they’ve actually done) is also something I can understand, and would explain the so-called “wire-tapping”. I work for government, we have the same systems in check. E-mail, phone logs, etc. are monitored to determine how much company time the worker is spending on personal business (i.e. how much non-work they’re performing during hours they’re getting paid for). It isn’t incredibly shocking that a multi-million dollar business would partake in such monitoring. Again, if the workers were as complacent as Michael Holley indicated, it may be of utmost importance to changing the culture of football operations from people who care more for how much they could soak the organization for than how much they could contribute to the organization’s success.

If Pioli (or any other GM that could’ve been, or could still be, brought in) wanted to change a complacent culture satisfied with doing the bare minimum and having little interest in a championship that was gained by more than luck (if hard work was the alternative), I think we’d all be supportive of that change.

That being said, I doubt the candy wrapper story was made up, to which I can only say this: I can understand wondering why the hell you’re paying maintenance to do a job they’re obviously not doing (the wrapper was sitting for about a week after all… which by my count is at least 4 days too long, even if they were understaffed or only cleaned two to three days a week), but the taking of the wrapper as evidence makes the whole incident automatically extreme (and sounds on par with Mitch Hedberg’s “donut receipt” joke). That definitely could’ve been handled a lot better.

As far as his plans for rebuilding and his apparent secrecy of these plans are concerned, it’s frustrating as hell only being able to speculate what his intentions are/were. I, for one, believe (or maybe just really hope) that the plan was/is to build up the supporting cast first and drop in the intended franchise QB last. This would help prevent “David Carr Syndrome” or other 1^st round busts such as Brady Quinn was in Cleveland. Instead of custom building an entire team to one guy’s talents (thereby making it more difficult should that one guy go down), it would entail building a talented team and allowing the last guy (QB) to adjust to the talents around him (thereby making it less disastrous should that one guy go down temporarily). To get the QB first and build the team around him is akin to making the QB the entire foundation’s cornerstone. If it’s later learned that that cornerstone is not of the quality it was believed to be, the building stands to get irreparably damaged. To get the QB last is akin to building a quality structure first and using the QB as the capstone. If the capstone is of lesser quality than was expected, so what? It’s less damaging to the structure to replace a damaged capstone than to replace a damaged cornerstone. The downside is that, as fans, we don’t know if this is the plan until it happens. It could very well be. It could very well be that Cassel was perceived to be the guy for real (rather than a QB deemed adequate to man the helm while the rebuilding took place… I guess in my metaphor “the scaffolding”). Will Pioli say? No.

Which brings us to the secrecy. I can understand this to an extent. Part of the existence of a salary cap in the NFL is to promote competition and to provide no team with an unfair competitive advantage due to finances. But each team wants a competitive edge to build the strongest team possible within the restrictions of these limited resources. Kansas City is not a large market, so the competitive edge of “come here, we’ll make you famous” isn’t much of one for Chiefs execs (past, current or foreseeable future). Fan loyalty can help lure talent, but that’s more our thing than a FO thing. The Chiefs don’t have overwhelming, modern day championship prestige (yet). So what competitive edges can there be? I would reason that not letting your competition know your goals heading into deals would prove to be a great advantage. If everyone expected KC to draft a QB in the first round of next year’s draft (let’s say they finished with a pick lower than No. 1 Overall), and a move was made to jockey the team in the position to draft the QB of their choice, how much greater would the trade cost be knowing that the team’s intent is to draft a team’s most valuable asset (QB)? If, however, you lowered your trade partner’s expectations to believe that your intent is in the interest of drafting a lesser position player, that deal will likely become less costly (meaning that your own team can hold onto more assets, be it player, asset, or money to re-invest in another portion of the team). It’s a competitive edge built on manipulating others’ speculation of your intents, and there may be considerable success in doing so; unfortunately, the decision to put your competitor’s speculation in doubt also casts doubt within your fanbase’s speculation.

As for owning up to his mistakes, I’ll go back to Babb and the salary cap situation: Babb (local media) fabricated a negative misconception of something the Chiefs were actually doing well and it spread like a fire causing a wave of damage in its wake. That was with bad knowledge of a situation the team was actually doing pretty well. What could be expected of this same local media if Pioli admitted to an actual error? Holy bejeezus, that would not end well.

Overall, I can appreciate wanting personnel dedicated to making the franchise a perennial contender, and I can understand building the supportive components of a team up first before dropping in the franchise QB. It’s not the broad goals behind (what I think is) Pioli’s rebuilding plan I question, so much as Pioli’s execution of this plan. Keep the ideology, but do better at enacting the plan (or, Clark, find someone else who can).

Eric Winston

Spoke in a moment of passion. While morally justified in sentiment, he lacked the censorship to scope his claims down to only indicate the fans that partook in the behavior. CBA dictates that players are open to media. He spoke to media in conjunction with this clause. So, I really can’t begrudge him the action of speaking with the media.

I’ve been saying for weeks that negativity from fans affects the players more than fans might think. After weeks of negativity, and the greetings of a negative banner on Sunday, he construed some cheers as being in the morally negative bent. Looking through comments on various sites pertaining to this issue, it’s easy to find people admittedly partaking in this deplorable behavior (cheering a player getting injured), so Winston’s perception of the intent behind some of these cheers does hold some merit.

There is some understandable and justifiable betrayal felt on behalf of the fans (at least the portions whom, in a moment of passion, Winston lumped in with the bad ones), but attempting to look at thing empathetically from Winston’s point of view, the portion of fans that cheered Cassel’s injury are a part of the same fanbase whose overwhelming response to his FA visit convinced him to stop seeking potentially greater fortune, and a greater media market, elsewhere and to settle for less money if it meant great fans. He made a major life choice based on how great the fanbase presented itself to him, and in short time saw just how negative the fanbase/local media could get [the local media is crawling with negativity, fans (though not all) have been acting out in negative fashions for weeks (even if just verbally), and it culminated with a portion of those fans doing something so deplorable and anti-supportive of the players]. Given that consideration, I wouldn’t be surprised if Winston felt a little bit of betrayal, too.

Ultimately my point on this is that fan attitude does affect player attitude, and this whole fiasco is a case in point.

Fans who cheered Cassel’s injury

Winston was correct in stating that this is not the Roman Coliseum and the players are not gladiators.

For those that use the flawed logic that NFL stadiums are constructed in the image of the Roman Coliseum so football is like the modern equivalent, you should probably know that the architectural design of NFL stadiums is not intended as an allegory to ancient Rome. The Romans designed the Coliseum as they did because it architecturally allowed for greater seating capacity. The properties of such design haven’t changed, and this is why stadiums are made in such a fashion. Incidentally, uncomfortable-as-all-get-out bleacher seating may also be used to accommodate more people. It’s an attendance maximization thing, not a throwback to days of yore.

For those that use the logic that “it’s okay to cheer MMA and boxing, so why not a football player’s injury?”, you should probably know that the rules are different going into each contest. Beating the crap out of each other is an integral part of MMA and boxing matches, and the participants willingly submit themselves to such punishment. Incidentally, it’s not unheard of for professionals in these sports to schedule matches several months apart to accommodate for the fact that they’re going to get brutalized and need copious amounts of time to recover in between bouts. Injuries in football, on the other hand, are incidental to the sport (not integral) and any action done by a player to intentionally injure another (or even that increase the odds of injury, such as helmet-to-helmet shots) are generally frowned upon. Remember that whole Bounty scandal thing? Yeah, the main part of that was the targeting of players for the purpose of injury (that money may or may not have been put towards these goals is secondary). Remember all those fines players accrue for helmet-to-helmet hits? Yeah, that’s what those are about, too.

There’s no denying that big hits or hard hits get a viewer’s adrenaline going, or that it is pants-crappingly awesome to see a player pop back up from such hits like they’re no big deal. But sometimes those players don’t bounce back up, and that’s when it’s time for humanity to kick back in. Maybe if the injury is a more minor one (ankle sprain, broken finger, etc.) to an opponent’s superstar, you can thank your lucky stars that your team got a reprieve from his awesomeness for the rest of the game, but when you get into potentially life-altering injuries such as concussions, ACL tears and the ilk, it’s time to dial it down.

To those of you convinced that Cassel’s injury is the only thing that would take him out of the line-up and that your voice isn’t being heard, you may be right, you may not be right. Maybe Cassel really was the best QB on the squad (I just vomited in my mouth a little). That being said, I personally didn’t care for the public display of discord by use of a banner flying over Arrowhead; such displays have the potential to place the fanbase as a whole in a bad light. That being said, I respect that you care so much about your team to spend extra money for such a display,

I would suggest and alternative: it may go against younger generations’ grain to not make public statements (ala Facebook or Twitter), but there’s a thing called letter writing that involves a pen and paper which would be more low key (as in less inflammatory to the fanbase) and cheaper, too. I’m in no way condoning sending threatening letters to One Arrowhead Drive (that’s kind of illegal), but sending letters highlighting your devotion to the team and expressing your disapproval of certain things that are being done which you don’t agree with (preferably with well-reasoned arguments, as you’d be taken more seriously) might be much more effective. As I write this, it occurs to me that Lamar Hunt was fond of conducting business via letter writing (even as technology advanced into allowing more instant communications), so to do so as a fanbase may very well strike a personal chord within the Hunt family as it pertains to fan concerns. The least that could be expected? Solid evidence of fans’ concerns that can’t be as easily discarded and ignored as pressing a “Trash” button in e-mail. Pioli flipped over a candy wrapper, how much attention do you think will be paid to stacks of letters filling up the joint?

Hopefully some of what I said has shed new light on certain things. Again, some of it is speculation, so my guess is as good as yours, but hopefully you have gotten to considering alternative intents. Tune in next week when I’ll be looking forward to 2013’s expected cap hits/player personnel moves. As always, Go Chiefs!!!

Following a disappointing loss at home to the San Diego Chargers, the Chiefs will stay inKansas City again this Sunday, this time to square off against the Baltimore Ravens. Needless to say, with the way the Chiefs have been playing thus far, this game is likely an easy write-off for most Kansas City fans, but despite this (and after a two week hiatus), I’ve decided to soldier on in the Know Your Enemy series.

Offense

The Baltimore Ravens are currently ranked 5^th in the NFL for scoring on the season, and are performing so well that some analysts and pundits have opined that the Ravens’ offensive performances have actually been exceeding its defensive performances (compared to the previous decade or so of being an indisputably defensive juggernaut).

The Ravens’ offense is steered by QB Joe Flacco. Flacco made some noise over the offseason, proclaiming himself as an “elite quarterback.” Most people chuckled to themselves upon hearing this, but he has put in a commendable season thus far. While I am not willing to label him as elite quite yet, Flacco has played with poise and engineered one fourth-quarter comeback on the year thus far (Week 3’s controversial win over the New England Patriots). In four games, Flacco has completed 63.5% of his passes for 1,269 YDs and 7 TDs, good for a passer rating of 95.8.

But what is a QB without a few good targets to throw to? Though I would not put the Ravens receivers on par with the Falcons receivers (Roddy, Julio, and Gonzo) they may well have the same amount of talent (or slightly more) spread across five players in WRs Torrey Smith, Anquan Boldin, and Jacoby Jones, and TEs Dennis Pitta and Ed Dickson. The most notable of these five are Torrey Smith and Dennis Pitta.

Though largely ineffective in last week’s game, Pitta has 18 catches for 188 YDs and 2 TDs on the season and appears to be a valuable target for Flacco in the red zone. Though not receiving quite the targets that Pitta is receiving, Ed Dickson also can contribute quite a bit at TE when called upon and should be perceived as something of a threat.

Meanwhile, Torrey Smith is looking to have a breakout year, having already registered 16 catches for 332 YDs and 3 TDs on the season. Some in-game commentators have sounded shocked by Torrey Smith’s on field production; however, I personally don’t find this too shocking considering that he put up pretty decent stats last season (50 catches for 841 YDs and 7 TDs) despite both having his rookie preseason shortened by the lockout and playing a significant chunk of the season with a hamstring injury.

Between Anquan Boldin and Jacoby Jones, you might think that Boldin is the bigger threat, which he may well be becoming, but up until last week Boldin has been relatively disappointing this season, not getting much separation (and, consequently, targets) during the first three games. No, after Torrey Smith and Dennis Pitta, Jacoby Jones looks to be the next biggest receiving threat on this Ravens offense. Having watched all of the Ravens’ games this season, I swear Jacoby Jones seems to be good for two to three HUGE catches per game thus far. Even if Jones doesn’t appear to be much of a factor during the first three quarters of the game, the Chiefs defense should not sleep on him because he has been showing week in and week out that he can be relied upon to make crucial, fourth quarter catches even if they’re among his only targets of the game.

As for the Ravens backfield, Ray Rice continues to impress both on ground and through the air. If Flacco and the passing offense didn’t step up their game this year, you might hear a lot more chatter about Rice. Instead, it seems like Rice’s consistently great play is so expected that the passing game is the new hot thing to talk about. Rice also factors into the passing game receiving and is currently topping the Ravens charts with the most receptions (though with, understandably, less yardage given where his routes take him).

As for their offensive line, the Ravens could be doing a little better. C Matt Birk is 36 years old, and while he’s still an excellent center, a lot of his excellence comes from his knowledge of the game as his physical abilities are in decline, and LT Michael Oher of “The Blind Side” fame is not quite as good on the blind side as you’d expect him to be. I know several Ravens fans griping about wanting the team to move him back to RT where he fares better and trying again on the drafting a LT front. RT Kelechi Osemele is a rookie, LG Ramon Harewood is in his second year (though it is his first year playing in games), and RG Marshall Yanda is in his fifth.season. Yanda has been elected to the Pro Bowl once and may be Baltimore’s best OL at the moment in terms of age, position and ability.

Defense

As previously stated, the Ravens defense is starting to get overshadowed by their offense; however, this does not mean their defense is bad or even average. As much as the Ravens defense has been underperforming compared to last year (when they were No. 2 Defense overall), they are still a top ten defense (coming in at No. 10 right now).

In case you’ve been living under a rock and haven’t heard, the Ravens defense is anchored by timeless players MLB Ray Lewis and S Ed Reed. Though the good news is that these guys are a year older and a bit more of their age is showing, the bad news is (that like Tony Gonzalez) even a slightly less physically capable Lewis and Reed can still be counted among the elite at their positions. Also showing age is NT Ma’ake Kemoeatu who is actually starting to show greater signs of wear.

Besides Reed and Lewis,Baltimore’s next two greatest defenders are DE Haloti Ngata and S Bernard Pollard. You probably know Pollard from such KC snafus as “letting go of Bernard Pollard.” And if you don’t know who Ngata is or what he is capable of, you really should consider just getting rid of that aforementioned rock you’ve been living under.

One positive about facing the Ravens current defense is that they are fronting some lesser experienced players right now. The DE opposite Haloti Ngata is Pernell McPhee, a fifth round draft choice by the Ravens taken in last year’s draft. Due to the loss of LB Terrell Suggs to injury and the loss of LB Jarret Johnson to free agency, the Ravens have been forced to play with rookie Courtney Upshaw and 3^rd year player Paul Kruger at OLB and second year player Albert McClellan at MLB..

CBs Lardarius Webb and Cary Williams flesh out the starting defense, and though capable backs, are overshadowed by the stellar safety play.

Special Teams

Baltimore’s kick returner duties are handled by rookie WR Deonte Thompson and the Punt Returner duties are handled by Jacoby Jones. The Ravens’ kick return game is currently slightly better than the Chiefs’, and their punt return game is slightly worse.

Both teams’ kickers and punters look to be about a wash thus far this season, with Ravens P Sam Koch posting similar stats to Colquitt, and rookie K Justin Tucker posting comparable stats to Succop. Justin Tucker replaces Billy Cundiff at kicker after Cundiff messed up what should have been an easy kick last season in the AFC championship which kept the Ravens from the Super Bowl. It is yet to be seen if Tucker can make such clutch kicks himself, with his only real opportunity to do so this season being during the Ravens win against the Patriots in Week 3. In the last seconds of the game, Tucker shanked a FG far right of center, but luckily it was high enough to go over the top of the goalpost rather than banking off the goal post and according to the NFL Rule Book over the post counts as between the posts and such a play is non-reviewable as only the official directly underneath the post was in any position to make the call. Whether this kick was Tucker experiencing very good luck masking non-clutch play, or whether he experienced bad (but not quite bad enough) luck to turn what would normally be a clutch kick into a near miss is anyone’s guess at this point. If the game’s on the line and the ball isn’t within the 25 yard line, I’d probably be holding my breath were I a Ravens fan until enough time and opportunity passes to determine whether or not my kicker could hit a clutch kick.

_______

As a Chiefs fan, it is admittedly hard to go into this game with a positive outlook. If the Chiefs offense (and particularly Cassel) can play turnover-free football, there might be a fighting chance. And I don’t mean a zeroed out turnover differential where a Cassel INT is canceled out by the defense forcing a turnover. This offense, under Cassel, is likely to not be mentally tough enough to put up with one more turnover, even if it’s made up for by the defense later in the game.

But I will remain positive going into this game for one major reason: negativity is not helping this franchise succeed, and may very well be helping to make it worse.

A scientific study performed at California State University back in 2009 looked into what causes “choke” and “clutch” performances. In a nutshell, the study determined that when an individual first learns a skill, they learn it explicitly; the thought process is methodical, and the motion mechanical (slower and more awkward). After time and practice, these skills develop into becoming implicitly performed, quickly and smoothly. In the realm of pro sports, quick and smooth action tends to be paramount to success (if you telegraph a decision by going about it slower in thought and execution, bad stuff tends to happen). In studying what causes some people to choke and some to be clutch, it was determined that, as pressure to succeed gets higher, how the individual copes with the pressure has a lot to do with how they fare overall. The “chokers” allow the pressure of the situation to seep into their consciousness, they get so concerned with the implications of how they’ll perform their task that they’ll revert back to thinking of the task explicitly; their actions get slow and choppy and they tend to fail (which makes sense since they’ve basically reverted back to how they performed the task when they first learned, a/k/a when they sucked most at the task). Those capable of putting the gravity of the situation out of mind are more likely to be able to perform the task implicitly and, having refined thought and movement, are much more likely to succeed (“be clutch”).

Assuming the findings of this study are true (and I’m apt to believe them as they make perfect sense to me), being demonstratively loud and negative towards people you want to succeed appears to be counteractive to the results you want. Pressure to perform is increased, and the more pressure that mounts, the more likely the individual(s) will perform even poorer. If negativity is only going to exacerbate the problems, I’m not gonna be a part of that.

All this being said, do what you like in showing either your support or dissent, but if you do approach the situation negatively, don’t be the least bit surprised if your actions garner negative results; and not just negative results in the form of current players’ performances, but negative results in the form of luring talented people to the team to perpetuate an upgrade. If Pioli does get fired, Double D may be right in predicting Marty to be his successor; no good person without pre-existing ties to this franchise will likely want to step into such a volatile and hostile environment.

Here’s hoping for a win on Sunday. Go Chiefs.

Denny Medley-US PRESSWIRE

Well, Chiefs fans, for those of you who read my article last week, you should’ve walked away knowing a little bit more about salary cap management. You may or may not have jumped to my rallying cry to show the player and team some love, and let the NFL world know that when they go up against the Chiefs they’re not just going up against the players and coaches, they’re going up against every Chiefs fan that bleeds red and gold.

Whether you did or not certainly depends on the individual. Some of you may be too disgusted by Clark Hunt and Scott Pioli’s management of your beloved Chiefs to look past your perception of them and root for the players. After all, Hunt and Pioli are cheapskates (to use the nicer term), right?

Well, according to Spotrac.com, it appears that, of the 32 NFL teams, the Kansas City Chiefs are spending the most cap dollars of any team on active player contracts in 2012.

I’ll wait for you to seek medical attention for your broken jaw; mine slammed pretty hard off of my desk, too…

That was not a misprint: the Kansas City Chiefs, owned by Clark Hunt and family, managed by Scott Pioli, appear to be paying the most of any team on active player contracts this season. Take a look for yourself:

Now, I want to be clear. Spending “the most cap dollars… on active player contracts” does not necessarily mean that the Kansas City Chiefs are using/accounting-for the most cap dollars overall, it means that they’re paying the most cap money towards players currently on the team.

What does that mean?

Though most news outlets will report cap space availability for teams, this is a new day and age, and comes with it a new CBA, wherein available cap space money can be rolled into the next year without the need for teams to exploit loopholes*. This will affect how much cap dollars a team can spend on its players in a given season. This can really alter each team’s cap room which, in turn, will make cap space availability numbers a little less useful without context.

*It used to be that NLTBEs were accounted into the cap during the season they were set, and were the only cap dollars that could be rolled over, provided the player the NLTBE was assigned to didn’t earn it. So to rollover remaining cap monies, teams could make a ridiculous NLTBE late in the season that had no way of happening, say setting an NLTBE in Week 15 that would have your 3^rd string QB receiving all remaining cap dollars if he could throw 10 TDs by the end of the season. He, of course, wouldn’t, but since the NLTBE was accounted for, but not met, the money could be rolled over into the next season. The new CBA made adjustments to this by just letting teams rollover cap dollars without the need for trickery, and having NLTBEs count against the next season’s cap should they be met.

Ex: Let’s say Team A rolls over $1 million from last year’s season into this year’s season, and Team B rolls over $20 million. If after spending, both teams find themselves with a cap availability of $1 million, it won’t be because both teams spent the same amount of money. Rather, Team B would’ve spent more money as it spent both the league defined cap, plus $19 million of the $20 million it rolled over; whereas Team A would’ve only spent the league defined cap, and just didn’t touch its rollover.

But even that is only a portion of how people can confuse salary cap availability with money spent by the club on its active players’ contracts. In the NFL’s salary accounting policies and procedures, there is a certain thing that negatively impacts a team’s salary cap, that doesn’t seem to get a lot of media attention: dead money.

What is dead money? (you ask because you don’t use contractions)

Dead money is generated when a player leaves a team (usually by being cut, but sometimes through retirement or a trade*) and certain parts of their contracts were either guaranteed or solely within the club’s responsibility to pay (e.g. signing bonus). It gets its name because, even though the player is no longer with the team, and therefore doing the team no good, the money must be absorbed and paid for by the club, and it does cause a cap hit. So any dead money that exists keeps a club from spending that much more money on players who are (or can be) signed to the 53-man roster.

*For those left wondering, whether you thought to ask yourself or not, players willfully leaving, or willfully being allowed to leave,  via FA don’t generate dead money, as their contract would’ve been fully satisfied, and there’d be no money left unpaid for a team to absorb.

Ex: Team A and Team B each have a salary cap of $100 million (for the purposes of this example there were no rollovers). Team A has dead money to the tune of $10 million. Team B has dead money to the tune of $2 million. After spending the money on this year’s team, it’s reported that Team A has $1 million in cap availability and Team B has $5 million in camp availability. At face value, and since availability gets reported much more heavily than dead money figures, it appears that Team A is spending more money on their current team than Team B. This is an incorrect assumption. After deducting each team’s dead money from their initial cap, Team A had $90 million to spend for the year, and Team B had $98 million. So though Team A appears on the surface to have spent more money on current player contracts (what with $1 million left compared to Team B’s $5 million left) doing the math shows that Team A has actually only spent $89 million on this year’s roster [$100 million (cap) - $10 million (dead money) - $1 million (available money)]; whereas Team B has actually spent the greater sum having devoted $93 million cap dollars on this year’s roster [$100 million - $2 million - $5 million].

Let’s take a look at each team’s dead money figures:

It should be noted that $460,000-520,000 in dead money is pretty well par for the course for any team in a given year, just due to cuts to fringe players. Here you’ll see the Chiefs have the 7^th least amount of dead money affecting this season’s cap with $2,117,187. Interestingly enough, Demorrio Williams accounts for $1.6 million of this figure, with the remaining $517,187 being spread between 7 different (former) players with Gabe Miller accounting for the second highest figure ($148,875) and Brandon Bair, the least ($4,666).

Another pitfall in using cap availability in judging how much a team is spending on its players’ contracts is, as I touched on last week, that LTBE goals will, for accounting purposes, appear as cap hits on the current season’s salary cap, but whether or not players will earn this/these goal(s) is, of course, not a guarantee until it happens.

So to a common observer who a) doesn’t consider how rollovers affect the cap, b) doesn’t consider dead money and c) doesn’t consider how things such as LTBEs must be taken into account, it’s a quick and easy jump to assume that the more cap space a team has available, the less money that team is spending on its current team. This is the Kansas City Chiefs’ current plight. Fans see that $14.5 million in cap space is remaining, the third most in the league, and assume that Clark Hunt and Scott Pioli are cheap bastards (to use the less nice term). Many Chiefs fans are furious that they’re not spending more. However, as stated at the beginning, of all 32 teams, the Kansas City Chiefs appear to be spending the most cap money this season towards active player contracts.

But how can that be? Wasn’t it just reported back in February that the Chiefs had $63 million in cap space remaining?

At the time that that report was released a few things were taken into account that increased that figure, while several things were not taken into account that would lower that number. Basically, the reported figure was artificially larger than it actually was.

Namely, the $63 million figure included the $24 million (approx.) that the Chiefs rolled over from last season*, but it did not include contract escalators (which, by the way, tend to be non-negotiable devices built into contracts) which amounted to approximately $18 million. Nor did this figure include the money the team was required to pay out to players for NLTBEs offered to them and achieved during the 2011 season and estimated to be about $5 million. Nor did it include money for RFA Tenders (which really wound up just being Jovan Belcher’s for $1.9 million).

*The Chiefs announced through their official team site that they were rolling over $20 million; however sites such as NFL.com, ESPN & Spotrac reported the rollover as approximately $24 million. Given these sites reputability and independence from the organization, we’ll assume the higher number

After deducting the values that were not deducted prior to the report’s release, the Chiefs’ so-called available funds dip to about $38 million (a much more believable figure). Now deduct for Routt’s signing, Dwayne Bowe’s franchise tag and Jovan Belcher’s RFA Tender and we’re down to about $22 million, which is what was reported just before free agency.

Now deduct for the signings of Winston, Boss, Hillis, Quinn, and the rookie class, deduct for the re-signing of Travis Daniels, add money that was freed up through the restructuring of Tyson Jackson’s contract, deduct for Abram Elam and Edgar Jones, and we’re down to $16.5 million. As suggested in last week’s article, it is likely that the $2 million differential between this $16.5 million and the current $14.5 million is due to LTBEs being set for this season.

Okay, so now I see how they went from $63 million to $14.5 million, but if how much the Chiefs are paying on active player contracts is correct, it only appears to be about $8 million over the league defined cap… Pioli just did an interview a week or so ago where he said the Chiefs were spending about $20 million cash over the cap this season.

You are correct in your observation that the contracts amount to about $8 million over the league’s defined base cap. That being said, Scott Pioli is correct that the team is spending about $20 million cash over this same cap.

Alright, now you’re just $*%#@!# with me.

There is a difference between how much cap dollars a team spends in a given season, and how much “committed cash” it spends in a given season. While some things, such as base salary, workout bonuses, roster bonuses, etc., count equally towards both cap dollars and committed cash [Ex: $1 million base salary accounts for $1 million towards the cap and $1 million towards the cash], other things, such as signing bonuses and option bonuses, are accounted for differently.

Ex: Eric Winston signed a 4 year deal that comes with an $8.4 million signing bonus. The entirety of this signing bonus was given to him right away; however, it’s prorated over the course of the 4 year deal so that it hits the cap equally each contract year. So this particular deal is hitting the cap by $2.1 million this year, but hits the committed cash by $8.4 million this year.

Obviously, Winston’s contract isn’t the only contract lending to the difference in cap dollars and committed cash, but at least you can see how the difference comes about.

__________

So, are Pioli and Hunt cheap bastards? Looking at cap availability alone one would think “yes”; however, everything else seems to indicate otherwise. When the Chiefs announced the rollover of last year’s cap space into this season, Clark Hunt stated that the rollover money would be put to use in continuing to re-sign the Chiefs free agents, as well as to go out and sign some free agents from other teams.

The FO lived up to Clark’s word.

Beginning the 2011 season, the Chiefs had 27 players set to hit FA this past offseason. By controlling the player budget enough that Pioli had some idea of how much money could be rolled over, he was able to re-sign Hali and Flowers to extensions early on in the season, and re-signed Succop to an extension in December (and look how huge that turned out being this past weekend). The team also brought back Brandon Siler, Cory Greenwood, Jake O’Connell, Travis Daniels and Amon Gordon (with only Gordon not working out… by the way, no dead money was generated by Gordon’s short-lived contract). Bowe received the Franchise Tag and Jovan Belcher an RFA Tender which, though not as good as extensions, were at least enough to assure their return to the team (and had some other team picked up Bowe at the cost of 2- 1^st Round Picks, or Belcher for the cost of 1- 2^nd Round Pick, something tells me us fans could’ve lived with it). Of the 17 players that hit FA but were not retained, Carr and Orton are likely the only two to complain about. Six were contemplating retirement, four were just terrible, one couldn’t stay healthy with the Chiefs, and four were still perceived as desirable enough to be picked up. The Chiefs, in turn, picked up Routt, Winston, Boss, Hillis, Quinn, Abram Elam, and Edgar Jones as far as players on roster and hitting the cap go. They also picked up Kyle McCarthy, Martin Rucker and Jacques Reeves who all find themselves on IR and don’t count against the cap.

That’s a pretty good offseason. To be where they’re currently at cap-wise, but to have retained Carr, likely would’ve meant no Routt, no Boss and no Winston. To use more of the cap than is currently available (say by re-signing Carr but still signing Routt, Boss & Winston) means making a tougher time of re-signing the Chiefs pick of next seasons 17 scheduled free agents, and not having much money available to take advantage of other teams’ cap casualty cuts (i.e. next year’s Routts, Boss’s & Winstons).

Some of you might not like to hear it, or even want to accept it (even after all the work I just put in showing how they’re spending money and spending it wisely), but it appears the money isn’t being pocketed, and the current regime isn’t likely to end anytime soon. In fact, it looks like things are getting in order (non-Pioli-negotiated contracts are on the way out) and Pioli & Co. are just hitting their stride. But it should be a positive to know that Clark Hunt does care about the team’s success more than he cares about pocketing the money. Now if only the coaches and players can maximize their talents and do it on a consistent basis, we might just have ourselves a team worthy of championships…

Well, Addicts, if nothing else you’ve come away from this knowing more about your favorite NFL team. Maybe you’ve already given up too much hope to reverse the lynch mob, but the management seems to be giving all they can to the team and the fans; looks like it’s time for the team and the fans to reciprocate. While the team leaves it all out on the field on Sunday, why don’t we be there to back their efforts, and give Philip “Cry Me A” River(s) another miserable Arrowhead experience. GO CHIEFS!!!

This upcoming Sunday the Kansas City Chiefs head down to New Orleans to give the Saints a time of it. Given that the Saints have been in the national limelight for years (for both good and bad reasons), and that I haven’t been the only staff writer inspecting the upcoming opponent, I’ve decided to take a hiatus on Know Your Enemy this week and address another issue.

It has come to my attention that there are Chiefs fans out there complaining about the Chiefs cap. I don’t see a problem with it. I mean, scroll up and take a look at that bad boy.

Isn’t it great?

What human being could resist the urge to pounce on the debonair gentleman or courtly lady enlightened enough to don this sexy piece of Chiefs apparel? The wearer instantaneously lets others know that they’re not only intelligent, loyal and a humanitarian, but also that they have a keen fashion sense, all by sporting such an adornment on their crown. Heck, it might as well be a crown.

As for the complaints about cap room, unless your Mr. Moneybags and got a fitted cap, there should be a strap in the back you can adjust to tighten it up… Hold on a sec…

They meant salary cap?…

Are you sure???

Okayyyy. Luckily I know a thing or two about how that works.

Following the Falcons Week 1 aerial assault against the Chiefs’ lacking defense, it was clear to all that Kansas City’s CB depth, or lack thereof, should be an area of great concern (and after Sunday’s whomping by the Bills that concern probably extends to the entire defense). This observation was shortly followed by the announcement that the Chiefs still have $14.5 million in available salary cap space (misconstrued by some as being as high as $30 million). An ugly incident occurred through Twitter and Reddit, and even parties not directly involved in this exchange took to the Web to express their own displeasure over KC’s secondary issues and why it shouldn’t exist given the Chiefs’ available cap room; the common consensus being that Clark Hunt (and family) and Scott Pioli must be cheap bastards.

I can’t deny the Chiefs’ secondary concerns, and even wrote about this concern myself during the preseason. But I’m not sold on the salary cap being what it is as a matter of cheapness. No, I’m much more inclined to believe that the cap will be spent on players, just a little bit down the road and in such a way that the cap room currently looks deceptively large. I’ve already pondered that Pioli and the FO may want to roll the available cap into next season to help retain players such as Bowe, Albert and/or Dorsey and/or have cap space remaining to sign some bigger names entering free agency.

But another option exists. One that would pay the Chiefs’ current players more, but only if they can produce on the field. That option is the incentive bonus.

But isn’t that accounted for in the salary cap?

Glad you asked. There are two types of incentive bonuses: those Likely To Be Earned (LTBE), and those Not Likely To Be Earned (NLTBE). Only LTBEs are accounted for in the salary cap during the season they are expected to be earned. NLTBEs being what they are, not likely to be achieved, are not deducted from the cap in the season they are earned, but rather from the following season’s salary cap. This is where it might pay the Chiefs organization to carry extra money into the 2013 season.

Why take that precaution if the goals are not likely to be earned?

While the goals that are set are determined by the team, the nomenclature of whether such goal is likely or not likely to be earned is determined by league definition. Simplistically, an LTBE goal is one that was attained during the previous season and is therefore expected to be duplicated, whereas an NLTBE goal is a higher goal than was achieved in the previous season and is not considered to be expected to be met. Example: Dwayne Bowe had 5 TDs during the 2011 season. An LTBE goal for him this season would be to get 3 TDs; whereas an NLTBE goal would be 8 TDs (even though Bowe exceeded this goal in 2010).

So what happens if an LTBE goal or an NLTBE goal isn’t met?

If an LTBE goal isn’t met by season’s end, the money that was earmarked for that player/unit is released into the available cap space and may be rolled over into the next season. If an NLTBE goal isn’t met, it just doesn’t have an impact on the current, or next, season’s salary cap.

What kind of goals may these be?

The CBA identifies three categories of incentive goals: (1) Team Incentives, (2) Individual Incentives & (3) Honors and Recognized Media Incentives. Team Incentives and Individual Incentives can be made in most every major statistical category you can think of. Honors and Recognized Media Incentives pertain to the larger honors (Pro Bowl Selection, All-Pro Selection, etc.).

__________

On September 7^th, Pro Football Talk reported that the Chiefs had approx. $14.5 million in available cap space. The latest report prior to this indicated that the Chiefs had approx. $16.5 million in available cap space. No player additions that would’ve affected the team’s accounting were made in the interim, so the safe bet is that the approx. $2 million differential comes from the making of LTBE goal(s). It should be noted that “win the division” is always considered, by definition, to be an LTBE, and it’s likely that such a goal accounts for some of this differential.

What isn’t known is how much of the remaining cap space is earmarked for the potential earning of NTLBEs. Again, the team’s or player’s performance from the previous season determines whether a goal is likely or not likely, and we can all agree that the 2011 season was disappointing. It wouldn’t take setting goals too high for them to be considered Not Likely To Be Earned. But such goals could include finishing with a winning record, making a deep playoff run, etc.

These are things that both the Chiefs organization as well as its fans want, and are within the potential of the team to earn. But paying the money upfront does not guarantee the player/unit/team will fulfill their potential. In fact, by setting things up so that the players only receive the money by earning it makes perfect sense. If the players earn the money, then great, it’ll mean the team has succeeded to a desirable level, the players will get the money they deserve, and, thanks to the cap management, the money can be paid out without putting the team in a compromising position that would require “cap casualty cuts” next season. If the players don’t produce, that’ll suck, but at least significant rollover cap funds will be available next season to help pull in free agents that may stand a greater chance of helping this team get to where it wants to be.

I know not having Brandon Carr sucks, especially considering the defensive failures of the first two games. But you know what else sucks? Cutting valuable players because you played fast and loose with your cap, and paying players a lot more than they’ll ever earn for the same reason.

More is going on behind the scene than meets the eye. For as much as Pioli gets demonized for this, that and the other thing, I’m not convinced that he’s deserving of such scorn. The way some people would spin it, every letdown the Chiefs experience, collectively or individually, is squarely on Pioli’s shoulders. But one person can’t control the actions of others. Limit their actions, maybe, but not control them. The coaches are not currently living up to their potential. Same with the players. Oh, they have shown at points in the past that they can perform much better than they have been; they just haven’t gotten a handle on it this season thus far. I’m not going to blame Pioli for these individuals’ failures. Their failures belong to them.

Now, I don’t profess to know what exactly is causing these failures. But I do know that I still love the Chiefs. And like with any loved one that makes a mistake, I’m not gonna go into a rage, verbally berate them and tell them to do better or else. I have been appalled at the amount of people that so quickly jumped to that reaction. Such actions have a way of demoralizing any person, and a lack of morale is the last thing this team needs right now. No, I’m gonna support my beloved Chiefs and encourage them to start performing at the level I know they’re capable of, and I appeal to all of you to do the same. A while back, one commenter made the statement that the home crowd shouldn’t make a difference in how well a team performs, and if that’s the case, why is homefield advantage such a huge deal come playoff time? I’ll tell you why: it’s because fan support does matter, it matters a lot more than you might think.

The sky doesn’t have to fall, but the less support there is, the more likely that baby will come crashing down. It took a flurry of Twitter messages conveying fan loyalty to the Chiefs, and respect for his individual abilities, to convince Eric Winston to come to a smaller market in Kansas City, even though he likely could’ve landed a big contract at a dozen other places. I’m curious as to how much drive and motivation could be stirred up in exploding your current Chiefs players’ Twitter accounts with positive, morale-boosting messages. We’re looking for someone to light a spark; what if we could be that spark? Idle support begets idle response. Chiefs fans were once undeniably the best fans in football, let’s embrace that legacy and kick it up a notch. Let the boys hear some noise! Let ‘em know that we not only want to see them kick some ass in New Orleans, but that it’s time to put the women and children to bed and go looking for @#$%#$% dinner… GO CHIEFS!!!!

Denny Medley-US PRESSWIRE

In a couple days the Kansas City Chiefs leave for Buffalo, NY to square off against the Bills in the Chiefs’ first road game of the regular season. Tensions are high for both teams as both suffered crushing defeats in their first games of the season. Of course, Eric Berry also has a bone to pick with Stevie Johnson, but if Stevie’s smart, he may just get “injured” before the game even starts and avoid the abuse every KC defender is likely to inflict on him.

Continuing the Know Your Enemy series, let’s take a look at this weekend’s opposition:

Offense

The Buffalo Bills’ offense is led by QB Ryan Fitzpatrick. Fitzpatrick is the type of QB that when he’s on he’s on, but when he’s off he’s really off. Last year, the Bills started off strong and some started to think that they could be the real deal; this started with Ryan Fitzpatrick’s early on. Unfortunately for Bills fans, that also ended with Fitzpatrick when the Bills followed up this hopeful beginning with a  massive losing streak. Fitzpatrick wound up throwing 20 INTs over the last 13 games of the 2011 season. That trend appears to have continued. Fitzpatrick threw 3 INTs to the Jets last week; one of which was a pick six. This is also the fourth game in Fitzpatrick’s last nine starts in which he threw 3+ INTs. Mind you, Fitzpatrick also threw for 3 TDs on Sunday, but two of those came midway through the 4^th quarter when the Jets were leading 41-14, and have been considered by many Buffalo news outlets to be junk TDs.

As far as receiving threats go, Stevie Johnson shouldn’t be underestimated and Donald Jones does well enough, but neither of these players come close to being more formidable than Julio Jones and Roddy White. Likewise Bills TE Scott Chandler is no Tony Gonzalez. Add to the mix WR3 David Nelson suffering an ACL injury in Sunday’s game that has him out for the season, and the subsequent replacement of him by rookie T.J. Graham whom the Bills’ coaches acknowledge is behind in learning the pro game, and the Chiefs are looking to have an easier time with pass defense this weekend.

Onto the running game, there’s good news and there’s bad news. The good news (at least for us) is that Fred Jackson will be out for a knee injury that he incurred during the Bills loss to the Jets. The bad news? Jackson’s back-up C.J. Spiller is no slouch. Though listed as No. 2 on the depth chart, Spiller prides himself in preparing for games as though he were the No. 1 guy, and he looks like he could be a No. 1 RB in the NFL even without injuries elevating him to that position. Following Jackson’s injury in Sunday’s game, Spiller managed to finish the day with 14 carries, 169 yards and 1 TD. To spare you doing the math, that’s an average of over 12 yds/carry. This average is as large as it is due to two large breaks of 56 yards and 49 yards, the 56 yarder being his TD carry. Even factoring out those big gains, though, Spiller still averaged over 5 yards per carry. I won’t go so far as to say Spiller is a better back than Michael Turner (there has to be more frequent and consistent success before that could ever be said), but the Chiefs’ defense will have to be wary of Spiller’s presence on the field and prevent any big breakaways Spiller is hoping to repeat this week.

One last note on Buffalo’s offense: you may or may not have heard of/remember Brad Smith. Drafted out of Missouri in the fourth round of the 2006 Draft by the Jets, the Bills retained his services last year in hopes of utilizing his unique athleticism. Listed as a QB/WR, the Bills intend to utilize Smith in the capacity of a Wildcat QB. Last year’s shortened offseason saw the Bills not quite being able to get this new look off the ground last season; however, with Smith getting in a full offseason this year, the coaching staff will be looking to integrate the Wildcat package all the more into their offensive attack this season. It doesn’t hurt that the Bills hired David Lee to be their QBs coach this season. For those of you who don’t know, Sporting News named Lee “Innovator of the Year” in 2008 for introducing the Wildcat offense to the pro game during his time as OC for the Dolphins. If the Chiefs look to be doing a sound job of neutralizing Spiller and frustrating Fitzpatrick, don’t be surprised to see some Wildcat added to the mix.

Defense

Have you heard that the Buffalo Bills signed Mario Williams? Of course you have. Have you heard that Mario Williams did next to nothing against the Jets? Perhaps not, but it is true. Mario Williams walked away from Sunday’s game recording only one tackle, and not so much as one QB pressure. He’s still the $100 million dollar man on what could be the best defensive line in the NFL, but he didn’t come close to showing why he garnered such a contract and why the Bills’ DL is speculated to be among the best against the Jets. So the good news is that Mario Williams can be neutralized altogether, with the less-than-good news being that he’ll probably have a pretty big chip on his shoulder following Sunday’s game. Though the Bills did not register a single sack in their game against the Jets, the Chiefs OL has shown growing pains in gelling as a unit and allowed the Falcons to register three. In addition to Mario Williams, the Bills DL consists of Marcell Dareus, Kyle Williams and Mark Anderson. Though it may be possible for the Chiefs OL to duplicate the output of the Jets’ generally less talented OL, it will be a hard fought battle to keep these four guys from putting the pressure on Cassel.

Buffalo’s linebacking corps isn’t incredibly noteworthy, but I would be doing him a disservice to not mention OLB Nick Barnett, the Bills greatest threat at the LB position. Prior to getting signed by the Bills last season, Barnett was drafted by, and played eight seasons for, the Green Bay Packers and was even selected by the Associated Press as a second team All-Pro in 2007. Though 31 and a few years removed from national recognition, has consistently registered 100+ tackles per season over his 10 years of experience (save for 2 years, 2008 & 2010, in which he was injured for a significant amount of games).

The Bills’ secondary may be Cassel’s bread and butter. Starting CBs Stephon Gilmore and Aaron Williams are both young guys, and though both players were taken early in their respective drafts (Gilmore 10^th overall this year, and Williams 34^th overall last year) and should develop into excellent cornerbacks in time, the key phrase there is “in time”. Both players’ performances over the preseason and during the first regular season game have caused some concern among the Bills’ coaching staff. The main problem against the Jets is that they were allowing their receivers to run too wide and open. I’m sure Chan Gailey has been and will be stressing this issue during this week’s practice in preparation for the Chiefs, but I’m equally sure that the youth of these players may very well cause them to go to the other extreme and incur quite a few pass interference calls in this weekend’s game. Were we playing Buffalo later in the season, these players might be greater cause for concern, but for now Kansas City should be able to exploit some good matchups.

Special Teams

The Bills are one of those teams that have decided to carry three kicking specialists: a FG kicker, a place kicker, and a punter. Rookie placekicker John Potter has gotten much praise for his work up ‘til now as he has consistently sent his kickoffs through the back of the endzone; Punter Brian Moorman has been consistently good over the years at placing his punts inside the 20; and PR Leodis McKelvin is not a bad guy to have averaging 10 yards per punt return. The Bills punt coverage team does leave much to be desired though, and allowed the Jets to return a punt 68 yards for a TD early in the second quarter.

______

Overall, can’t say I’m too terribly concerned about Sunday’s matchup. The Bills look to be a much easier team to exploit and defeat than the Falcons proved to be. One thing to note about Fitzpatrick’s performance against the Jets is that he performed that poorly without New York registering any sacks; with Tamba back and Houston hungry, Fitzpatrick would be a fool to think he could get so lucky a second week in a row. Given the efficiency Cassel displayed in the first half of the Falcons game, I’m one Brandon Flowers away from calling this game a definite lock.

Potential, major momentum shifts caused by Chiefs’ D: 1) Rattle Fitzpatrick early and let the interceptions spring forth; 2) Make Spiller eat turf early and often

Potential, major momentum shifts caused by Chiefs’ O: 1) Neutralize Mario Williams early and let him throw another hissy fit; 2) Play physical enough to goad the young CBs to commit pass interference until they start playing as open as they did last week

Potential, major momentum shifts caused by Chiefs ST: 1) Break open a big PR or KR, even if it can’t be returned for a TD, giving up a huge chunk of yardage should spur PTSD in some of the coverage teams’ personnel

That’s my outlook on the Chiefs’ opponent for the upcoming weekend. If there’s something I missed, you know what to do.

Kyle Terada-US PRESSWIRE

“It is said that if you know your enemies and know yourself, you will not be imperiled in a hundred battles; if you do not know your enemies but do know yourself, you will win one and lose one; if you do not know your enemies nor yourself, you will be imperiled in every single battle.” – Sun Tzu, Art of War

The Kansas City Chiefs square off against the Atlanta Falcons on Sunday. As Addicts, odds are that we as fans are well aware of the Chiefs’ strengths and weaknesses, even if we choose not to outwardly express our thoughts and concerns on certain issues. We know our Chiefs, so to speak. But beyond a few players or personnel, not all of us can say the same about knowing the Falcons.

Though Central Pennsylvania tends to be a melting pot for NFL fans, I can’t say that I know any Atlanta Falcons fans that I can speak football with on a regular basis. Deciding to be proactive, I looked a little further in depth to what Atlanta excelled at last season, and what they might be looking to do this season, and wasn’t really pleased with what I discovered.

Offense

The Falcons are generally perceived as one of the more balanced offenses in the NFL. The likes of Matt Ryan, Roddy White, Julio Jones and Tony Gonzalez pose a clear passing threat, and Michael Turner has been one of the better premier backs in the league for some time. This is well-known.

Julio Jones put in an impressive preseason and has shown that he should be worth every bit that GM Thomas Dimitroff gave up in order to draft him. This should also be known.

What may not be known by the average fan is that the Falcons are among the fastest starting teams in the league. Since 2008, the Falcons ranked first in the league for points scored on their first offensive possession (173), and last season ranked third in the league in this category scoring 51 points on opening drives, which includes six touchdowns. It could be said that Atlanta has become quite accustomed to putting up points right off the bat, and if Kansas City can stall such efforts it may be a bigger momentum-shifting, tone-setting course of events than might otherwise be suspected.

Further, the Falcons and Matt Ryan have publicized Atlanta’s intentions to make more big play attempts in the passing game this season. They are going to throw the deep ball, and they are likely going to throw it more often than other teams, and with much more serious threats in Julio Jones and Roddy White. Matt Ryan has gone so far as to state that “… [completing] one out of three [passes] on balls way down the field [is] not a bad day”, so do not expect a couple failed attempts to be enough to deter Atlanta from going to the air on Sunday. The threat of the deep ball will be a daylong threat, and it will be up to the Chiefs’ banged up secondary and hurting pass rush to keep this threat from becoming a reality.

Additionally, the Falcons boast an 83% scoring efficiency on drives lasting 10 or more plays during the period of 2008-present, and own a 40-13 Win/Loss record during this period when Matt Ryan throws at least one touchdown pass during a game. So on top of guarding against the quick, big play, Kansas City will have to safeguard against the long drawn out drives. Peachy.

On a more positive note, Tony Gonzalez is winding down on his career, and though he has not experienced quite as big of a dropoff in productivity as, say, Antonio Gates, he is not the same player we remember so fondly from his time in Kansas City. Returning to Kansas City may give him an added boost in his play, but overall he’s not as big of a threat as some of us may remember; make no mistake about it, though, he is still a threat. Additionally, there has been a lot of speculation over several outlets that Michael Turner may be looking at a decline in his production. Turner has been around long enough for the general wear and tear that comes with being an NFL running back to take its toll on his body and slow him down a bit. The only other Atlanta running back getting a lot of notice this preseason has been Jacquizz Rodgers, and quite frankly, Nate Eachus put in better performances than Jacquizz Rodgers. When the Chiefs’ No. 5 RB looks better than the Falcons’ No. 2 (or 3) RB, it either says great things about the Chiefs, terrible things about the Falcons, or some combination thereof; in any case, if Turner can be shutdown, the remaining options aren’t looking too threatening.

Defense

If the Falcons’ offense is exceptionally good at scoring on their first possession, the Falcons’ defense is exceptionally good at preventing opposing teams from scoring on first offensive possessions. In fact, the Falcons only allowed 16 points to come from opponents’ first possessions last season, with only one touchdown contributing to that total. Since 2008, the Falcons have only allowed 20.1 points per game, and the organization seems to chalk this up in large part due to the team’s ability to set the tone of the game by preventing opponents from scoring on their first possessions. If you’re Romeo Crennel and Brian Daboll, this one seems pretty clear: score, and score at the first opportunity. Even if the drive takes several plays until meeting the end result of points on the board, it will be a great blow to the Falcons to shove the ball down their throat and have them second guessing their defensive decisions and strategy.

During the offseason, Atlanta traded a seventh-round pick to Philadelphia to retain the services of Asante Samuels. This move gives the Falcons three very good players in their secondary at the CB position: Samuels, Dunta Robinson and Brent Grimes. Samuels himself is a bit of a ballhawk, but has been justifiably labeled as a bit of a liability at times. Samuels tends to play on instinct, and while sometimes those instincts help lend to his interception totals, he is apt to give up the big play when those instincts cause him to make the wrong decision on where the ball is going.

Brent Grimes is one of the better CBs in the league, and should be likened a bit to Brandon Flowers. Just as Flowers may not be much of a household name outside the AFC West, Grimes may not be much of a household name outside the NFC South. But like with Flowers, this doesn’t make Grimes any less great.

As for Dunta Robinson, he has been somewhat subjected to the stigma of not living up to his potential; this is likely to change this season. The Atlanta Falcons are putting a high priority on getting to the QB this season, and have been devising new blitzing schemes to better incorporate their personnel in reaching this goal; Dunta Robinson is a large part of these new plans. DC Mike Nolan will be playing Robinson out of the slot position, and allowing Robinson to take on a more physical style of football from this position. Robinson is expected to see more blitzing opportunities and couldn’t be happier for it. This might not be too much of a factor for Kansas City. Though Cassel didn’t look too good in the preseason on the longer developing plays where blitzing was involved, the Chiefs did realize quite a bit of success in throwing the shorter, quicker passes utilizing Charles and Hillis out of the backfield, and McCluster and the TEs over the middle. A successful drive against the Falcons may not involve a lot of impressive deeper down the field style plays, but may rather involve chipping yardage off one play at a time and rendering the Falcons’ new blitzing designs largely ineffectual.

Rubbing salt in the defensive wound, the Falcons lost MLB Curtis Lofton during the offseason which will not only have their LB corps hurting quite a bit, but is a big loss to their leadership on that side of the ball. I am much happier that the Chiefs will be facing a Falcons defense without Lofton than a Falcons defense with him.

Special Teams

The Falcons appear to boast an impressive punting game. P Matt Bosher is consistently successful at dropping the ball inside opponents’ own 20-yard lines, and the punt coverage unit was the NFL’s best last year, holding opponents to an average of 4.8 yards per return.

K Matt Bryant is 37 and has likely lost some kicking strength. While I wouldn’t classify him as great, he is performing at a slightly above average level, and can be trusted to ace kicks less than 40 yards, with 40+ yard attempts being a little iffier.

As for Atlanta’s return game, it looks to be in a transitional stage with untested (in regular games) returner Jacquizz Rodgers currently topping the charts. With poor coverage any returner could take it to the house, but the Chiefs do not appear to be likely to give up a TD to a team at this stage of their return game.

______

Overall, Sunday’s game will definitely be a tough battle, as Atlanta looks to be among the more well-rounded teams in the league.

Expected momentum shifts the Chiefs’ defense may cause: 1) stopping the fast start; 2) preventing the big play multiple times in a row; 3) holding Atlanta’s drives to nine plays or less before forcing the punt.

Expected moment shifts the Chiefs’ offense may spur: 1) enacting a fast start of their own; 2) beating the blitz; 3) making Atlanta’s D doubt itself (and their FO sorry for letting Lofton go) by striking up the middle by land and by air.

Expected momentum shifts on special teams: 1) engineering punt returns for double digit yardage; 2) forcing Matt Bryant to attempt 40+ yard FGs.

And, of course, the final momentum shifter is Kansas City’s 12^th man: Make it loud, Chiefs fans, and remember, there’s no shame in making their ears bleed: it just adds more red to the field.

Denny Medley-US PRESSWIRE

The Kansas City Chiefs got spanked by the Seattle Seahawks. As infuriating as it is to write that sentence, there’s no way around it. So, who’s to blame? [This is a cue for the Matt Cassel detractors to skip to the Comments section. This article is probably not for you. I’ll wait.]

…

Now that I’ve cut down on my readership (which in hindsight was probably a terrible idea), I will say that I think only a small amount of blame should fall on Cassel. WRs dropping passes that should by all means be caught dead to rights is much more a WR failure than a QB failure. Cassel’s fumble occurred from behind as a result of pass blocking failure, and, if he were standing around like a slouch it’d be one thing, but it’s harder to blame Cassel for not protecting the ball when he was reeling up to launch it (I’m actually incredibly curious what the end result would’ve been had Cassel been able to get the pass off, and, right before the fumble, instantly noticed that despite being under pressure and stepping forward Cassel didn’t lose track of where the line of scrimmage was and such a pass would’ve remained legal). And, though it’s never good to see your team’s QB throw a pick, the Chiefs were down by 23 points at the end of the third quarter and in a third down situation, facing certain sack Cassel made a choice that many NFL QBs (including ones among the elite) would’ve made by trying to dump the ball to the only teammate capable of catching it and keeping the drive alive, it just failed in the worst way possible. If the game were closer, I think we should be more upset at the end result (pick six), but in this particular situation, I’m inclined to cut him a break; if he does it in the regular season when the score is closer, or there’s more time left in the game, then I’ll start calling for his head.

Through the first two preseason games, Cassel looked like a better, more confident QB than we’re used to seeing. Does he still checkdown? Yes, but when that habit has been combined with a supporting run game, the Chiefs have been quite successful this preseason. I don’t think checkdowns are a problem when the plays are called right. In fact, one of the most absurd observations I heard following this last game’s blowout is that, during the only TD drive Cassel engineered, he checked down on all but maybe one pass, which I find absurd because why should anyone complain about checkdowns when the end result is a TD? Trying to throw a deeper ball got the team nowhere, after all. Besides that, a checkdown-laden, successful drive makes the opponent’s D more tired, the Chiefs’ D better rested, and yields less time on the clock for the other team to counter with points of their own.

The offensive playcalling witnessed in the Seahawks game was definitely off compared to the much more successful playcalling in the previous two games. Overall, I think the talent is there, and keeping the playcalling of the first two games and slowly working in the bolder plays of the last game will reap rewards over the long haul, so we shouldn’t be too worried going forward, despite this last game’s final score (offensively).

What fans should be worried about is the secondary. Jalil Brown may or may not have unrealized potential, but a CB replacing Brandon Flowers needs more than unmet “potential” if the Chiefs’ secondary wants to be more than a sieve. And the sieve-like tendency isn’t restricted to this year; going over last year’s statistics, it appears there should be less worry over the run defense, and more worry over the pass defense.

I’ve decided to compare the 2011 Kansas City defense to the Top 3 defenses of the season (Pittsburgh, Baltimore and Houston) to see how the Chiefs stacked up. We’ll start with examining the run defenses.

As can be seen, the KC had the greater numbers across all categories, which looks pretty bad at first glance. But note that opponents tended to run the ball a lot more against KC’s defense than against the other three teams. To even the playing field (so to speak), I decided to determine the likely results of a rushing attempt against KC versus a rushing attempt against the other three teams; this requires generating a TD% and 1^st Down% for each team. [TD% is equivalent to the TD stat divided by Attempts; 1^st Down% is equivalent to 1^st Downs divided by Attempts. As you’ll note, Y/A has already been calculated and included in the table, as this is a more commonly broken down statistic.] The determination of this breakdown is as follows:

As can be seen, the Chiefs still had a significantly higher than desirable TD% having allowed 2.76% of rushing attempts to result in a TD; however the team fared better than most of the other three teams only having allowed 18.9% of the rushing attempts against them to result in a first down, with Baltimore being the only team performing better. As can be seen in the first table, the Y/A average is negligible, and shouldn’t require too much improvement to match a Top 3 defense. Overall, there is still room to improve the run defense to the level of a Top 3 defense, but, as you’ll soon see, the difference is a lot more lopsided when comparing pass defenses.

The pass defense stats for each of these teams are as follows:

Looking over the table you’ll see that, despite having had less attempts made against them, and having allowed less completions, the Chiefs defense allowed the highest number in each of the remaining categories. So, right off the bat you should know the comparison isn’t going to bode well at all for Kansas City. But keeping with the formula used in comparing run defenses, I’ve calculated the TD% and 1^st Down% to determine the likely results of a passing attempt against KC versus a passing attempt against the other three teams, throwing in the pass completion percentage, as well.

Not only were opponents significantly more likely to complete a pass against the Kansas City defense than the other three teams, but they were also significantly more likely to see that completion turn into a TD or 1st Down, and by a much greater margin than when comparing run defenses. These numbers are unacceptable, and should have us a lot more worried about the team’s pass defense than their run defense, especially when you consider that last year’s secondary consisted of Brandon Carr, Brandon Flowers and Kendrick Lewis, none of whom are currently able to play for the team (Flowers and Lewis over those pesky injuries, and Carr over that pesky “on another team’s roster” thing).

Only so much of last year’s pass defense failures can be blamed on the rotating starters at the SS position, and on Belcher (a/k/a the defense’s Matt Cassel), and while I think that Routt will adequately replace Carr, and Elam will be a suitable fill-in for Lewis, not even the return of Eric Berry will fully make up for the (albeit temporary) loss of Flowers and the subsequent promotion of Jalil Brown to starting CB.

As the defensive situation currently stands, mobile QBs certainly seem to be an Achilles’ heel, as do better WRs than Jalil Brown can handle (such as Amendola). Only time will tell how Kansas City’s secondary will shake itself out, but make no mistake about it, the Chiefs’ pass defense should be a primary cause for concern, and three above average players in the secondary will be lucky to duplicate last year’s disappointing figures, let alone improve on those numbers. With Berry knocking off more of the rust accrued from not playing last season, and the front seven improving in the pass rush (Hali’s suspension for the Atlanta game notwithstanding), we may have more hope than I’m letting on; however, let us still hope that Lewis and Flowers (especially Flowers) find their way onto the field sooner rather than later, or the Chiefs will very likely be in for a rocky start.

Jeff Curry-US PRESSWIRE

Well, Kansas City fans, at this point during the week I’m sure we’re all a little exhausted of hearing about the the Chiefs’ failure against the Rams Saturday night. The Chiefs secondary was lacking in some things (to say the least), the injured status of Kendrick Lewis and Brandon Flowers has us all concerned and Ricky Stanzi performed miserably. To boot, we all have questions pertaining to just what caused Tamba Hali’s suspension. But let’s try to brighten up here. Bowe is back, Cassel is continuing to do well in Daboll’s offense and, at the pace he’s going, Peyton Hillis is looking to be a strong candidate for Comeback Player of the Year. Further, the Chiefs are better off seeing the weakness in their D now instead of, say, the fourth preseason game; the two remaining preseason games should provide us fans with a good litmus test for what to expect from our Chiefs at the start of the regular season now that Crennel knows just what kind of adjustments need made that could hamper some of the better QBs in the league, several of which the team’ll be facing right off the bat.

Before making my predictions last week, I considered how I saw the Chiefs’ 53-man roster fleshing out and drew the following conclusions:

ST: K – 1, P – 1, LS – 1

OFF: QB – 3, RB – 4, WR – 7, OL – 8 or 7, TE – 3 or 4 (8 OL & 3 TE, or 7 OL & 4 TE)

DEF: DL – 7 or 8, LB – 8, DBs– 10 or 9 (7 DL & 10 DBs, or 8  & 9, respectively)

When considering this structure, I felt a few position group numbers were a little high, but a quick look at last year’s roster, courtesy of Pro-Football-Reference, assured me that I’m pretty well in the ballpark. And, yes, having a minimum of nine guys in the secondary and a possible ten still seems a little excessive, but when you consider that last year’s active roster, at one point or another, included Brandon Flowers, Brandon Carr, Eric Berry, Kendrick Lewis, Jalil Brown, Travis Daniels, Javier Arenas, Reshard Langford, Jon McGraw, Donald Washington & Sabby Piscitelli, I’m not too far off base. Of the nine or ten DBs I expect to make the roster, do I expect all of them to be on the active roster come game day? No; just as I don’t expect the 7^th WR, 8^th OL, 8^th LB, or 3^rd QB to be on the active roster. Remember, though it’s a 53-man roster, only a maximum of 46 players may be active on game day (up from the previous CBAs 45-man limit), which leads us to this week’s predictions:

1.  With Flowers and Lewis out for an indeterminate amount of time, Crennel will take a hard look at the DBs on roster (I know, I’m friggin’ Nostradamus, right?). Chalking up Saturday’s problems to a secondary that is “young”, “inexperienced” and lacking “maturity”, Crennel will focus mostly on filling out the roster with the more veteran players. Though some of these players’ ceilings may not be as high as some of the newer guys, their consistency and reliability in the short term will prevail over longer term, but potentially better, developmental projects. As I see it the roster will consist of : 1. Flowers; 2. Routt; 3. Berry; 4. Lewis; 5. Abram Elam; 6. Travis Daniels; 7. Jalil Brown; and, 8. Javier Arenas. This leaves one maybe two spots to take on either Jacques Reeves and a project player, or two project players, with the likely candidates being Dequan Menzie, Terrance Parks and Tysyn Hartman. Dequan Menzie may be in the same boat as Junior Hemingway; an injury plagued camp may spell practice squad, but I think the odds of that are worse than with Hemingway, and choosing Menzie and either Parks or Hartman over Reeves to fill out the bottom of the roster wouldn’t be too surprising. That being said, I could somewhat understand if Reeves was chosen to stay on roster with the other candidates being practice squad eligible. In any event I would not be shocked to see all three of Menzie, Parks & Hartman keep ties with the team, even if one or two is/are kept in the capacity of practice squad player(s). The remaining options (Fenner, Fanor, etc.) just don’t strike me as making the cut in any capacity.  That includes Donald Washington, who despite being a veteran and “more mature”, seems to me to be too costly of a save at this point.

Scott Rovak-US PRESSWIRE

2. Stanzi will still make the roster, but as the No. 3 QB and only for the purposes of continued development. He’s just not looking that good right now, and if a playoff berth is still in the cards and push comes to shove (Cassel and Quinn are unable to play), Pioli has enough sense to make a powerplay for a much better QB. The three I could see getting the most consideration in this hypothetical situation are Matt Moore, Matt Hasselbeck and Mark Sanchez. Moore has the most (and recent) experience in a Daboll-driven offense and could slide in and understand the terminology, assignments, etc. the easiest. Hasselbeck, on top of the reasons Paddy pointed out, not only provides consistently good play, but given his age would not be perceived as a threat to Cassel. And I think Sanchez is simply better than he’s given credit for: he’s actually improved every year he’s been in the league, he has playoff wins under his belt, and given a more stable locker room and stronger supporting offensive cast, I think he would surprise. Obviously, this hypothetical scenario also takes place later in the season where Moore, Hasselbeck and Sanchez may be seen as expendable for the right price. In any case, I don’t see Stanzi taking the field if the Chiefs still have a shot at the playoffs; until he shows us significantly more than he has, I think I’d rather see Zorn suit-up and take the field.

3. Following another lackluster game performance, Josh Bellamy’s stock has dropped some, but he should still be counted as a candidate for the last WR slot (though arguments for Markshausen and, as KCMikeG pointed out, Jamar Newsome have gotten stronger). Bear in mind that a) the last WR isn’t likely to sniff the active roster, b) injury to Bowe or Baldwin will be overcome by Breaston resuming the role of the No. 2 WR, a role he held for most of his career (remember: Boldin played out of the slot in Arizona), and c) an injury to McCluster will result in Breaston, and eventually Wylie, being able to fulfill the role being carved out by Dex. If Breaston or Wylie get injured, it’ll be a blow, but likely not a humongous one. If any two of Bowe, Baldwin and Breaston get injured, the Chiefs would definitely be in trouble, but unless both of those injuries were expected to be long-term, I’d anticipate we’d see Daboll calling for more 2-TE sets until one of the guys returned.

Cary Edmondson-US PRESSWIRE

4. I’ve grown quite fond of Kendrick Lewis. As last year wore on after Berry’s injury, Lewis started to improve by leaps and bounds, and I firmly believe he is a better player now than he otherwise would’ve been at this point in his career had Berry not been injured. In the face of adversity, Kendrick rose to the occasion, and how can you not love a player capable of that? But that being said, I agree with AA’s own Lyle Graversen that the loss of Flowers is greater than the loss of Lewis. Abram Elam will provide adequate temporary replacement of Lewis until Lewis can heal up; however, one of the greatest disappointments concerning Kendrick’s injury is that the newly implemented defensive scheme of putting Lewis and Elam in at safety and letting Eric Berry roam freely and wreak havoc is in danger of not being utilized until his Lewis’ return. Enter Travis Daniels. I’ll admit, I was pretty indifferent to Travis Daniels prior to this season (didn’t love him, didn’t hate him), but since he switched to taking on safety duties, I have a little more hope in his capability to make significant contributions to the team. There are two preseason games left, and I would not be the least bit surprised to see Daniels tested harder at safety to see if he can provide suitable replacement for Lewis in the new scheme so it can start being effectively used before Lewis heals up and returns. With Tamba a certain loss in the Atlanta game, and Flowers and Lewis uncertainties as to whether or not they’ll play, Daniels being coached up enough so that the new scheme isn’t a liability may be integral to a Chiefs victory on opening day. That may be a lot of faith to put into Daniels, but a roving Berry may be the team’s best hope for a victorious pass defense without Flowers, Lewis and Hali in the mix.

Thus concludes my predictions/observations for this week, Addicts. If you disagree with anything I’ve said or proposed, or think that there’s a player I’m not giving enough credit to (or giving too much credit to, for that matter), let me hear it in the “Comments” section. And as always, Go Chiefs!!!!!

Denny Medley-US PRESSWIRE

Scott Pioli and Romeo Crennel find themselves in an uncommon predicament in Kansas City. The Chiefs have more depth than they’ve had in years, and it’s time to start pruning back the roster. While Pioli has more notable experience at this task due to his time in New England, RAC’s experience as HC in Cleveland was probably less “which player is better” and more “which player sucks less”.

Further, the CBA explicitly leaves it to each team to determine its own cutdown schedule, which for Pioli, at least, tasks him with determining what moves are best for the team that’ll play the regular season and what moves are best for the ledger. You see, while the Chiefs could hold, in theory, hold all players until the end of the preseason, making all cuts and practice squad assignments in one fell swoop, they also have to pay each player each week they remain on roster (plus housing, meals and other costs). For players that have not yet accrued one NFL season the rate is $850 per week. For the remaining players, who are considered veterans with at least one season under belt, the sum is $1,600 per week.

Being in a position not so concerned about the business aspect of the NFL, Crennel will obviously be interested in getting the best players for his team on the 53-man roster.

A few position groups look a little tighter than others and will warrant longer looks. The Chiefs’ RB/FB group, DL & OL look particularly tight. Their LB corps also looks tight outside of DJ, Hali, Houston & Belcher/Siler, but the talent dropoff is a little bit more noticeable for the remainders (which is bound to happen when compared to DJ, Hali and the emerging Houston). The WRs and DBs are overcrowded, but a few names are clearly improving and impressing over others so it might not be as tight as it looks on paper. QBs look pretty straightforward (Cassel, Quinn & Stanzi on roster and Tanney on the practice squad), as does TE (Boss, Moeaki & Maneri on roster for sure; maybe Biere or O’Connell if they decide to keep a fourth).

A couple important things to note is that, while it is a 53-man roster, the practice squad is allowed up to 8 players (9 if the team puts an international player on the squad as the 9th person, which doesn’t look to be pertinent to the Chiefs this year). So realistically, of the 90 men on roster, only 29 must be cut from the team completely. Also an interesting point to note is that, while any team can sign a player from another team’s practice squad, they may only do so in the interest of adding the player to the second team’s own 53-man roster; the CBA prohibits teams from taking a player off another team’s practice squad just to turn around and put the player on their own practice squad.

Following Preseason Week 1, here are a few observations and predictions concerning how Pioli & Co. may handle the cuts this season:

John Rieger-US PRESSWIRE

1. Shaun Draughn and Cyrus Gray both look like they could be solid contributors in the regular season. Putting one of these players on the practice squad could be synonymous with cutting them, as I think another team would be likely to clear a spot on their 53-man roster to take a chance on them. Inversely, I don’t see the Chiefs carrying more than 4 players in the backfield, which means they might have to do without a fulltime FB. Hillis can provide these services, if needed, and the team’s decision to crosstrain a few TEs in the role may make Shane Bannon expendable. Notice I said “expendable” rather than “relegated to the practice squad for another year”. The Steelers starting FB went down to an ACL tear during the Steelers preseason opener against the Eagles, and is likely to be out for the entire season.* The Steelers have a way of making good use of their FB on roster and may be looking to replace him for the season. Todd Haley might look no further than KC in recommending a replacement to HC Mike Tomlin, and Haley’s eyes may be on the waiver wire or KC’s practice squad (as the case may be). Now the Steelers have shown a tendency to prefer FBs that are more in the FB/TE hybrid vein, so maybe this circumstance won’t arise, but it bears keeping an eye on.

* Been there, right? Hey, maybe the injury bug followed Haley to Pittsburgh. Wouldn’t that be nice?

2. In limited punting opportunities, K/P Matt Szymanski put up numbers comparable to Colquitt’s. Additionally, Szymanski did consistently great during his opportunities on placekicking duties. While it’s likely that Colquitt will remain the Chiefs’ punter this season, and that the Chiefs won’t carry more than one kicker and one punter on the 53-man roster (other position groups are too crowded and the additional spot could be better used elsewhere), more importance has been placed on STs this year, and the future prospect of only needing to use one roster slot for a K and P is enticing (and we all know Pioli loves versatility). I expect Szymanski to get a practice squad slot and to receive a lot of focus on punting this season. If it looks like he could suitably replace Colquitt, Pioli may just let Dustin’s contract expire at the end of the season and move forward with the player that may potentially develop into a suitable K as well a few years down the line.

Denny Medley-US PRESSWIRE

3. The DL looks thicker. Just a few months ago a lot of fans were taking it for granted that players like Powe and Amon Gordon would make the roster, myself included; now, I’m not too sure. Toribio has progressed more than any of us probably anticipated and will likely remain in the Top 2 in the depth chart at NT. Gordon does have an edge on Powe, as he can handle either DE or NT duties, but even there depth at DE looks just as thick and may not accommodate Gordon. Besides Tyson Jackson and Glenn Dorsey, the Chiefs have Allen Bailey who looks to provide the team with a better pass rush from the DL, the solidly built veteran Ropati Pitoitua, and Brandon Bair has started to make a little bit of noise on the field. Eight players for the DL seems like a little much, especially if Poe can prove his stamina before the preseason is over and be a three-down player. Powe may have a shot of making the roster, if RAC determines that Dontari can provide DE services consistently enough to go with the anticipated NT services (thereby rendering Gordon as aged and obsolete a’la Kelly Gregg). But as of right now, I expect 7 men to carry over to the 53-man roster with the last spot going to either Bair or Gordon.

4. My fourth and final prediction following Week 1 concerns the WR situation. I can reasonably see 7 WRs making it to the 53-man roster. Bowe, Baldwin, Breaston, McCluster & Wylie are almost sure to be locks with the remaining WRs duking it out for the last two slots. I think Terrence Copper’s proven effectiveness on special teams and his veteran presence might give him an edge for the sixth slot. The real battle will be over the final slot, and I think the top contenders will be Josh Bellamy, Zeke Markhausen and Junior Hemingway. Markhausen has more experience (though ever so slightly) over the other two, Bellamy has been turning heads in practice (though his play was a little lackluster against the Cards), and Pioli and the KC scouts obviously saw something they liked in Hemingway (though injuries have plagued his training thus far). Hemingway’s injuries haven’t just deterred the Chiefs from getting a good read on him, but the other NFL teams likely won’t risk a roster slot on him, plus his upside looks better than Markhausen, so Junior might be a prime candidate for the practice squad. This leaves Bellamy and Markhausen vying for the last slot. Zeke having enough experience to be a little more used to the speed of the game at the NFL level is reassuring; however, Bellamy has created buzz and may not stay around long if relegated to the practice squad. Additionally, Bellamy has a certain kind of experience that no other KC WR has: Bellamy played double duty, as needed, in college as both a WR and a CB. While ultimately going undrafted and getting signed by the Chiefs as a WR, Bellamy may have future stock in being crosstrained for defense. But for the here and now, Bellamy could earn a roster spot for his ST ability as his time playing D in college likely means that his tackling technique is noticeably more refined than his competitions’ at WR in KC. I expect Bellamy to continue to work hard in practice and to earn a spot on this year’s roster.

So there’s my take following Preseason Week 1. What’s your take, Addicts? Sound off…

A favorite pastime for Chiefs fans this offseason has been debating whether or not a Matt Cassel-led Kansas City Chiefs can achieve Super Bowl glory. Abounding arguments eventually degenerate to: you need an elite QB to win a SB, and Matt Cassel is not an elite QB.

Some of the more brazen fans would allude to the possibility that Matt Cassel still might become elite. While there still may be time for him to develop, and it’ll be interesting to see how Tom House’s work with Cassel on his throwing mechanics will translate to the field on game day, the odds of eliteness aren’t too good. However, with all the changes we hope to see, we should be looking at a Top 20 passing offense at the least.

“Big whoop,” I imagine you saying. “In what world does a team with a QB lucky to break the Top 20 have a real chance at a Super Bowl title? Sure, Trent Dilfer and Brad Johnson did it. But two teams in the past 12 years are not the kind of odds to hang your hopes on.”

Methinks you doth protest too much.

I’m not gonna rehash the little factoids such as Rex Grossman getting the Bears to the SB in the 2006 season. Or that just this past season we were poor special teams play away from witnessing two non-elite QBs in the big game. Though go-to favorites, we’re all Addicts here, and those arguments are old hat.

But what if I told you that the ’00 Ravens and ’02 Bucs weren’t the only teams to win a SB in the past dozen years without elite QB-play? That three other teams made it happen in a way our very own Chiefs could well duplicate this year? I present to you the ’01 Patriots, the ’05 Steelers and ’07 Giants.

“Wait just a minute, slappy; Brady, Roethlisberger and Eli Manning are all counted among the elite.” Yeah they are… now. But let’s take off the rose-tinted glasses and go back in time to the years these QBs got their first SB rings… And it’s not nice to call me “slappy”…

The date is Feb. 3, 2002: Rams vs. Patriots. After Drew Bledsoe suffered a serious injury in Week 2 of the season, the Patriots had been left to play a sixth-round pick out of Michigan that only just entered his second year as an NFL pro. He hasn’t done too bad over the season, but, still, the Patriots finished off the season ranking only 22^nd in passing. By comparison, they ranked 13^th in rushing, and their defense 6^th in points allowed. Brady has only posted 2,843 passing yards on the season (a career low in seasons he saw significant playing time), 18 TDs (another career low), and a 2.9 percent INT rate (a career high). Further, the Patriots barely made it through the playoffs, and were fortunate that their divisional round game against the Raiders was officiated by a team of refs that were aware of an obscure rule that kept what could’ve been a fumble merely an incomplete pass, opening up an opportunity for K Adam Vinatieri to make an insanely long kick in terrible weather conditions… the kind of kick Hollywood would glorify, but moviegoers would think to be too highly unlikely, if not impossible, to happen in real life. Following up on that near loss, the Patriots met trouble in the AFC Championship game against the Steelers. Brady went down to injury and Bledsoe came back in and was able to save the day.

So it was a rough road, but the Patriots were able to make it into the Super Bowl. Let’s see how Brady did: completing 16 out of 27 passes (a 59.25% completion rate), Brady had 145 yards passing on the day and one TD (an eight-yd pass to David Patten). Not quite yet the showing of an elite QB. So where did the win come from if not on the back of the QB? I see they rushed for a combined 133 yards, almost matching their passing production (not too shabby). Still, the Pats total combined offense didn’t surpass Kurt Warner’s passing offense (365 yards), and chipping in 92 yards rushing for the Rams just adds to the lopsidedness. Guess the Pats’ defense is owed a lot of credit considering all that production didn’t result in more points. Okay, and Ty Law had a 47-yd INT return for a TD. That would definitely help. And Vinatieri shows up again with 37-yd and 48-yd FGs; the 48-yarder getting the win. Guess we know who’s getting the MVP… Wait! It was Brady?!?! I guess giving the K his due would offend your QBs delicate sensibilities. But what about Ty Law, or someone else on D that shut down the Rams when it was needed the most? “What’s that? Defensive players get the SB MVP with the same frequency they win the Heisman, and Ray Lewis just got MVP in the previous SB?” Okay. Let the history book insinuate that Brady was better than he was that early on; in the meantime, sports photographers will make a killing selling Vinatieri pictures and prints to the New England fans that knew better.

Moving on, let’s examine Roethlisberger and the 2005 Steelers. You know what? This one’s easy. The Steelers finished the season ranked 24^th in passing offense, 5^th in rushing offense and 3^rd in Defensive Points Allowed. They had as many TDs rushing as they did passing (21) and four of those passing TDs weren’t even thrown by Roethlisberger. Big Ben had 2,385 passing yards on the season, and had a pathetic showing in the SB, posting a Passer Rating of 22.6. Seriously. Ben completed 9 of 21 passes for 123 yds in the SB, and 2 INTS. The only Pittsburgh TD reception came on a WR pass from Antwaan Randle-El to Hines Ward. If the 2002 Bucs are proof that a team can win it all with a disgustingly high scoring defense, the 2005 Steelers are proof perfect that a team with a shutdown defense and a top notch running game can win it all.

The 2007 Giants are perhaps the toughest to defend. Eli finished the season with 3,336 passing yards (right around Cassel’s top end). While he did post 23 TD receptions on the year, he led the league in INTs with 20… by no means a good ratio, let alone an “elite” QBs ratio. He also completed only 57.7 percent of his passes (Cassel’s career average is 59 percent). All in all, the Giants passing offense on the season was ranked 21^st, their defense 17^th in points allowed (though 7^th in yards allowed), and 4^th overall in rushing offense with their RBs contributing 15 TDs on the season. So their defense was about average, their running game well above average, and their passing game considerably below average.

What makes a tough point to argue is that Eli put in a significantly better SB performance than either Brady or Ben in their first go-rounds (especially Ben… 22.6 Passer Rating?!?! C’mon!) Eli completed 19 of 34 passes (a 55.9% completion rate) for 255 yds, two TDs and one INT. What shouldn’t be overlooked is the fact that the Patriots were having a perfect season, losing no games and averaging just shy of 37 points per game and despite this, the Giants’ defense really stepped it up and held the Pats to 14 points (including overcoming a near successful game winning drive in the final minute of play).

It should also be remembered that the Giants’ final drive was kept alive by David Tyree knowing enough to break his route and give Eli a target down-field before getting sacked… and also making a miraculous helmet catch that may well define the term “circus catch”. While Eli deserves some credit for staying on his feet; Tyree deserves the bulk of the credit for his situational awareness and making such an unlikely catch.

So, there you have it: three more teams and three more SBs, where the quality of QB play was much less elite and much more Cassel-esque. And while these players may be elite now, their production and circumstances indicate that in these years their teams won, not on the strength of their QB, but on the strength of the team as a whole. Be it a strong defense keeping the score low, a running game that pounded the ball and controlled the clock, or particularly good special teams play, these teams persevered and earned the coveted title.

Overall, our beloved Chiefs have the makings of such a team. Our defense is primed to crack the Top 10, if not the Top five. If Charles and Hillis return to some semblance of their 2010 form, the Chiefs are pretty much guaranteed a Top 5 run game, if not No. 1. And the increased talent and strength of our offensive line should keep the Richard Seymours of the world at bay long enough for Ryan Succop to keep us alive when we need it the most. Everyone wants a playoff win (and it has been a while), and as heartbreaking as it may be to hope for a higher goal and fall short, I see no reason why we can’t win it all this year and bring the Lombardi Trophy to where it would look best: Kansas City. Go Chiefs!!!!!!!!

After the selection of Dontari Poe with the 11th overall pick, Scott Pioli surprised Chiefs Nation further by taking not one, but two more linemen with the next picks, this time on the offensive side of the ball.

It’s hard to surmise which pick was more surprising. Illinois OT Jeff Allen didn’t get much media coverage before the draft, but do you know who did? C Peter Konz and OT Mike Adams, both of whom were still available. “C’MON, PIOLI! Who is this guy?” cried Chiefs Nation. And the internet exploded killing hundreds and severely injuring thousands as Chiefs fans scoured the message boards everywhere lamenting the passing of Konz and Adams, and trying to find out just who Jeff Allen is (true story).

But then Pioli goes and drafts Donald Stephenson in Round 3. Okay; he’s a home boy and was invited to the Chiefs’ local pro day, at least we know who he is. But didn’t most pundits predict him to go in the 5th Round, some as early as round 4 to be fair, but more than that as late as Round 6?!?

With the exception of the pass rushing variety and the automatic-upgrade-to-any-team variety, linemen are not sexy draft picks. They’re just not. Linemen are like most businesses’ support staffs: if they do their job well, they run the risk of going unnoticed and their talents taken for granted, so only when they falter are they guaranteed to get attention. But also like support staffs, their success is vital in keeping things running like a well-oiled machine.

As we learned shortly after the pick, Jeff Allen played throughout his entire college career, starting at RT and making the move to LT shortly thereafter, and earning awards, honors and mentions all along his way. Allen is projected to ultimately supplant Ryan Lilja at LG, a move not uncommon when college players turn pro (just this year the League even saw a veteran make the move when PIT moved Willie Colon, formerly a T, to G for the upcoming season). A move like this tends to be less mentally taxing on a player than you might think. Whereas D-Linemen can succeed well knowing their own individual assignment and trusting their teammates to know theirs, O-Linemen succeed best when they know not just their individual blocking assignment, but also the assignments of the guys beside them… Oh! Also their mirror counterparts at the other end of the line.

Whether you’ve only played football in video games or played physically at some level in your life, you should probably know that when a play is added to the offensive playbook it’s actually added twice: one the way the play was originally drawn up, and the other, the mirror image of that play. Usually something minute in the play call tells the players which way the play’s going. [Ex: Say a run play’s called the “25 Pitch”. The play calling system we’re using might be that the “5” in “25” means the pitch is going to the left. If the play’s called as “26 Pitch”, the “6” would mean it’s going to the right.] When looking at the play in its original and in its reverse, the change in WR routes and/or RB assignments is usually pretty noticeable between the two versions. What might be overlooked, or not even considered without thinking, is that blocking assignments change between the two as well. It’s beneficial to an OL to not just know what they’re doing individually on one version of the play, but also what their mirror counterparts are doing on the other side, because they’ll be expected to do the same when the play’s called in the opposite direction. Bear in mind, this is also while knowing what blocking assignments the man next to you in line will be required to make. Ultimately, the best OLs wind up knowing what everyone’s assignments on the line are, because it’s kind of important.

The real consideration when an OL changes position is whether or not they have the physical tools to make the transition.

Cs can be a little bit smaller than their fellow linemen, as their blocking assignments will often involve assisting a G on a block, picking up a smaller blitzer (read: LB or S) or (in runs up the gut) blocking a LB downfield (also called “on the next level”). Plus, the half a moment it takes to snap the ball is a half a moment during which your teammates have already engaged in their blocks (so making a C’s assignment to be to assist a G on a block or pick up a blitzer makes sense, as these things can wait a half moment).

Gs, working between the C and a T, can have a little less side-to-side foot quickness than, say, Ts, but should count forward moving speed as one of their greatest assets as they’ll be required to, often enough, break from the line on a pull or a trap.

Ts, not necessarily having someone to their outer side (if no TE is lined up), benefit most from side-to-side foot quickness as there’s a whole open field on the outer side of them that they absolutely must be able to defend. I hear that the failure to do this is called “Barry the Bullfighter Syndrome” around these parts.

Well, Chiefs fans, today is Valentine’s Day, and that means only one thing: margaritas.

However, while it might be our tradition to spend every Valentine’s Night at a Mexican restaurant (the tacky-red-paper-hearts-per-person quotient is much lower), I realize everyone approaches this fake holiday in his or her own special way. Even back in third grade—which, frankly, is where the celebration of this day should begin and end—when societal norms and, more specifically, Mrs. Brockmeyer demanded that we give paper valentines to everyone in class, we had to decide which valentines best represented us, as well as which of our secret crushes would receive the more risqué—and risky—messages.*

*Was “You rock, Valentine!” coming on way too strong?

Just as a set of perforated Transformers valentines (“Let’s roll, Valentine! You’re a Mega Friend!”) perfectly represented who I was back in 1984, today’s Kansas City Chiefs fans need valentines that speak to us, that capture the angst and occasional joy of this tumultuous relationship in which we’ve entangled ourselves. And among all the boxes of Harry Potter, Shrek, and Smurfs valentines at the local CVS, I couldn’t find any. So—you can guess what’s coming next—I had no choice but to make a few of my own.

Feel free to print, perforate, and share as you wish. Perhaps—just like the Indianapolis Colts on draft day—you’ll get lucky.

 —————————————————————

—————————————————————

—————————————————————

—————————————————————

—————————————————————

——————————————————————————————————————————

—————————————————————

—————————————————————

So, that happened. Another NFL season (and postseason) has come and gone. Forgive my lack of enthusiasm as I watched the New York Giants win the Super Bowl for the fourth time in my lifetime, and the New England Patriots lose it for the fourth time (to go along with their three championships). In fact, in the 38 Super Bowls I have lived through (not that I really remember Super Bowls IX through, oh, XV or XVI), 27 different teams have participated. Not one of them has been the Kansas City Chiefs—their Super Bowl appearances live in other people’s memories.

But the good news, of course, is that as soon as Tom Brady’s last “Hail Myra” pass landed incomplete in the end zone and Super Bowl XLVI officially came to an end, the Chiefs were immediately back in contention. All eyes, and odds, are now focused on 2012-13, and the earliest probabilities are already in. The MGM Grand Las Vegas and at least one leading gaming site have opened betting season with the Chiefs as 50-1 shots to win Super Bowl XLVII, which is as good or better than 13 other teams. Not quite as favorable as the 40-1 odds they were given a year ago, but much better than the one-in-100 chance set before the Chiefs’ 2010 AFC West Championship season.

In other words, the odds-makers don’t really know what they’re doing, at least at this stage—out of last year’s top five preseason favorites, three didn’t even make the playoffs. But for fans, it’s amusing to see just how favorably (or not) our team’s prospects are marked in the books of various distinguished sports-betting establishments, and ask ourselves, “What if…?”

Last year at this time, I made a list of the XLVI reasons the Chiefs could win it all. A number of those “reasons” are now no longer with the team or else tore up their knees within the first few weeks of the season. So I’ve learned my lesson—and I’m not about to try to come up with XLVII reasons now. After all, so many things can happen: the most important players can get hurt, the coach can go crazy, the GM can go crazier…I mean, what are the odds?

Ah. Good question. Why don’t we find out?

(more…)

“Winning isn’t everything—it’s the only thing.”

This legendary sports quote is most often attributed to legendary coach Vince Lombardi,* but rarely is it reprinted in its entirety: “Winning isn’t everything—it’s the only thing I love more than picking up candy wrappers.”

*Speaking of Green Bay, I didn’t get to see much of the games this past weekend, but I’m looking forward to Sunday. What time is Saints-Packers?

In the history of sports and coaching—particularly the rarified domain of big-time professional sports ownership and leadership—there have always been idiosyncratic personalities. That’s not news, and it’s one of the reasons why Kansas City Star reporter Kent Babb’s examination of “Arrowhead Anxiety” was as credible in its concept as it was dreadful in some of its details.

The sidebar—“Gold, greed lead to murder”—is actually unrelated.

Babb’s story was a solid piece of reporting, based on weeks of investigation and reflection and more than 30 interviews (as it should be—I wish I hadn’t been so pleasantly surprised by its thoroughness). For that alone, it deserved to be on the front page. As to whether it deserved to be the front page—for anyone who hasn’t seen the hard copy, Babb’s story (and its accompanying, menacing graphic) occupy about 80 percent of the broadsheet (right)—or to be the only sports story discussed in Kansas City and to make its way to many other markets, I have mixed feelings.

Actually, not mixed at all—I hate that we’re talking about this, because even though football is the undercurrent and the reason we care, actual football-on-the-field is removed from this discussion. I understand it’s interesting that Chiefs executives may seem more preoccupied with the surreptitious routes their employees take to lunch (so as not to be seen fraternizing with one another) than they are with Dwayne Bowe’s pass routes,* but does that mean we should be? Can’t we all just get back to relishing the end of Tebow Time?**

*I stole that clever route comparison from Nick Wright, who spent about four hours—three-and-a-half hours too many—discussing this on his show yesterday.

**And its return next fall, which, I feel, will ultimately be a good thing for the Chiefs (and all of the Denver Broncos’ opponents).

Yes, I’m writing about it right now, and no, I don’t think I’m hypocritical for doing so. Not wanting to talk about something and believing it can’t be ignored are two different things. I’m adding to the hubbub,* but I hope that by talking it out now, we will all see this story fade away sooner.

*Couldn’t decide whether to go with “hubbub” or “hullabaloo.” Hullabaloo? Yeah, I should have used hullabaloo.

Because I don’t have much at all to add—it’s hard to imagine how anyone could—to the comprehensive scrutiny laid down by Big Matt and Lyle yesterday. I appreciate the points made all around. I agree with most of Matt’s observations and roughly 100 percent of Lyle’s conclusions (and in the comments, it sounds like Matt agrees more than disagrees, too). So before I leave it at that, I will share just a couple of my own, none-too-profound reactions to the article and its allegations…

(more…)

“I want [my players] to be strong, I want them to be tough, I want them to be physical, I want them to be aggressive, I want them to be tenacious….did I forget anything? Smart? Yes, that should’ve been at the forefront.”

—Romeo Crennel, upon accepting the job as head coach of the Kansas City Chiefs
January 9, 2012

Yep, the Kansas City Chiefs and Romeo Crennel made it official. This interim is over, and yesterday they got together to let the world know: They are in love. For now, at least. Even when you’ve started out as friends, any serious relationship takes work—What’s the give and take? How do we want to raise our family? Who will be our starting quarterback?—and this partnership might take more work than most.

The Chiefs, of course, are at a crucial juncture. Some think one small tweak* could lead them to the Super Bowl. But the possibilities are downright Shakespearean. Will we see tragedy, as we did for too many recent years, or comedy—you know, the good Shakespearean kind that always has a happy ending but for some reason isn’t really funny at all? Or just another comedy of errors?

*Peyton Manning?

Crennel has said all the right things publicly—he is here to win a championship and thinks it can happen and soon—but what is he really thinking?

At times when I feel like I don’t have nearly as much as others to add to this ongoing Chiefs conversation in terms of facts, figures, and analysis (these times include the off-season, the pre-season, the post-season, and, occasionally, the regular season), I opt to have some fun and squeeze my ramblings into rhyme or rap or greeting cards or even Mad Libs.

So here we go: In tribute to Romeo Crennel’s namesake* and with apologies to Bill Shakespeare (or whoever really wrote Romeo & Juliet and those other plays that bear his name) and to all of you, I offer our fair Romeo’s first inner monologue as Chiefs head coach—yes, in iambic pentameter (except, you know, when it’s not)…

*Seriously, Crennel is named after Shakespeare’s Romeo. He even has a sister named Juliet.

(more…)

It was a painful Christmas weekend for the Chiefs and their fans. Hope was high when the day began and even later, the best outcome seemed highly possible: everything was falling into place—if only Kansas City could pull out a win at home. But a failed field-goal attempt at the end of regulation meant overtime and ultimately, one big play and a relatively short field goal—and the Chiefs were officially out of the playoffs.

Hard to believe it was 40 years ago.

Wait. What? Which game were you watching?

Yes, one day after the Raiders defeated the Chiefs in overtime, for their fifth straight win at Arrowhead*, I found myself masochistically sitting through another heartbreaking Chiefs loss in overtime. Double overtime.

*The last time that had happened at Arrowhead? It hadn’t.

I’ve written before about my joy in reliving past Chiefs glory that I was not living to enjoy in the first place. On Sunday, I almost too eagerly took the chance to experience some of the pain I wasn’t yet born* to appreciate, either: The NFL Network had cobbled together some never-before-rebroadcast archival footage for an hour-long special commemorating “The Longest Game Ever,” Kansas City’s 1971 division playoff against the Miami Dolphins, which was—spoiler alert!—the longest game ever, lasting well into its second overtime before—double spoiler alert—Kansas City succumbed 27-24 on a Garo Yepremian field goal.

*Though, as I indirectly explained to my daughter, the game plays a role in my being born:

[There is] a story I like to repeat, though I most definitely was not there: On December 25, 1971, [your grandmother] was watching the historic Chiefs-Dolphins divisional playoff, which I’m sure you know is still the longest game in NFL history (that’s why it’s historic!). When the game went into a second overtime, she had to choose whether or not to leave to go on a scheduled date with your grandfather. She went. This started a process—one that, I hope, your own mother will be the one to explain to you in several years—that eventually resulted in me.

In fact, when my father came to pick up my mom, it was the first time he had ever met his future in-laws, who were visiting—and at that moment glued to the TV. They would claim, jokingly—though we were never sure how much so—that they couldn’t remember meeting him that day.

Though it is part of my own family’s lore, I had never known all the little details and dramas of that day—an unseasonably 63-degree Christmas Day, which was seen as an ominous sign against a team from south Florida. The players were somewhat bummed to be playing on Christmas, an NFL first, though Len Dawson reminds viewers that many were just happy to be playing for an extra paycheck in an era when football salaries didn’t always make ends meet (Bobby Bell was working full time for General Motors—being an all-Pro linebacker for the Chiefs was merely his second job).

In the end, it would come down to the kickers. Miami’s Garo Yepremian, who looks not unlike Wallace Shawn as Vizzini in The Princess Bride, was “the smallest man in professional football,” and had spent the previous two years selling his own line of neckties. Jan Stenerud, meanwhile, was “not just a kicker, but also an athlete”—no offense, kickers—who revolutionized the position as the first dominant soccer-style kicker,* and is still the only “pure kicker” voted into the Pro-Football Hall of Fame. In fact, this game featured 15 future Hall-of-Famers (12 on the field, both head coaches, and one beloved owner). Statistically, though, the game belonged to the unlikely Ed Podolak, whose 350 all-purpose yards set an NFL playoff record that still stands.

*Have you seen the straight-ahead style kickers used to use? It’s amazing they ever made a field goal from more than 10 yards away.

However, the game would be most remembered for how the foremost kicker in the league turned into the Lin Elliot of his day, if only for one day. Stenerud missed two field goals, including a potential game-winner near the end of regulation, and had another attempt blocked in overtime. Yepremian also missed, but not twice. Eighty-two minutes and 40 seconds after the game began (according to the game clock), the short, bald former tie-maker unmade this tie with a 37-yard field goal, and the favored Chiefs were out. Inconceivable!

(more…)

I would like to open today’s post with a brief statement. This will just take a moment…

I TOLD YOU SO.

Sure, I’m not usually the type of person to say, “I told you so,” precisely because when I make a rare prediction, it usually turns out not to be so. But six weeks ago today, I posted the following:

The Kansas City Chiefs will beat the Green Bay Packers.

That’s right. You read it here first…

The Chiefs will beat the Packers. How do I know this? The same way I am able to evaluate every other question raised during this up-and-down Chiefs season: I have no idea. But they will. And the Packers may very well be 13-0 by the time they visit Arrowhead on December 18… They may even be resting some starters. In any event, I don’t expect the Chiefs will be playing the spoiler in terms of Green Bay’s cruise back to the playoffs. But at least [the Packers] will leave here feeling rotten.

Perhaps you infer from my giddiness that I did not have the most confidence in my own prediction. Like I said, I don’t often get these things right. Clearly, the Kyle Orton Era in Kansas City has indeed lasted more than one minute, and now the discussion is whether it should and/or will last more than one season.

I won’t say I expected Sunday’s shocker, but I felt it was really possible, a gut feeling loosely supported by historical data. I had been thinking back to the Chiefs’ triumph over the then-reigning-champion Pittsburgh Steelers in 2009—a year in which KC only won three other games—which led me to do a little research. I found that, since 1979, the Chiefs had been 6-2 (now 7-2) at home against defending Super Bowl champs. So there.

But I certainly didn’t predict that by the time this game arrived the Chiefs would have lost their starting quarterback and then ditched their head coach—the two major developments that made the difference in this upset. This changes everything. Or, rather, everything has changed. From the first drive forward on Sunday, this felt like a new team (with the same, but improved defense).

I’ll let others continue the discussion about what these new circumstances on the sidelines and behind center might mean for the Chiefs into 2012 and beyond. For now, I just care about next week and the week after that. That’s right. I’m feeling overly optimistic again.*

*It’s sorta, like, my thing.

So I will double down and offer one more “bold” prediction: The Chiefs will win the AFC West.

(more…)

Now that recent Kansas City Chiefs Head Coach Todd Haley has been “relieved of his duties” (and, presumably, his salary), it’s time to dust off that resume. This is a tough time to be looking for employment, and prospects are especially grim for a man whose primary job skills are his ability and tendency to yell at quarterbacks and NFL officials (honestly, the only place an NFL coach can get hired right now is Coors Light). Fortunately, it seems that Haley has already been busy revising the top part of his resume to reflect his hard-earned experience as a member of the Chiefs organization. Let’s take a look!

(more…)

Many plots unfolded during Sunday’s game between the Kansas City Chiefs and the Chicago Bears at Soldier Field—some comic, some tragic, and it’s not necessarily easy to tell which is which. The Chiefs broke their four-game losing streak and their string of approximately 417* consecutive offensive drives without a touchdown. Quarterback Tyler Palko got his first touchdown pass and his first win as an NFL starter, which officially makes him better than Brodie Croyle. Kansas City kept its slim playoff hopes alive. Todd Haley continued to dress like a middle-school gym teacher.

*Approximately.

And, for anyone who missed it (and if you looked away for even a moment, you might have), recently acquired quarterback Kyle Orton came in for the first play of the second quarter, his first play as a Kansas City Chief, which also turned out to be his last play—of the game, perhaps of the season, and therefore, since he is only signed for the rest of the year, possibly of his entire Chiefs career. Orton had been plucked off of waivers several days earlier to fill in for quarterback Matt Cassel, who is sidelined with a hand injury. So what does Orton do? He gets sidelined with a hand injury. See? Tragic and comic.

Orton may very well return in the weeks to come—he has recovered from just this type of dislocated-finger injury before—but some observers are speculating that the Chiefs may have just paid $2.5 million for one incomplete pass, making that flea flicker “quite possibly the most expensive single play in franchise history.”

And in case this is indeed the end, the only chance Chiefs fans and Kyle Orton will have to know each other, let’s not forget this time we’ve had together. True, we’ve had our ups and downs—or rather, Orton was up, and then he went down. But respect must be paid.

And I really must learn to use iMovie. Don’t worry…the following video is only twice as long as Orton’s total playing time for the Chiefs. So let us pause for just a moment or two (all we’ll need) to relive the Kyle Orton Era in Kansas City…

Note: This post was written immediately following the Chiefs’ 34-3 dismantling by the Patriots on Monday Night Football. But let’s be honest, it could have been written hours earlier.

So, for starters, let’s look at some positives, or at least some not-totally-negatives-in-the-context-of-the-really-big-picture: Last night was not the Chiefs’ worst performance in the history of Monday Night Football. That, of course, was the infamous Monday Night Meltdown at Arrowhead Stadium in 1998, when the Chiefs lost it (the game and their composure) against the Denver Broncos and got flagged for a record 14 personal fouls (or at least that’s how I remember it).

And watching Tyler Palko—besides bringing back stirring memories of the preseason—was not the worst experience I’ve had watching a Chiefs quarterback. That, of course, came during my first-ever game at Arrowhead in the early ‘80s, at which I had the chance to witness Todd Blackledge throw a record 14 interceptions (or at least that’s how I remember it).*

*Yes, I’ve referenced this a time or two before here. I should ask my dad if he can remember the exact date of that game so I can track down the stats; it may indeed have been 14 interceptions.

But—despite the fact that Steve Young would later refer to them as “the Washington Generals”*—the Chiefs did not completely embarrass themselves last night. Before you object, please note my use of the modifier “completely” (come on, I even italicized it). For 20-some minutes, the defense made us proud, and the offense was at least putting itself in a position to make costly mistakes.

*At first, I thought he had said “Washington Sentinels,” making the kind of Palko/Falco reference that only the most brilliant commentators can come up with. But, no, it was just some lame Tom-Brady-and-the-Patriots-are-the-Harlem-Globetrotters joke.

Look, it’s hard to say that the Chiefs, despite allowing more than twice the two- touchdown spread, really failed to meet expectations. There wasn’t a single person, on this staff or on this planet, who thought K.C. had a fighting chance.*

*Or even much of a chance of fighting, like in ’98.

(more…)

“I wish I could say something classy and inspirational, but that just wouldn’t be our style.”

—Shane Falco, The Replacements (2000)

Yes, it’s hard to know what to say right now. It’s been hard to know what to say about these Kansas City Chiefs pretty much since this season or even the preseason started. Last week, we saw the team’s four-game winning streak come to an end and now, apparently, the streak of games-without-season-ending-injuries-to-marquee-players has been halted at six. Of course, it is easy to say how bummed* we all feel on a personal level for quarterback Matt Cassel, who likely will be unable to play football or jazz piano or do needlepoint for the rest of 2011. But how we feel about the prospects of this team with his replacement, Tyler Falco Palko, is harder to articulate.

*”I feel rather bummed for Matt Cassel, on a personal level.” Okay, now you go.

Palko will be making his first NFL start, and it’s a doozy: on Monday Night Football against the New England Patriots. No one is really sure what to expect, not even Palko’s own high-school coach, who also happens to be his father: “What are you going to do? I just hope I don’t lose my dinner,” Bob Palko told the Pittsburgh Tribue-Review, when asked about watching his son lead the charge into Foxborough.

So a big part of the storyline—”Cassel Returns to New England”—that likely helped land the Chiefs on national TV for this game in the first place is now gone, but it is being replaced with an equally compelling narrative: The Chance.

(more…)

We knew the Denver Broncos would come out running the football but I don’t think anyone would anticipated them running it as much as they did.

The Broncos had well over 200 yards rushing vs. the Chiefs defense. Despite knowing it was coming, the Chiefs could not stop Denver.

To illustrate just how bad this game was for the Chiefs, Tim Tebow had only one pass completion midway through the 4th quarter before Tim Tebow hit Eric Decker on a 56-yard touchdown bomb in which Decker burned both Brandon Flowers and Reshard Langford.

On the other side of the ball, the Chiefs offense was its usual inconsistent, unproductive self. Drivers were hard to come by as were yards. None of the Kansas City receivers made an impact and every time the Chiefs did do something right, it seemed they wiped it out with a stupid penalty. On one play, rookie WR Jonathan Baldwin made probably the greatest catch you will ever see only to have it wiped away.

At this point, it is time to consider that the Chiefs are just as bad as we thought they were earlier in the season. They had a few decent games, but it seems they just don’t have what it takes to compete in 2011.

We’ll be breaking down the game on the Arrowhead Addict Post Game Show on AA Radio. Join AA’s senior editor Patrick Allen and senior staff writer Big Matt at 3:30 central and listen as they break down what went wrong and where the Chiefs go from here.

Apparently, the Chiefs don’t do so well against AFC East opponents at home in 2011. That is one thing we did learn this weekend. Not only did the winless Miami Dolphins’ streak of, you know, being winless come to an emphatic end with a 31-3 exorcism at Arrowhead, but a couple of other streaks fizzled out on Sunday, too, starting with K.C.’s own recent undefeated stretch. So it looks like there will be no unprecedented 13-3 season after an 0-3 start, no 16-game run to a Super Bowl title. Oh well.

Perhaps, too, this marks the conclusion of Head Coach Todd Haley’s days as a bedraggled, unwashed sideline hobo. “I want to take my hat off to Miami,” he said after the game, effectively announcing an end to the streak in which he has worn the same streaked cap since the autumnal equinox.

But what’s weird, or not so weird, is that—other than dropping the Chiefs back to 4-4 for the first half of the season (and, hey, who saw even that as a strong possibility back in mid-September?)—the unfortunate events of November 6, 2011, tell us almost nothing about what is coming next for this team in the second half of the season.

Will these Chiefs beat the Denver Broncos at home this Sunday? I have no idea. Probably? Maybe not?

Will these Chiefs win the AFC West? I have no idea. Maybe? Probably not? It is possible. Of course it’s possible. They are currently in a three-way tie for first, and as rough as their second half looks, the road facing each of their divisional compatriots looks just as tough. This team could still end up 6-10 or 8-8 or even 9-7, but which nine? Which seven?

So, at the midway point, I might as well make one semi-bold prediction:

The Kansas City Chiefs will beat the Green Bay Packers.

That’s right. You read it here first. Unless, of course, you’d already read it somewhere else, and that’s okay, too.

(more…)

Monday nights are usually when I sit down, reflect on what the Kansas City Chiefs did or didn’t do over the weekend just past, and pull something out of my ass together for my Tuesday post. But on this particular Monday night, it so happens I was a bit distracted by something rather compelling that I was watching on television. I only had time to jot down some observations during breaks in the action as it unfolded. So consider these my Quick Slants. Some of them are even football-related…

• Hey, nice graveyard rendition of Danse Macabre by the Philharmonia of Greater Kansas City during the MNF intro (my friend Kristin was the Zombie bassist on the left).
• Not a big fan of all those not-so-terrible white towels. The idea was lame enough at Busch Stadium during the World Series and it’s no more impressive at Arrowhead. What? Is everyone surrendering? Or just waving their tighty-whities in the air? Hard to tell.
• Is that a five-inch Herm Edwards screaming at a couple of clueless tools to “ice down those Coors Lights, baby?” Finally—a coaching job worthy of Herm’s stature.
• Lamest Halloween costume seen in the crowd: Zach Galifianakis’s “Alan” with beard, sunglasses, and strap-on baby (with sunglasses) from The Hangover. Soooo 2009. (And there’s no good reason to remind Chiefs fans of 2009.)
• Did I hear that right about Chiefs center Casey Wiegmann? 10,502 snaps in a row? I wonder if that statistic about a routine, seemingly mundane element of the game will take on more significance later…
• Newest addition to Todd Haley’s nasty-as-he-wants-to-be ensemble: Navy undershirt with some kind of emblem that resembles either a grease stain or maybe a patch of sweat.

(more…)

“This, then, is the mark of the man, the beard. By this, he is seen to be a man. It is older than Eve. It is the token of the superior nature… It is therefore unholy to desecrate the symbol of manhood, hairiness.”

— St. Clement of Alexandria, circa 180

After the Kansas City Chiefs came back from 17 down to notch their first-ever win in Indianapolis two weeks ago, Head Coach Todd Haley declared to the world (or, at least, to a glaringly lit room full of sports reporters) that he would ne’er desecrate his symbol of manhood so long as his team continued to reap victories on the football field. “As long as we’re winnin’, I’m not shavin’,” he said of his decision, supposedly made during the game in San Diego.

I’ll be honest—I didn’t really believe Haley at the time; it seemed like this could be another one of his, you know, jokes.* But when he emerged before Sunday’s game against the Raiders, it was clear: the man ain’t shavin’. Nor, it would appear, is he bathing, at least not effectively, or changing or washing his nasty off-red cap and hooded velvet man-blouse, which over the last few weeks has turned from a dark gray to a splotchy black.

*Like the one time two times he put Jamaal Charles behind Thomas Jones on the depth chart. That was hilarious!

But the accoutrements of genius will always look like signs of madness to the unqualified eye, just as credit and blame are often a function of who’s doing the assigning. In the last several days, some of Haley’s decisions over the past couple of years—such as who to bench, and when—have inspired a few rounds of the passionate, highly confrontational, and only vaguely mean-spirited debate that the devotees of this site can take pride in. But aside from the effect of Haley’s direct interventions in the playing time of LJ, DJ, and JC, for example, let’s look at the coach’s repertoire of general-purpose motivational devices:

• Dividing the season into “manageable” quarters
• Liberal use of obscenities
• Yelling at players
• Starting sideline fights with quarterback, receivers, and/or others as needed
• Turning routine post-game handshakes into newsworthy morsels for the media
• Introducing bean-bag games—the kind normally played by senior citizens or drunken tailgaters*—into the locker room

And now…

• Not shaving, bathing, or doing laundry

*Or drunken senior citizens, who may or may not be tailgating

(more…)

As any respectable quantum astrophysicist will tell you, a black hole is an object with sufficient density that the force of gravity prevents anything from drifting beyond it; its defining feature is the appearance of an event horizon—a boundary in space-time through which matter and light can only pass inward towards the mass of the black hole. Nothing, not even light, can escape. (I, of course, did not learn this from any quantum astrophysicist. I cut-and-pasted it from Wikipedia.)

The Black Hole also happens to be the first movie I can remember that both enthralled and terrified me (according to Wikipedia, it came out in theaters when I was only five years old*). I have no recollection whatsoever as to what the movie was about,** but I remember being very frightened by the violent, faceless drones and morbidly fascinated by the concept that there was a place somewhere out there that could swallow everything that got near it. It gave me nightmares. I still can’t believe that this was a Disney movie.***

*Not that Wikipedia necessarily knows how old I am or when I was born…though, yeah, probably.

**If you have three minutes and twenty-nine seconds to kill, watch this trailer and tell me if you have any clue in hell as to what this movie is about either.

***Though come to think of it, two other traumatic moments of my early childhood involved seeing Bambi’s mother get shot and watching Dumbo get taunted mercilessly because he was different. WTF, Disney?

I mention all this because a black hole—and you probably realize that I am now referring to that Black Hole—is precisely what this Chiefs team and its fans need right now: an inescapable force to pull us in and push us forward into a situation both fascinating and infuriating (like this guy).

(more…)

I’m not much of an NBA fan*, so upon hearing the latest news of that league’s lockout—Commissioner David Stern has cancelled the first two weeks of the NBA season—all I could think was this: Ah, if only those first two weeks of the NFL season had never happened! The Chiefs would now be 2-1, the only blemish a loss at San Diego (expected) by the score of 20-17 (quite closer than expected). The team would still have a healthy Eric Berry and Jamaal Charles (assuming they wouldn’t have been injured in Weeks Three, Four, or Five). And Todd Haley would probably not be desperate enough to pledge to go unshaven (and to continue wearing velour hoodies and dirty sweat pants) so long as the Chiefs keep winning.

*I don’t know—watching monster-sized millionaires smash into each other on a football field doesn’t seem nearly as ridiculous as watching full-grown multi-millionaires scurry around in shorts on a squeaky court.

It’s so hard to analyze this team right now. The Chiefs seem both better and worse than their 2-3 record. Over the course of five weeks, they have laid down and died, and then fought back when it made no sense for them to have any fight left. And hindsight, as it does, has changed the context, too. While there’s no excuse for the embarrassments of the first two weeks, the two L’s on the schedule—against the only team New England hasn’t been able to beat this year and a team no one has been able to beat—aren’t looking as bad. The two wins, meanwhile, came against teams that were winless at the time, but both were real victories, requiring comebacks and last stands.

So the team may not be hopeless, but still doesn’t inspire much hope. Plus, even the “Suck for Luck” dream is dead, as the Chiefs are now in line behind or alongside 10 other teams—including the Eagles and Falcons!—for that first draft pick. As Lyle put it plainly in his post yesterday, “the odds of the Chiefs getting the #1 overall pick are about as likely as the Chiefs winning the division at this point.” And that, frankly, is depressing. This team seems destined for mediocrity of the mediocre kind: Four wins? Five wins? Maybe six? The Chiefs still don’t have an identity and it’s hard to imagine exactly what identity will emerge. I can see this team losing to Denver and then beating the Patriots or Packers. I really can.

So…it’s probably just as well that we are heading into the bye week, that curious once-a-year (per team) phenomenon that the NFL introduced in 1990 (according to Wikipedia), in order to extend the season by a week and “provide time for teams to rest” (according to nflbyeweek.com*). Perhaps we should all take a rest, too, some time to clear our heads and clear the slate.

*Yes, that’s real: there is an entire web site—one page—dedicated solely to a listing of NFL teams’ byes by week. It is brought to you by the same people who created whatdayoftheweekisitwhereyoulive.org and clickheretoseeawebpage.net.

(more…)

For the past two days, much has been made* of the second-quarter sideline exchange/argument/tiff/spat/discussion/hissy/fight between the Kansas City Chiefs’ once-Pro-Bowl quarterback and their once-Coach-of-the-Year runner-up. With about five minutes left in the half and the Chiefs trailing the also-winless Minnesota Vikings 7-3, Matt Cassel appeared to quickly bail out on a broken screen play. And Todd Haley appeared nonplussed about it, a sentiment he then appeared to share with his quarterback as the TV cameras zoomed in.

*When has this not been the case? We spend all day, every day, thinking, talking, and writing about what happens during three hours of game action once a week. Making much is what we do.

This fifteen seconds of infamy has been posted, reposted, played, and replayed dozens of times on the blogosphere since Sunday, without any real revelation as to what exactly took place.* All that we know—or so we’ve been told by others who are also making much of this—is that it seems like Cassel and the Chiefs were different, much more fired-up, after this one outburst of emotion. And they put together enough of a second-half effort to get their first win in 2011 (the year, not just the season).

*However, this clip does reveal a couple of interesting developments on the fashion front: First, Cassel manages to get his sideline hat onto his head properly in one single, swift motion. Considering recent history, a good sign! Also, after swinging way too far towards the lying-around-the-house-in-the-wife’s-old-sweatshirt-on-laundry-day look two weeks ago and rebounding hard with a comfortable-yet-commanding dark fleece in San Diego, Haley seems to be splitting the difference now, with a gray-sweatsuit-and-dingy-old-hat ensemble that looks more like what you might wear working in the yard while listening to the game. We may need to start a Haley Style Watch to keep him in line.     

Cassel himself would later thank his coach for the “open dialogue.” But what was really said? It’s not very easy to read lips, but here are a couple possible snippets…

(more…)

There was a moment during Sunday’s game in San Diego—well, there were several, but this one in particular will make the point—when nothing else about the Kansas City Chiefs’ woeful 2011 season mattered: With a minute-and-a-half left, the Chiefs had just tightened the score to 20-17, and the Chargers—having just failed to convert a third-and-eight—decided to go for it on fourth-and-inches, on what they hoped would be the last meaningful play of the game. But San Diego and Philip Rivers forgot the whole “sneaky” part essential to a successful quarterback sneak. The Chiefs saw it coming from a mile (actually, inches) away, and even an overly generous spot and the fickle imprecision of an official chain measurement couldn’t deny them a huge stop.

The Chiefs, only down by three, now had the ball, the momentum, decent field position, and—thanks in part to the fact that Rivers hadn’t run nearly as many seconds off the clock as he could have*—plenty of time with which to work. A quick 23-yard pass to Leonard Pope into San Diego territory underlined just what was happening here: the Chiefs weren’t struggling to set up a tie game and overtime, they were driving toward their first win of the season.

*No, there weren’t any well-coached teams out there this day.

But the fact that it would be their first win was—in the moment—completely irrelevant to me. There was no context outside of the scoreboard and the game clock. It didn’t matter that even three points might still be a tall order for a team that in three games so far had been outscored 109-27. It didn’t matter that the Chiefs were going to have to finish this drive without Jamaal Charles or Tony Moeaki. It didn’t matter that last year, with those players, on this same field, the soon-to-be-playoff-bound Chiefs had been wholly embarrassed 31-0 (albeit with Brodie Croyle filling in for Matt Cassel). It didn’t matter either that this year, until the last few possessions, Cassel had looked shakier than Croyle at his worst.

So what? The same pieces of this puzzle that had completely fallen apart on us the first two weeks appeared to be coming together. Even the same blank sideline expression of head coach Todd Haley (overcompensating for last week’s strawberry/melon-colored velour hooded blouse with a slightly more bad-ass black windbreaker) now seemed less clueless and more confidence-inspiring. Despite everything—again, because nothing else mattered—it looked likely that the Chiefs could beat the Chargers, in very dramatic fashion, and announce themselves as the champions of this game on this day. This was the Super Bowl.

This moment, this dose of adrenaline, was precisely the kind of fix that had lead to our addiction in the first place. The reason we are Chiefs fans, and stay Chiefs fans, is for the ever-present anticipation of the next one of these moments. As I’ve tried to deal with the opening debacles of this season, I’ve pointed out that I (merely) expect to be entertained. On Sunday, the Chiefs fulfilled that expectation. Even their last play on offense—as stultifying a way to lose a game as Cassel’s interception was—was still another moment: it felt good to be angry, to care.

(more…)

Chiefs Only Two Back In Race For AFC’s Top Seed

Chiefs Will Need To Settle For 14-2 Season

Chiefs Unbeaten Against Division In 2011

Clark Hunt Celebrates Another Year Of Record Profits

No, this is not going to be another Pollyanna-ish pep talk. To quote the guy who was proofreading the alphabet and noticed something missing between E and G: “F that.”

The point (if there’s a point) is that there really is no way to put a positive spin on what’s happening. The sad fact is that essentially all of us will admit there’s no way we’ll see any of those headlines a month or even a week from now (except, of course, for that last one). And there’s really no way to make sense,* or for that matter, fun, of all this, either.

*Be warned, this post will have a lot of asterisks and even double asterisks,** if only to fill space where there is no coherent line of reasoning.

**See?

There is no comedy here, unless it’s a Divine Comedy: The lockout was the first level of hell* and it has descended from there to the preseason and down with each regular-season game, and each new torn ACL. To paraphrase Mel Brooks, “Tragedy is when Jamaal Charles cuts his finger; comedy is when the Detroit Lions walk into an open sewer and die.” (Not exactly sure how or whether that applies, but I gotta fill this post with words, people.)

*Or if you insist on being an I-told-you-so realist, it probably started with the final regular-season game last year against the Raiders, followed by the Wild Card blowout…

Like all of you, I’ve got my computer desktop set with the official, AA-endorsed wallpaper. What a brilliant, visual reminder that the season hasn’t even really begun. And yet, it still feels all but over. (more…)

So this is how my glorious NFL opening weekend ends: Sitting here in the waning moments of Monday, rooting for the Raiders to beat the Broncos so that I can finish near the top of my pick ‘em pool—but hoping they do so without too much help from Darren McFadden, lest my fantasy-league opponent come from behind in the final game. The Chiefs? Oh, right, that’s what this weekend was originally supposed to be about…

What is there to say, really? What occurred Sunday afternoon at Arrowhead was worse than the lockout, worse than the horrible preseason—unless, as I daydreamed at times during the game, this still was the preseason. How else to explain the lack of competition and emotion, the stadium that emptied in the third quarter, and all those Chiefs on the field who probably don’t deserve to make the team? All we could hope for was that none of our top starters would get hurt.

Well, shit.

(more…)

As of the time of this post, the kick off of the Kansas City Chiefs’ 2011 season is a mere 120 hours away. It had been my intention, in a final effort at unbridled optimism before the first game starts, to put together the ultimate Season-Opening Pep Talk. Instead, since we’re all in this together, from the highs of last season to the lows of the lockout to whatever the hell you might call this preseason, I decided it would be better if we all write our own.

But to help, I composed this quick-n-easy Mad Lib. For anyone who doesn’t remember how this works, it’s pretty simple: Just fill in the first word that comes to mind after each prompt on the list, and then match it to the corresponding space(s) in the form that follows. If it all works out, you should have yourself a perfectly uplifting speech* to rally your spirits for Sunday!

*Special thanks to The Sports Cliché List for help in structuring a more authentically stereotypical pep talk.

(more…)

Well, Chiefs fans, the bad news is that it’s still the preseason. The good news: The preseason is almost over. And that means that this, thankfully, is my last preseason post.* And since, try as I might, I’m just not able to follow through on this one idea I had of reimagining the Chiefs coaching staff as the cast of Entourage (which is what’s currently playing on the DVR), I guess I’ll have to fall back on my default optimism.

*In a way, I’d like to think of these August posts as my own preseason performances. After a long lockout that saw me resorting to, among other things, visualizing the Best Picture nominees as NFL Films, comparing Steve DeBerg to Abraham Lincoln’s first-term Vice President, extolling the virtues of soccer, and exploiting my infant daughter, I reserve the right to seem rusty now that I am back to writing about what, just for the sake of argument, I will call “actual” football games. But, much like our dear Chiefs, I promise to get my groove back by Week One.

So, putting aside the fact that I could not care less about the outcome of these preseason games—or for that matter, really, the performances, so long as no one gets hurt—could the Chiefs be showing us a little more right now? Of course. Are there reasons to be disappointed by what appear to be some severe shortcomings and a lack of cohesion in game situations? Uh…yeah. But should we be worried? I think you know my answer to that, but I’ll spell it out for you anyway: It starts with “H” and ends with “ell no!”

(more…)

 “As I’ve conveyed over the last three years, everything that happens within these walls is family business.”

— Coach Todd Haley, “responding” to questions about Friday’s alleged
Thomas Jones-Jonathan Baldwin locker-room bout

“I thought I did address it…I addressed it as family business…I’m sorry if you didn’t think that.”

— Haley, when asked about it again three days later

Well, there you have it, Chiefs fans. Just in case you didn’t already realize you weren’t truly part of this “family,”* there are apparently certain things that only “family” gets to talk about—and that doesn’t include you.

*Hey, remember that whole months-long argument over how to divide the “family” finances? And remember how you weren’t allowed to say anything, even though you’ve anted up a chunk of your allowance for who-knows-how-many years?

Yes, the Pioli Administration has always been notorious for its stonewalling, and its newspeak has been well-documented and well-dissected on this site. But am I the only one who feels this “family business” business has taken it up a notch—and, frankly, is just a little creepy?*

(more…)

Last week, I finally sat down to undertake what has become an annual (and particularly anal) preseason ritual: entering all of the Chiefs’ regular-season games into the old Google calendar. Usually, this happens much earlier in the summer, but this year there was that whole lockout thing, and I don’t like putting things on the calendar that are technically still tentative. And no, I don’t actually rely on Google to remind me when there’s a Chiefs game about to start—it’s not like I have ever found myself, say, alphabetizing my Garbage Pail Kids collection at noon on a fall Sunday and been struck with a sensation that there was something else I was supposed to be doing. I just like seeing that sacred time blocked out on the calendar (and color-coded red, of course).

When I was done, I got up, left the computer…and then realized that I hadn’t marked off the times and dates of the preseason games. I thought about it for a second, and this is what I thought: “F(orget) that.” And just like that, my boycott began. I didn’t watch Friday night’s mess* and I have only a vague notion of when the next one is (and will, probably until I read about it on this site).

*Not at the time, at least—more on that in a bit.

(more…)

WARNING: This post ends with a bad rap parody.

It’s hard to believe, maybe, that this week marks the four-year anniversary of the debut of HBO’s Hard Knocks: Training Camp with the Kansas City Chiefs. In fact, to celebrate,* the NFL Network broadcast a HK:TCWTKCC marathon yesterday. For one day, it was August 2007 all over again, and the whole gang was there: Herm Edwards, of course, and Gunther “%&#^@!” Cunningham, along with the stars of the show: Turk and Tank. Boomer Grigsby. The Croyles (mostly Kelli). And poor, poor Bobby Sippio.

*”To celebrate” is one way to put it. “To kill six dead hours in the middle of a Monday” is another.

It can also be hard to remember that, at the time, things didn’t look so bad. There was hope. We were coming off a 2006 season in which the Chiefs—though some of you, I’m sure, got “this thing twisted and think we backed into this deal”—were a playoff team, with an All-Pro running back that had just lead the league in carries and finished second in yards. Meanwhile, All-World tight end Tony Gonzalez had been signed to a five-year extension. And now, HBO was reviving its acclaimed NFL training-camp reality series and wanted to feature the Chiefs and only the Chiefs—and had been spending the whole summer hyping it.

No, we didn’t know at that moment just how hard we would all be knocked over the next three years. As late as that Halloween, it still seemed like we would continue to have something to root for. First, there were those 24 unanswered second-half points in San Diego to erase a double-digit halftime deficit. Then, in a very sloppy game in Oakland, the Chiefs outlasted the Raiders to prevail 12-10, securing a 4-3 record and, heading into their bye week, first place in the AFC West. That was October 21, 2007.

The Chiefs would not win again until September 28, 2008. They would lose 12 games in a row and 28 of their next 30, getting outscored 808-499 during that stretch—though the close, late-game losses would be the most pathetic and painful.

(You know, just in case you didn’t remember all that.)

But the point is that now, four years later, though we may whine and moan about our young Chiefs’ growing pains, we also have much to cheer. Which means it’s time for another parody.

So with all apologies* to Jaz-Z for hijacking his original (and to Charles Strouse and Martin Charnin, who co-wrote the original original), please enjoy, if possible. Just don’t ask me to perform it for you.

(more…)

In the history of the hated—from Al Davis to John Elway to Philip Rivers and everyone in between—the name Brandon Siler doesn’t exactly make the blood boil. Still, when it was announced that the linebacker, who had spent his entire four-year career with the San Diego Chargers, would be the newest Brandon on Kansas City’s defense, it was another small victory, and not only because Siler will hopefully fill a real need for the Chiefs. Our gain is a little sweeter when it’s also a rival’s loss.

Brandon Siler, being interviewed while changing out of his Chargers rags and into his new Chiefs uniform.

And that got me thinking about those times in recent Chiefs history when we’ve had the chance to see an old rival reborn in red and gold—and even wash away his sins with a game-changing or dominating performance against his old team. Even something as relatively mundane as a well-executed third-down conversion or defensive stop for short gain has an added ounce of gratification. There’s that feeling of “Yeah, that’s right—he’s with us now.”

So, in no particular order, here are a few of the notable former AFC West adversaries who saw the light (or were traded, or discarded by the forces of darkness and picked up as a steal in free agency, etc.) and used their football force for good.

(more…)

Click on the banners to take you to the full article

By all accounts the deal is about done, and it seems to be something both sides can agree on.  I’m no lawyer, to pour over the minutiae and say who got the better of it.  I’m hopelessly biased against the owners in any case.  But, I mean, shouldn’t it be a given that you’re going to unanimously approve a plan you wrote?  I would guess all the disagreement pretty much gets weeded out during authorship, right?  Was a “we did it!” press conference before the players had even seen the proposal really necessary?

But that said, I am going to look at this lockout, after the fact, as a small blessing. Besides leaving the league and its players (and definitely its owners) in a better state for having hashed out their differences—and I really do believe that—it has given me a new appreciation that I didn’t think I’d allow myself to feel. It isn’t all just going to be ponies and gum drops and rainbows and chicken spiedini from here on. Some very bitter and lingering truths about the owners and the players (but mostly the owners) came to light, and as ticket prices and team profits continue to rise, much of the same fan frustration will remain.

Ladner, Merlin, and Randy after the jump:

(more…)

As Kansas City Chiefs fans, today is the first day of the rest of our lives.

While the NFL labor mess ultimately melted away as so many of us have been expecting it eventually would, this still feels like a new beginning. After all, a time when football’s future wasn’t endangered by the players and owners’ bickering was becoming difficult to remember. Before the lockout finally came to an end yesterday, it had persisted for 143 days. The entire 2010 NFL season—post-season and Super Bowl included—lasted 147. Soon enough, hopefully, this will all feel like a cruel joke.

But so what? Let’s schedule a group therapy session in a few months and see how we feel then. Right now, it’s time to focus on the present (and near future).

Speaking of focus, I’ll be honest—before joining AA early last year (around Halloween, whatever that might imply), I had been a diehard during-the-season Chiefs fan, and remained interested but much less obsessed in the months when there were no games. Fall and winter Sundays were sacrosanct and I would feed on pre-game hype all week long. But if I wasn’t the first person in the world to know about a summer free-agent signing, it didn’t exactly ruin my day.

All of that changed this February, when it was made clear to me by Dear Leader that while the NFL’s work was done for the season (or longer), mine here was not. Coming up with something new to write about the Chiefs every week* during a normal NFL off-season is insane enough, but during this off-off-season? For so long, it felt almost a little disingenuous, as if there was an unwritten caveat to every conversation-starter: “How tough is the Chiefs’ 2011 schedule (you know…assuming they wind up playing it)?” “Which free agents should KC go after (you know…if they ever get the chance to go after free agents)?” “Just how big of a jackass will Clark Hunt prove himself to be (you know…if…well—pretty big, actually)?”

*What ever would possess someone to do it every day, I cannot possibly understand—it’s Arrowhead Addict, not Arrowhead Nutjob—but I’m glad such a person exists.

(more…)

On Monday, I tried one last time to sell everyone on the idea of signing Aubrayo Franklin. Nick broke down the Calm Before The Storm for us and our head man Patrick Allen even combined the Chiefs universe with the magical world of Harry Potter. Jeremy had a good piece up about the Battle At Fullback this season and Andrew gave us his list of the Top Players Under The Age Of 27. The newest member of the AA family Chris Matthews rolled out his latest episode of his animated series One Arrowhead Drive, if you haven’t seen it yet definately take the time to check it out.

I would also like to take a moment to throw a shout out to AA’s resident artist, Tony Rangel, who’s work you are now seeing for most of the feature posts. I won’t speak for all of the writers, but I really love my Armchair Addict logo and think his work really gives the sight a great look. In case you haven’t been paying attention, I included a couple below just to refresh your memory. Thanks again for the great work Tony!

Well Addicts have a great rest of your weekend and let’s hope its the last weekend of this lockout.

Just Get The Deal Done Already!!!!!!!!!!!!!!!!!!!!!!

Well Addicts this post is hitting a little bit late, sorry about that. I do however want to make sure you have links to another great week of posts from the staff here at AA. This labor stoppage is driving us all crazy so until they finally get the stupid thing done you can pass the time with these great write ups from our features writers.

On Monday our man Big Matt tried to deal with the news of Mike Vrabel’s retirement (it was pretty hard on him). On Tuesday Victor gave us the best piece of the week when he introduced us to the world’s newest Chiefs fan (congrats Victor). Next up was Ladner with his piece that explained the “set up” Godfather style. Thursday is was Merlin who discussed Bob Gretz’s list of the greatest Chiefs of all time. Finally, earlier today Randy gave us a preseason wrap up to get us ready for the first preseason game that now looks like it should actually happen.

Another good week here at AA, so make sure you check out anything you might have missed.

July 12, 2011

Dear Vivien,

I am writing you this letter—okay, so it’s a blog post for my regularly scheduled slot*—with the hope that long before you are able to read and understand this, and optimistically within a matter of days from now, the NFL owners and players will have resolved their silly little labor dispute (no, I cannot explain that to you now—we are still busy trying to explain it to each other) and you will grow up in a world flush with Kansas City Chiefs football, as did your father and those before him.

*Daddy likes to multi-task. So sue him.**

**Not literally. This is just an expression. You’ll learn.

As your father, I see it as my responsibility to ensure that you grow up to know the wonderful joy, occasional disillusion, and ultimate, satisfying bond of being a Chiefs fan. It is, of course, only one of my many important jobs as your dad—which, as you must know, also includes (though it’s never intentional!) embarrassing you thoroughly, beginning with this letter. Sorry, kid—I think I may have seen that Google “Dear Sophie” ad one time too many.

Vivien Jeanette Wishna, born June 20. (Same birthday as Len Dawson.)

First of all, I want to commend you on how far you’ve already come in just three weeks: you eat constantly, burp and fart at will, and don’t even bother to get up when nature calls.* And you complain loudly the moment things don’t go your way. In short, you are well on your way to becoming a real American—and more specifically, a real American football fan.

*Embarrassed yet?

But Vivi, I think you’re really going to love being a Chiefs fan. There is much fun to be had and many thrilling moments to be shared, at home, at Arrowhead, or anywhere. I should warn you, though, that it isn’t always going to be easy. Once you’ve mastered certain mysteries in your young life—walking, talking, algebra, etc.—you will still inevitably have to contend with the inexplicable: A draw play called on third down? An all-time-great running back sitting on the bench? Holding? Holding!?! YOU CALL THAT HOLDING?!?!?

But perhaps, as I really hope, you’ll look back on this era of Chiefs history—with its grainy, “3-D high-definition” video (soooo 2011!)—as the time the team started its return to glory.

(more…)

It's Friday night and I hope you're partying like D-Bowe pre-Haley!

Hello KC Chiefs fans! It’s Friday night and if your Friday night is a little less “D-Bowe” and a little more like the bald dude behind him in the picture above you might need a little something to pass the time. What better then catching up with all the great AA features you might have missed this week. Despite the football blackhole that the lockout has created your staff here at AA just keeps cranking out the goods. So if you missed anything here’s your chance to get caught up.

On Monday, our man Big Matt got things started by telling us all “What Matt Want” when it comes to the trio of Todd Haley, Scott Pioli, and Clark Hunt. On Tuesday, it was Victor’s turn and he’s thinking KC may be becoming a “Futball Town“, which in my opinion would qualify for our head man Patrick Allen’s list of 100 things scarier then no football. Speaking of which, #29-20 hit the site this week and is a must read. The humor kept on coming with Ladner Morse’s piece on where some big names might be if there “Were No NFL“. Finally, earlier today Randy gave us a good piece on the “Control” Todd Haley has on his team.

So what’s on your mind Addicts? Anything from the pieces above still weighing on your mind? Anything exciting happen this week? I spent the week at a cabin just off a lake in Oklahoma (the kind of cabin with AC and a hot tub), so clearly it was a pretty taxing week for me with all the hiking, boating, and cooking out. Feel free to use the comments for this post to share just about anything.

Tonight, Chiefs fans, for the second week in a row, there will be big-league, professional football* played in Kansas City—in a glittering, filled-to-capacity stadium—and broadcast live on national television.

*Or, of course, as it’s called in this country, “soccer”—which makes a hell of a lot more sense. I mean, have you seen a soccer ball? It’s round! It doesn’t look anything like a foot!

Last Thursday was a monumental day for the other football team founded by our beloved Lamar Hunt. Sporting KC—the team formerly known as the Wizards, who were originally nicknamed, in a fit of either marketing brilliance or complete cluelessness, the Wiz—christened their brand-spankin’-new stadium, Livestrong Sporting Park, named for the foundation of the much admired cyclist, cancer-survivor, and alleged illegal doper Lance Armstrong. With ESPN2’s cameras focused in, SKC battled the Chicago Fire—a team named for one of the largest and most deadly disasters in U.S. history—to a decidedly indecisive scoreless tie, or what my father would call “a close game.”*

*Throughout my childhood, my father—who simply was not as avid a fan as my mother or me—would walk in on us riveted to the last thrilling seconds of a nearly tied football or college basketball game and invariably say the same thing: “Huh. Close game!”

It ain't Arrowhead. But right now, neither is Arrowhead.

Now, tonight, the U.S. men’s national team is in town to take on Guadeloupe, which as it turns out, is in fact a tiny island nation in the Lesser Antilles with a population one-fifth that of the KC metro area, and not, as I had thought, just some guy named Guadeloupe. This is a crucial match for the U.S., which is hoping to stay alive in its quest for the Gold Cup of the Confederation of North, Central American and Caribbean Association Football, or CONCACAF—an acronym that is actually longer than the word “acronym.”

Based solely on what you’ll see here on local front pages, TV news, and billboards, it would be hard to deny that Kansas City is—at least for this week and/or until the NFL owners and players settle their dispute or Clark Hunt announces he is giving all of his employees raises and adopting a gaggle of orphans and/or a litter of really cute, abandoned puppies to show what a good guy he is—a fútbol town.*

*Or, if you prefer, a “soccer city.”

So here’s a quick refresher on just some of the subtle differences between our football, the game of inches, and soccer, the game of feet. Yes, it’s been done before, but so has “Here’s Why The NFL Lockout Still Stinks.” Let me have my fun.

(more…)

Well, Chiefs fans, we are now just three months away from the start of the 2011 NFL season. Unless, of course, we’re not.

As the owners and players await their fate in court and seem no closer to sitting down to talk, we start to face the real possibility that this little tiff may ultimately ruin more than just our offseason. And as Patrick reported yesterday, the league already has some not-so-top-secret plans for a much shorter regular season, should it come to that:

The reports are that the proposed eight-game season could start in late November. The Chiefs open the third week of November by taking on the Patriots in New England. They then have vs. Steelers, @Bears, @Jets, vs. Packers, vs. Raiders, and @Broncos. That would be seven (brutal) games. It would include four road games and three home games. My guess is that the NFL would add one more game to the end of the year. I’m not sure how the other schedules for other teams work out, but it would make sense for the eighth game to be at Arrowhead vs. the Chargers. This would mean the Chiefs would play the division once, plus five out-of-division opponents.

This is just one scenario.

Indeed. Well, it just so happens that I was able to get a hold of a few random pages of the NFL’s lockout contingency manual. Here are a few more scenarios, each more nightmarish than the last…

(more…)

Quick trivia question: Who exactly is Hannibal Hamlin?

a)    The cannibalistic serial killer in Silence of the Lambs.
b)    The star of the hit ‘80s legal/inappropriate-office-sex drama L.A. Law.
c)    The Kansas City Chiefs’ all-time leader in punts inside the 20-yard line.
d)    The Vice President under Abraham Lincoln from 1861-65.

Well, as anyone with either a passion for 19^th-Century American political history or access to Google already knows, the answer is not a), or b), or even c). Hamlin, a U.S. Senator from Maine, was the other half of Lincoln’s ticket. He was later appointed ambassador to Spain, and was considered, I’m sure, an all-around great guy by his friends as well as the staff at his favorite diner in Bangor.

What does this fact have to do with the Kansas City Chiefs? Well, in and of itself, absolutely nothing. So why do I bother mentioning it (other than as a bit of minutiae I picked up in eager anticipation of last night’s premiere of Ridley Scott’s new docu-thriller Gettysburg on the History Channel*)?

*Seriously. It was AWE-some. You should check it out on rerun.

Consider: Passed over for a second term in favor of Andrew Johnson, Hannibal Hamlin’s tenure as #2 expired in March 1865, mere weeks before Lincoln’s career-and-life-ending-injury at Ford’s Theater forced Johnson to enter the presidency with little more than a few practice speeches under his belt. Indeed, he was not up to the task, and the country spent the rest of the decade mired in a long, painful rebuilding process known as Reconstruction. Congress even tried to cut Johnson before his contract was up.

I think you know where I’m going with this: Whether in the White House or the National Football League, a good backup is essential, particularly at the leadership position.

(more…)

No, the world didn’t end on Saturday—the reports of the Rapture and our impending demise were greatly exaggerated. But the pictures we saw the next day from Joplin, and have been seeing for weeks from Alabama and Mississippi (and now also Kansas and Iowa and Minnesota), look more than enough like a real Armageddon.

When tornadoes tore through Alabama, it got our attention; we were all touched and even inspired by Javier Arenas‘s story of survival and singular mission to help others, as detailed in Lars Anderson’s recent Sports Illustrated cover story. When a mile-wide twister, the single deadliest in the U.S. in almost 60 years, mangled Joplin on Sunday, the story hit much closer to home, literally for some, as those members of our AA team and their families felt the anguish first hand. I’m sure that’s true, too, for many of you out there.

I remember that when I read how Alabama head football coach Nick Saban was encouraging his players to reach out to the people of Tuscaloosa—“Just by your presence and being with them, you can help people,” he said—I was cynical at first. Perhaps because while Arenas’s first move after cheating death was to load up his SUV with $1,600 worth of supplies to hand out, Saban hasn’t yet announced how much of his $4.15 million salary for the 2011 season will be earmarked for disaster relief. Or maybe because the focus seemed to be on sports as a temporarily helpful but otherwise superficial distraction: “We can create a psychological escape for the people of this town,” Saban told SI. “They have a great passion for sports, and we’ll be there for them.”

Sure, sports are and can be a healthy diversion, especially in times like this, what another SI reporter, writing days after September 11, 2001, likened to “pulling a blanket over your head when you’re a kid—suddenly the world goes away and nothing outside that little space even exists; it’s delicious.” But that’s just the game. And being a fan extends beyond the game. There’s something much more important going on here, and we’re starting to see it.

(more…)

Here we are, Kansas City Chiefs fans, at what is supposed to be the midpoint between the end of last season and the beginning of the next. I am falling into my usual mid-offseason crisis—however, this time there’s no guarantee of recovery. There may still be faint light at the end of the tunnel, the tunnel that will hopefully lead out onto the field at Arrowhead Stadium on Opening Weekend in September. But as we await our next day in court—and with the ominous first comments from the U.S. Court of Appeals for the 8^th Circuit, it ain’t a’lookin’ so good—we don’t know how long the tunnel is going to be…

Here’s what we do know: The 2010 season turned out to be one hell of a party. And as the party wore on into the wee hours of the playoffs, I remember that everything was going great… The Chiefs were in the postseason at home for the first time since the early-mid George W. Bush administration. It was a sell-out crowd. The temperature at game time was a balmy 20 degrees Fahrenheit. In the first quarter, the Chiefs were keeping it close against the favored Baltimore Ravens. Excitement was building. And then, I distinctly remember, this happened.

But from that point on, everything became a blur. And now we’re left to piece together how exactly we got to where we are today… and whether we’ll ever find our friend Doug.*

*Actually, there is no player currently on the Chiefs roster named Doug, the last one being Doug Terry in 1995. There is, however, a Dwayne—who has, on occasion, gone missing.

(more…)