Unheralded Chiefs receiver proves doubters wrong after game-defining play in Week 12 vs. Panthers
Kansas City Chiefs WR Justin Watson managed a bit of vindication in the final minute of Week 12's tilt with the Carolina Panthers. A few times during the Week 12 win, Watson was subject to outside criticism. He dropped a pass in the second quarter on second down on a drive that stalled in the red […]
Kansas City Chiefs WR Justin Watson managed a bit of vindication in the final minute of Week 12's tilt with the Carolina Panthers.
A few times during the Week 12 win, Watson was subject to outside criticism. He dropped a pass in the second quarter on second down on a drive that stalled in the red zone. Later, DeAndre Hopkins was on the sidelines in the red zone on third down, while Watson entered the game. The drive again stalled and Watson caught some heat from fired-up fans on social media.
Watson played the most snaps of any wide receiver in Week 12, which left many throughout the Chiefs Kingdom scratching their head. Why do the Chiefs keep relying on Watson, when they could use DeAndre Hopkins, JuJu Smith-Schuster, Mecole Hardman, or even Xavier Worthy? Watson helped the Chiefs gain the slightest advantage in the game's defining moment. He knows the scheme and does the dirty work better than perhaps every other receiver on the roster.
When Patrick Mahomes took off to scramble on his 33-yard run in the final minute of the game, every single Panthers defender on the left side of the field was looking at No. 15. They saw a potential opportunity to crash down and limit an explosive play from the quarterback, but Watson didn't let them have that moment. No. 84 blocks, not one, but two defenders on the play, clearing the lane for Mahomes to have such a long scramble.
If Watson hadn't made either block, Mahomes likely wouldn't get the team into field goal range, let alone get a first down on the play. It's the type of play that will be forgotten in the grand scheme, but it could have been the difference between a win and a loss if it's not made. As it turns out, Watson was intentionally put in that position from a schematic standpoint.
“I kind of have a route that’s meant for the scramble drill,” Watson told reporters after the game. “Whenever he releases, I work with him. Playing with Pat and his body language and where the guys are at when he’s going to tuck (the ball) and run, I saw a look in his eyes, and I threw a block for him. He made a great cut.”
Mahomes didn't even know for certain that it was Watson who made the block after the game, but he had a strong suspicion.
"You're at the end of the game, you're trying to get us in field goal range," Mahomes told CBS Sports sideline reporter Evan Washburn after the game. "I think it was Justin Watson maybe? Someone made a hell of a block. . ."
He reiterated this to reporters on the podium following the win.
"Yeah, we expected a man coverage," Mahomes elaborated. "They got into a type of like match zone, so they covered up our routes, and I got off to the left. And at that point in the game, yards are more important than getting out of bounds. With the three timeouts, I try to just cut through. And I think it was Justin Watson. I haven't seen the video, but I thought he got a great block."
Chiefs K Spencer Shrader is already proving his new team right for signing him after Harrison Butker’s injury
Kansas City Chiefs K Spencer Shrader is proving his new team right on and off the field.
