Kaleb Johnson Did Not Play a Snap and Green Bay's Backfield Is Still a Mess Without Josh Jacobs
By Verdexed Fantasy Desk

Green Bay lost 39-22 at Minnesota on Sunday, and the most useful information in the box score was who did not appear in it. Kaleb Johnson, the running back the Packers acquired from Pittsburgh after Josh Jacobs was placed on the commissioner's exempt list, did not play a single offensive snap.
Instead Green Bay used two backs. MarShawn Lloyd carried 13 times for 37 yards. Chris Brooks carried seven times for 29 yards and led the position in snaps. That is the entire picture, and it is worse for fantasy managers than a clean committee would be.
The setup was supposed to be simple
Jacobs has been unavailable since late August, when the league placed him on the exempt list following a legal matter that began with an arrest in Wisconsin in May. The initial charges were later reduced to two misdemeanors by the Brown County District Attorney. While on the exempt list he is paid and may be at the facility for meetings, individual work and medical treatment, but he cannot practice or play. The Packers have publicly expressed hope he can play at some point this season, which is not a timeline.
Green Bay responded by trading for Johnson, a back with prior familiarity with members of the coaching staff. The reasonable expectation was a committee with Johnson getting meaningful early-down work.
Instead Johnson was a healthy inactive at the position group level, and the Packers split the job between a former third-round pick who has struggled to stay on the field and a journeyman.
What the usage actually means
There are two readings, and they point in different directions.
The first is that Johnson simply was not ready. Acquired late, new playbook, limited practice reps, and a coaching staff unwilling to put a back on the field who cannot handle protection assignments. If that is the explanation, Johnson's role grows over the next two or three weeks and he becomes the back to own.
The second is that the staff has looked at him and decided he is not part of the plan. Zero offensive snaps in a game where the team ran 20 times between two other backs is a strong statement if it is a deliberate one.
The tiebreaker is the practice report and the coach's language this week. A staff that intends to use a player says so. A staff that has moved on gets vague.
Game script poisoned the well
It is worth noting the Packers trailed badly. Green Bay led 22-10 in the third quarter and then gave up 29 unanswered points, which meant a lot of the second half was spent throwing. Jordan Love finished 21 of 42 for 387 yards with two touchdowns and an interception. Christian Watson caught six passes for 147 yards and two scores, including an 81-yard touchdown.
Twenty carries as a team in a game you led by 12 is low, and it is low because the second half went sideways. A normal game gives the backfield 24 to 28 carries, which changes the individual lines without changing the split.
The Packers' decision to go for a fourth-and-one rather than take a field goal after a Minnesota offsides penalty, with Love stopped for no gain on the sneak, was the turning point the coaching staff will answer for this week. That is a coaching story, not a fantasy one, but it is the reason the run volume evaporated.
The Verdexed model take
The model projects Lloyd at roughly a 45 percent share of Green Bay's designed runs, Brooks at 35 percent, and the remainder unassigned pending clarity on Johnson. That unassigned bucket is the important part: the model is explicitly declining to project a back who has not played, which is the honest treatment of zero snaps.
On the offense as a whole, Green Bay's projected pass rate moved up after Week 1, driven by Love's 42 attempts and by a defense that surrendered 29 points in a half. That helps Watson and the receivers considerably more than it helps anyone in the backfield.
The model's clearest conclusion: none of Green Bay's three backs currently projects as a startable fantasy asset in a 12-team league. A 45 percent share of 22 carries in a pass-leaning offense is a low-end flex at best, and the touchdown equity is split three ways whenever Green Bay reaches the goal line.
Fantasy fallout
Lloyd is a hold, not a start. Thirteen carries for 37 yards is 2.8 yards per attempt, and the volume is not large enough to overcome that efficiency. He is a bench stash with upside if Brooks fades or if Green Bay commits to him.
Brooks is not worth a roster spot in most formats. Leading the snap count in a 20-carry game is not a fantasy role.
Johnson is the speculative add. If you believe the first explanation above, that he simply was not ready, then the cheapest moment to acquire him is right now, while the box score says zero. That is a bench-slot bet in a deep league, not a FAAB priority.
Christian Watson is the actual Green Bay player to own out of this game. A 147-yard, two-touchdown line with an 81-yard score, in an offense that just showed it will throw 42 times when it has to, is the real takeaway.
Betting angle
Green Bay's rushing props are the market to fade. The Packers have three backs, no declared starter, and a pass-leaning profile. Any individual Packers back's rushing yardage line that opens above a low baseline is priced on a role nobody has.
The team total is more interesting. Green Bay scored 22 and lost by 17, which the market will read as an offensive problem. It was mostly a defensive collapse. That distinction tends to create value on the offense in the following week.
What's next
Jacobs' status is the ceiling on all of this. Nobody in Green Bay's backfield is a weekly starter while the depth chart has three names and no clarity, and nobody becomes one until either Johnson earns snaps or Jacobs becomes available. Watch the Wednesday practice report and listen to how the coaching staff talks about Johnson. That is the whole fantasy signal this week.