Drew Lock’s rookie buzz silenced by Kansas City Chiefs

The Denver Broncos are much better off with Drew Lock under center for the long term, but the short-term buzz was silenced on Sunday.

It was a wonderful two-week ride for the Denver Broncos.

For the last few years, ever since Peyton Manning called it quits back in March, 2016, the Broncos have been searching for signs of life—anything, really—at the quarterback position. A wonderful coaching job by Gary Kubiak made Trevor Siemian look somewhat passable, but even then, Denver was never going to beat the Kansas City Chiefs or contend for another Super Bowl.

Siemian came and went. So did Paxton Lynch. John Elway traded for Case Keenum and then again for Joe Flacco. The carousel spun around, the only constant was one losing effort after another. Soon enough, the seat began to heat up under Elway—that is, until a few weeks ago when the Broncos finally decided to install second-round pick Drew Lock as the starting quarterback.

Those two weeks were a good time.

During his first two NFL starts, Lock had excitement about the team’s future as high as the city’s elevation. First, he put away Philip Rivers and the Los Angeles Chargers in a home win showing a nice touch and two touchdown passes. The very next week, he went on the road and bested Deshaun Watson and the AFC South-leading Houston Texans. In that game, he put up another three touchdown passes and showed the cannon of an arm and confident approach that made him a highly regarded prospect in the first place.

For two weeks, it seemed as if the Broncos had their answer. That is, until they met the Chiefs.

Let’s be clear: one week doesn’t change things for Denver. Lock is still a very impressive young quarterback who has a bright future in the AFC West. He was playing in front of family and friends in the very home of his childhood favorite team in the midst of snow against a Super Bowl contender. Lock will have better days, even at Arrowhead, and Denver has every reason to still feel solid about the future under center.

That said, the way the Chiefs silenced the league-wide buzz on Sunday was something to behold.

• In the two games prior to playing the Chiefs, Lock had completed 72 percent of his throws. On Sunday, against the Chiefs, he completed only 45 percent (18 of 40).
• During the previous two games, Lock had been hit 7 times and had taken a single sack. On Sunday, the Chiefs hit Lock 9 times and racked up 2 official sacks.
• Lock’s passer rating through his first two games was 111.4. Against the Chiefs, it was a paltry 50.8.
• In wins over the Chargers and Texans, he had 5 touchdowns. He wouldn’t throw a single score against K.C.

Only 12 times this season has a quarterback had that low of a completion percentage and only four games have featured a passer rating that low as well. In short, Lock turned in one of the single worst quarterback performances of the year at Arrowhead.

That’s what the Chiefs did to Drew Lock and the momentum he’d gained in his first two starts.

The future is undoubtedly brighter for the Broncos, as we’ve already said, with Lock under center. Even after today’s performance, no one is talking about going back to Flacco or inviting other options. Lock has earned the benefit of the doubt and will not only finish out the season as the starter but should have the positioned locked down (pun not intended) for the next year or more.

That said, the Chiefs put on a clinic on Sunday against a division rival in a game they could have easily overlooked. It’s this sort of focused play, even in the face of injuries or the elements, that make them so dangerous. The AFC was already on notice about this team’s offense, but the Chiefs are playing dominant football on both sides of the ball. Drew Lock was just the latest witness to the damage.