The Product Owner Is the Starting Pitcher

People often describe a product owner in tidy terms.

The person who organizes requirements.
The person who sets priorities.
The person who writes specs and talks to the development team.

None of that is wrong. It is just too small.

A good PO does not simply pass requirements around. A good PO controls the early shape of the product game. What pitch to throw. Which batter to challenge. Which fight to avoid. Where to spend energy. How long to stay on the mound.

In that sense, a PO is less like a manager and more like a starting pitcher.

The manager sees the whole game from the dugout. The catcher calls each pitch. The fielders handle their zones. But the first rhythm of the game starts in the pitcher’s hand.

If the starter collapses in the first few innings, the whole team plays from behind. The bullpen gets used too early. The defense tightens up. The offense gets impatient. If the starter holds the game through the fifth or sixth inning, the team can play its own baseball.

Product work is similar.

When the PO defines the problem poorly, the development team starts the game already down runs. The customer problem stays vague while features keep piling up. Priorities wobble. Meetings multiply. Eventually someone asks the question that should have been asked at the beginning.

“Why are we building this?”

If that question comes too late, the damage is already there.

The first pitch matters

For a starting pitcher, the first pitch is not just the first pitch. It is a signal. Are we attacking the zone today? Are we trying to draw a chase? Are we going to trust the fastball? The hitter, catcher, and bench all start reading the game from that first throw.

For a PO, the first pitch is problem definition.

What problem is this product trying to solve?
Does the customer actually feel that pain?
Does it need to be solved now?
If we solve it, does anything valuable change for the business?

If this part shakes, everything after it shakes.

Too many product teams talk about features too early. What the screen should look like. Where the button should go. Which technology to use. But there is a pitch that has to come before all of that.

“Where exactly is this customer stuck?”
“Is the pain strong enough that they would pay to remove it?”
“If we solve this, will their behavior actually change?”

If the PO does not ask these questions, the team is not pitching. It is just swinging its arm.

You cannot throw every pitch at full power

A starting pitcher does not throw every pitch as hard as possible. The pitcher has to manage the whole game. Some batters should be retired quickly. Some deserve a tougher fight. Sometimes giving up one run is better than opening the door to a big inning.

A PO has the same job.

If every requirement receives the same weight, the product breaks. If every customer request goes in, the roadmap turns into a patchwork. If everything the CEO mentions becomes urgent, the team loses direction. If developers build whatever seems interesting, the product slowly becomes an internal toy.

A PO’s job is not to add more. It is to cut.

The PO has to decide which fight the release must win. Which batter can be walked. Which market can wait. Which feature does not need to exist yet. Which workflow does not need automation yet.

A good PO does not create more work. A good PO leaves only the fights the team can win.

If you only have one pitch, hitters will figure you out

A great fastball is not enough if it is the only thing you throw. A starter needs a fastball, slider, curveball, changeup, and the judgment to use them at the right time.

A PO’s pitches are ways to solve problems.

Some problems need a feature.
Some can be solved with better wording.
Some disappear when the operating process changes.
Some can be solved by changing the sales motion.
Some are better solved by changing the customer segment.

A beginner PO solves every problem with a feature.
A good PO keeps the feature as the last card.

A feature is not finished when it ships. It has to be maintained. It has to be explained. Customer support has to know it. Data starts accumulating around it. Bugs appear. Later, it becomes hard to remove.

So the PO has to keep asking:

“Does this really have to be solved inside the product?”
“Is there a lighter pitch?”
“Do we really need to challenge this hitter with a fastball right now?”

Products usually become complicated not because the team lacks skill, but because the team keeps choosing the heaviest possible way to solve each problem.

Getting hit is part of the job

A starting pitcher gives up hits. Sometimes home runs. The point is not to avoid getting hit forever. The point is what happens on the next pitch.

A PO gets hit too.

Customers behave differently than expected. A launched feature does not get used. Internal stakeholders pull in different directions. Development schedules slip. The market changes. The original hypothesis turns out to be wrong.

When the PO panics, the whole team panics.

“Then let’s try this too.”
“That customer said this, so let’s change direction.”
“The CEO is worried, so let’s do that first.”

If the pitching plan changes after every batter, the game falls apart.

A good PO is not stubborn. A good PO has standards. When the hypothesis is wrong, the PO admits it. But the PO does not react to every noise. Customer feedback and data matter, but they are not transcripts to copy into the roadmap.

Review the pitch that got hit. Then choose the next one.

That is the job.

The PO does not need to throw a complete game

A starting pitcher does not need to finish every game. A good starter hands the game over in a state the team can win. Six solid innings. Damage controlled. The bullpen can do its job.

A PO does not complete the product alone either.

The designer sharpens the problem. The developer separates possible solutions from impossible ones. Sales and customer support bring signals from the field. The founder adds business judgment.

The PO’s job is not to have every answer alone. The job is to keep the team aware that they are playing the same game.

What is the score?
Which inning are we in?
Which hitter are we facing?
Where is the inning we absolutely have to survive?

Without that shared view, everyone can play well individually and still lose the game.

The PO owns something close to wins and losses

If we judge a PO by output, the role becomes small. A few specs. A few tickets. A few meetings.

But if we think of the PO as a starting pitcher, the standard changes.

Did the PO prevent early runs?
Did the team get to work in its own rhythm?
Did the PO separate dangerous fights from fights that could wait?
Did the customer problem stay clear until the end?
Did the product’s chance of winning go up?

A PO throws pitches. Those pitches are not requirements. They are judgments.

A good PO does not make the team busy. A good PO creates a game the team can win.

When a starting pitcher walks to the mound, everyone knows the first few innings will shape the game.

Product work is the same.

The PO has to throw the first pitch well.

Only then can the team play its own baseball.