Product Management: Making Better Decisions About What to Build and Why

Most organizations have no shortage of ideas for their products. Customers ask for new features. Executives see new markets. Sales wants whatever will close the next deal. Developers spot fixes that would make the product more reliable or easier to maintain.

Many of these ideas are good, and the people pushing them usually have solid reasons. The trouble is that no organization can do them all. Choosing one means delaying or dropping another, and the cost of that choice is often unclear.

Product management is the discipline of deciding which customer problems and business opportunities deserve investment, guiding products toward valuable outcomes, and evaluating whether those investments pay off. It goes well beyond writing requirements, keeping a roadmap, or coordinating teams. A feature can look valuable on its own and still be a poor bet next to the alternatives.

Many organizations focus on delivery because it's easy to see. They track throughput, release frequency, and how much planned work gets done. Those numbers say something about operations but very little about whether the team is working on the right things. A team can get very good at shipping features nobody uses, while a smaller competitor wins by focusing on a few problems that matter.

From our experience

My team produces a lot of YouTube videos, and doing one well takes considerable effort. We choose a topic we think will resonate, set up lighting, microphones, and cameras, then record, edit, and publish. But after all that work, there's no guarantee anyone will watch it. Finishing the video on schedule tells us almost nothing about whether it was worth making. Developing a complex product for an uncertain market is the same problem, only with much more money at stake.

Good product management improves those investment decisions. It requires clear strategy, a sensible approach to uncertainty, honest attention to tradeoffs, and a willingness to reconsider decisions when the evidence changes. Delivering more only helps when the work is worth doing.

When Efficient Delivery Produces Disappointing Results

Blockbuster is a good example of how a company can keep introducing new products and services without getting the business results it needs. By the early 2000s, Blockbuster was facing growing competition from Netflix as customers became less interested in driving to stores, hoping a movie was available, and paying late fees. Blockbuster recognized these problems and responded with several new offerings.

The company eliminated late fees, launched a DVD-by-mail subscription service, and introduced Total Access, which allowed customers to exchange mailed DVDs at physical stores. It eventually invested in digital rentals, too. Some of these were genuinely good ideas. Total Access even offered something Netflix couldn't at the time: online rentals combined with immediate exchanges at thousands of retail locations. Blockbuster wasn't standing still.

Unfortunately, those investments weren't enough to turn the business around. Eliminating late fees reduced revenue, Total Access was expensive to operate, and leadership eventually scaled back the program. Meanwhile, Blockbuster still had thousands of stores to support as customers continued shifting toward more convenient ways to watch movies. The company introduced new offerings but couldn't make the transition quickly or profitably enough to replace its declining traditional business.

Blockbuster's story shows the difference between delivery efficiency and product effectiveness. Delivery efficiency measures how much output you get for the effort spent. Product effectiveness asks whether that output creates enough value to justify the investment. We don't know how efficiently Blockbuster's development teams worked, but we do know that introducing new capabilities didn't produce the business results the company needed.

Blockbuster was right to keep innovating, but new offerings couldn't save a business model that was losing relevance. Before investing in additional features, more people, or faster delivery, product leaders need to understand what business problem they're trying to solve and whether their investments are producing meaningful results.

Product Strategy Gives You a Basis for Choosing

Product strategy tells you which opportunities deserve attention and which should wait or be dropped. It identifies the customers you plan to serve, the problems worth solving, the advantages you want to build, and the results you're aiming for. When the strategy is clear, teams can make many decisions on their own because they understand the reasoning behind them.

You notice a missing strategy fastest in prioritization meetings. Sales pushes features prospects have requested. Operations wants reliability improvements. Engineering wants technical fixes that will save time later. Each has a point, but without shared direction, there's no good way to compare them. The meeting becomes a negotiation, and the roadmap fills with reasonable-looking projects that don't add up to anything. This is why defining the product before development begins matters.

For example

Consider Apple's decision to discontinue the Newton, an early handheld personal digital assistant. Introduced in 1993, it offered touchscreen interaction, handwriting recognition, and tools for managing contacts and calendars. Apple invested heavily in the technology, but the Newton struggled with disappointing sales, technical problems, and competition. Even after substantial improvements, it never achieved the commercial success Apple had hoped for.

When Steve Jobs returned in 1997, Apple was struggling financially. Rather than continue investing in the Newton, Jobs discontinued it in 1998. That meant walking away from years of development and technology that still had potential. It points to something organizations often struggle with: an investment can have merit without deserving continued funding.

Strategy doesn't spell out every feature, but it provides a basis for concentrating resources and deciding what to stop doing. Those choices become especially important when managing multiple products, where investing in one product necessarily limits what you can do with another.

Strategy also rests on assumptions, and some will prove wrong. Apple's decision didn't mean handheld computing had no future. Some of the ideas behind the Newton would eventually appear in the iPhone and iPad. The opportunity was real, but that didn't necessarily make the Newton the right investment at the time. Good strategy provides clear direction while leaving room to change when the evidence does.

Product Discovery and the Cost of Being Wrong

Every product decision is made without complete information. You're estimating how customers will behave, whether a solution will solve their problem, what it will cost to build, and whether the payoff will be worth it. Product discovery helps you decide which uncertainties are worth investigating before committing more money.

Customer interviews, observation, prototypes, experiments, and workflow analysis can all improve those decisions. But research also costs time and money. Spending weeks studying a small interface change might cost more than simply releasing it and observing the results. That same approach could be reckless for a major investment that's expensive to reverse.

The right amount of discovery depends on how much it costs to be wrong, how much it costs to learn more, and how easily you can change course. Understanding the current state and desired future state helps establish what problem you're solving, while stakeholder alignment helps uncover competing needs and assumptions before they become expensive surprises.

For example

Google Glass offers an interesting example. When Google introduced its smart glasses in 2013, the technology attracted enormous attention. The glasses could display information, take photos, record video, and respond to voice commands. Through its Explorer program, Google put the technology into the hands of early adopters. But the experience exposed problems beyond technical feasibility: high prices, limited battery life, privacy concerns, and an unclear reason for most consumers to wear them.

In 2015, Google ended sales of the original consumer Explorer Edition. Rather than abandon the technology entirely, it developed enterprise versions for workplaces where hands-free access to information had a more specific purpose, including manufacturing and logistics. Even that narrower market didn't justify continued investment, and Google discontinued Glass Enterprise Edition in 2023. The history of Google Glass shows how a technically impressive product can struggle to find a use case that justifies the investment.

Google couldn't have predicted every problem. Sometimes the only way to learn is to put a product in people's hands. What matters is recognizing what the evidence tells you and being willing to reconsider the investment. Discovery earns its cost when it changes decisions.

Prioritization and the Cost of Delay

Prioritization isn't simply ranking features by importance. It's deciding how to invest limited people and money across opportunities with different benefits, costs, risks, and timing. A ranked backlog can help, but the real question is which investments deserve resources now and which should wait.

Timing matters because value can change. An investment that prevents customers from leaving every month may deserve attention before one promising a larger benefit that will still be available next year. Every decision also carries an opportunity cost. Spending three months on one initiative means giving up whatever else those resources could have accomplished.

For example

Southwest Airlines' scheduling crisis in December 2022 shows how expensive delaying an investment can become. For years, employees and unions had raised concerns about outdated crew scheduling technology. When severe winter weather disrupted operations, Southwest struggled to locate and reassign crews, ultimately canceling more than 16,700 flights. The crisis cost the airline more than $1 billion.

Southwest subsequently announced substantial investments in technology and operational improvements. We can't know how much of the disruption earlier investment would have prevented, but the example shows why reliability and risk reduction deserve consideration alongside new revenue opportunities. Their value often comes from avoiding losses rather than generating visible gains.

Techniques for prioritizing a product backlog can help make these tradeoffs explicit. Weighted scoring and value estimates provide structure, but they can also make guesses look more precise than they are. Use them to expose assumptions and improve discussions, not to replace judgment.

A product manager should be able to explain why an investment was chosen, what was delayed or abandoned to make room for it, and what new information would justify reconsidering the decision. Good prioritization keeps investment choices current as circumstances change, rather than defending a ranking.

How AI Changes Product Investment Decisions

AI is changing the economics of product development. Prototyping, experimentation, and parts of software development are becoming less expensive, allowing teams to explore ideas that previously required substantial investment. That's an advantage when it helps test assumptions before committing to a full build. But making something easier to build doesn't necessarily make it worth building.

The initial development cost is only part of the investment. Products still need integration, security, testing, maintenance, and support. AI-powered capabilities can introduce additional costs related to model usage, monitoring, evaluating results, and handling unexpected behavior. A working prototype might demonstrate technical feasibility without proving that customers will value the solution enough to justify those costs.

AI also makes it easier to confuse technical possibility with customer value. Just because a team can automate a task doesn't mean customers need that capability, trust it, or benefit enough to pay for it. The same investment questions still apply: What problem are we solving? What evidence supports the opportunity? What will it cost over time? How will we know whether it worked?

AI expands what organizations can build. It doesn't eliminate the need to decide what's worth building. For Product Managers or Product Owners looking to apply AI in their work, our Professional Scrum Product Owner – AI Essentials course explores practical ways to use AI for customer understanding, prototyping, testing, and product decisions.

Product Leadership and Decision Authority

Product managers are often held accountable for results without authority over the decisions that drive them. They might own revenue or retention while sales makes promises to customers, executives dictate features, and department heads control resources. The product manager ends up coordinating decisions made by others rather than directing the product.

Good product leadership requires clarity about who makes decisions, what evidence informs them, and how disagreements get resolved. Stakeholder alignment doesn't mean everyone agrees on a solution. It means people understand the problem, the desired outcome, the constraints, and how decisions will be made. That's an important distinction when moving from order taking to making product decisions.

Amazon offers an interesting example. As the company grew, dependencies between teams made decisions more difficult. Amazon responded partly through its two-pizza team approach, organizing small teams around specific products or services. Team size mattered less than giving teams clear ownership and the authority to make decisions about their work.

Amazon calls this single-threaded ownership. Teams focus on a particular product or service, manage priorities, and remain responsible after launch. Leadership provides direction and oversight without requiring every decision to move through multiple departments. This reduces coordination overhead and allows teams to respond more quickly to what they learn.

We see the opposite pattern in many organizations. Teams are formed around technology or capabilities, such as Web, Mobile, and Data. Leadership takes a larger goal, breaks it into pieces, and assigns each piece to the team that owns that technology.

From our experience

I saw an extreme version of this while teaching a Professional Scrum Product Owner class for a well-known supercomputer manufacturer. One student asked how to keep all of their Product Owners' priorities in sync. I asked how many Product Owners they had. The answer was 39, all working on a single product. Each one was aligned to a different technology area, and together they had created a web of dependencies that made almost every decision a negotiation.

Most organizations aren't that extreme, but the same problems show up at any scale. Nobody can easily see progress toward the larger goal, because the work is spread across teams that each track their own tasks. The people doing the work often can't see how their piece connects to anything bigger. And when something has to give, no one on the teams is in a position to make the tradeoff. They were asked to finish their tasks, so that's what they focus on. Every meaningful decision travels back up to leadership, because that's the only place where the whole picture exists.

Much of this comes down to how an organization defines its product. When "product" means a technology component, value gets split across teams and nobody owns the outcome. When a product is defined so that value can be delivered end to end, a single Product Owner can make real tradeoffs toward real goals. That's why we cover defining the product in every Professional Scrum Product Owner class we teach.

Not every organization should copy Amazon's structure. But accountability works better when the people responsible for results can see the goal and have the authority to make tradeoffs toward it. When decision rights are unclear, escalation replaces analysis, and influence can matter more than evidence. Improving product management therefore requires examining how the organization makes decisions, not just developing individual product managers' skills.

Product Delivery Should Keep You Able to Learn

Delivery turns product decisions into something customers can use. How you organize it also determines how much risk you carry and how quickly you can respond when assumptions prove wrong. Large commitments made far in advance create dependencies, increase unfinished work, and make changes expensive. Once substantial money has been invested, organizations often keep going even when the evidence suggests they shouldn't.

  1. Strategy
  2. Discovery
  3. Prioritization
  4. Delivery
  5. Measurement
Use evidence to revisit decisions.

Smaller, usable releases reduce that exposure. They let teams observe how customers behave, uncover technical limitations, and test whether expected benefits materialize before committing more resources. But breaking work into smaller pieces doesn't automatically produce better results. An increment that provides no usable value, generates no meaningful feedback, and reduces no significant risk may simply make progress easier to report.

Speed deserves the same scrutiny. Faster delivery helps when timing matters, but rushing at the expense of quality creates defects, rework, and higher long-term costs. Scrum, Kanban, and other approaches offer useful practices for organizing work, but none can determine which investments deserve funding.

Good product management keeps delivery connected to investment decisions. Teams need clear outcomes, real feedback, and the freedom to change direction when evidence challenges the original plan. The point of delivering in small pieces is to learn quickly enough to make better decisions about what happens next.

Measuring the Results of Product Investments

Delivery activity is easier to measure than the results of product decisions. Features completed, release frequency, and roadmap progress are visible and simple to report. They can reveal operational problems, but they can't tell you whether customers are getting more value or the business is achieving its goals. An organization can know a lot about how work is progressing and very little about whether it was worth doing.

For example

Useful measurement starts with the outcome an investment is supposed to change. Suppose a company redesigns customer onboarding because too many customers abandon the setup process. Counting completed features tells you little. More useful measures include how many customers finish setup, how quickly they get their first meaningful result, and whether they continue using the product afterward. Those measures connect directly to the problem the investment was intended to solve.

Interpreting results takes care because many factors influence outcomes. Improved retention might come from changes in pricing, customer demographics, or market conditions rather than the latest release. Where practical, experiments and comparisons can help establish whether an investment really made a difference.

Define success before development begins, then review the evidence afterward. When something ships successfully but fails to produce the expected benefit, that should inform future investment decisions. Without this feedback, organizations risk repeatedly funding convincing proposals without learning which ones truly work.

Product Management and Product Ownership

Product management is a broad discipline covering product direction, customer needs, investment decisions, and performance over time. Product Ownership is an accountability defined in Scrum. The Product Owner is accountable for maximizing the value of the product resulting from the Scrum Team's work and for effective Product Backlog management. The two overlap considerably, but how they fit together depends on how an organization divides responsibilities and authority.

In some organizations, Product Owners handle much of what product managers traditionally do, including customer research, strategy, prioritization, and evaluating results. In others, product managers focus on commercial and strategic decisions while Product Owners work more closely with development teams. Either arrangement can work, provided decision-making authority and accountability are clear.

Problems arise when organizations introduce both roles without deciding who owns the important decisions. A Product Owner might be expected to maximize value without meaningful influence over strategy, while a product manager might set direction without enough exposure to customers or delivery constraints. The more useful questions are who decides what to invest in, who sets product direction, and who determines whether those investments are paying off.

As the supercomputer example above shows, splitting ownership across technology areas can leave no one accountable for the whole product. Rigid boundaries between job titles matter far less than making sure the important decisions are made by people with the information and authority to make them well.

How Product Management and Business Analysis Complement Each Other

Product management and business analysis often contribute to the same decisions from different angles. Product management focuses on product direction, investment, customer value, and results over time. Business analysis helps organizations investigate needs, understand existing processes, evaluate alternatives, and define what successful change should look like.

For example

Suppose an organization wants to reduce the time it takes to approve customer invoices. Product management helps determine how important the problem is and what investment it deserves. Business analysis can map the current approval workflow, identify where invoices stall, understand what finance and sales each need, and clarify what needs to change. Together, these activities reduce the risk of investing in a solution before the problem is understood.

The boundaries aren't always clear, nor do they need to be. Product managers often perform business analysis, and business analysts frequently contribute to product decisions. What matters is having the skills to investigate problems, evaluate options, and make informed investments. Our Business Analysis Training helps professionals develop these skills and apply them to real business challenges.

Seven Questions That Reveal Whether Product Management Is Working

Organizations often try to improve product management by introducing new roles, tools, or frameworks. Those changes can help, but they won't accomplish much if the underlying decisions remain poor. A better starting point is to examine how your organization chooses investments, evaluates alternatives, and learns from results.

Consider a recent product investment that required significant resources. What problem were you trying to solve? Why was it worth pursuing? What alternatives did you consider, and did the results justify the investment? These seven questions can help identify where product management needs improvement.

1. Are strategic choices explicit?

Can teams explain why certain opportunities deserve investment while others don't? If almost anything can be described as strategic, the strategy probably isn't providing much direction.

2. Does discovery effort match the risk of being wrong?

Are you spending enough time investigating expensive, uncertain decisions without overanalyzing small, reversible changes? Good discovery helps you learn what matters before committing significant resources.

3. Do prioritization discussions include opportunity cost?

When choosing an investment, do you consider what gets delayed or abandoned? Prioritization should account for alternatives, timing, risk, and the cost of waiting.

4. Can product decisions be made without constant escalation?

Do the people accountable for product outcomes have enough authority to make meaningful decisions? Frequent escalation often signals unclear decision rights rather than poor communication.

5. Does delivery produce feedback that changes decisions?

Do customer behavior, technical discoveries, and operating results influence what gets built next? Short development cycles accomplish little if teams never reconsider their plans.

6. Are investment results reviewed?

Do you define expected outcomes before development and evaluate them afterward? Shipping successfully doesn't mean an investment delivered the value you expected.

7. Are AI initiatives held to the same standard?

Are AI investments evaluated for customer value, cost, risk, and expected outcomes? The ability to build something with AI doesn't automatically make it a worthwhile investment.

Turning the Answers Into a Plan

You don't need to improve everything at once. One organization may struggle with understanding customers, another with decision authority, and another with delivering value quickly enough. Identify the weakness causing the greatest problems and concentrate your improvement efforts there. Adopting every recognized product management practice won't help much. Improving the few decisions that have the greatest impact on results will.

Developing Stronger Product Management Capabilities

Good product management comes down to making important decisions with limited resources and incomplete information. Strategy provides direction, discovery improves understanding, prioritization guides investment, and delivery creates opportunities to learn. Leadership and measurement help ensure those decisions produce worthwhile results.

Improving product management takes more than introducing a new framework or changing job titles. Organizations need to examine how decisions are made, identify what's getting in the way, and develop the skills and authority to make better choices. The right approach depends on whether the biggest challenge is understanding customers, evaluating opportunities, managing competing priorities, or measuring results.

At Responsive Advisors, we help professionals and organizations strengthen these capabilities through practical training, coaching, and consulting. Our focus is on applying sound product management principles to real business challenges, where resources are limited, priorities compete, and decisions have consequences.

Robert PIeper

About the Author

Robb Pieper

CEO and Principal Advisor at Responsive Advisors

Robb Pieper is the founder of Responsive Advisors, where he has spent more than a decade developing products and services and helping organizations improve how they work. With a background in software development and an MBA with a concentration in Finance, he brings both technical and business perspectives to product management. He works with leaders and teams to make better investment decisions, solve meaningful customer problems, and deliver measurable business results.