32:51
product sense
Product sense — the intuitive, trusted judgment behind good product decisions — is not an innate gift but a skill built deliberately through humility, curiosity, empathy, direct customer immersion, and structured coaching practices.
Marty avoided the term 'product sense' for years, preferring 'do your homework,' before adopting and redefining the term itself as something you can and must develop, not something you're born with.
Good product sense is visible in practice: senior executives learn over years who genuinely knows customers, products, and tech trends, and customers/salespeople can sense within minutes whether a product person understands and cares.
Bad product sense stems from not having done the homework — not really knowing customers, product usage, or tech trends.
Christian's own product-sense failure (17 failed ideas, roughly $26 million lost, a board calling out giving a 23-year-old that much money) is attributed to overconfidence after an initial unearned win; recovery came from real customer/business/tech immersion plus humility.
A common startup anti-pattern: founders who built genuine product sense in one industry through years of immersion mistake their success for personal genius, skip the immersion/humility work in a new domain, and lack product sense there.
Marty states he has never met anyone who couldn't develop product sense, given the right traits and coaching, though he calls this belief unprovable.
Five traits enable developing product sense: humility, curiosity, empathy, a genuine desire to engage with users/customers, and a sense of agency (agency ties back to a prior podcast episode).
Domain/tenure expertise is a double-edged sword: necessary baseline understanding of users, but can breed dogma (e.g., object-oriented programming treated as universally necessary) and erode the humility/curiosity needed for continued learning.
Generative AI is cited as a new paradigm — probabilistic rather than deterministic — that many long-time programmers struggle to adapt to precisely because of entrenched domain expertise.
New PM onboarding should be built around four pillars: time with users/customers, immersion in usage data, learning the company (transferable skills plus company-specific constraints and personalities), and going deep on the competitive/technology landscape.
Christian frames the essence of product management as synthesizing many parallel, partial sources of knowledge (sales, engineering, support, customers) into daily build decisions — the PM is 'a reflection of all those inputs.'
Marty is wary of fully automating this synthesis with a single AI tool that ingests and auto-prioritizes all inputs, calling that abdicating product sense to a tool rather than augmenting it.
Product sense can be built deliberately via visible mentorship, reading biographies for decision-making process rather than chronology, and studying the history behind admired products.
Once someone has developed real expertise, colleagues stop caring how they learned it and only judge current competence — framed as 'humility only lasts a minute.'
Product Sense (reframed) — Defined in the episode as good judgment in product work — the intuitive, trusted ability to decide what to do — built through experience rather than an innate gift like smell or taste. Apply: Treat product sense as a skill to deliberately develop through humility, customer immersion, and data, not as a fixed trait some people simply have or lack.
"Do Your Homework" — Marty's earlier substitute phrase for product sense, meaning going out and working directly with customers so you actually know them, their issues, and what the data says. Apply: Before making product decisions, go do the work of talking to customers and reviewing usage data rather than relying on assumption.
Five-Trait Product Sense Framework — Marty's list of traits that enable developing product sense: humility, curiosity, empathy, a genuine desire to talk to users/customers, and a sense of agency. Apply: Assess and cultivate these five traits in yourself or a coachee — for example, via a manager pushing them toward real users — as the developmental path to product sense.
Immersion/Shadowing Technique — Christian's practice of spending 90 days, every day 9-to-5, shadowing a single customer (a job seeker) before starting a new product role, grounding customer insight in direct experience rather than assumption. Apply: Before making decisions for a customer segment, embed with an actual member of that segment for an extended period instead of starting normal work immediately.
SVPG Service Model — SVPG is described as a service company, not a product company, that provides advice and methods on how good product teams work rather than building tools for them. Apply: Build product/industry sense through an advisory model — continuously talking to many teams and teaching how good teams operate rather than selling them software.
Continuous Listening Across Teams — Marty's practice of talking to a huge number of product teams almost daily, listening for recurring themes and struggles that signal what to write or teach about next. Apply: When the same problem keeps recurring across many teams even after addressing it once, treat that as a signal to revisit and improve the explanation or solution.
"Pick the Right Tool for the Job" — A philosophy taught to Marty that a programming language is just another tool, not something to be proprietary about, and that knowing more languages broadens career options. Apply: Choose languages/tools based on fit for the problem rather than personal preference or sunk-cost attachment, and keep learning new ones.
Constraint Reframing — A mindset that treats domain constraints as opportunities to innovate ('we can do this') rather than as walls that limit what's possible. Apply: When facing a domain constraint, reframe it as a design challenge to solve creatively rather than accepting it as a hard limit.
Four-Pillar New-PM Onboarding Foundation — Marty's onboarding framework for new product hires covering four areas: time with users/customers, immersion in usage data, learning the company (transferable skills plus company-specific constraints and personalities), and going deep on the competitive/technology landscape. Apply: Structure a new PM's first few months around these four pillars to build a foundation of product sense quickly, even for hires coming from great companies.
Learning from Adjacent Colleagues — Using colleagues in customer-facing roles, such as customer service and customer success, as sources of product-sense-building knowledge. Apply: Deliberately seek out and learn from customer service/success staff as an additional input source alongside direct customer contact.
Caution Against Tool-Based Synthesis Abdication — Marty's stance, prompted by a request for a single AI tool to ingest all input sources and auto-prioritize results, that doing so would mean abdicating product sense to a tool even though it's technically feasible with generative AI. Apply: Use generative AI to assist with synthesizing customer/sales/engineering input, but keep the judgment and prioritization function with the human product person rather than fully delegating it.
"Find the Smartest Person in the Room" — Christian's technique for identifying the most valuable source of insight on a team — not necessarily whoever claims to be smartest — by observing how others react to their input. Apply: Watch for social cues like colleagues deferring to or double-checking with a particular person, and treat that person as a key source to learn from.
Visible Mentorship Technique — Christian's deliberate choice to be taught by a mentor in a visible glass conference room, so colleagues could see both his humility in learning and the mentor's endorsement of him. Apply: When seeking mentorship on an unfamiliar domain, do it visibly so the mentor's credibility transfers to you in the eyes of the wider team.
Biography Reading for Decision-Making Analysis — A CEO's technique, passed to Marty, of reading biographies/autobiographies (e.g., Steve Jobs, Abraham Lincoln) not to follow the historical timeline but to study the inputs behind a leader's hard decisions. Apply: When reading a biography, focus on reconstructing what information or inputs the subject used to make a specific critical decision, since history already reveals the outcome.
Studying Product Histories/Case Studies — A technique of picking a product you love and researching how it was built, as in Marty's example of Tony Fadell's account in 'Build' of deciding to manufacture custom screws for the Nest thermostat. Apply: Pick a product you admire, research the decisions and inputs behind its creation, and extract the reasoning process rather than assuming it was a matter of visionary luck.
The overconfidence trap: an early, unearned success attributed by Christian to 'knowing nothing' and pure curiosity was later misread by himself as proof of skill, and the resulting arrogance (not the initial failure) is framed as what actually destroyed his judgment.
Deep domain expertise is explicitly called a 'superpower' that is also dangerous, because real innovation requires questioning assumptions that experts have stopped questioning.
Visible mentorship is framed as a social-credibility mechanism, not just knowledge transfer: Christian deliberately chose a visible glass conference room so onlookers would see both his humility in learning and the mentor's implicit endorsement of him.
Marty draws a specific, deliberate boundary around where generative AI is allowed to operate in the product process — refusing a request to build a single tool that ingests and auto-prioritizes all inputs, even though he says it's technically feasible.
Reading biographies is reframed from a leadership-inspiration exercise into a decision-analysis exercise: the CEO who assigned Marty this reading emphasized reverse-engineering the inputs behind one specific hard decision (illustrated via Lincoln and via Tony Fadell's account of manufacturing custom screws for the Nest thermostat), not following the narrative arc.
Humility is framed as a transitional tool tied to the learning phase rather than a permanent trait — once competence is achieved, the story of how it was acquired becomes irrelevant to others, which both hosts treat as a distinct and somewhat surprising observation about how expertise is socially perceived.
«that's not what product sense is and when they think of it as innate something you're you're born with then it becomes like an excuse»
— 01:43
«if you can't beat them join them»
— 02:26
«It's something you can and need to develop.»
— 02:43
«It's good judgment in product work — it's how you decide what to do — that intuitive ability that your hypotheses are trusted and convincing to other people.»
— 03:43
«In just minutes the customer can tell you understand — and not only that you understand, but they can tell you care.»
— 05:06
«The most important product sense element is this sense of humility — that is the cornerstone of our discipline.»
— 07:43
«If you don't have humility, why would you bother spending your time talking to customers?»
— 09:15
«God, that's so true — the person I spent time with didn't have a bank account.»
— 13:07
«This is the great thing about product sense: you never stop learning.»
— 16:07
«It's probabilistic rather than deterministic.»
— 19:39
«it's just another tool you know you pick the right tool for the job»
— 20:07
«you are basically sort of abdicating the product sense to a tool»
— 23:46
«we should do it in one of those conference rooms that you know are visible where everybody could see me learning like I am going to school»
— 26:11
«the humility it only lasts the minute»
— 27:29
«people forget how you learn they just care that you know»
— 27:40
Reception
Viewers responded very positively, praising the interviewer's questions and the session's value while asking for more content.
The episode combines personal-narrative evidence (Christian's $26M failure, 90-day shadowing story, M&A mentorship story) with a coach's structured toolkit (the five-trait framework, four-pillar onboarding plan, visible-mentorship and biography-reading techniques) to argue product sense is coachable rather than innate. It closes with a promotional segment for SVPG's newsletter, workshops, and its 'Transform' book, and a standard mental-health disclaimer for the 'Product Therapy' format.
32:51