Justin

Watson

One of Watson’s missed connections was a ball that was thrown behind him that nevertheless should have been caught. Somehow the Chiefs’ No. 3 pass catcher with 460 regular season yards, Watson was an abysmal 66th in receiver yards per route run (1.25). He also committed four drops and lost a fumble. Hardly ideal when you’re a role player. Watson bettered 50 yards one time after Week 5. Heading into his age-28 season, Watson is signed for $1.47 million in 2024, but there is little chance he sees that full salary. If he’s back at all in Kansas City, it should be at a reduced rate.

Skyy Moore is on injured reserve and Kadarius Toney missed this game because of a hip injury, keeping Watson in the starting rotation for Week 16. He finished third on the team in targets and was just one shy of Travis Kelce. In a potential shootout with the surprisingly lively Bengals, Watson will have solid odds of finding the end zone again in Week 17. He will rank as a touchdown-or-bust WR5.

Watson caught only one pass, but it was a big one on a three yard dime in tight coverage to give the Chiefs a 21-14 lead. In most seasons, it might seem foolish to have Watson on your fantasy roster, but no other Chiefs receiver aside from Rashee Rice seems to be stepping up to do anything. However, Watson still is only a deep league target.

Watson committed three ugly drops and was targeted twice downfield on routes that were run incorrectly, adding some context for box score watchers. His 11 targets handily led the team but the mental errors were the true story here. His third and final drop came on fourth-and-25 with under a minute remaining as he saw the ball glide effortlessly through his mitts on a target beyond the first down marker, ending the game in the process. Head coach Andy Reid could be seen laying into the young receiver on the sideline on multiple occasions, which would be more telling of potential future snap rates had fellow downfield option Marquez Valdes-Scantling not committed two drops of his own, including a would-be go-ahead touchdown with under two minutes left on the clock down the middle of the field with nobody within three yards.

Watson supposedly led the Chiefs in targets, though you wouldn’t know that by looking at his counting stats. Patrick Mahomes attempted to find him for a few deep shots but the two were unable to connect in this game. Watson will pop up for the occasional long catch but isn’t a reliable fantasy option.

He finished third on the team in receiving yards and tied for fourth on the team in targets. He may wind up being more valuable in fantasy than Kadarius Toney and Skyy Moore, but that’s not saying much.

Watson was ruled out before Sunday’s contest, and could miss several weeks after suffering a dislocated elbow in Week 6. The Chiefs will have all of their key playmakers ready to go in Sunday’s divisional tilt with the Bolts.

Watson avoided IR but was never expected to play this week. The veteran receiver is out for Sunday and is likely to miss the next two games before returning. Watson’s absence will open up snaps on offense for Kadarius Toney.

Watson’s elbow injury isn’t nearly as serious as it appeared to be on Thursday against the Broncos. Watson won’t practice Wednesday and appears to be a long shot to suit up in Week 7 against the Chargers. That could open up more targets for the rest of the underwhelming KC wideouts.

Things could’ve been much worse for Watson, who was forced from Thursday Night Football with a nasty elbow injury. The veteran receiver is still expected to miss some time, but as Rapoport noted, his return should be “sooner, rather than later.”