There are questions that belong to the job you have. And there are questions that belong to the job you may want next. The earlier you start paying attention to both, the less abrupt that transition becomes. For a product manager, the first set is familiar. What problem are we solving? What should we build? What evidence do we have? What can the team deliver? What happened after we shipped it?
Those questions matter. Getting good at them is part of the job. But as your scope grows, another set of questions starts showing up around the edges. Why is this worth funding? How does this make money? What does it cost to serve? What happens to the economics if adoption doubles? Why should the company put capital here instead of somewhere else? What assumptions about the customer, market, or business model have to be true for this investment to make sense?
You do not have to own a P&L to start learning how to answer those questions. In fact, waiting until you own one is probably the worst time to begin.
Pricing is one place you can practice
Pricing is useful because it forces several product questions into the same conversation. What does the customer value? What are they actually paying for? What behavior does the pricing model encourage? How does the company make the economics work? What changes when usage grows? Who is the product economically attractive for? Different organizations answer those questions in very different ways. At a startup, the product team may be sitting in the middle of pricing from the beginning because everybody is sitting in the middle of everything.
At a larger company, pricing might involve merchants, sales, revenue operations, business leaders, finance, marketing, or some combination of them. A product manager may have significant influence, limited influence, or no formal ownership at all. That is fine. The lesson is not that product should own pricing. The lesson is that a product person can learn a lot by understanding how the decision gets made.
Ownership and fluency are different things
This distinction matters. You do not have to own a decision to become fluent in it. A PM working on an enterprise product may not set the contract price, but understanding why one customer segment is more valuable than another will affect prioritization. A PM working on a retail system may never determine the price of the merchandise, but understanding margin, inventory turns, labor cost, and return on invested capital can change how they frame the value of their work.
A PM working on an AI capability may not control the company’s packaging strategy, but understanding inference cost, support burden, and willingness to pay changes the conversation about whether usage growth is actually good growth. That fluency changes how you talk about the product. Instead of saying: “We need three engineers for six months.” You can begin asking: “What business outcome are we buying with six months of this team’s capacity?”
Instead of: “Customers really want this.” You can ask: “Which customers want it, what behavior would change, and what would that change be worth?” Instead of: “Adoption is up.” You can ask: “What happens to revenue, cost, margin, or operational capacity when adoption goes up?” The feature did not change. Your altitude did.
This is part of becoming more strategic
“Be more strategic” is frustrating advice because it can mean almost anything. Sometimes what the person giving that advice is really looking for is a change in the questions you ask. Can you connect the product decision to the business decision? Can you see the tradeoff outside your immediate backlog? Can you explain why the work matters in the language another part of the company uses to make decisions? Can you understand enough about the economics to recognize when a seemingly good product outcome creates a bad business outcome?
That does not require pretending to be the CFO. It requires curiosity beyond the boundary of your current responsibilities. Sit in on the pricing conversation when you can. Ask the sales leader why a particular deal matters. Ask the merchant how they think about margin. Ask Finance how the business case was modeled. Ask an operations leader what return they expect from the capital being committed. Ask what happens to the economics when your metric moves.
You are not trying to take over anybody else’s job. You are trying to understand the system your product lives inside.
It also changes the promotion conversation
There is an awkward version of the career conversation that happens when someone wants more scope but is waiting for their manager to describe every behavior required to earn it. “What do I need to do to get promoted?” Sometimes that question is necessary. Expectations should be clear. But there is an advantage to making part of the answer visible before the conversation happens. If the next level requires stronger business judgment, start building business judgment.
If it requires broader organizational thinking, start learning how adjacent leaders make decisions. If it requires making investment tradeoffs, start asking about the economics behind the investments your team is already making. Then the promotion conversation changes. It is no longer: “Tell me what strategic thinking looks like.” There is already evidence. You have been practicing it.
Start before someone gives you permission
Leadership scope tends to introduce new responsibilities faster than it gives you time to learn them. Budget. Portfolio tradeoffs. Commercial strategy. Capital. Organizational design. Executive communication. You can wait until each one appears on your job description. Or you can start learning the questions early. Pricing happens to be a useful place to begin because it sits at the intersection of customer value, business value, behavior, and economics. But pricing is not really the point.
The habit is. Learn to look beyond the decision you own and understand the decisions connected to it. You do not need the P&L yet. You need to be ready when it arrives.