What makes great product managers: habits, strategy, and craft

Executive overview

Most PM advice focuses on strategy and communication, but the habits that actually separate great PMs are simpler and rarer: radical simplification, disciplined follow-through on results, and willingness to do unglamorous work. Product strategy is not a separate discipline — it is a structured document that walks from company mission down to team priorities, making disagreement locatable and decisions defensible. Content and frameworks are tools, not answers; applying them without judgment is the trap.

The best PMs ship more, follow up on what they shipped, and do whatever it takes — including the boring stuff.

The three habits of the best PMs

• Simplification: find the one thing and stay with it long enough to finish it — most teams drown in complexity or switch too early
• Read your writing out loud; if it sounds wrong, rewrite it in plain speech
• Delete the first two paragraphs of almost every doc you write — they are almost always unnecessary setup
• The Minto pyramid: put your conclusion first, then supporting arguments
• Keep strategy bets, priorities, and next steps to three items maximum
• Following up on results: set calendar reminders two weeks, one month, six months after launch to pull metrics and share them — few PMs do this and it is highly visible
• Following up teaches you why things worked or didn't, compounding your judgment over time
• Carrying the water: if you find yourself thinking "that's not my job," that is probably the thing you should do
• The PM is often the emotional center of the team; keeping people motivated is real work, not a side effect

How long it actually takes

• Expect four to five years before feeling genuinely confident as a PM
• Staying at one company long enough to see two or three product cycles teaches more than frequent job-hopping
• You learn the consequences of your own decisions — rare and undervalued
• The PM who ships the most and follows up learns the fastest

Breaking into product management

• Getting a PM title on your resume is the unlock — screen for it first, then screen for what they shipped
• Most reliable paths: lateral move within a current company, or joining an early-stage startup
• Networking and persistence matter; one candidate emailed repeatedly until the timing was right
• Large-company rotational programs exist but are scarce

How to write a product strategy

A strategy doc is homework for the PM, not a presentation — write it to be confident in your own decisions, then share it so others can locate their disagreements precisely.

Structure (in order):

1. Mission — company mission and team mission
2. Landscape — competitors, SWOT, market dynamics, key risks
3. Current goals — what the business is working toward this quarter or year
4. Honest product accounting — what works, what doesn't, customer feedback, support signals
5. Technical hurdles — debt, engineering concerns, things coming down the pipe
6. Opportunity — top one or two opportunities given the above; where you can win and why
7. Challenges — what has to be true for this opportunity to work
8. Solution — three bullets on what you would build
9. Plan — sequencing, resourcing, rough cost

• Share with everyone; walk the logic chain from mission to team priority so anyone can point to exactly where they disagree
• Engineering and design counterparts typically engage most deeply — they are signing their teams up too
• Add a summary at the top (Minto principle) so executives can read above the fold and find the recommendation immediately
• Docs can run 20+ pages when you include screenshots, competitive data, and market context — that is fine; the summary carries the room
• A strategy is useful at quarterly or annual planning, when a team feels like it is treading water, or when a new opportunity emerges

The one-pager (PRD / spec)

• The most important section is background and context: what is the problem, why does it matter, and why does it matter now
• Answer those three questions clearly before any proposed solution
• Use the doc as a living home base: log decisions made, things ruled out, and links to artifacts
• Share it with engineering before going further — ask them to tear it apart

Contrarian takes

• "Data-driven" is a red flag: teams that lead with dashboards often neglect qualitative research and lose sight of why things are happening; talking to ten users surfaces more insight than most dashboards
• Using good judgment to do the obviously better thing is faster and often more correct than running every decision through data
• Product content can be dangerous: frameworks lose nuance when packaged for broad audiences; the point is never the framework — it is creating impact; apply tools selectively and know why you are deviating from advice you have read

On creating product content

• Writing and podcasting are among the most career-accelerating investments a PM can make: networking, personal brand, inbound recruiting, and accelerated learning
• The act of making content forces you to process and summarize what you are learning — most people skip this step
• Write about things that are genuinely interesting and useful to you; audiences detect inauthenticity immediately
• The most basic things you know are often the most valuable to share — what feels obvious to you is not obvious to everyone
• Early output will be imperfect; that is normal

Lightning round picks

• Books: The Presentation Secrets of Steve Jobs, Thinking in Bets (Annie Duke), Scaling People (Claire Hughes Johnson)
• Favorite interview question: "What is the worst product you have ever shipped?" — reveals humility, self-awareness, and experience
• Products: Future Fit (training), Pump Log (focused single-purpose app)
• Life motto: if it's worth doing, it's worth doing well