Slide 01

You Just Reinvented Peter Gibbons

CxO + VP Engineering

Core thesis

Your AI adoption program did not create productivity. It created a 58-year-old engineer generating "hello world" in 47 languages to hit a 30-query minimum. You trained your best people to perform mediocrity.

Peter finishes his sprint work by 11 AM. Waits until 2:47 PM for product direction. His daughter ships features in hours at a startup. His enterprise spent four months building governance around a metric nobody believes in.

The film quote "My only real motivation is not to be hassled." Same equation. Different decade. More back pain.

Slide 02

You Measured Queries Instead of Output and Got Exactly What You Incentivized

Structural problem

What Peter actually does

Finishes sprint work by 11 AM. Waits four hours for product to send direction that takes two weeks to document specs he could implement in three days.
Runs AI in the background generating documentation nobody reads. Just enough activity to keep his GenAI adoption metrics green.
Hits exactly 31 queries per day. The minimum is 30. His manager tracks it.
Generates variations of "hello world" in different languages. The AI responds: "You're absolutely right!" No question was asked.

What Peter proved he could do

In October, he tested using AI at full speed. Burned through his backlog. Asked for more work.
His manager told him to "find ways to stay busy." HR had concerns about his time tracking.
He can ship features in a quarter of the time. But accelerating triggers scrutiny about "fit" and "trajectory."
His daughter ships in hours. No scrum master. No mandatory queries. Just outcomes.

Slide 03

The Cost of "Just Enough Not to Get Fired"

CFO lens

Sprint work completed 11 AM

Peter finishes his assigned work before lunch. Then waits. Checks stock prices. Generates fake queries. You pay for a full day.

Spec wait time 2 weeks

Product takes two weeks to document specifications Peter could implement in three days. The handoff is the bottleneck.

Potential throughput gain 4x

Peter proved he can ship in a quarter of the time. You told him to slow down. Multiply that across every senior engineer in your org.

It's not that I'm lazy, it's that I just don't care. If I work my ass off and Initech ships a few extra units, I don't see another dime.

Peter Gibbons, Office Space (1999) — and every senior engineer who figured out the math in your org

Slide 04

You Hired People Skills to Manage Engineers Who Build Things

Operating model

The Scrum Master

"You got a case of the Mondays?"

29 years old. Never written a line of production code. Has "people skills." Asks Peter about his velocity. It is Thursday.

The Agile Coach

"Have you tried timeboxing your waiting?"

Holds an "AI-Enabled Agile Transformation" certification from a two-week workshop. Suggests being intentional about blockers. Peter has been writing code since before this kid was born.

The Manager

"Brian in Platform is at 75 queries"

Notes Peter is at exactly 31 queries. The minimum. Brian is at 75. "Now that's someone who really gets it." Brian is generating noise. Peter is generating just enough noise to survive.

The pattern Every layer you added to "support" engineering is a layer that rewards performance theater over shipped work. The governance is the disease pretending to be the cure.

Slide 05

Four Changes. No Reorg Required. Start Monday.

Implementation

01

Kill the spec queue

Remove the two-week spec waiting period. Let Peter write his own specifications. He has 35 years of domain knowledge. He knows what needs building.

02

Kill the query minimum

Eliminate the 30-query floor. Measure shipped work, not AI activity theater. If Peter ships three features with zero queries, that is a win.

03

Kill the handoff delays

Stop letting slower teams gate faster ones. If Peter can implement in three days what takes product two weeks to specify, remove the dependency.

04

Pay for outcomes

Peter has financial goals: two tuitions, seven years to Medicare. You have financial goals: ship faster, beat competitors. These are not in conflict. They are the same goal.

Alignment Peter's incentives and your business goals are not in conflict. They are the same goal. You just built a system that pretends otherwise.

Slide 06

Pay for Outcomes. Or Keep Paying for Theater.

Decision close

The 35-year veteran

Pay Peter for outcomes. Let him ship at full speed. Watch what happens when a 35-year veteran with nothing to prove and everything to lose finally gets permission to do his best work.

Peter is not checked out because he does not care. He is checked out because caring does not pay. You made it that way.

His daughter ships in hours. No scrum master asking about velocity. No mandatory queries. Just outcomes. She is winning. Peter is waiting.

Twenty-six years later The fear is realer. The tools are better. Nothing else has changed. Until you change it.