Wednesday, September 16, 2026

Andy Reid’s 150th Chiefs Win Is Another Reminder of How Completely He Changed This Franchise

 The Kansas City Chiefs’ 31–10 victory over Denver gave fans plenty to celebrate.

Kenneth Walker III exploded in his debut. Patrick Mahomes returned. The defense dominated.

Quietly tucked inside all of that was another Andy Reid milestone.

The victory was Reid’s 150th as head coach of the Kansas City Chiefs.

One hundred and fifty.

Reid was already the winningest coach in franchise history, so the number does not change his place in the record book. What it does is provide another opportunity to appreciate how radically the Chiefs changed after he arrived.

It can be difficult to remember the franchise Reid inherited because the current version of Kansas City has been successful for so long.

Before Reid arrived in 2013, the Chiefs had just finished 2–14.

Kansas City was not viewed as the center of the NFL universe. Arrowhead was still Arrowhead and Chiefs Kingdom was still passionate, but sustained championship expectations belonged somewhere else.

Reid changed the standard before Patrick Mahomes ever became the starter.

Kansas City went 11–5 in Reid’s first season. The Chiefs became a consistent playoff team. The organization stabilized. Winning seasons stopped feeling exceptional and started becoming expected.

Then Mahomes arrived, and Reid’s already successful tenure became historic.

The pairing produced championships, record-setting offenses and a period in which Kansas City became the opponent every AFC contender measured itself against.

That is why 150 wins should not be reduced to a coaching statistic.

Those wins represent a cultural transformation.

Reid created an environment in which players develop, assistant coaches grow, veterans want to play and the organization rarely seems surprised by adversity.

Even last season’s 6–11 collapse did not erase that foundation.

Monday night may have been the best evidence.

Kansas City entered a new season with Mahomes returning from a major knee injury, substantial roster turnover and questions across several position groups.

The Chiefs responded by beating the defending AFC West champions by three touchdowns.

That looked very much like an Andy Reid team.

My Take

There are going to be bigger celebrations for Andy Reid someday.

A Hall of Fame ceremony feels inevitable.

His name will live permanently in Chiefs history.

But I think milestones like 150 wins are worth noticing while he is still standing on the sideline.

Chiefs fans know what the franchise looked like before 2013.

Reid did not simply inherit Patrick Mahomes and ride along for the championships. He built a winning organization first. Mahomes then elevated that organization into something extraordinary.

That distinction matters.

The greatest coaches do more than win games. They change what a franchise believes is normal.

Before Reid, Chiefs fans hoped for a great season.

Under Reid, they expect one.

One hundred and fifty Kansas City victories later, that may be his greatest accomplishment.

Sources:

The Mansoor Delane Injury News Is About as Good as the Chiefs Could Have Hoped

 Mansoor Delane’s NFL career began about as dramatically as possible.

On his third professional snap, the Kansas City Chiefs’ first-round rookie intercepted Denver quarterback Bo Nix.

Then came the part nobody wanted to see.

Delane injured his shoulder and left Kansas City’s 31–10 victory without returning, immediately creating concern about a secondary that had already undergone significant offseason change.

The first follow-up report provides some relief.

NFL Network reported Tuesday that Delane is expected to miss only “minimal” time because of the injury. NFL.com also reported that the rookie was undergoing further evaluation after the game.

There is no reason to rush him back, particularly this early in the season. But avoiding a significant long-term absence would be an important break for Kansas City.

Delane is not simply another young defensive back on the roster.

The Chiefs traded up to select him sixth overall because they believe he can become a foundational piece of Steve Spagnuolo’s next secondary. Kansas City moved on from several established defensive backs during the offseason and placed considerable responsibility on a combination of returning veteran L’Jarius Sneed and young players such as Delane.

The opening interception showed why.

A rookie corner’s first NFL game usually comes with a long list of things to learn. Delane needed only three snaps to make a game-changing play.

That is the frustrating part of the injury. Chiefs fans got a glimpse of what the rookie can bring and then immediately had to wonder when they would see him again.

Kansas City handled his absence well against Denver. The defense continued suffocating the Broncos and held them to 176 total yards.

But surviving one game without Delane is different from wanting to play weeks without him.

The Chiefs drafted him to be part of the solution, not a player they hope to replace.

My Take

The phrase I care about here is “minimal time.”

That is not the same thing as saying Delane will definitely play Sunday against Indianapolis, and the Chiefs should not treat it that way.

It is September.

Kansas City’s goal should be having Delane healthy for the long season ahead, not proving how quickly he can return from a shoulder injury.

Still, after watching him leave Monday night, this is encouraging news.

His interception was exactly the kind of moment Chiefs fans hoped to see from the No. 6 pick. He looked comfortable, trusted what he saw and made the play.

Now I want to see what happens when he gets hundreds more snaps instead of three.

If the early report is correct and this truly is a short-term issue, the Chiefs may have avoided what could have been a major setback for their rebuilt secondary.

That is a very good development two days after an otherwise excellent opening night.

Sources:

Kahlil Benson Just Turned the Chiefs’ Biggest Week 1 Concern Into One of Their Best Stories

 The Kansas City Chiefs entered Week 1 with one question hanging over Patrick Mahomes’ return more than any other:

Could they protect him?

Josh Simmons was unavailable, and Kansas City handed the left-tackle job to Kahlil Benson, an undrafted rookie who had not played the position in college. His assignment in his first NFL game was hardly forgiving. Denver’s Nik Bonitto entered the season with 27.5 sacks over the previous two years.

That looked like the kind of matchup capable of ruining an otherwise carefully planned comeback for Mahomes.

Instead, Benson became one of the best stories of the night.

According to the Chiefs and Next Gen Stats, Benson allowed just one pressure on 32 pass-blocking snaps. His 3.2 percent pressure rate was the best among all rookie offensive tackles in Week 1.

Think about the path required to get there.

Benson was not drafted. He was not even one of Kansas City’s original undrafted free-agent signings. He came to rookie minicamp as a tryout player after starting at right tackle for national champion Indiana in 2025. Out of dozens of players trying to earn another day in the NFL, he played well enough to get a contract.

Then he survived training camp.

Then he made the 53-man roster.

Then injuries moved him to a position he had not played since high school.

Then Andy Reid put him on national television against one of football’s better edge rushers.

And Benson responded by allowing one pressure.

That does not mean Kansas City has permanently solved left tackle. Josh Simmons remains an important part of the Chiefs’ plans, and one good game should never be mistaken for a complete evaluation of a young offensive lineman.

But depth changes seasons.

The Chiefs spent much of the offseason trying to make sure Mahomes would not again be asked to compensate for instability in front of him. Benson’s performance suggests Kansas City may have found something far more valuable than emergency depth.

He may be a legitimate NFL tackle.

The running game helped him. So did Andy Reid’s play design and the presence of an experienced interior line. That should not diminish what Benson accomplished. Every offensive tackle receives schematic help at times. Eventually, the player still has to block the defender across from him.

Benson did.

My Take

I spent plenty of time worrying about the Chiefs’ offensive line before Week 1, so I am not going to pretend I expected this.

I didn’t.

An undrafted rookie making his NFL debut at left tackle against Denver’s pass rush sounded like exactly the wrong situation for a quarterback playing his first game after major knee surgery.

Instead, Benson looked like he belonged.

The important thing now is not to turn one good night into unrealistic expectations. Young tackles get exposed. Defensive coordinators study film. Future opponents will identify the techniques Benson handles well and the ones he does not.

The test gets harder from here.

But Kansas City now knows something it did not know a week ago: when Benson’s name was called in a difficult situation, he did not merely survive.

He performed.

For an undrafted rookie who arrived at Chiefs rookie camp on a tryout, that is one remarkable beginning.

Sources:

Tuesday, September 15, 2026

Travis Kelce Just Passed Jason Witten — and the Only Tight End Left Is Tony Gonzalez

 There was so much happening at Arrowhead on Monday night that a piece of NFL history almost felt like a side story.

Patrick Mahomes was playing his first real football in nine months.

Kenneth Walker III was running through Denver.

The Chiefs defense was suffocating the Broncos.

And Travis Kelce quietly moved past Jason Witten into second place on the NFL's all-time list for receiving yards by a tight end.

Only Tony Gonzalez remains ahead of him.

Think about what that means from a Kansas City perspective.

Two of the three most productive receiving tight ends in NFL history built their legacies in a Chiefs uniform.

That is remarkable.

Kelce's milestone came on a 59-yard reception during Kansas City's 31–10 win. It pushed his career receiving total to 13,073 yards, moving him beyond Witten and leaving Gonzalez as the final name above him.

Kelce reportedly treated the accomplishment the way he treats most individual milestones: as something secondary to winning.

That reaction is part of why his career has become what it has.

The statistics are enormous, but Kelce's place in Chiefs history cannot really be explained by a spreadsheet.

He became Mahomes' most trusted answer when a play broke down.

Third down.

Red zone.

Playoffs.

Super Bowl.

When Kansas City needed somebody to understand what Mahomes was seeing in real time, Kelce was usually the player moving into the same open space.

Their connection helped redefine what a tight end could look like in a modern passing offense.

Kelce was not simply lining up next to a tackle and running traditional tight-end routes. Andy Reid moved him everywhere. He aligned in the slot, outside, in motion and in formations designed specifically to force defenders to reveal coverage.

Then Mahomes arrived, and the relationship between quarterback and tight end became almost improvisational.

That combination produced championships.

Now it is producing history.

The Gonzalez comparison makes the milestone especially interesting for Chiefs fans because the two careers represent very different eras of the franchise.

Gonzalez spent years producing at an elite level for Kansas City without enjoying the postseason success that eventually surrounded Kelce. He was greatness during years when the Chiefs were often searching for stability.

Kelce became greatness during the most successful period the franchise has ever experienced.

Different eras.

Different offenses.

Different circumstances.

Same uniform.

My Take

I do not think Chiefs fans should rush through these Kelce milestones.

There will be plenty of time someday to debate where he ranks among the greatest tight ends ever. There will be arguments about Gonzalez, Rob Gronkowski, postseason production, longevity, blocking and every other measurement football fans can invent.

Right now, I would rather appreciate what Kansas City has witnessed.

The Chiefs went from Tony Gonzalez to Travis Kelce within a relatively short stretch of franchise history.

Most teams spend decades hoping to find one tight end capable of becoming a franchise icon.

Kansas City got two players who now sit at the very top of the NFL record book.

And Kelce is still adding to his total.

I do not know whether he will eventually catch Gonzalez in career yardage. That is not really the point.

Passing Witten means the list has narrowed to two names.

Tony Gonzalez.

Travis Kelce.

For Chiefs Kingdom, that is one heck of a list.

Sources:

The Most Encouraging Chiefs Number From Week 1 Might Be 176

 Patrick Mahomes' return generated the attention.

Kenneth Walker III generated the highlights.

But the number that may tell us the most about the Kansas City Chiefs' 31–10 victory over Denver is much less glamorous:

That is how many total yards the Broncos managed Monday night.

Denver finished with only nine first downs and converted just two third downs. Kansas City's defense sacked Bo Nix four times and forced turnovers while preventing the Broncos from building any sustained offensive rhythm.

For a defense that entered the season with legitimate questions, that is a statement.

Kansas City's secondary underwent major change during the offseason. Steve Spagnuolo was again being asked to blend veterans, young players and new pieces into a defense complicated enough to disguise pressure without creating coverage mistakes.

The first game was not supposed to provide a finished product.

Instead, the Chiefs looked remarkably coordinated.

The tone was set almost immediately when rookie cornerback Mansoor Delane intercepted Nix on Denver's opening possession. Delane unfortunately injured his shoulder on the play and did not return, but the defense did not unravel after losing him.

That may be as important as the interception itself.

NFL defenses rarely get through a season with their preferred eleven players available every week. The best units survive substitutions without changing their identity.

Kansas City did that Monday.

Denver briefly answered with a touchdown drive, but the Chiefs controlled almost everything afterward. The Broncos never found a consistent running game, struggled on third down and repeatedly found themselves playing the kind of football Spagnuolo wants opponents to play: behind schedule and unsure where the next pressure is coming from.

That allowed the pass rush to become increasingly aggressive.

Four sacks are useful.

The uncertainty that produces them is even more valuable.

When a quarterback cannot identify whether pressure is coming from the edge, the interior or the secondary, the entire offense slows down. Protection calls become more difficult. Routes have to develop faster. Running backs hesitate before releasing into patterns.

That is when Spagnuolo's defense becomes miserable to play against.

And Kansas City accomplished it while the offense was doing something equally helpful: controlling the game on the ground.

Complementary football is an overused phrase, but Monday was a good example of what it actually means. Walker's rushing success kept Kansas City out of constant third-and-long situations and helped the Chiefs control the game. The defense responded by repeatedly getting the ball back.

Neither unit had to spend the night compensating for the other.

My Take

I expected the Chiefs defense to need time.

One game does not erase that expectation, but 176 yards gets my attention.

What impressed me most was not any individual sack or turnover. It was how uncomfortable Denver looked for most of the night.

That is the Spagnuolo effect when everything is working.

The quarterback starts holding the ball just a fraction longer. The offensive line starts pointing and communicating before the snap. Receivers have to adjust to changing leverage. The offense begins reacting to Kansas City instead of dictating to it.

That is the defensive identity the Chiefs need.

There is also an important caution here: Delane's shoulder injury bears watching. He made an immediate impact before leaving, and Kansas City cannot afford to lose too many pieces from a secondary that is still establishing itself.

But the way the defense responded after his departure was encouraging.

If Kansas City can combine a legitimate running game with a defense capable of holding quality opponents under 200 yards, Mahomes may not have to be Superman every week.

That should scare the rest of the AFC.

Sources:

Kenneth Walker III Just Changed What the Chiefs Offense Can Be

For years, opposing defenses have entered games against the Kansas City Chiefs with one overriding objective:

Make somebody other than Patrick Mahomes beat them.

Kenneth Walker III may have just changed the meaning of that sentence.

Walker made his Chiefs debut Monday night and ran for a career-high 173 yards in Kansas City's 31–10 victory over the Denver Broncos. His biggest moment came early in the third quarter, when he broke loose for a 60-yard touchdown that turned a 14–7 game into a two-score Kansas City lead.

By the end of the night, the story was no longer simply that Mahomes had successfully returned from major knee surgery.

It was that the Chiefs suddenly looked capable of winning without asking him to perform a weekly magic act.

That matters enormously.

Kansas City's offense became increasingly difficult to watch at times last season because too many possessions seemed to reach the same point: Mahomes had to solve the problem. Protection broke down, the running game failed to create favorable downs, or the offense stalled until the quarterback was forced to create something outside the structure of the play.

Monday night looked different.

Walker gave the Chiefs an answer that did not require Mahomes to hold the football, escape pressure or manufacture an impossible throw.

Hand it off.

Let Walker find the crease.

Make the defense tackle him.

And then do it again.

The Broncos entered the season with a defense expected to be among the NFL's best. That makes Walker's performance more meaningful than a big statistical night against an overmatched opponent. Kansas City did not merely use the running game to protect a lead late. The Chiefs used it to create the lead.

The 60-yard touchdown was the obvious highlight, but the larger value came from the pressure Walker placed on Denver's entire defensive structure.

A defense that has to respect the run cannot devote every resource to confusing Mahomes. Linebackers have to step forward. Safeties have to respect run fits. Edge defenders cannot attack the quarterback without discipline. Play-action becomes more convincing because the handoff is no longer an empty threat.

That is where this could become much bigger than one spectacular debut.

Mahomes does not need Kansas City to become a run-first offense.

He needs defenses to believe that Kansas City could beat them by running the football.

There is a major difference.

Andy Reid can still spread the field, use motion, attack mismatches and let Mahomes improvise. But if Walker continues forcing defenses to devote real attention to the backfield, every other part of Reid's offense becomes harder to defend.

And for a quarterback returning from reconstructive knee surgery, that is about the best possible development.

My Take

This is exactly what I wanted to see from the Chiefs offense.

Not because I expected 173 rushing yards every week. Nobody should.

What matters is that Denver had to respect something besides Mahomes.

For much of the Mahomes era, Kansas City could get away with being unbalanced because the quarterback was so extraordinary that conventional rules did not always apply. But after last season—and after the injury—I do not want the Chiefs building an offense around the assumption that Mahomes can rescue every bad situation.

Walker gives them another way to win.

If a defense wants to play light boxes and flood the passing lanes, run the ball.

If a pass rush wants to attack aggressively upfield, punish it with the run.

If Kansas City gets a fourth-quarter lead, make the opponent tackle Walker until the clock disappears.

The Chiefs acquired him to change the backfield.

After one game, I am wondering whether he may change the entire offense.

That is a much bigger deal.

Sources:

Saturday, September 12, 2026

Alohi Gilman May Get an Early Chance to Show Why the Chiefs Brought Him In

 One of the easiest mistakes to make in the NFL is waiting until a starter is officially ruled out before paying attention to the player behind him.

The Chiefs may be giving us a reason not to make that mistake with Alohi Gilman.

Kansas City's official injury report showed defensive back Chamarri Conner missing both Thursday and Friday practice with a knee injury. As of Saturday morning, the Chiefs had not yet posted his final game designation for Monday night's opener against Denver.

That does not mean Conner will miss the game.

It does mean Gilman's role suddenly deserves more attention.

The Chiefs added Gilman during an offseason in which the secondary changed dramatically. That matters because Steve Spagnuolo does not run a defense where defensive backs simply stand in one spot and repeat one assignment all afternoon. Safeties rotate. Corners travel. Players disguise pressure, exchange coverage responsibilities and have to understand what the entire defense is doing—not just their own job.

Gilman spent the offseason learning that language while also working his way back physically from a back issue. This week, he said he feels ready and talked about Kansas City's emphasis on detail, physicality and playing fast.

Those are encouraging words.

Monday night could provide an early opportunity to see whether they translate.

Denver's offense is a difficult assignment for a defensive back who is still becoming comfortable in a new system. Jaylen Waddle brings speed. Courtland Sutton brings size. Bo Nix can extend plays and put stress on coverage rules once the original route structure breaks down.

That means communication at safety becomes critical.

One missed call can turn a manageable gain into an explosive play. One late rotation can leave a corner expecting help that never arrives. One bad angle against Waddle can erase an otherwise excellent defensive series.

That is why experienced depth matters more than fans sometimes realize.

The Chiefs lost multiple established defensive backs during the offseason. They brought L'Jarius Sneed back, invested in young players and added Gilman to help stabilize a group that will probably keep evolving well into the season.

Spagnuolo has done this before. His best defenses rarely look exactly the same in September and January. He experiments with personnel, finds roles that fit individual players and gradually expands what the unit can handle.

Gilman could become part of that process immediately.

My Take

I am not predicting that Chamarri Conner will miss Monday night's game. The Chiefs still have another practice report to come, and his official status matters more than speculation.

But this is exactly why Kansas City invested in veteran flexibility during the offseason.

A defense with championship ambitions cannot collapse because one defensive back is unavailable or limited.

If Gilman is asked to play an expanded role, I will be watching three things: communication before the snap, tackling in space and whether he looks comfortable when Denver uses motion to force the secondary to adjust on the fly.

He does not need an interception to have a good game.

Sometimes the best safety play is the one nobody notices because the ball never goes where the quarterback wanted it to go.

Kansas City's secondary is going to be tested immediately this season. If Gilman can step into a larger role without the defense changing its personality, the Chiefs may have found something they badly need in 2026: dependable depth that allows Spagnuolo to stay aggressive even when the lineup changes.

Sources:

Jaylen Waddle Is the Perfect First Test for the Chiefs' Rebuilt Secondary

 The Kansas City Chiefs did not ease their rebuilt secondary into the 2026 season.

They get Jaylen Waddle immediately.

Steve Spagnuolo made the challenge clear this week when he said Kansas City has to know where Waddle is on the field. That sounds obvious when talking about a receiver with game-changing speed, but it becomes much more complicated when the defensive backfield is still establishing its new identity.

The Chiefs are not simply rolling last year's secondary back onto the field.

Trent McDuffie is gone. Jaylen Watson and Bryan Cook also departed during an offseason that reshaped the back end of the defense. L'Jarius Sneed is back in Kansas City, first-round pick Mansoor Delane is part of the new group, and Spagnuolo once again has to turn a collection of different skill sets into a unit that can disguise coverage without losing communication.

Then Denver added Waddle.

That is about as direct a stress test as a new secondary can receive.

Waddle changes the geometry of a defense. If a corner gives him too much space, Denver can take the easy completion and let him create after the catch. If a defender gets too aggressive at the line and loses leverage, Waddle has the speed to turn one mistake into six points. If the safety cheats too far toward him, somebody else gets a more favorable matchup.

And Denver does not need Waddle to be the entire offense.

Courtland Sutton remains a physical outside threat. Bo Nix is healthy. The Broncos return remarkable continuity from last year's team, which means Kansas City's defense is facing an offense that already understands what it wants to be.

The Chiefs, by comparison, are still learning what their new secondary can become.

That does not mean Kansas City should play scared.

Actually, I think the opposite is true.

Spagnuolo has always been at his best when he can be aggressive without being predictable. Sneed gives him a veteran who understands the system and is comfortable playing physical football. Delane brings the kind of young coverage talent the Chiefs clearly believe can become a major part of the defense. The supporting group gives Kansas City options to change matchups instead of leaving one corner attached to Waddle for sixty minutes.

The challenge is making all of those moving pieces look coordinated.

That is where Week 1 could tell us a lot.

If the Chiefs can disguise their intentions, pass receivers cleanly through zones and keep Waddle from generating explosive plays after the catch, I will feel much better about the secondary than I would after a quiet game against a limited passing offense.

Denver is not limited.

That is what makes this useful.

The Chiefs are trying to get back into the AFC conversation after missing the playoffs. They do not have months to slowly discover whether the secondary works. The AFC West is too good for that. Denver already believes it belongs among the conference's best teams, and the Broncos have built an offense capable of attacking hesitation.

Kansas City has to answer with communication and confidence.

My Take

I expect Spagnuolo to make Waddle earn everything.

That does not necessarily mean double-covering him on every snap. Doing that would make the defense too easy to diagnose. I expect Kansas City to change the picture—press him at times, give him cushion at others, rotate safeties late and force Bo Nix to confirm what he is seeing after the snap.

The goal should not be to make Waddle invisible. Elite receivers usually find a way to get touches.

The goal should be to prevent the one play that changes the entire game.

No 60-yard catch because two defenders thought the other one had help. No shallow crossing route that becomes a touchdown because the pursuit angle was poor. No busted coverage after a pre-snap shift.

Make Denver drive the field.

If Kansas City's rebuilt secondary can do that against Waddle in Week 1, then one of the biggest offseason questions may start turning into an answer much sooner than expected.

Sources:

Eric Bieniemy Is Calling for an Old-School AFC West Fight — and the Chiefs Need It

 There are plenty of reasons Monday night's season opener will get national attention. Patrick Mahomes is returning. The Denver Broncos are coming to Arrowhead. Kansas City is trying to prove last year's 6-11 collapse was an interruption rather than the beginning of a decline.

But one of the most interesting comments of the week came from offensive coordinator Eric Bieniemy, who described the matchup as an "old-school AFC West blood match."

That phrase fits the opponent. It may also describe exactly what the Chiefs need to become again.

For several seasons, Kansas City's offense has been defined by what happens when Patrick Mahomes creates something that should not exist. The broken play becomes a first down. The impossible throw becomes a touchdown. The third-and-long situation becomes another highlight that ends up being replayed for years.

That ability still matters. Nobody should want the Chiefs to coach the improvisation out of Mahomes.

But the 2026 version of Kansas City cannot depend on magic every Sunday.

Denver is the wrong opponent for that kind of football anyway. The Broncos enter Week 1 with a defense that was among the NFL's best last season, and defensive coordinator Vance Joseph is not going to spend Monday night waiting politely for Kansas City to get comfortable. His defense attacks protections, changes pressure looks and tries to force quarterbacks into decisions before the offense wants to make them.

That is why Bieniemy's language matters.

The Chiefs need to be willing to win an ugly game.

Run when Denver expects a run. Finish blocks. Stay ahead of the chains. Take four yards instead of hunting for forty. Make the Broncos tackle Kenneth Walker III for four quarters. Let the offensive line build confidence by moving forward instead of asking it to survive obvious passing downs against one of the league's most dangerous pass rushes.

Kansas City spent years being able to survive almost any kind of game because Mahomes could erase mistakes. The danger in that success was eventually becoming too comfortable with the idea that he always would.

Last season should have ended that assumption.

The Chiefs went 6-11. They missed the playoffs for the first time since 2014. The offense too often looked like it was waiting for something spectacular to rescue it.

Bieniemy's return gives Kansas City a chance to change the attitude before it changes the statistics.

I do not expect the Chiefs to become a three-yards-and-a-cloud-of-dust team. Andy Reid is still Andy Reid, and Mahomes is still Mahomes. Kansas City will spread the field, use motion, create mismatches and take its shots.

But there is a difference between being creative and being soft.

Against Denver, the Chiefs may need to prove they can play through contact before they prove they can play around it.

The Broncos know the situation. They know Mahomes is returning from major knee surgery. They know Kansas City's offensive line has been dealing with uncertainty. They know pressure can turn a carefully planned comeback into a chaotic night very quickly.

The Chiefs know it too.

That is what makes Bieniemy's message so important. "Play hard" and "play fast" can sound like coaching clichés in September, but this particular team has something to reclaim. Kansas City is no longer entering the season as the unquestioned team everyone else is chasing. Denver won the division last year. The Broncos arrive at Arrowhead with legitimate championship expectations of their own.

This is not a ceremonial reopening of the Mahomes era.

It is a fight for the AFC West hierarchy.

My Take

If the Chiefs win Monday night, I do not care whether it looks beautiful.

In fact, I would almost prefer that it does not.

A 24-20 win built on tough runs, long drives, disciplined protection and a defense that forces Denver to earn every yard would tell me more about this team's ability to rebound than a handful of spectacular Mahomes throws.

We already know Kansas City can be brilliant.

What we need to find out is whether these Chiefs can be physical, patient and relentless again.

If Bieniemy really can bring that edge back to the offense, the phrase "old-school AFC West blood match" may end up being more than a good quote.

It may become the beginning of Kansas City's new identity.

Sources:

Chris Jones Lands on Chiefs Injury Report — How Worried Should Chiefs Fans Be?

Just when it looked like the Kansas City Chiefs were heading into Monday Night Football relatively healthy, one name suddenly appeared on Friday’s injury report that no Chiefs fan wanted to see:

Chris Jones.

The Chiefs’ star defensive tackle was listed as a limited participant Friday because of a calf injury after not appearing on Thursday’s injury report.

With Kansas City preparing to open the season against the Denver Broncos at Arrowhead Stadium on Monday night, that immediately becomes one of the biggest stories to watch over the weekend.

But before we start imagining the Chiefs taking the field without No. 95, there are a couple of reasons not to hit the panic button just yet.

The Good News: Jones Still Practiced

There is a big difference between being limited in practice and not practicing at all.

Jones participated Friday, even if his workload was reduced. We also don’t yet know exactly when the calf issue occurred or how serious it is.

The timing is certainly interesting. Jones was not listed on Thursday’s injury report and was a limited participant Friday.

That makes Saturday’s practice and the Chiefs’ final game-status designation extremely important.

If Jones practices again—even on a limited basis—I’ll feel considerably better about his chances of playing Monday night.

If he doesn’t practice?

Then my concern level goes up significantly.

Why Chris Jones Matters So Much Against Denver

There are certain players on an NFL roster who simply cannot be replaced by inserting the next guy on the depth chart.

Chris Jones is one of them.

Kansas City’s entire defensive front becomes more dangerous when Jones is in the middle because opposing offensive lines have to account for him on virtually every snap.

Double-team him and somebody else gets a favorable matchup.

Block him one-on-one and you’re taking your chances against one of the best interior defensive linemen of his generation.

And against Denver, that pressure could be especially important.

Broncos quarterback Bo Nix is exactly the kind of quarterback Steve Spagnuolo would like to make uncomfortable early. Interior pressure has a way of destroying the timing of an offense before plays ever have a chance to develop.

Jones doesn’t even need to record sacks to impact the game.

Collapse the pocket.

Force Nix to move.

Make Denver alter its protections.

Create opportunities for Kansas City’s edge rushers.

That’s the Chris Jones effect.

Take him out of the equation and Spagnuolo suddenly has to manufacture some of that disruption through scheme rather than simply having No. 95 wreck things in the middle.

There Are Other Injuries Worth Watching

Jones isn’t Kansas City’s only concern heading into Monday night.

Left tackle Josh Simmons missed both Thursday and Friday practices because of a back injury, while defensive back Chamarri Conner also missed both practices with a knee injury.

Those situations may actually be more concerning at the moment because neither player was able to participate Friday.

The encouraging news is that several other Chiefs carrying injury designations have been full participants, including Patrick Mahomes, Rashee Rice, Xavier Worthy, Trey Smith and L’Jarius Sneed.

So while the injury report looks fairly long on paper, most of those names appear to be trending in the right direction.

Jones is different simply because his injury appeared unexpectedly.

My Take

Am I worried?

A little.

Am I panicking?

Not yet.

If Chris Jones had completely missed Friday’s practice after suddenly appearing with a calf injury, I would be considerably more concerned.

The fact that he was still able to participate—even in a limited capacity—is at least encouraging.

But calf injuries are also something I never like seeing with big defensive linemen. Jones relies on explosion, leverage and the ability to drive through offensive linemen. Even a relatively minor calf problem could potentially affect that explosiveness.

And this isn’t exactly the opponent where I’d like Kansas City testing how well the defense functions without him.

Denver is no longer a team the Chiefs can simply assume they’re going to beat because Patrick Mahomes is on the other sideline.

This is an AFC West game. It’s the season opener. It’s Monday Night Football. And Denver comes into Arrowhead expecting to compete.

I want Chris Jones standing in the middle of that Chiefs defensive line when it happens.

Saturday Becomes Very Important

By the time Kansas City releases its final injury report, we should have a much better idea of what we’re dealing with.

If Jones practices and receives no game designation, Chiefs Kingdom can probably exhale.

If he’s listed as questionable, the waiting game continues.

And if he doesn’t practice Saturday, we may have a legitimate Week 1 concern on our hands.

For now, I’m putting this firmly in the “keep a very close eye on it” category.

Because there are plenty of players the Chiefs could probably survive being without for one game.

Chris Jones isn’t one of the players I want to find out about.

What do you think?

How concerned are you about Chris Jones’ calf injury?

Do you think the Chiefs can still control Denver’s offense if Jones is limited—or even unavailable—Monday night?

Let me know your take.

Go Chiefs!

Source: This post discusses reporting from The Kansas City Star regarding Chris Jones being added to Kansas City’s injury report, along with the Kansas City Chiefs’ official Week 1 injury report.

There are hot takes, and then there are Skip Bayless hot takes.

 There are hot takes, and then there are Skip Bayless hot takes.

This one definitely qualifies.

Bayless recently suggested that Patrick Mahomes tearing his ACL might actually turn out to be a good thing for the Kansas City Chiefs quarterback in the long run. The reasoning is that the injury could force Mahomes to change parts of his game—particularly his tendency to extend plays, scramble and create offense outside the structure of the play.

At first glance, calling a torn ACL a “good thing” sounds ridiculous.

And I’m certainly not going to go that far.

But underneath the headline-grabbing wording, I actually think there is an interesting point worth discussing.

Mahomes Has Always Been at His Best When Chaos Begins

One of the things that has made Patrick Mahomes special throughout his career is his ability to turn a broken play into something spectacular.

The pocket collapses.

Mahomes escapes.

The defense loses track of Travis Kelce.

Mahomes throws from some ridiculous angle that quarterbacks are taught never to use.

First down.

We’ve watched it happen so many times that Chiefs fans almost expect it.

But there is also a downside.

Sometimes Mahomes’ confidence in his ability to make something happen can lead him to hold onto the football longer than necessary. Instead of taking the easy completion, he may try to extend the play looking for something bigger.

And sometimes instead of simply delivering the ball on schedule, he starts improvising.

Most quarterbacks would never get away with it.

Mahomes does because he’s Patrick Mahomes.

But that doesn’t necessarily mean it’s always the best option.

Bayless Might Actually Have a Point

The argument Bayless makes is essentially that recovering from the knee injury could encourage Mahomes to become more selective about when he leaves the pocket.

That could mean staying in the pocket an extra moment.

Trusting the offensive line.

Taking the five-yard completion.

Getting the football out on time.

Living to play another down instead of trying to turn every broken play into a highlight.

And if Mahomes adds more of that discipline to everything he already does?

That could be scary for the rest of the NFL.

We sometimes forget that quarterback development doesn’t stop when a player becomes a superstar.

Tom Brady evolved.

Peyton Manning evolved.

John Elway evolved.

The great quarterbacks eventually learn that beating defenses mentally can be just as devastating as beating them physically.

Mahomes is now entering another stage of his career where that evolution may become important.

The Injury Wasn’t a Good Thing

This is where I disagree with the way Bayless framed the argument.

The injury itself wasn't good.

There is nothing positive about watching your franchise quarterback suffer a torn ACL.

Mahomes underwent surgery in December and spent months working through rehabilitation. The fact that he attacked the recovery process aggressively and worked his way back to full practice participation is impressive.

But we shouldn't have to pretend the injury was somehow beneficial to recognize that something positive could come from the experience.

There is a difference.

Mahomes has now experienced something he really hadn't dealt with before: a major injury threatening his ability to play football.

That can change the way an athlete approaches the game.

Maybe he slides sooner.

Maybe he throws the ball away instead of fighting for another three yards.

Maybe he takes the checkdown instead of scrambling around for eight seconds.

Maybe Andy Reid and the Chiefs design the offense to get the football out of his hands quicker.

None of those things would make Mahomes less dangerous.

They might actually make him harder to defend.

Remember What Happened Before the Injury

There is another part of this discussion Chiefs fans shouldn't ignore.

Kansas City's offense had already been changing before Mahomes suffered the injury.

The explosive plays that once seemed automatic weren't coming nearly as frequently.

Defenses adjusted.

They started taking away the deep ball and forcing Kansas City to methodically move down the field.

Mahomes had already been learning how to win differently.

The spectacular 50-yard bomb might have been replaced by an eight-yard completion underneath.

And honestly?

That's what elite quarterbacks eventually have to do.

Defensive coordinators spend entire offseasons studying Mahomes. They aren't going to repeatedly give him the same opportunities he had earlier in his career.

Mahomes has to evolve.

The Chiefs offense has to evolve with him.

Protecting Mahomes Has to Matter More Than Ever

There is another lesson Kansas City should take from all of this.

Patrick Mahomes is the franchise.

Everything revolves around No. 15.

That means protecting him can't simply mean improving the offensive line.

It also means protecting Mahomes from Mahomes.

I mean that in the best possible way.

His competitiveness is one of the reasons he's great.

Mahomes believes he can make every play.

He believes he can escape every defender.

He believes he can get the extra yard.

That attitude has produced some unforgettable moments.

But there are times when the smartest play might be the most boring one.

Throw it away.

Slide.

Take the checkdown.

Punt.

Come back on the next drive.

Chiefs fans might not enjoy watching Mahomes become slightly more conservative, but I'll happily trade a few spectacular scrambles for having him healthy in January.

A Different Mahomes Could Be an Even More Dangerous Mahomes

This is the part of Bayless' argument I find fascinating.

What happens if Mahomes becomes a better pocket quarterback because of this experience?

Not because he suddenly loses his ability to improvise.

But because he becomes more selective about using it.

Imagine a version of Mahomes who operates efficiently within Andy Reid's offense for most of the game and only unleashes the backyard-football version when Kansas City truly needs it.

That's a nightmare for defenses.

You can't sell out against the scramble because he may stay in the pocket.

You can't sit on underneath routes because Mahomes can still attack you deep.

You can't play man coverage without worrying about him running.

You can't play zone without giving him opportunities to find holes.

The physical talent is still there.

The creativity is still there.

The difference could simply be knowing when not to use it.

My Take

I don't believe tearing an ACL is ever a “good thing.”

But I understand what Bayless is trying to say.

Adversity changes athletes.

Sometimes it exposes weaknesses.

Sometimes it forces adjustments.

And sometimes those adjustments extend careers.

Patrick Mahomes has already accomplished more than most quarterbacks could ever dream of accomplishing. But his next challenge isn't proving he can make impossible plays.

We've already seen that.

The next challenge may be proving he doesn't always need to.

If this injury causes Mahomes to become more disciplined in the pocket, quicker with his decisions and more selective with his scrambling while still maintaining the creativity that made him great, then something valuable could eventually come from an awful situation.

And that's the part the rest of the NFL probably doesn't want to think about.

Because Patrick Mahomes with all of his old tricks plus another level of patience and pocket discipline?

That might be an even tougher version of No. 15 to beat.

What do you think, Chiefs Kingdom?

Could Mahomes actually come back from the ACL injury as a better quarterback, or would you rather see him continue playing the aggressive, improvisational style that made him a superstar?

Friday, September 11, 2026

Kansas City Chiefs’ Left Tackle Problem Is Real — But D.J. Humphries Isn’t the Answer

 The Kansas City Chiefs suddenly have a very uncomfortable question to answer heading into Week 1:

Who is going to protect Patrick Mahomes’ blind side?

With Josh Simmons battling a back injury and missing Thursday’s practice, the Chiefs could find themselves turning to Kahlil Benson at left tackle when Kansas City opens the 2026 season against the Denver Broncos on Monday Night Football.

That uncertainty makes almost any veteran offensive tackle who becomes available worth discussing.

And that brings us to a familiar name: D.J. Humphries.

Matt Conner of Arrowhead Addict recently raised the issue after the Washington Commanders released Humphries, arguing that while Kansas City clearly needs some insurance at tackle, going back to Humphries would be the wrong move.

I agree.

I Understand Why Chiefs Fans Would Consider Humphries

On the surface, it makes sense.

Humphries is a former first-round pick. He has nearly 100 NFL starts under his belt. He made a Pro Bowl. Most importantly, he already knows the Kansas City Chiefs organization.

When you're staring at the possibility of an inexperienced tackle protecting Mahomes in the first game of the season, signing an experienced veteran sounds comforting.

But sometimes familiarity gives us a false sense of security.

The Chiefs already tried this.

Kansas City brought Humphries in during the 2024 season when the team was desperately searching for stability at left tackle. Instead of becoming the solution, Humphries lasted one start before suffering a hamstring injury that sidelined him. Since then, his career hasn't exactly experienced a resurgence. He appeared in eight games for the Los Angeles Rams last season but started only one. Washington signed him in late August and released him just a couple of weeks later.

That doesn't scream "solution."

It screams another temporary patch.

At Some Point, You Have to Find Out What You Have

This is where I think the Chiefs may be making the right decision, even if it makes Chiefs Kingdom nervous.

Kansas City's current offensive line group includes Josh Simmons, Kahlil Benson, Jaylon Moore, Diego Pounds, Kingsley Suamataia and one of the best interior combinations in football with Creed Humphrey and Trey Smith.

If Simmons can't go Monday night, Benson may get an enormous opportunity.

Is that risky?

Absolutely.

An undrafted young tackle potentially making a Week 1 start while protecting Patrick Mahomes against a division opponent on Monday Night Football isn't exactly the scenario any Chiefs fan would draw up.

But there comes a point where Kansas City has to determine whether Benson can actually play.

Training camp practices and preseason games can only tell you so much.

Eventually, the lights come on.

The Bigger Concern Is Patrick Mahomes

This situation also feels different because of what's happening behind the offensive line.

Mahomes is returning after suffering torn knee ligaments last December. He's participating fully in practice and appears ready to go for Week 1, but protecting him should be priority No. 1, No. 2 and probably No. 3 for this franchise.

That's exactly why I don't believe the Chiefs should sign a tackle simply because fans recognize his name.

If Brett Veach is going to add someone, that player needs to represent a legitimate upgrade.

That's the standard.

The question shouldn't be:

"Is D.J. Humphries experienced?"

Of course he is.

The question should be:

"Is D.J. Humphries better right now than Kahlil Benson, Jaylon Moore or the other options already on Kansas City's roster?"

Based on what we've seen over the last couple of seasons, I'm not convinced the answer is yes.

Don't Confuse Experience With Improvement

This is something NFL teams face all the time.

A recognizable veteran becomes available and immediately fans start connecting dots.

We've seen him play before.

We know his name.

He's played in big games.

He has experience.

Therefore, he must make the roster better.

Except that isn't necessarily true.

Humphries' résumé is impressive when looking at his entire career. But Kansas City wouldn't be signing the 2021 Pro Bowl version of D.J. Humphries.

They'd be signing the 2026 version.

That's an important distinction.

The Chiefs need to evaluate the player Humphries is today—not the player he was several years ago.

My Take

I'm definitely concerned about left tackle.

How could you not be?

Patrick Mahomes is coming back from a major knee injury, Josh Simmons has a back problem, and the Chiefs may have to trust an inexperienced Kahlil Benson against Denver in Week 1.

That's far from ideal.

But I also don't believe making a move simply for the sake of making a move helps anything.

If Brett Veach finds a veteran tackle who clearly improves this offensive line, absolutely go get him.

If a trade opportunity develops for a legitimate starting-caliber tackle, explore it.

But bringing back D.J. Humphries because he's available and familiar with Kansas City feels more like reacting to the problem than actually solving it.

And there's another possibility Chiefs fans should consider.

Maybe the Chiefs know something about Kahlil Benson that we don't yet.

Kansas City kept Benson on the 53-man roster for a reason. The coaching staff has watched every practice, every rep and every meeting. If Andy Reid, Andy Heck and the Chiefs' offensive staff believe Benson deserves an opportunity, I'm willing to see what the kid can do.

That doesn't mean Kansas City should stop looking for offensive tackle help.

They absolutely shouldn't.

It means the Chiefs should look for the right tackle—not simply the most familiar one available.

D.J. Humphries had his opportunity in Kansas City.

Right now, I'd rather see the Chiefs find out whether one of their young tackles can become part of the future than go back to a veteran who already showed us why he probably isn't.

What do you think, Chiefs Kingdom? Would you bring D.J. Humphries back as insurance, or would you trust Kahlil Benson and the tackles already on the roster?

This post is commentary inspired by reporting from Matt Conner of Arrowhead Addict. Kansas City Chiefs – My Take is an independent fan blog and is not affiliated with the Kansas City Chiefs or the NFL.

Thursday, September 10, 2026

Clark Hunt Says the Chiefs’ New Stadium Likely Won’t Be Called Arrowhead — My Take

 For generations of Kansas City Chiefs fans, Arrowhead hasn’t just been the name of a football stadium.

It has been part of the identity of the franchise.

Arrowhead means tailgating on a cold Sunday morning. It means the smell of barbecue filling the parking lots hours before kickoff. It means the tomahawk chop echoing through the stands. It means one of the loudest home-field advantages in professional football.

And eventually, it may become a name associated only with the Chiefs’ past.

Chiefs Chairman and CEO Clark Hunt indicated Thursday that the team’s new stadium in Kansas City, Kansas, probably will not be called Arrowhead when the Chiefs move into their new home for the 2031 season.

For Chiefs Kingdom, that's going to take some getting used to.

Clark Hunt Wants to Honor Arrowhead — Without Recreating It

Hunt made it clear that while the Arrowhead name may not follow the team across the state line, the Chiefs aren't trying to erase what Arrowhead Stadium represents.

According to Hunt, the organization wants the new stadium to incorporate enough elements of the current stadium that longtime fans will immediately recognize its influence. The goal is to honor Arrowhead's legacy while creating something designed to serve the Chiefs for another 50 or 60 years.

We've already seen that philosophy reflected in the initial stadium renderings released by the Chiefs.

The new enclosed stadium is expected to hold approximately 70,000 fans, feature more than 20,000 parking spaces, and include a translucent ETFE roof. The Chiefs have also emphasized that the seating bowl and overall design are being engineered with Arrowhead's legendary crowd noise and gameday atmosphere in mind.

That's important.

Because if we're being realistic, the Chiefs were never going to build Arrowhead Stadium 2.0.

They are trying to build something much bigger.

This Stadium Is About More Than Eight or Nine Chiefs Games

One of the biggest reasons the Chiefs are building a modern enclosed stadium is obvious: Kansas City wants access to events that the current Arrowhead simply isn't designed to host.

Hunt specifically mentioned the possibility of bringing events such as a Super Bowl to Kansas City and potentially hosting future World Cup matches when the tournament returns to the United States.

The new stadium is scheduled to open for the beginning of the 2031 NFL season in Kansas City, Kansas. The Chiefs say the stadium itself represents roughly a $3 billion investment and will anchor a much larger development in Wyandotte County.

This isn't simply a football stadium.

It is being designed as a year-round sports and entertainment destination.

And that may ultimately explain why the Chiefs want a new identity for it.

But Losing the Arrowhead Name Still Hurts

Here's where I think a lot of Chiefs fans — myself included — are going to struggle.

Arrowhead is one of those rare stadium names that actually means something.

Think about some of the great venues in American sports.

Lambeau Field.

Fenway Park.

Wrigley Field.

Madison Square Garden.

Arrowhead Stadium belongs in that conversation.

Nobody says, "The Chiefs have a tough home-field advantage in Kansas City."

They say:

"You have to go into Arrowhead."

That's different.

The name itself has become intimidating.

Players know it. Coaches know it. Broadcasters know it. NFL fans around the country know it.

You can't manufacture that kind of brand recognition with a marketing campaign.

It takes decades.

That's why I would love to see the Chiefs find some way to keep Arrowhead connected to the next stadium.

Maybe Arrowhead Isn't Really Going Away

There is one interesting possibility.

Earlier this summer, the Chiefs filed trademark applications for several names connected with the future development, including:

Arrowhead Sports and Entertainment Complex

Arrowhead Sports Complex

Tailgate Town

and

Kingdom Commons.

That makes me wonder whether the stadium itself gets a completely new name — potentially even a corporate naming-rights partner — while the surrounding district carries the Arrowhead name.

If that's the compromise, I could live with it.

Imagine something along the lines of:

"Welcome to Arrowhead Sports and Entertainment Complex, home of the Kansas City Chiefs."

The stadium could have its own name, while Arrowhead remains the name of the Chiefs' home territory.

That would preserve some continuity between generations of Chiefs fans.

The Timing Is Kind of Ironic

There's another interesting twist to all of this.

Just last month, the Chiefs and G.E.H.A. announced that beginning with the 2026 season, the current stadium would once again officially be known simply as Arrowhead Stadium, dropping the GEHA Field naming convention.

Chiefs fans overwhelmingly identify the stadium as Arrowhead anyway, so returning to the traditional name felt right.

Now, barely a month later, we're learning that the name probably won't make the trip to Kansas in 2031.

Enjoy seeing Arrowhead Stadium on the signs while you can.

My Take

I understand what Clark Hunt and the Chiefs are doing.

The new stadium represents a new era.

It will be enclosed, technologically advanced, capable of hosting enormous events and surrounded by an entertainment district unlike anything the franchise has had before.

Giving that stadium its own identity makes sense.

But I also think the Chiefs need to be extremely careful here.

Arrowhead isn't just intellectual property. It's part of Chiefs culture.

Buildings come and go. Names sometimes shouldn't.

If the organization can preserve the Arrowhead name somewhere within the new development, I think that's the right move.

Call the actual stadium something new if you have to.

Build the dome.

Bring us a Super Bowl.

Bring another World Cup to Kansas City.

Build restaurants, hotels, entertainment districts and everything else that comes with a modern NFL destination.

But somewhere above the entrance to the Chiefs' new home, I'd still like to see one word:

ARROWHEAD.

Because wherever the Chiefs play, that name belongs to Chiefs Kingdom.

What Do You Think, Chiefs Kingdom?

Should the Chiefs' new stadium continue to be called Arrowhead Stadium?

Would you be okay with Arrowhead becoming the name of the surrounding sports and entertainment district instead?

Or do you think a completely new stadium deserves a completely new name?

Sound off in the comments.

Source: Ron Kopp Jr., Arrowhead Pride, “Clark Hunt reveals Chiefs likely won’t call new stadium ‘Arrowhead,’” September 10, 2026.