Case Study 2 — Nineteen Carries Is a Running Back: Teo's El Paso Budget

A high-school case that worked, told the way Teo Arriaga told it to me in his first week in our building. The school, its coaches, and its players are fictional.


Setup

Before he came to Austin, before he was a graduate assistant, Teo Arriaga spent one season as an assistant at a big public high school on El Paso's east side. He was twenty-two, a year out of playing quarterback at a Division II school in New Mexico, and he was hired to coach the quarterbacks. The head coach, Rudy Saenz, called the plays.

The quarterback: Adrian Molina, a senior, five-foot-eleven and about 175 pounds. He was the fastest player on the roster, a smart passer with an average arm, and the team's starting free safety. He also returned punts.

The offense: a shotgun spread with a running back, one tight end most of the time, and a run game built on inside zone, the zone read, and quarterback power.

The problem. Through three games, Adrian averaged nineteen designed carries a game: zone-read keeps (he kept on almost every read, because he was better than the back), quarterback power on third down, and a quarterback draw whenever the offense needed eight yards. He also played around fifty snaps a game at safety.

In Week 5, a fourth-quarter quarterback power on 2nd-and-6 near midfield put Adrian's shoulder into a linebacker's facemask. He got up with a stinger — a burning, numb arm from a nerve stretched in the neck and shoulder. The trainer held him out for the last two series. The sophomore backup went three-and-out, the backup safety was a step late on a post, and they lost by six.

On Monday, Teo asked Saenz for ten minutes and a whiteboard.


What happens

The Monday whiteboard

Teo told me he wrote one number and one sentence:

19 + 50 = 69. A running back takes 19 carries and sits on defense. Adrian takes 19 carries and plays 50 snaps of safety.

"Coach," he said, "nineteen carries is a running back. We have a running back. He's a junior who carries the ball well and never plays defense."

Saenz was not a man who liked twenty-two-year-olds telling him how to run his offense, Teo said, but he was a man who liked winning, and he'd just watched his season's best player sit on a cooler for two series of a game they lost. He asked the question that every head coach asks: "So what do we call instead?"

The budget

Teo's proposal was a one-page card, and it's the same structure as the QB-Run Package in this chapter's Project Checkpoint.

Line Teo's proposal
Designed carries Ten a game, at most. Counted on a sideline card by the defensive coordinator's student manager, who already tracked Adrian's defensive snaps
Who can break it Saenz only, and only in the fourth quarter of a one-score game
QB Power Only inside the 10 or on third- and fourth-and-2 or shorter
Zone read Give-first. Keep only on a clear crash: the end's shoulders turned in and his hips past the back's track
Draw Only against a two-high look with linebackers who bail deep
Finish rules Out of bounds or down before the second defender; never lower your head into a safety; first down is enough outside the 10
The slide A drill, every Tuesday and Thursday, ten reps, feet first
The backup Two series in the first half of every game the score allowed, so he wasn't seeing varsity speed for the first time in a fourth quarter

The piece that made Saenz lean forward, Teo said, wasn't the budget. It was the wide side of the field.

High school hash marks sit 53 feet 4 inches from each sideline — much closer to the sideline than the NFL's 70 feet 9 inches. With the ball on a hash, the wide side ("the field") has room for a quarterback keep to bounce outside; the short side ("the boundary") has a sideline waiting a few steps outside the end. Through three weeks, Adrian's keeps had gone to the side the play was drawn, whatever the hash. Half of them had gone into the boundary, where the keep is a run into the sideline.

Teo's rule: read the end to the boundary, keep to the field. Run the zone toward the short side so the read end is on the wide side, and the quarterback's keep has the whole field to work with.

The game: Week 6, the district rival

The opponent was a crosstown district rival with a good defensive coordinator who had clearly watched the first three weeks. On film, his ends had been coached to crash on every zone read and his safeties to fill the alley hard — the high-school version of the scrape exchange: the end takes the back, the safety takes the quarterback.

Second quarter, tied 7–7. 2nd-and-6 at the opponent's 38, ball on the left hash.

The call was the zone read with the zone run to the left, toward the boundary, and the read end on the right, the field side.

PRE-SNAP: high school, 2nd-and-6 at the opponent's 38, LEFT hash
zone read: run to the boundary (left), read the field-side end

   boundary (short side)                        field (wide side)
  |                                                              |
  |     $           W     M                F                     |
  |  C           E   T   N   E                  *            C   |
  |  X       Y  O   O   O   O   O         H                  Z   |
  |                     R Q                                      |
  |  ball on the left hash: ~18 yds of room       ~35 yds of     |
  |  to the left sideline                          room to the right

📊 Diagram (described): A high-school field with the ball on the left hash. The short side, the boundary, is on the left, with about eighteen yards between the ball and the sideline; the wide side, the field, is on the right, with about thirty-five yards of room. The offense has its tight end and one receiver to the boundary and a slot and a wide receiver to the field. The quarterback is in the shotgun with the running back on his left. The defense has a safety rolled toward the boundary side, two linebackers, and its four linemen; the right end, on the field side, is the read end.

POST-SNAP: the end crashes; the safety has to come from the boundary

  |   $  fills the alley -- on the WRONG side: he expected       |
  |   |  the keep to the boundary                                |
  |   v         W x   M x                                        |
  |            E x  T x  N x  (E) crashes on the back            |
  |  X       Y  O   O   O   O   O     \         H -->]*          |
  |         R <== zone left    Q ----------------------> keeps   |
  |                                    to the field: +17        |

📊 Diagram (described): At the snap the line blocks inside zone to the left and the running back takes his track toward the boundary. The field-side end, the read end, crashes down toward the back, so the quarterback keeps and runs to the right, toward the wide side of the field. The safety whose job is the quarterback had aligned toward the boundary, expecting the keep to go that way, and is now on the wrong side of the formation. The slot receiver blocks the nickel on the field side. The quarterback runs seventeen yards before going out of bounds.

Adrian kept, turned the corner with the whole field in front of him, and went out of bounds at the 21 after seventeen yards. He didn't take a hit. Three plays later the back scored on inside zone, 14–7.

The opponent's coordinator adjusted the way good coordinators do: in the third quarter his ends stopped crashing and sat, staying wide to take the quarterback. Under the give-first rule, that's the easiest read in football. Adrian gave. The running back carried eleven times in the second half, mostly into the space the sitting end had left.

Fourth quarter, 14–10. 3rd-and-goal at the 4. This was what the QB Power line on Teo's card was for. Quarterback power, the back kicking out the end, the backside guard pulling. Adrian followed the puller into the end zone untouched: 21–10. Final, 24–17.

The card at the end of the night

Teo kept the manager's card. It read:

Designed Keeps QB Power Draw Hits taken (offense) Defensive snaps
Week 5 21 13 5 3 14 48
Week 6 8 5 2 1 4 55

Fewer carries, more yards per carry, a quarter of the hits, and seven more snaps at safety. The running back had his first 100-yard game of the season. Adrian finished the year healthy and started both ways in the playoffs.


Analysis

Why it worked: the budget made the read honest. When Adrian kept on almost every read, the zone read wasn't an option; it was a quarterback run with a fake. The opponent's coordinator knew it and crashed his ends at the back with no fear, because the back was never getting the ball anyway — the end was really just getting a head start on the quarterback. Give-first restored the conflict. An end who crashes gets punished by a keep; an end who sits gets punished by a give. "If he can tackle the back, he can't tackle you," as Rome puts it in Austin, only works if the quarterback is willing to give when the end sits.

Why it worked: geography. At high school, the hash moves the arithmetic as much as the read does. A keep to the wide side has roughly twice the room of a keep to the boundary, and the defense's quarterback player — the alley safety — usually aligns where the keep has been going. Running the zone toward the boundary and reading the field-side end put the keep in open grass and put the safety on the wrong side.

Why it worked: the expensive carries got saved for the expensive places. Two quarterback powers, both where one or two yards were worth a hit. One draw, against the look it was built for. Every designed run had a reason to exist on that down and in that place.

What it cost. Adrian's raw rushing yards dropped. A Friday-night crowd that loved watching him run saw less of it, and some parents said so. Saenz took that heat, Teo said, because he'd watched the Week 5 sideline. Budgets always have a constituency against them in the moment. That's why you write them before the season.

The contrast with the NFL case. In Case Study 1, the defense had already priced the quarterback's legs into every third-and-long call, and the scramble ran into a spy. Here, a defense that had over- priced the quarterback — crashing ends, a safety cheating to the keep side — got punished by an offense that made the quarterback a threat instead of a workhorse. The same idea runs through both: a running quarterback is worth most when the defense can't be sure which bill it's paying.


Discussion questions

  1. Teo's card counted "hits taken (offense)" and "defensive snaps" together. Why is the combined number the right one for a two-way player?
  2. Explain the "read the end to the boundary, keep to the field" rule. How would it change on an NFL field, and why?
  3. In the third quarter the opponent's ends sat instead of crashing. What would a give-first quarterback do, and what counter from Chapter 12 would you call next if the sitting end also started squeezing the back?
  4. Saenz could break the budget only "in the fourth quarter of a one-score game." Is that the right exception? Write a better one, or defend it.
  5. The Week 5 loss came partly because the backup quarterback had never played meaningful snaps. How does the "two series in the first half" line protect the starter as well as the backup?

Your turn

Write a one-page budget card for a high-school quarterback who also starts at cornerback and returns kicks. Include: designed carries per game (and why that number), who tracks it, who can break it and when, where QB Power lives, the zone-read rule, the hash rule for keeps, and one practice drill. Then fill in a hypothetical Week 1 line of the tracking card.