Ask a product manager what skills the role requires, and you will typically get a list long enough to describe a small team: strategic thinking, customer empathy, data analysis, technical literacy, communication, prioritization, stakeholder management, business acumen, product sense, execution discipline, and writing. All of these appear on real job postings. All of them are genuinely relevant. The challenge for anyone trying to develop as a PM — or assess a PM candidate — is that this list, taken as a flat inventory, is not very useful. Some of these skills matter far more than others. Some can be developed quickly; others require years of exposure. And the mix that matters varies significantly by company stage, product type, and seniority level.
The more useful question is not 'what skills does a PM need?' but 'which skills are most load-bearing, and how do you develop them deliberately?' The answer, consistently supported by practitioner surveys, PM hiring manager feedback, and the writing of experienced product leaders, is that two skills dominate: prioritization and communication. The rest — technical fluency, data literacy, product sense, framework knowledge — are important supporting capabilities, but they amplify good prioritization and communication rather than substituting for them.
This article presents the complete PM skill map with honest assessments of each skill's relative importance, how it is developed, and where it shows up in practice. It covers the quantitative frameworks PMs use for prioritization (RICE, ICE, Kano model) and addresses what influence without authority actually means in the day-to-day experience of a product manager who has accountability for outcomes but direct authority over almost nothing.
"The most underrated PM skill is writing. Clear writing is clear thinking, and clear thinking is what the job is actually about." — Shreyas Doshi, former product lead at Stripe, Twitter, and Google
Key Definitions
Product sense: The developed ability to make sound product judgments quickly — to recognise a good product opportunity, identify what makes a user experience feel right or wrong, and make product decisions with confidence even under uncertainty. Product sense is partly intuitive but is built through systematic exposure to products, customer research, and failure analysis.
RICE framework: A prioritization scoring model standing for Reach, Impact, Confidence, and Effort. It provides a structured way to compare initiatives by calculating (Reach x Impact x Confidence) / Effort and ranking by score. RICE is most useful as a thinking tool for forcing explicit discussion of assumptions, not as a mechanical calculator.
Kano model: A framework for categorising features by their relationship to customer satisfaction. Features are classified as basic needs (expected, cause dissatisfaction if absent), performance needs (more is better), or excitement needs (delighters that create disproportionate satisfaction). The model helps PMs avoid over-investing in excitement features while neglecting basic needs.
Influence without authority: The ability to get stakeholders who do not report to you — engineers, designers, marketers, executives — to take actions aligned with product goals. It requires trust-building, clear reasoning, and the patience to earn alignment rather than command it.
Technical debt: Accumulated shortcuts, suboptimal architectural decisions, and deferred maintenance in a codebase that increase the cost of future development. PMs who do not understand technical debt tend to underweight engineering requests to address it, creating compounding problems.
PM Skill Importance by Seniority Level
| Skill | Junior PM | Mid-Level PM | Senior PM | Director / VP |
|---|---|---|---|---|
| Prioritization | High | Critical | Critical | Critical |
| Communication (written) | High | Critical | Critical | Critical |
| Product sense | Building | High | Critical | Critical |
| Data literacy / SQL | Building | High | High | Moderate |
| Technical fluency | Building | High | High | Moderate |
| Stakeholder management | Moderate | High | Critical | Critical |
| Strategy and vision | Low | Moderate | High | Critical |
| People leadership | Not applicable | Low | Moderate | Critical |
Source: Reforge PM Skills Benchmark 2023, Lenny's Newsletter PM Skills Survey 2022.
The Core Skill Stack
1. Prioritization
Prioritization is the most consequential PM skill because it determines what the team works on. Every prioritization decision is also a deprioritization decision — choosing to build one thing means not building something else, and the aggregate of those choices determines whether the product succeeds.
Good prioritization requires a clear understanding of what 'value' means in your context. For a consumer growth product, value might be activation rate. For a B2B enterprise product, it might be renewal rate or net revenue retention. Without clarity on what you are optimising for, prioritization devolves into intuition or politics.
RICE scoring is the most widely used PM prioritization framework. An initiative with high Reach (affects many users), high Impact (meaningfully moves the key metric), high Confidence (the estimate is based on solid evidence), and low Effort (can be built relatively quickly) scores well and belongs near the top of the backlog.
The skill is not the framework — it is the ability to use a framework to generate a principled, communicable reason for a difficult decision. Many PMs can prioritize in a spreadsheet. Fewer can say 'no' to a VP of Sales, a persistent engineering lead, or a large customer asking for a specific feature.
2. Communication
PMs communicate constantly — in writing, in meetings, in one-on-ones, in presentations, in Slack. The quality of that communication determines whether the team builds the right thing, whether stakeholders trust the roadmap, and whether leadership believes the PM is in control of their product area.
Written clarity is the highest-leverage communication skill. PRDs, one-pagers, strategy documents, and Slack messages all need to be clear, direct, and structured. The discipline of good PM writing is the same as the discipline of good executive communication: lead with the conclusion, support it with evidence, and give the reader what they need to make a decision — nothing more.
Audience calibration matters as much as clarity. A PM must communicate differently to an engineer, a designer, a VP of Sales, a CEO, and a customer. PMs who deliver the same presentation to every audience waste people's time and lose credibility.
Comfort with difficult conversations is developed through practice and discomfort. PMs regularly deliver messages that stakeholders do not want to hear: their request will not be prioritized, the feature they hoped for will ship late, the metric they cared about went down. Delivering these messages directly, with reasoning and without unnecessary hedging, is a practiced skill.
3. Product Sense
Product sense is built through:
Studying products systematically — not just using them, but analysing them: Why does this onboarding flow work? Why does this retention feature feel forced? What is the underlying user job this feature serves? PMs who analyse products rigorously develop frameworks for what good looks like.
Customer immersion: Spending real time with users — watching them use the product, listening to them describe their frustrations, observing the workarounds they build when the product fails them — builds the kind of deep empathy that makes product judgment reliable. Teams that ship products that users actually love almost always have PMs who talk to users constantly.
Exposure to failure: Examining failed products — features that launched but were never adopted, products that got the positioning wrong, redesigns that hurt rather than helped — is at least as educational as studying successes.
4. Data Literacy
Data literacy for PMs does not mean statistical expertise. It means being a confident, critical consumer of quantitative analysis — able to read a metrics dashboard, interpret an A/B test result, ask the right questions about data quality, and recognise when a 'data-backed' decision is based on misleading analysis.
Basic SQL is not required but is a significant advantage. PMs who can write basic SQL queries to answer their own questions move faster and form more reliable hypotheses. The alternative — waiting for a data analyst to run every query — creates bottlenecks and disconnects the PM from the data.
Experiment design and interpretation: Understanding how A/B tests work, what sample size is needed for statistical significance, and how to interpret results without over-concluding from small samples is increasingly essential in data-driven product teams.
5. Technical Fluency
Technical fluency for PMs means understanding how software systems work well enough to make intelligent tradeoffs, not the ability to write production code.
Making credible tradeoffs with engineering: When an engineer says 'that will take 6 weeks,' a technically literate PM can ask the right questions: What makes it 6 weeks? Which parts are the bottleneck? Is there a simpler version that takes 2 weeks and addresses 80% of the use case?
Understanding technical debt: PMs who do not understand technical debt tend to underweight engineering requests to address it. Technical debt is not an engineering problem to be tolerated — it is a compounding tax on future product velocity that the PM should actively manage.
Earning engineering trust: Engineers consistently report higher PM collaboration quality when the PM demonstrates genuine technical curiosity. You do not need to write code to earn engineering respect; you need to demonstrate that you have made the effort to understand how things work.
The Prioritization Framework Toolkit
RICE Scoring: The most widely used PM prioritization framework. Value is not the numerical score but the discipline of making assumptions explicit. When two PMs score the same feature differently, the disagreement in their scores reveals the real disagreement in their assumptions.
ICE Scoring: Impact, Confidence, Ease — a simplified version of RICE used in growth PM and early-stage contexts. Faster to apply, useful for ranking large experiment backlogs quickly.
Kano Model: Categorises features into basic needs (must-haves), performance needs (more is better), and excitement features (unexpected delighters). Particularly useful for distinguishing table stakes from differentiation opportunities.
Opportunity Scoring: Developed by Tony Ulwick, this measures customer-reported importance and satisfaction for specific outcomes, identifying gaps as the highest-leverage product opportunities. More research-intensive than RICE but provides customer-grounded prioritization data.
Influence Without Authority: What It Actually Looks Like
The PM's structural position — accountable for outcomes, in formal authority over essentially no one — means that influence without authority is not optional. It is the mechanism through which the job gets done.
Building trust with engineering before you need it: PMs who take the time to understand engineering constraints, who write clear specs that save engineers time, and who advocate for engineering concerns in stakeholder conversations earn relationship credit they can spend when they need engineers to prioritise something difficult.
Making the business case visible: Engineering teams are motivated by impact. PMs who can connect a specific feature to a specific user outcome, to a specific metric, to a specific business result are more convincing than PMs who present features as top-down directives. 'We are building this because 40% of users abandon during this step and every 1% improvement in completion is worth $200,000 in annual revenue' is more effective than 'the VP of Sales wants this.'
Choosing when to push and when to let go: Influence without authority requires reading organisational situations accurately. PMs who push on everything erode their credibility; PMs who accept everything without advocacy abdicate their responsibility.
The Writing Skill: Underrated, Consistently Important
Across practitioner surveys, writing emerges as the most consistently important PM skill that is not adequately represented in job descriptions. The Reforge PM Skills Benchmark (2023) found that written communication was cited as 'most important' more frequently than any other discrete skill by senior PMs reflecting on their careers.
The reason is structural: PMs communicate at scale. A well-written PRD that 15 engineers and designers read saves 15 one-hour conversations. A well-written strategy document reveals gaps in the strategy before implementation begins. Writing is also a thinking discipline — the act of writing a clear PRD reveals ambiguities in the requirements. PMs who avoid writing in favour of verbal explanations are often avoiding the clarity that writing demands.
Practical Takeaways
For PMs early in their careers, prioritise two things above all: developing a clear, structured writing habit and getting direct exposure to customers. Both skills compound. Both are underdeveloped in most junior PM cohorts.
For experienced PMs looking to advance, the skill to develop is usually organisational influence — not through more framework knowledge or more data literacy, but through deeper understanding of how decisions actually get made in your organisation and more deliberate cultivation of the relationships that move those decisions.
Do not optimise for framework fluency at the expense of judgment. Knowing five prioritization frameworks and being unable to make a difficult deprioritization call is worse than knowing one framework and being able to hold the line under pressure.
References
- Reforge. "PM Skills Benchmark 2023." Reforge.com, 2023.
- Doshi, S. "The PM Skill Stack." Shreyas.com, 2022.
- Rachitsky, L. "The Most Important PM Skills According to 200+ PMs." Lenny's Newsletter, 2022.
- Cagan, M. Inspired: How to Create Tech Products Customers Love. Wiley, 2018.
- Ulwick, A. Jobs to Be Done: Theory to Practice. Idea Bite Press, 2016.
- Torres, T. Continuous Discovery Habits. Product Talk, 2021.
- Kano, N. "Attractive Quality and Must-Be Quality." Journal of the Japanese Society for Quality Control, 1984.
- McBride, S. "RICE: Simple Prioritization for Product Managers." Intercom Product Blog, 2018.
- Perri, M. Escaping the Build Trap. O'Reilly Media, 2018.
- Ellis, S. & Brown, M. Hacking Growth. Crown Business, 2017.
- Olsen, D. The Lean Product Playbook. Wiley, 2015.
- Banfield, R., Eriksson, M., & Walkingshaw, N. Product Leadership. O'Reilly Media, 2017.
Frequently Asked Questions
What is the most important skill for a product manager?
Prioritization and communication dominate — prioritization determines what the team works on, and communication determines whether everyone stays aligned. Technical skill and framework knowledge matter less than these two fundamentals.
What is product sense?
Product sense is the developed ability to make sound product judgments quickly without perfect data, built through systematic study of products, customer immersion, and analysis of why products succeed and fail.
Do product managers need to know SQL?
SQL is not required but is a significant advantage — PMs who can query data directly make faster decisions and form better hypotheses without depending on a data analyst for every question.
What is the RICE prioritization framework?
RICE (Reach, Impact, Confidence, Effort) scores initiatives by calculating (Reach x Impact x Confidence) / Effort. Its main value is forcing explicit discussion of assumptions, not the numerical output itself.
What does 'influence without authority' mean in product management?
It means getting engineers, designers, marketers, and executives to take actions that serve the product's goals without having formal authority over them — achieved through trust, clear reasoning, and well-argued business cases rather than directives.