The best PMs aren't more skilled. They're more free.

In 2014, I had a decision on the table: migrate the video classification pipeline from CPU to GPU using CUDA.

The problem was concrete. We processed video at scale - frame extraction with FFmpeg, visual features with HOG (Histogram of Oriented Gradients), classification with SVM. We tested shallow neural networks, but they didn't perform on our volume with the hardware of the time. HOG + SVM was the state of the art we could afford, and it worked - but it ran frame by frame on CPU, and that didn't scale.

CUDA would change that. Parallel batch processing of frames, feature extraction with real throughput. The CPU cost per hour of video would drop significantly. The technical path was clear in my head.

I didn't do it.

The reason wasn't technical. It wasn't strategic. It was that I didn't know if I could cover the month. GPU in 2014 wasn't a commodity - it was infrastructure cost I couldn't justify when the team's payroll was on the line.

Years later, at the company's exit, what got bought was exactly that capability - processing video at scale with real performance. I did it eventually, almost breaking the company, but I did it for the wrong reason: operational cost reduction, not value creation. The exit happened. But it would have been better, and sooner, if I'd bet where it mattered when it mattered.

That's the decision I carry. And it's the most honest thing I can bring about what wealth has to do with product.

Conviction has a cost

Disagreeing has a political cost. Killing a feature has a relational cost. Betting on a long path has a short-term cost.

This isn't abstraction. It happens in specific meetings:

• Disagreeing is telling the VP that the metric he presented to the board last week is measuring the wrong thing.
• Killing a feature is telling the founder their pet project has no traction and nobody uses it.
• Betting long is holding three months of visible delivery to rebuild a layer only you understand needs to be rebuilt.

Each of those decisions has a second cost nobody talks about: the invitation next time. Whoever pays the political cost once gets marked. They land on the short list of "maybe we don't bring them to this call." The next disagreement weighs more because it carries the previous one.

Whoever can't pay that cost doesn't bet. Simple as that.

And that cost is rarely technical or strategic — it's financial. Whoever needs next month's paycheck can't afford to be right.

The freest PMs at the company aren't always the most senior. They're the ones who can walk out on a Friday without a plan B.

The problem isn't skill

You can have taken every course, read every product book, have the best discovery and delivery track record in the company.

You'll still make decisions out of survival when the month gets tight. When the reserve is zero. When the only way out is this job, this company, this roadmap.

And here's the trap nobody talks about: skill makes it worse. Because skill shows you the right path. You know the feature is wrong. You know the roadmap is optimizing the wrong KPI. You know you should say no.

And you approve it anyway. Because the month doesn't wait.

The PM who doesn't see the problem suffers less. The PM who sees it and can't act lives in daily dissonance — and that charges interest in health, motivation, and sleep. Not in a month. In years.

Seniority doesn't fix it. Framework doesn't fix it. Discovery course, mentor, executive coach — none of it fixes it. The problem isn't competence — it's freedom.

Decision-making freedom doesn't come from seniority

It comes from financial autonomy.

Morgan Housel has a line in The Psychology of Money that nails it: real wealth isn't what you spend — it's what you don't have to spend. It's optionality. It's flexibility. It's the ability to say no without falling apart.

Translated to product: it's the ability to disagree with the VP without calculating this month's rent.

A high salary isn't wealth. A high salary that hits checking and leaves at the same pace is income — not freedom.

I know a senior PM pulling $15k/month with zero reserves. I know a mid-level PM at $7k/month with 12 months of runway in the bank. The second has more decision-making freedom than the first. Always.

Stock options don't count until they're liquid. RSUs vesting three years out are a promise, not wealth. Series A equity is a lottery with a pretty name. The only math that matters is one question:

If I get laid off today, how many months can I go without changing anything in my life?

That's the distance between you and necessity. And that distance shows up in every product decision you make — even when you think it's not in the room.

Wealth changes how you build product

With a reserve, you kill what's wrong. You walk into the meeting, present the data, defend the position even if the VP doesn't want to hear it. You accept the conflict because you know conflict in product is the price of the right decision — not a soft-skill failure.

Without a reserve, you optimize what's safe. You ship what the stakeholder asked for. You write the PRD that will pass review. You call that alignment.

The difference shows up in specific places:

• In prioritization: with a reserve, you cut the feature that became a sacred cow. Without a reserve, you put it on the roadmap as a "low-cost experiment" and move on.
• In discovery: with a reserve, you say 8 interviews isn't enough signal to bet the quarter. Without a reserve, you validate the hypothesis the board already wants to hear.
• In tech debt trade-offs: with a reserve, you pick the fight for the refactor that will hold the product for the next two years. Without a reserve, you ship velocity this quarter and leave the debt for the next PM.
• In hiring: with a reserve, you hold the role three more weeks to find the right person. Without a reserve, you hire the "ok" because the squad needs to deliver.

The product you build when you have a choice is different from the product you build when you need the job.

And that difference doesn't show up in one quarter. It shows up in two years of roadmap stacked on top of each other. In what became legacy. In what never got built.

It doesn't matter how much you make right now

The habit of building wealth precedes the high salary — not the other way around.

Whoever waits to earn more to start never starts. Because lifestyle expands with income, and the logic of "when I make X, I'll start saving" has no finish line. There's always a bigger X.

Run the cold math: a PM making $5k/month saving 15% has reserves. A PM making $12k/month spending $12k/month doesn't. The math doesn't care about your level on the ladder — it cares about what goes out being less than what comes in. Simple as that.

Starting small isn't symbolic. It's where the habit forms. It's where you learn the difference between what you want and what you need — and that difference is the only thing that doesn't change when your salary doubles.

I told my 22-year-old self that what I saved at 25 would be worth more than what I'd save at 35. He didn't listen. It is what it is!

The invisible cost of having no choice

It never shows up on the statement.

It shows up in the feature you approved knowing it was wrong. In the job you stayed at six months longer than you should have. In the product you could have built if you'd had the freedom to bet.

It also shows up in the small, everyday things: in the comment you didn't make in review because picking the fight cost something. In the hire you accepted because pushing back drained you with HR. In the squad change you asked for but didn't push because "the timing wasn't right." In the hard feedback you swallowed in the 1:1 because you needed the bonus.

In 2014 I knew exactly what CUDA would solve in our pipeline. HOG on CPU didn't scale, and I knew it. I didn't bet because I didn't have the financial freedom to take on a cost I couldn't guarantee the following month.

That cost is real. It's cumulative. And it only becomes visible in hindsight — when the exit happens, when the product loses to the competitor, when the engineering team resigns because technical debt became unpayable. That's when you do the math on what could have been.

And that math never closes in favor of whoever didn't bet.

The best investment a PM can make in their own career isn't a course, isn't a certification, isn't one more discovery book.

It's building the wealth that gives you the right to work on the product you're obsessed with (actually want to build) — and say no where you don't want to be.

Because a PM who can't choose where they are isn't building product. They're surviving.