top of page

Einstein, Bourdain, and Mike Tyson never managed a product. Their wisdom applies anyway.

  • Michael Amenta
  • Aug 8, 2025
  • 6 min read

Updated: Jun 15

Meaningful impact requires the unreasonable conviction to push for systemic change over local optimizations.


The product management title explains almost nothing about the job. 'Mini CEO' is grandiose. 'Director of engineering work' is vague. Poor Tom Smykowski from Office Space had the same problem.


From Office Space movie: "I am good at dealing with people! Can't you understand that? What the hell is wrong with you people?!"

This challenge matters more than ever now that AI - whether directly or indirectly - is reshaping what organizations build, how they build it, and their staffing models for product, technology, and design.


Effective PMs push back on senior stakeholders, defend unpopular priorities, and question assumptions that the organization has stopped examining. Like internal affairs in a police department, effectiveness in the role creates organizational tension. And holding tension requires character more than craft. So rather than define the function, which leaves room for mediocrity, it's more useful to identify the character that drives success. 


Eight timeless sources - Bohr, Munger, Saint-Exupéry, Einstein, Deming, M. Tyson, Shaw, and Bourdain - illuminate what that character looks like across six core pillars.


Humility

Every sentence I utter must be understood not as an affirmation, but as a question. - Niels Bohr

Like most people, I like to think I have good ideas. In hindsight, my first idea is usually (read: always) rubbish. The end output is often more successful precisely because open-mindedness allows an ineffective idea to evolve into a better one.


PMs sit at the center of a network of specialists who each see something unique. Engineers see what's technically fragile. QA sees what breaks under real conditions. Design sees where customers naturally look to do something. And Insights teams see blind spots in designs. The PM who treats these perspectives as validation is wasting them. The PM who treats them as challenges to their current thinking gets a materially better product.

Knowing what you don't know is more useful than being brilliant. - Charlie Munger

Bohr and Munger are making the same point from different disciplines: the boundaries of your knowledge are more valuable than the knowledge itself. Map them honestly, and you'll build better products than someone twice as smart as you.


Vision & ideation

If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea. - Antoine de Saint-Exupéry

Vision arises from passion for the problem. A PM who's disconnected from the mission will eventually run out of ideas to build and lose connection to strategy. This can confine them to a role of execution quality: the domain of project management.


But ideation without rigor is just enthusiasm. Product managers are expected to solve problems that are undefined, constantly shifting, and often not fully articulated by anyone. Before proposing solutions, the best PMs spend significant time simply identifying the right problem to solve and aligning stakeholders on what a solution might look like.


It’s not that I’m so smart, it’s just that I stay with problems longer. Most people say that it is the intellect which makes a great scientist. They are wrong: it is character. - often attributed to Albert Einstein

Discovery work then draws from more ambiguous and siloed data, competing ideas, and no guarantees that any answer is the right one. The discipline required isn't primarily intellectual. It's a willingness to stay with a hard problem longer than most.


Discernment & judgement

Without data, you're just another person with an opinion. - W. Edwards Deming 

Opinions can easily form and harden with institutional experience. PMs develop a sense of knowing what needs to be built next and that sense increasingly feels trustworthy. However, when I've been forced to validate a proposed idea with data, the data frequently fails to support my opinions with the same conviction.


The proximity that makes PMs valuable also makes them susceptible to certainty. Deming's discipline is the corrective: validate ideas with data and counter-arguments first. Direction must begin with discernment.


Perseverance

Everybody has a plan until they get punched in the mouth. - Mike Tyson

MVPs exist precisely because plans don't survive contact with real users or markets. But the more persistent threat isn't the market; it's the stakeholder with an urgent request.


The pre-development process takes time, and throughout it, PMs are bombarded with things that someone senior wants immediately. Many blink in this environment. The pattern for mediocre teams is familiar: start an initiative, abandon it when leadership gets excited about the next new thing, repeat. When everything is prioritized, nothing is. Strategy disappears and, with it, impact, morale, and trust.


So a PM must be a staunch defender of priorities even against more senior leaders. This means the job, on many days, looks less like product strategy and more like being a general who gets things done.

From Seinfeld show: "It's the job of a general to by God get things done"

Fortunately, there are a few reliable methods for holding the line with stakeholders. Ask 'why' repeatedly until the root problem is surfaced that points to a core solution, rather than another custom feature. Explicitly remind sponsors that building their newest request means the last critical one misses its deadline. Establish a precedent that roadmap changes require new data of significant importance, rather than the recency bias from a recent phone call. And widely disseminate team vision, core KPIs, and strategic priorities so, when a new request doesn't fit the team's reason for being, the case against the request makes itself. 


Doubt

In anything at all, perfection is finally attained not when there is no longer anything to add, but when there is no longer anything to take away... - Antoine de Saint-Exupéry

Even after an idea has been stress-tested by specialists and refined through open-mindedness, it remains a hypothesis. It hasn't met real users, real constraints, or real market conditions yet. Certainty at this point is a liability.


The practical application of doubt is lean product development: ship the smallest possible version of the idea that still tests the core premise, then let real-world data drive what comes next. Saint-Exupéry's standard is the right one: keep removing until there is nothing left to take away without eliminating the premise itself. What isn't built is as important a decision as what is. Unnecessary features don't just waste development time; they obscure the signal that's needed to learn from.


The virtuous cycle this principle creates of build, test, learn, and refine produces better products faster than any amount of upfront planning. Doubt is the engine.


Unreasonableness

The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -George Bernard Shaw

There is a meaningful difference between goals that target incremental improvement and goals that target transformation. The former optimizes what exists. The latter requires questioning whether what exists should be part of the system at all. The best PMs aim for transformation.


This almost always means pushing beyond the boundaries of the individual product. 10x improvement rarely lives inside the scope of a single squad; it lives in how a single product connects to other teams, other systems, and other ways of working. Persuading those teams to change, or convincing leadership to require it, is uncomfortable work. This will be seen as overreaching. It will be judged as unreasonable.


However, Shaw's logic holds: all progress depends on the unreasonable person. The goal isn't to be liked by everyone; it's to push for what matters, while maintaining kindness. Being liked and being effective aren't the same thing, and confusing them is what keeps most PMs inside their lane when the real opportunity sits just outside it.


Anthony Bourdain captured the spirit of it from a different angle:

Without experimentation, a willingness to ask questions and try new things ... and act like an idiot ... we shall surely become static, repetitive, and moribund. -Anthony Bourdain

A PM who has stopped being willing to look foolish has probably stopped finding the most interesting problems.


What excellent product management requires

Taking the six pillars together reveals a pattern. Humility requires honesty, vision requires passion and patience, discernment requires evidence, perseverance requires courage, doubt requires awareness, and unreasonableness requires conviction. Staying with hard problems longer than feels comfortable is character. Defending priorities against senior pressure is character. Pushing beyond one's remit toward true transformation - while remaining kind - is character.


As Einstein is often quoted: it is not intelligence that makes a great scientist. The same is true of product management. The craft can be learned. The tools can be mastered. But the eight perspectives above are less a skill set than a disposition, one that has to be chosen, repeatedly, under pressure, when choosing otherwise would be easier.


Get email updates on the latest from Do this well
Leave comments, questions or requests
 
 
bottom of page