Fantasy Football Week 2: Stop Chasing Week 1 Points. Chase Usage.

Week 1 creates one of the easiest traps in fantasy football.

A player scores twice, suddenly he looks indispensable. Another player finishes with seven fantasy points and managers start wondering whether the draft pick was a mistake. Waiver wires move, Week 2 fantasy football rankings change and lineup decisions start being made from one game's box score.

But the box score is usually the least interesting part.

One week is nowhere near enough time to know how good an offense will be, how efficient a player will remain or which touchdown rates are sustainable. It can, however, tell us something much more useful: how teams actually intend to use their players.

That distinction matters heading into Fantasy Football Week 2.

Instead of asking who scored the most fantasy points in Week 1, the better question is who was actually on the field, running routes, earning targets, handling carries and getting opportunities in valuable situations.

Those are the numbers that can change a fantasy decision.

Fantasy Football Week 1 Results Tell You What Happened. Usage Tells You Why.

Fantasy scoring compresses an entire game into one number.

That is convenient for standings. It is not always convenient for analysis.

Touchdowns can completely reshape a player's weekly score. One long reception can turn an otherwise quiet afternoon into a strong fantasy finish. Game script can create extra passing volume or eliminate it. A running back can handle significant work and still finish outside the top scorers because the touchdowns went somewhere else.

That is why Week 2 fantasy football analysis should begin underneath the points.

For running backs, carry share matters, but so do targets and passing-down usage. For wide receivers and tight ends, simply counting targets is not enough. Routes run and route participation tell us whether the player consistently had an opportunity to earn those targets in the first place.

Snap share can help too, although it needs context. A receiver can play plenty of snaps because the offense is running the ball. A running back can lose early-down work while maintaining the third-down and receiving opportunities that are especially valuable in PPR formats.

The goal is not to find one magic stat.

It is to figure out whether Week 1 revealed a real role.

Jalen Coker's Fantasy Points Were Huge. His Role Is More Interesting.

Jalen Coker provided one of the loudest fantasy performances of the opening weekend.

Carolina's receiver caught eight passes for 138 yards and two touchdowns against Chicago. NFL.com's official game log confirms the 8-138-2 receiving line.

It would be easy to stop there.

Two touchdowns and 138 yards will naturally move a player up fantasy football waiver wire lists. But those touchdowns are not the strongest reason his Week 1 matters.

Coker reportedly drew nine targets while running 40 routes, with a 24.3 percent target share. That means the production did not come from two random catches on a limited number of snaps. He was regularly involved in Carolina's passing structure.

There is a major difference between a receiver catching three passes for 100 yards on four targets and a receiver producing while repeatedly being asked to run routes and command opportunities.

Both might finish with similar fantasy totals.

Only one performance gives us strong evidence that the opportunity could exist again.

That does not mean Coker will produce 138 yards every week. It means Week 2 fantasy rankings should care about the process underneath the 138 yards, not attempt to project another 138-yard game.

That is a much more defensible way to react to an early-season breakout.

The 49ers Backfield Shows Why Carries Alone Can Mislead You

San Francisco gave us a different kind of Week 1 problem.

Rookie Kaelon Black received 14 carries in the opener against the Rams. Christian McCaffrey had 10.

If your analysis stops at rushing attempts, that immediately looks like a major backfield shift. NFL.com's Week 2 waiver analysis specifically highlighted Black's 14 carries, noting that he received four more than McCaffrey.

But there was another side to the workload.

McCaffrey reportedly drew eight targets and caught five passes, while Black had just one target. Black clearly earned meaningful rushing work, but McCaffrey remained heavily involved as a receiver.

That is exactly why fantasy football usage has to be read as a profile instead of a single number.

Black's 14 carries matter. They tell us San Francisco was comfortable giving the rookie legitimate work instead of treating him purely as an emergency backup.

McCaffrey's receiving involvement matters too. It tells us that fewer carries did not necessarily mean he disappeared from the offense.

The useful Week 2 takeaway is not that one number has suddenly replaced everything we knew before the season. It is that the distribution of opportunities has changed enough to deserve attention.

That is what early-season information is supposed to do. It should update the assumptions, not erase them.

Rhamondre Stevenson Shows Why Targets Can Change a Running Back's Role

Running back analysis gets especially misleading when it focuses only on rushing yards.

Rhamondre Stevenson's Week 1 is a useful example.

With TreVeyon Henderson dealing with an ankle injury, Stevenson handled 75 percent of New England's running back carries and caught five of six targets for 44 yards, according to NFL.com's Week 2 fantasy analysis.

The six targets may ultimately matter more for fantasy evaluation than a small difference in rushing efficiency would.

Targets are valuable opportunities, particularly in PPR and half-PPR leagues. More importantly, receiving usage can keep a running back involved when game script moves away from traditional rushing attempts.

That does not mean one six-target game establishes a permanent receiving role. Henderson's availability can alter the backfield. Opponent, score and personnel packages can change how New England distributes touches.

But now there is something concrete to evaluate.

Instead of asking whether Stevenson scored enough fantasy points last week, managers can ask whether the receiving opportunities continue when the backfield is closer to full strength.

That question tells us much more about his rest-of-season fantasy football value.

D'Andre Swift Is a Good Example of Separating Production From Repeatable Opportunity

D'Andre Swift's opening game produced exactly the sort of fantasy score that can overwhelm analysis.

Against Carolina, Swift rushed 18 times for 124 yards and scored three rushing touchdowns.

The three touchdowns obviously mattered enormously to his Week 1 fantasy finish.

But projecting another three rushing touchdowns would miss the point entirely.

The useful information is that Chicago trusted Swift with 18 rushing attempts while its offense generated enough scoring opportunities for him to repeatedly finish drives.

There are two different pieces of information there.

The workload tells us something about Swift's role. The touchdowns tell us what happened with those opportunities in one particular game.

The first can help inform future decisions.

The second needs much more evidence before it becomes an expectation.

That separation becomes especially important when building fantasy football Week 2 projections. A projection should not simply move last week's touchdowns into this week's column.

Routes, Targets and Carries Need Context Too

There is a danger in replacing one oversimplification with another.

“Fantasy points do not matter, just follow volume” is not much better than blindly chasing last week's scoring leaders.

Volume has to be interpreted.

A receiver can earn 12 targets because his team attempted 55 passes while trailing for most of the afternoon. A backup running back can collect fourth-quarter carries after the game is effectively decided. A tight end can run plenty of routes but rarely become the quarterback's first read.

This is why early fantasy football start sit decisions work better when several pieces agree.

Was the player consistently on the field? Did he participate when the team passed? Did actual opportunities follow that playing time? Were those opportunities concentrated in meaningful situations? Is there an injury, game script or unusual circumstance that could disappear one week later?

The stronger the answers, the more seriously Week 1 should change the evaluation.

One statistic rarely answers all of that.

Week 2 Is About Updating Your Priors, Not Rewriting Them

The hardest part of 2026 fantasy football after Week 1 is deciding how much new information deserves to matter.

Ignore everything and you miss genuine role changes.

React to everything and one unusual Sunday can completely distort your roster.

The better approach sits between those extremes.

Preseason projections, historical performance and expected roles still matter. Week 1 simply gives us our first meaningful set of regular-season evidence to compare against them.

When the evidence agrees with the preseason assumption, confidence in that role can increase.

When it contradicts the assumption, investigate why.

When the only thing that changed is the player's fantasy-point total, be careful.

That distinction matters whether you are working through the Week 2 fantasy football waiver wire, comparing two flex options, checking updated fantasy rankings or trying to understand why a highly drafted player disappointed in his first game.

Fantasy points are the outcome.

Usage is part of the explanation.

And after one week of football, the explanation is usually where the better information is hiding.

The better Week 2 question is not, “Who scored the most last week?”

It is: What did Week 1 teach us about the opportunities that might still be there next week?