How to Be a Great Product Manager: 5 Habits for Better Product Decisions
TL;DR: Super good PMs do five things consistently: they frame the right problem, talk to customers every week, prioritize like they are placing bets with real downside, involve engineering early, and manage outcomes instead of output.
Ask ten people what makes a product manager great and you will hear a lot about process hygiene. Clean PRDs. Tidy roadmaps. Impressive stakeholder decks. Calm sprint rituals.
Those things help. They are not what makes someone exceptional.
A super good PM improves decision quality under uncertainty. They reduce the chance that a team spends six weeks shipping the wrong thing for the wrong user at the wrong time. They make it easier for design and engineering to do high-leverage work instead of expensive guesswork.
In other words, they are not there to look organized. They are there to help the organization make smarter bets, faster.
Super Good PMs Are Risk Managers, Not Roadmap Clerks
At the core, product management is risk management. Every serious product decision carries value risk, usability risk, feasibility risk, and viability risk. Great PMs treat each roadmap item as a hypothesis that has to survive contact with reality.
Average PM behavior lives at the artifact layer. The ticket is crisp, the roadmap is color coded, the status update is polished. Super good PM behavior lives at the risk layer. What needs to be true for this bet to pay off? Which assumption is most dangerous? What is the cheapest way to test it this week?
That mindset changes execution quality fast. Your roadmap stops acting like a promise board and starts acting like an investment thesis. Discovery stops being a quarterly ritual and becomes the mechanism that prevents avoidable waste.
Discovery Is a Weekly Habit, Not a Quarterly Ritual
Teresa Torres’ definition of continuous discovery is still one of the most useful operating anchors in product: weekly touchpoints with customers by the team building the product, in pursuit of an outcome.1
That weekly cadence matters because product decisions are made daily. If customer contact is sporadic, teams fill the gaps with internal narratives and loud opinions. You can feel this drift in planning rooms: confidence rises while evidence quality falls.
A super good PM keeps the loop alive even during heavy delivery periods. One meaningful customer conversation each week, done by the product trio and followed by lightweight synthesis, is often enough to keep priorities grounded in actual behavior. You do not need a giant research operation to do this. You need consistency.
Prioritization Is Not a Ceremony, It Is Capital Allocation
Roadmaps are not task lists. They are capital allocation decisions.
Every priority call spends scarce resources: engineering time, design attention, market timing, and organizational trust. Super good PMs make those tradeoffs explicit. They do not hide behind “this feels important.”
Frameworks like RICE help because they force clear assumptions about reach, impact, confidence, and effort.2 The formula is less important than the discipline. Once assumptions are visible, people can debate the inputs instead of the people in the room.
A useful smell test is this: can another team read your rationale and understand why option A wins over option B right now? If they cannot, you probably have intuition dressed up as process.
Bring Engineering In Before Scope Hardens
Teams still lose massive time by involving engineering too late. Atlassian’s 2026 product research points to this directly, including a high share of teams that do not involve engineers early and many teams that feel short on strategic planning time.3
That combination is brutal: less strategy time, late feasibility input, and higher downstream rework.
Super good PMs prevent this by making engineering part of problem framing, not just implementation. The best conversations happen before scope is politically locked. You get better options, better risk calls, and fewer “surprise constraints” two weeks before launch.
When engineers only join after commitments are fixed, you are not collaborating. You are negotiating damage.
Manage Outcomes, Not Output
Shipping is necessary. It is not sufficient.
Super good PMs keep output connected to outcomes while execution gets noisy. Marty Cagan’s framing is useful here: teams need outcomes they can directly influence, or empowerment quickly turns performative.4
This is one of the hardest parts of the role because output metrics are immediately visible and outcome movement is slower, noisier, and sometimes uncomfortable. But if you only manage output, you get clean delivery optics and messy product results.
The PM’s job is to hold both realities at once: maintain delivery momentum and keep the team honest about whether shipped work is actually changing user or business behavior.
The Operating Rhythm That Makes This Real
None of this survives as advice alone. It needs a repeatable operating rhythm.
In strong teams, the loop is concrete. New customer signal enters continuously instead of arriving in occasional research dumps. Priorities are revisited when assumptions change, not only when a quarterly plan says it is time. Cross-functional decisions happen before commitments calcify. Shipped work is read against intended outcomes, not only completion status.
Then the loop resets.
When pressure rises, weak teams usually cut discovery first. A super good PM does the opposite. They protect the learning loop because they know execution without learning is just polished drift.
That discipline is what turns product management from coordination theater into strategic leverage.
What “Super Good” Actually Looks Like
It is rarely flashy. It usually looks like fewer emergency pivots because risky assumptions were surfaced early, engineers who understand why they are building something instead of just what is in the ticket, and stakeholder debates focused on tradeoffs rather than status politics. Most importantly, it looks like customers feeling meaningful improvement more often because the team is learning faster than it is guessing.
Being a super good product manager is not about dominating roadmap meetings. It is about building a system where good decisions happen more often, with less friction and less drama.
If you are building that kind of system and you want strategy, work, and delivery signals to stay connected without heavy reporting overhead, that is exactly the layer we are building at One Horizon.5
Footnotes
-
Teresa Torres. “The Best Continuous Discovery Teams Cultivate These Mindsets.” Product Talk. https://www.producttalk.org/continuous-discovery-mindsets/ ↩
-
Intercom. “RICE: Simple prioritization for product managers.” https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/ ↩
-
Atlassian. “The State of Product in 2026: Navigating Change, Challenge, and Opportunity.” https://www.atlassian.com/blog/announcements/state-of-product-2026 ↩
-
Marty Cagan. “Outcomes Are Hard.” Silicon Valley Product Group. https://www.svpg.com/outcomes-are-hard/ ↩
-
One Horizon. Product and company overview. https://onehorizon.ai/ ↩
