Inside Read 3-2-1: Friday is about more than the scoreboard

Oregon gets Portland State next, and in most seasons that sentence would pretty quickly turn the page from whatever happened the week before. The Vikings are 0-3, have allowed 131 points, and are coming off a game in which North Dakota piled up 627 yards of offense in a 47-23 win. Portland State also lost 53-20 at San Diego State a week earlier, so there is nothing about Friday night’s matchup that suggests Oregon should be in another fourth-quarter fight.

That is also why I think this week is a little more interesting than the matchup itself.

Oregon does not need to prove it can beat Portland State. It needs to start proving that some of the things exposed in Stillwater are actually being corrected rather than simply covered up by a significant talent advantage. There is a difference, and with USC waiting immediately afterward, Oregon does not have much time to figure out which one Friday becomes.

Here are three observations, two questions, and one prediction coming out of Oklahoma State and heading toward Portland State.

THREE OBSERVATIONS

1. The Oklahoma State game looked more like a preparation problem than a collection of isolated mistakes

There were enough individual mistakes Saturday to fill an entire film session. Oregon missed tackles, lost contain, gave up explosives, struggled with movement along the offensive line, committed far too many penalties, and never established the kind of offensive rhythm we expected. But the more I replay the game in my mind, the more difficult it is to separate all of those individual mistakes from the larger question of preparation.

Dan Lanning essentially went there himself afterward. “I didn’t prepare our guys well enough to play,” he said while taking responsibility for the loss, later adding that Oregon needed “a higher temperament in practice, a higher level of focus in practice” and had to become faster at adjusting when opponents showed something different. He even acknowledged that he did not know whether Oregon had given its players enough of the looks in practice that eventually appeared in the game.

Like everyone else, that reality grabbed my attention within seconds. Why? Because the numbers I have been working through suggest something broader than Oregon simply losing a few one-on-one battles. Our first Offensive Predictability Score for the Oklahoma State game came out at 81 – far too predictable. At the same time the defense produced a 31 Defensive Chaos Score despite creating two interceptions. In these two ratings, you want a low predictability score for offense and a higher chaos score for defense. The Ducks were the opposite of where they should have been.

Oregon was giving away too much information offensively while creating too little uncertainty defensively, and those two things happening at the same time made the game look way too comfortable for Oklahoma State.

The Cowboys averaged 9.2 yards per play in the first half and spent much of the afternoon ahead of the chains. Oregon, meanwhile, was throwing on every third-and-4-or-longer situation we charted and had enough other sequencing and personnel tendencies that Oklahoma State players talked afterward about the details they had uncovered through film study. That does not mean the Cowboys knew every play before it happened, but it does mean Oregon needs to take a hard look at what its own film is telling opponents before worrying about what information might escape from a closed practice.

This is where Friday matters. Oregon can change some of those answers immediately, even against an opponent it should overwhelm.

2. Portland State cannot erase the Oklahoma State result, but it can tell us whether Oregon is beginning to fix it

Portland State has had a difficult start under Chris Fisk, but the Vikings have not been completely devoid of offense. They gained 357 yards while leading sixth-ranked UC Davis 21-0 at halftime in the opener, produced 375 yards and 21 first downs against San Diego State, and threw for 233 yards against North Dakota on Saturday. Their bigger problem has been sustaining any of it while preventing their opponent from eventually taking control.

That creates an unusual evaluation game for Oregon because I do not think the score will tell us very much unless something goes terribly wrong. A 52-10 Oregon win would look perfectly normal on Saturday morning, but I am going to be much more interested in what happened inside those numbers. Did the offensive line handle movement better? Did Oregon establish the run without becoming obvious about how it wanted to run it? Did the defense win first down and create the third-and-long situations it rarely found in Stillwater? Were there missed tackles and coverage busts that Portland State simply did not have the athletes to exploit?

While those are considerably more useful questions than whether Oregon covers whatever the final point spread becomes, I don’t know that we will truly understand those answers as real answers or a sort of ghost answer. They are expected to do those things against Portland State.

Portland State allowed 394 yards against San Diego State before getting overwhelmed 53-20, then surrendered 627 to North Dakota. Oregon ought to be able to move the football, which means Drew Mehringer has a chance to use the game for more than rebuilding confidence. I would like to see Oregon deliberately break some of its own tendencies, use Hill and Davison in ways that make personnel less informative to a defense, and get the offensive line repetitions against fronts and movement designed to address what Oklahoma State exposed rather than simply calling the easiest plays available against an overmatched opponent.

The same applies defensively. Portland State has thrown the ball 91 times over the past two games, including 52 attempts against San Diego State, so there should be opportunities to work through pressures, coverage communication, and some of the pass-rush discipline that disappeared Saturday. Oregon should dominate those situations, but how it dominates them will tell us more than the final margin.

3. A player-led team has to be accountable when things go wrong, too

We heard the phrase player-led repeatedly throughout fall camp, and I liked what it seemed to represent. Players wanted more noise at practice, more repetitions, and more responsibility for setting the standard themselves rather than waiting for coaches to create it for them. That all sounds good in August when everybody is undefeated, and the conversation is about what a veteran team might become. I think the more meaningful test comes after something like Stillwater.

Dan Lanning has taken a significant amount of responsibility for Saturday, and he should. Preparation belongs to the head coach and his staff, and Lanning did not hide from that when he said, “I didn’t prepare our guys well enough to play,” while also acknowledging Oregon did not have a good enough plan on either side of the ball. He later questioned whether the Ducks had even provided enough of the looks in practice that Oklahoma State eventually showed. Those are coaching issues, and Lanning putting his name on them rather than deflecting blame is exactly what I would expect from the person ultimately responsible for the program.

But preparation was only part of what happened. Oregon also missed tackles, lost contain, committed costly penalties, busted assignments and failed to execute in moments when the call itself was not the problem. Lanning made that distinction afterward, saying there were certainly better calls Oregon could make but that players still had to execute the ones they were given. That is where I think the idea of a player-led team becomes more complicated, because leadership cannot mean the players set the standard when things are going well while the head coach absorbs almost all of the public accountability when they are not.

Teitum Tuioti was the exception Saturday because he was also the only Oregon player made available to the media. He did not duck anything. He said the defense kept “killing ourselves,” included himself among the players who had not done their jobs and said the correction had to begin immediately in practice. He even went where most players probably would not when he wondered whether Oregon had become too lackadaisical or had spent too much time reading its own press clippings. Later, when asked where the championship defense everyone expected actually stood, his answer was pretty simple: “We can get there, we’re not there right now.”

I give Tuioti a lot of credit for that, but I also think a truly player-led program has to extend beyond one player answering for an entire locker room. Accountability to teammates obviously happens behind closed doors, and much of it probably should. There is also an accountability that comes with representing Oregon publicly — to the people who follow the program, fill Autzen Stadium and listen all offseason when players talk about championship standards. That does not mean putting players on display after a bad game or asking them to publicly blame one another. It means the leaders who have embraced ownership of the team should also be willing to stand in front of difficult questions when that standard is not met.

That is one of the things I will be watching this week as much as anything Portland State does Friday night. Tuioti said afterward that the first two games were not to Oregon’s standard and that “now there’s a problem. We’ve got to fix that problem.” If this team is genuinely player-led, fixing it should include players holding each other accountable in practice, demanding better execution on the field and, at least occasionally, being willing to explain publicly what that leadership looks like when Oregon falls short.

TWO QUESTIONS

1. Can Oregon fix its offensive tendencies without simply hiding them behind superior talent?

This might be my biggest question Friday because Oregon could probably run a fairly basic offense and still score plenty of points against Portland State. That would solve the immediate problem of winning the game, but it would do very little to answer what awaits at USC.

The 81 Predictability Score against Oklahoma State was not produced simply because Oregon passed 60% of the time. It came from the situations surrounding those calls: six of seven first-half possessions opening with a run, 11 straight passes on third-and-4 or longer, a 68% pass-following-pass rate, and the personnel tendencies Oklahoma State said it had identified on film. There was enough information available before some snaps that the defense’s decision tree became much smaller than Oregon should want it to be.

That does not mean Mehringer needs to spend Friday emptying the playbook. In fact, I would argue almost the opposite. This is a chance to run ordinary concepts from different presentations, break a few personnel tendencies, and make sure that when USC starts doing the same self-scout Oklahoma State did, some of the answers it thinks it has are no longer correct.

If Oregon scores 50 but still gives away the same information, the offense will have had a good night without necessarily becoming a better offense.

2. Can the defense manufacture disruption instead of waiting for turnovers to create it?

The strangest thing about Saturday might be that Oregon intercepted Mestemaker twice and still finished with a Defensive Chaos Score of only 31. Normally two takeaways would be evidence of a defense making the quarterback uncomfortable, but these came on tipped passes while Oklahoma State otherwise moved the football with remarkable consistency.

That is why I want to see a different kind of defensive performance Friday. Not simply interceptions or a couple of sacks after Portland State gets behind the chains, but tackles for loss on normal downs, pressure without sacrificing rush-lane integrity, tighter throwing windows and an ability to make an offense abandon what it wanted to do.

Oregon’s defense was supposed to be capable of creating that kind of environment this season. Through two games, Tuioti’s assessment is probably the fairest one available: they might get there, but they are not there yet.

Portland State is not going to answer whether Oregon has a championship defense. It can give us our first evidence that the Ducks have started moving in that direction.

ONE PREDICTION

The klahoma State loss will change Oregon more than any comfortable Portland State win possibly can

I am going bigger picture with this one because I think Saturday created the first genuine inflection point of Oregon’s season.

My prediction is that the version of Oregon we see by November will look meaningfully different from the one that played the first two games, particularly schematically. I expect more deliberate tendency-breaking on offense, a greater effort to create favorable running looks rather than simply relying on the offensive line to win them, and a defense that becomes more aggressive about manufacturing disruption when four-man pressure is not getting there.

That does not mean every problem disappears, and I am not ready after two games to predict that Oregon simply turns back into the national championship contender everyone imagined in August. The loss removed the luxury of assuming that identity already existed. Oregon has to build it now.

But there is also something useful about having assumptions broken this early rather than discovering their flaws in November. Lanning said afterward that Oregon had to identify the holes, patch them, and attack them rather than throwing away everything that has worked in the past. That sounds simple when a coach says it at a podium. The next several weeks will tell us whether the Ducks can actually do it.

Friday is the first chance to find out.