Why Verbal Reasoning Is the Most Underrated Product Manager Skill
Product managers spend their days at the centre of a verbal information flow. User research transcripts, stakeholder memos, engineering technical design documents, customer support tickets, sales call notes, competitor announcements, design review feedback, executive briefings. The PM's day is largely the work of reading these sources, extracting the relevant signal, and writing the artefacts (product requirements documents, decision memos, customer-facing announcements) that drive product decisions. Verbal reasoning is the underlying competence that determines whether a PM produces clear product direction or muddled noise.
Marty Cagan's "Inspired" (2017), the canonical text on modern product management, places written communication near the centre of the PM role. Cagan argues that the rigid product spec has been replaced by a discovery process in which the PM continuously synthesises evidence into structured arguments for what to build and why. This is verbal reasoning applied to product. Ken Norton's writing on hiring PMs at Google explicitly tests for verbal reasoning through the candidate's ability to read a complex situation and produce a structured written argument.
The Specific Verbal Reasoning Demands of Product Management
Writing the product requirements document (PRD). The PRD is the PM's primary verbal reasoning artefact. A good PRD states the problem precisely, identifies the customer segment, articulates the success metrics, lays out the assumptions, defines the scope explicitly, and provides the engineering team with a written argument that the work is worth doing. The PRD that engineers actually want to build from has verbal reasoning at its core: structured premises, precise definitions, and clear articulation of what is in and out of scope.
Synthesising user research. Customer interviews, usability tests, survey responses, support tickets, and analytics observations arrive as messy, contradictory, surface-level material. The PM's verbal reasoning extracts the underlying signal: what customers say they want versus what they actually do, what the gap between the two implies about the product, what specific behavioural pattern would unlock the customer outcome. The PM who reads research carelessly builds features that customers asked for but do not use. The PM who reads research carefully builds features that customers do not ask for but adopt rapidly.
Reading engineering technical design documents. Senior PMs read the engineering team's technical design docs to understand what is being built, where the tradeoffs lie, and which decisions have product implications. The PM who reads these documents carefully catches situations where the engineering choice the team has made will create a worse customer experience or a more complex future roadmap. The PM who skims them defers to engineering on decisions that are actually product decisions in disguise.
Stakeholder communication and alignment. Product managers communicate continuously with executives, marketing, sales, customer success, legal, finance, and engineering leadership. Each communication requires the PM to construct a structured argument tailored to the audience's concerns, anticipate the predictable objections, and provide the evidence that addresses them. The PM whose verbal reasoning is strong shapes organisational alignment around product decisions. The PM whose verbal reasoning is weak generates the kind of cross-functional friction that consumes weeks of executive bandwidth.
The Public Writing of Top Product Managers
The product community has produced an unusually substantial body of public writing in the past decade. Marty Cagan's books and Silicon Valley Product Group essays, Shreyas Doshi's writing on product management at Stripe and Twitter, Lenny Rachitsky's newsletter aggregating PM practice, John Cutler's writings on product operating models, Julie Zhuo's writing on design and product leadership at Facebook, Teresa Torres's "Continuous Discovery Habits" methodology. The PMs who wrote these texts share unusually strong verbal reasoning, applied to the structural problems of product management.
The PMs whose careers are advancing fastest in any major technology company are reliably the ones who write clearly about hard product problems. The promotion conversations that move a PM from senior to staff to principal level are dominated by the candidate's ability to articulate a complex product situation, defend a non-obvious recommendation, and bring others along through written argument. Companies including Google, Stripe, Airbnb, and Coinbase have explicit promotion criteria that test verbal reasoning through written product cases.
The PM Hiring Interview as a Verbal Reasoning Test
PM hiring at top firms is structured around verbal reasoning probes. The product sense interview asks the candidate to design or critique a product, requiring the candidate to read the prompt carefully, identify the assumptions, structure a response with explicit logical flow, and defend the response under follow-up questioning. The strategy interview asks the candidate to reason aloud about a product situation (a metric decline, a competitive threat, a market entry decision) in real time, demanding structured verbal reasoning under pressure.
Google, Meta, Amazon, Microsoft, Stripe, and the other major firms with formal PM interview processes report consistently that the candidates who pass are not the ones with the most product experience. They are the ones whose verbal reasoning, applied to product situations, is structurally cleaner and more rigorous than the competition.
How Product Managers Develop Verbal Reasoning
Most PMs enter the role with usable verbal reasoning from their prior career or education. The role develops the skill through repetition: writing PRDs, conducting research synthesis, drafting strategy memos, presenting at product reviews. The PMs who develop fastest seek out the writing-heavy parts of the role rather than delegating them. They write the PRD themselves rather than asking a contractor. They draft the customer-facing announcement themselves rather than handing it to marketing. They synthesise the research themselves rather than relying on the user researcher's executive summary.
The deliberate development practices that work for PMs are reading research papers in adjacent disciplines (behavioural economics, cognitive science, design research, organisational psychology), writing publicly (newsletters, blog posts, conference talks, internal product memos that circulate widely), and submitting writing for critical review by senior PMs whose verbal reasoning is stronger than the candidate's own.
The PMs whose verbal reasoning plateaus typically reach a level that is sufficient for senior-PM work and stop developing the skill. They produce competent PRDs and effective stakeholder communication but never write the influential strategy memo that moves their organisation. The PMs who continue developing the skill into the principal and director levels are the ones whose verbal reasoning was already strong on entry and who kept investing in it deliberately.
The Long-Term Compound
Verbal reasoning compounds across a PM career in a specific way. The PM who writes clear PRDs ships better products, which raises their internal reputation, which earns them more strategic problems, which develops their reasoning further. By the time the PM reaches director or VP level, the cumulative effect of stronger verbal reasoning across hundreds of product decisions is the difference between a career that ends at director and one that continues to chief product officer.
If you want a calibration on your verbal reasoning before the next PRD, the next product strategy review, or the next senior PM interview, take the Verbal Reasoning test to see where you sit on the same kind of items employers use to filter analytical roles, with diagnostic feedback on which specific sub-skills (inference, deduction, evaluation of arguments) would most benefit from deliberate practice as you advance in product.