Matt LaFleur says the quiet part out loud after Packers' Zach Tom disaster

Green Bay Packers v Cleveland Browns
Green Bay Packers v Cleveland Browns | Gregory Shamus/GettyImages

The Green Bay Packers were on a high through the first two weeks of the season, but the team came crashing down on Sunday with a 13-10 loss to the Cleveland Browns. To make matters worse, Green Bay left the game with some bad health news. Starting right tackle Zach Tom, who returned from injury on Sunday, had to leave the game after just one play.

Once fans witnessed that, it was clear the Packers made a mistake by putting Tom back into the lineup too soon. Matt LaFleur admitted that following the loss. The head coach said it was a mistake to rush Tom back so soon.

"Obviously, yeah. If a guy plays one play. We've got to have some discussions. We can't allow that to happen. It's disappointing when he plays one play," said LaFleur.

Matt LaFleur admits Packers made a mistake by letting Zach Tom play

The veteran tackle injured his oblique in Week 1 and missed Green Bay’s Week 2 game. Tom returned to practice ahead of the Week 3 game, despite admitting that he was still in pain. However, the offensive lineman is a competitor and was committed to showing up for his team. He did that on Sunday, but clearly wasn’t ready to return.

That's where the team was supposed to step in and protect him from his self. The majority of the time, players want to tough it out and play through whatever pain they’re dealing with. While that’s commendable, it could be detrimental. That’s why teams evaluate the situation, and help the player make the best decision.

The Packers didn’t do that. Now they have to hope that Tom didn’t suffer a setback that will make his time sidelined even longer.

It’s possible the one play could’ve undone any recovery progress the lineman made, and his return-to-play journey has to start over. Hopefully, that’s not the case, and Green Bay will have a healthy Tom back on the field sooner rather than later.

Loading recommendations... Please wait while we load personalized content recommendations