Tyquan Thornton Is Becoming the Deep Threat Patrick Mahomes Has Been Missing

 Third-and-12.

Overtime.

The Kansas City Chiefs are backed up inside their own 30-yard line.

This is where football games can end.

Instead, Patrick Mahomes looked downfield and found Tyquan Thornton.

Thirty yards.

First down.

Drive alive.

Kansas City eventually turned that possession into Harrison Butker's first overtime field goal, and the Chiefs ultimately escaped Indianapolis with a 33–30 victory.

Thornton's catch was enormous.

It also wasn't his only big play.

Earlier in the game, Mahomes hit Thornton for 45 yards, putting Kansas City at the Indianapolis 1-yard line and setting up another scoring opportunity.

Two catches.

Seventy-five yards.

Both changed drives.

That is exactly what Kansas City needs from him.

Speed Is Only Valuable If Defenses Respect It

Thornton has never lacked speed.

He ran a 4.28-second 40-yard dash coming out of Baylor.

NFL defensive backs know he can run.

But there is a difference between possessing speed and forcing defenses to respect it.

That requires production.

If a receiver runs deep repeatedly without catching the football, safeties eventually stop worrying quite as much.

Make a few plays like Thornton made Sunday night and the equation changes.

Now the cornerback cannot cheat.

The safety has to stay deep.

The middle of the field becomes larger.

And suddenly Travis Kelce, Rashee Rice and Kansas City's other receivers have more room underneath.

That is why Thornton doesn't need eight catches every Sunday to become extremely valuable.

He needs defenses to believe Mahomes will throw him the football when he gets behind them.

Sunday provided evidence that he will.

The Overtime Catch Was the Bigger Play

The 45-yard reception will probably make the prettier highlight reel.

I liked the 30-yarder better.

Kansas City faced third-and-12 in overtime.

Everybody knew Mahomes had to throw.

Indianapolis generated pressure.

Thornton still created separation in one-on-one coverage, and Mahomes delivered the ball downfield.

That's not a gadget play.

That's not catching a defense surprised by play-action.

That's a receiver winning when the Chiefs needed someone to win.

Those are the plays that build quarterback trust.

Mahomes now knows that when Thornton sees single coverage in a critical situation, he has another option.

That matters.

My Take

The Chiefs have spent years searching for ways to recreate the vertical pressure that once made their offense almost unfair.

I'm not comparing Tyquan Thornton to Tyreek Hill.

He doesn't need to be Tyreek Hill.

He needs to make safeties nervous.

Sunday night was a very good start.

If Thornton can consistently produce even two or three legitimate downfield opportunities per game, he changes the geometry of Kansas City's offense.

Think about what defenses already have to process.

Kenneth Walker is now threatening them on the ground.

Travis Kelce still commands attention in the middle.

Rashee Rice can create yards after the catch.

Xavier Worthy's speed has to be respected.

Then Thornton runs past somebody.

There are only 11 defenders.

Andy Reid's job is to make them choose incorrectly.

Thornton just gave him another way to do it.

The catch on third-and-12 in overtime is the play I'll remember.

Because speed gets you onto an NFL roster.

Making that catch when the Chiefs desperately need it gets Patrick Mahomes looking for you the next time the game is on the line.

Sources: Chiefs — Week 2 game highlights; Yahoo Sports — How the Chiefs escaped the Colts in overtime; A to Z Sports — Chiefs Week 2 winners and losers. 

Kenneth Walker Isn’t Just Giving the Chiefs a Running Game — He’s Changing the Mahomes Offense

 One great game can be a story.

Two great games can start becoming an identity.

A week after Kenneth Walker III exploded for 173 rushing yards against Denver, the Kansas City Chiefs' new running back delivered another performance Sunday night that made his Week 1 breakout look considerably less like an opening-night anomaly.

Walker rushed for 117 yards against Indianapolis and added 61 receiving yards, giving him 178 yards from scrimmage in Kansas City's 33–30 overtime victory.

And when the Chiefs absolutely needed him, Walker helped finish the game.

Kansas City got the ball back with 3:11 remaining in overtime after Indianapolis kicked a tying field goal. Walker carried the ball on three consecutive plays before Patrick Mahomes found him for a 22-yard completion that put Harrison Butker in position to kick the game-winning 40-yard field goal as time expired.

That sequence tells us something important.

Walker isn't simply another weapon in Andy Reid's offense.

He's becoming part of the answer when Kansas City needs to close a football game.

The Mahomes Numbers Tell Another Story

Patrick Mahomes threw for 382 yards and three touchdowns Sunday night.

Those are vintage Mahomes numbers.

But the more interesting development may be how Kansas City is creating some of those opportunities.

Indianapolis had to respect Walker.

That creates hesitation.

Linebackers have to think about the run.

Safeties have to respect what is happening in the backfield.

Defensive linemen cannot simply attack Mahomes every snap without worrying about their run responsibilities.

Then Andy Reid introduces play-action.

According to postgame analysis, Mahomes produced career-best single-game numbers using play-action against Indianapolis.

Think about how significant that could become.

Mahomes has spent most of his career terrifying defenses without the benefit of an elite running game.

Now imagine forcing those same defenses to hesitate before attacking him.

That fraction of a second matters.

It can be the difference between pressure and a clean pocket.

Between a linebacker dropping immediately into coverage and taking one step toward Walker.

Between a safety sitting on a route and having to respect the run.

Kansas City suddenly has another lever to pull.

Walker Is Becoming More Than a Runner

Sunday also demonstrated why Walker's receiving ability matters.

His 61 receiving yards meant Indianapolis couldn't simply think "run" whenever No. 9 lined up behind Mahomes.

The game-winning drive provided the perfect example.

Kansas City handed Walker the football three straight times.

Then Mahomes threw it to him.

That is exactly the kind of sequence that makes an offense difficult to defend.

Same personnel.

Different answer.

And because Walker can create yards after the catch, throwing him the football doesn't necessarily mean settling for a short gain.

Sometimes it means 22 yards and a game-winning field-goal opportunity.

My Take

After Denver, I wrote that Kenneth Walker might have changed what the Chiefs offense can be.

After Indianapolis, I think we can go one step further.

This is beginning to look intentional.

The Chiefs aren't simply giving Mahomes a running back.

They're building an offense where the running back changes how defenses are allowed to attack Mahomes.

That is a huge distinction.

Kansas City's offense has spent years operating under the assumption that Patrick Mahomes will eventually solve the problem.

Now defenses may have a problem before Mahomes even throws the football.

Do you attack him?

Walker can punish you.

Do you respect Walker?

Mahomes gets play-action opportunities.

Do you spread out to handle Kansas City's receivers?

Walker gets lighter boxes.

That's the kind of conflict Andy Reid loves creating.

Walker now has 290 rushing yards through his first two Chiefs games, including back-to-back 100-yard performances.

We don't need to wonder anymore whether the Denver game was a fluke.

The more interesting question is what this offense looks like once Reid has spent half a season figuring out everything he can do with his new running back.

That could be considerably more frightening.

Sources: ESPN — Chiefs laud Kenneth Walker III's impact through 2–0 start; Reuters — Butker's field goal lifts Chiefs over Colts in overtime; Chiefs — Week 2 game highlights. 

Chris Jones Being Questionable Changes the Math Against Jonathan Taylor

 Yesterday, the biggest defensive question for Kansas City was straightforward:

How do the Chiefs keep Jonathan Taylor from controlling Sunday night’s game?

Today there is another question attached to it.

Will Chris Jones be operating at full strength when they try?

Kansas City’s final Week 2 injury report lists Jones as questionable for Sunday night’s game against Indianapolis after he was limited during the practice week because of a calf injury. Rookie cornerback Mansoor Delane is also questionable with the shoulder injury he suffered against Denver.

The Delane situation is worth watching, but we have already discussed his encouraging recovery trajectory.

Jones creates a different conversation.

Kansas City’s plan for Jonathan Taylor begins in the middle of the defense.

Taylor ran for 98 yards and two touchdowns against Baltimore in Week 1 despite Indianapolis losing 41–23. He remains capable of turning an otherwise ugly offensive performance into a competitive game if a defense allows him to consistently reach the second level.

Jones is one of the players who can prevent that from happening before it starts.

Most fans naturally associate Jones with sacks and interior pass rushing. That is understandable. Few defensive tackles can destroy a passing play as quickly as he can.

But his presence affects the running game before the snap, too.

An offensive line has to account for where Jones is aligned.

If Indianapolis uses additional resources to prevent him from penetrating the backfield, somebody else receives a more favorable matchup. If the Colts attempt to block him one-on-one too often, Jones has the ability to wreck the play himself.

That is the basic problem elite defensive linemen create.

Their impact is not limited to the plays on which they make the tackle.

They change the blocking equation.

That becomes especially important against Taylor because Kansas City wants to prevent Indianapolis from living in second-and-manageable situations.

Give Taylor five yards on first down and the Colts can do almost anything.

Play-action remains credible.

Daniel Jones can use his legs.

Indianapolis can run again.

Kansas City’s pass rush has to respect multiple possibilities instead of attacking the quarterback.

Stuff the run early, however, and Steve Spagnuolo gets to play a very different game.

That is when the blitz packages expand.

That is when young rushers such as R Mason Thomas can attack.

And that is when Chris Jones becomes particularly dangerous.

My Take

I still think stopping Jonathan Taylor is the key to this game.

Chris Jones being questionable simply raises the stakes.

The good news is that “questionable” does not mean “out.” We will not know the Chiefs’ final active roster until closer to kickoff, and Kansas City has every reason to be cautious with a veteran this early in a 17-game season.

But if Jones plays, I will be watching his movement more than his sack total.

Can he anchor against double teams?

Can he penetrate on early downs?

Does Kansas City rotate him more frequently than usual?

Those details will tell us considerably more about his calf than simply seeing No. 95 in the starting lineup.

The Chiefs showed against Denver that this defense has more young playmakers than it did a year ago.

Sunday could provide the first test of whether those players can absorb additional responsibility when one of Kansas City’s superstars is less than 100 percent.

That is part of becoming a great defense.

Chris Jones can make everybody around him better.

The next step is proving everybody around him can help Chris Jones when he needs it.

Sources: Chiefs-Colts final Week 2 injury report coverage. Kansas City’s September 18 final report lists Jones and Mansoor Delane questionable for Sunday night. 

Derrick Johnson’s Ring of Honor Night Is About More Than Nostalgia

 The Kansas City Chiefs have spent much of the past decade celebrating championships, Patrick Mahomes highlights and a collection of postseason moments that would have seemed almost unimaginable to fans from an earlier era.

Sunday night provides an opportunity to remember one of the players who helped bridge those eras.

Derrick Johnson will be inducted into the Chiefs Ring of Honor at halftime of Kansas City’s Sunday Night Football game against Indianapolis as the newest member of the Chiefs Hall of Fame. The organization officially announced details of the ceremony Friday.

For longtime Chiefs fans, Johnson requires very little introduction.

Kansas City selected him 15th overall in the 2005 NFL Draft, and he spent 13 of his 14 NFL seasons with the Chiefs. He earned first-team All-Pro honors twice, made four Pro Bowls and accumulated 1,262 tackles as a Chief—the most by a linebacker in franchise history. He remains the only player in Chiefs history to record more than 1,000 tackles for the franchise.

Those numbers are impressive.

The era in which he produced them makes them even more meaningful.

Johnson did not arrive in the middle of the Mahomes dynasty.

He played through coaching changes, quarterback changes, losing seasons, rebuilding seasons and eventually the beginning of the Andy Reid transformation.

That matters when remembering his career.

It is relatively easy for younger Chiefs fans to think of Kansas City as a franchise where playoff appearances are expected and Super Bowl conversations begin every September.

That was not always Chiefs football.

Johnson experienced almost every version of it.

He played on the 2006 playoff team under Herm Edwards. He endured the two-win disaster of 2012. Then he remained in Kansas City when Reid arrived and helped the Chiefs begin the climb toward what the franchise eventually became.

Johnson was already 30 years old when Reid coached his first Chiefs game.

Instead of becoming a leftover from the previous regime, he became one of the defensive leaders of the new one.

In 2015, Johnson earned another first-team All-Pro selection at age 33 while Kansas City won its first playoff game in more than two decades.

That longevity deserves recognition.

So does the way he played.

Johnson combined the instincts of an old-school linebacker with the athleticism increasingly demanded by modern NFL defenses. He could diagnose a run, shoot a gap and make a tackle near the line of scrimmage, but he also had the movement skills to survive in coverage.

He became the kind of player Chiefs fans simply expected to see around the football.

My Take

I love that Derrick Johnson will get this moment at Arrowhead.

There are players associated with championships, and then there are players who helped keep a franchise’s identity intact while it was trying to find its way back to championships.

Johnson belongs in that second category.

He stayed long enough to experience both sides.

He knew what two wins felt like.

He also knew what playoff football under Andy Reid felt like.

That makes him an important part of the bridge between the Chiefs many of us grew up watching and the Chiefs the rest of the NFL knows today.

There is another reason Sunday’s ceremony feels appropriate.

Arrowhead itself is now living through its final seasons before the Chiefs eventually move to their new stadium. That makes opportunities to celebrate franchise history inside that building increasingly meaningful.

Johnson made hundreds of tackles on that field.

Sunday night, Chiefs Kingdom gets one more chance to stand and cheer for him there.

He earned it.

Sources: Chiefs — Important Fan Information for Sunday Night vs. Indianapolis. The Chiefs announced the September 20 Ring of Honor ceremony on September 18, 2026. 

The Colts Are 0-1, but Jonathan Taylor Is Exactly the Kind of Player Who Can Ruin a Comfortable Chiefs Night

 The Indianapolis Colts are coming to Arrowhead with an 0–1 record and a 41–23 loss sitting on their résumé.

The Kansas City Chiefs should ignore almost all of that.

They should pay attention to No. 28.

Jonathan Taylor was one of the few Indianapolis players who emerged from Week 1 looking exactly like himself. Against Baltimore, Taylor carried 19 times for 98 yards, caught three passes for another 23 and scored twice. He averaged 5.2 yards per carry, with five runs gaining at least 10 yards.

That is 121 yards from scrimmage on 22 touches in a game his team lost by 18 points.

In other words, Baltimore controlled the football game without really controlling Taylor.

Kansas City cannot assume it will have the same luxury Sunday night.

Chiefs defensive coordinator Steve Spagnuolo has already made it clear that Kansas City expects a much better Indianapolis team than the one that gave up more than 500 yards to Baltimore. Taylor sits at the center of that concern, along with quarterback Daniel Jones’ mobility.

That is the right mindset.

Week 1 results can create dangerous assumptions.

The Chiefs looked organized, fast and physical while limiting Denver to 176 total yards. Indianapolis looked disjointed while Baltimore piled up 506.

Football does not carry those statistics forward to the next kickoff.

What does carry forward is personnel.

And Taylor remains one of the most productive running backs in football.

He rushed for 1,585 yards and 18 touchdowns last season and has spent much of his career proving he does not need perfect circumstances to hurt a defense.

That makes him a particularly interesting test for Kansas City.

The Chiefs’ Week 1 defensive performance was impressive because Denver struggled to sustain anything. Indianapolis has a player capable of generating offense even when the rest of the unit is sputtering.

A six-yard run on first down changes an entire possession.

So does a screen that turns into 18 yards.

Taylor forces linebackers to play downhill, safeties to respect the run and defensive linemen to maintain gap discipline instead of attacking recklessly.

That can also help Daniel Jones.

Kansas City wants Indianapolis in obvious passing situations, where Chris Jones, George Karlaftis, R Mason Thomas and the rest of the pass rush can attack without worrying about play-action or the run.

Taylor’s job is to prevent those situations from happening.

If he consistently creates second-and-4 instead of second-and-9, the Colts’ entire playbook stays open.

The matchup becomes even more interesting because Kansas City’s linebacker depth has already taken a hit with Cooper McDonald moving to injured reserve. That story was covered yesterday, but its consequences start becoming real against a back like Taylor.

Nick Bolton and Drue Tranquill will have a lot to say about whether Sunday becomes comfortable or complicated.

My Take

This feels like exactly the kind of game where a fan base can get overconfident after one great week.

The Chiefs crushed Denver.

The Colts got crushed by Baltimore.

Kansas City is at Arrowhead.

It would be easy to look ahead and assume this should be simple.

Jonathan Taylor is why I will not do that.

The Chiefs defense proved something Monday night, but one dominant performance does not establish a season-long identity.

Sunday gives them a completely different test.

Can Kansas City stay disciplined when one of the best backs in football keeps attacking the same gap?

Can the linebackers tackle without giving away yards after contact?

Can the defense keep Taylor from turning short passes into drive-extending gains?

And most importantly, can the Chiefs force Indianapolis to abandon the run before Taylor gets a chance to take over?

If the answer is yes, I like Kansas City’s chances of making Daniel Jones carry the game.

That is where Spagnuolo wants this matchup to go.

But the Chiefs have to earn that right first.

Stopping Jonathan Taylor is how they do it.

Sources

NFL.com — Week 1 analysis and Jonathan Taylor’s 121-yard performance Read NFL.com’s Week 1 analysis

NFL.com — Jonathan Taylor 2026 game log and career statistics View Taylor’s NFL statistics

Arrowhead Pride — Chiefs expecting Indianapolis to rebound in Week 2 Read the Week 2 Chiefs-Colts report