Home/NFL

USA Today via Reuters

USA Today via Reuters

Whoa, did you catch the Chiefs’ game last Sunday against the Bills? Talk about a rollercoaster! The Chiefs were on fire, but then, bam — they hit a wall. What went wrong? Let’s dive into the crazy mess of questionable decisions and missed chances that turned this game on its head.

First off, let’s talk defense. Former Chiefs star Mitchell Schwartz didn’t hold back on Twitter, saying, “I don’t understand the rush plan today. No reason to go cover 0 there.” Like what were they thinking? Josh Allen was all over the field, practically throwing for 262 yards and rushing for another 55. With none such pressure, he could play the game like it was practice. No sacks? Come on, that’s not Chiefs football!

 

ADVERTISEMENT

Article continues below this ad

And then there’s Coach Andy Reid! We are late in the game. And down at 23-20. That’s when he decides to kick an extra point instead of going for a two-point conversion. He later sheepishly admitted, “I could probably call some more runs when it’s all said and done.” You think? The run game was almost non-existent with only 17 carries! How do you let that happen against a team known for a weak rush defense? It’s just baffling.

Kareem Hunt led the ground game with 14 carries for 60 yards, which isn’t half bad, but come on! The Chiefs didn’t mix it up. Each play felt too predictable, and it showed. Reid’s decision to shy away from the run not only hurt the offense but gave Allen way too many chances to run wild.

Don’t even get me started on how the Chiefs’ D just let Allen do whatever he wanted. Schwartz pointed out that they needed to “muddy up the rush lanes” for him — you know, make things tough. Reid’s conservative play-calling really left the team hanging!

ADVERTISEMENT

Article continues below this ad

What’s your perspective on:

Did Andy Reid's conservative play-calling cost the Chiefs a crucial win against the Bills?

Have an interesting take?

Consequences and moving forward for the Chiefs

That loss not only sent the Chiefs packing with a dent in their perfect season but also tightened things up in the AFC standings. The Bills, now at 9-2, snagged the tiebreaker and are eyeing that top seed. Yikes!

Now, look at McDermott. The dude went for it on 4th-and-2. When instead he could have played it safe with a field goal. He said it was mapped out during the week, and guess what? It worked! Allen took it to the house for a 26-yard touchdown, leaving the Chiefs scrambling. McDermott played it smart when it mattered, proving that sometimes you just gotta risk it for the biscuit.

ADVERTISEMENT

Article continues below this ad

So, what’s next? The Chiefs gotta regroup fast. With guys like Jaylen Watson and Charles Omenihu coming back, the defense should see a switch-up. Steve Spagnuolo has some work ahead. Let’s hope he regains that defense’s edge because Kansas City can’t afford another blunder like this.

They’ve got a game against the Panthers coming up, and it’s time for Reid to rethink his strategies. Every decision counts from here on out in this tight playoff race. The Chiefs can’t just sit back and let opportunities slip away. They gotta make some noise! The AFC is heating up, and the Chiefs have to step it up, stat!

Have something to say?

Let the world know your perspective.

0
  Debate

Debate

Did Andy Reid's conservative play-calling cost the Chiefs a crucial win against the Bills?