Product impact beyond delivery speed: Measuring decisions that create value
Many product managers are measured on how quickly they move products from idea to market. Whether that's a new software feature, a consumer product, a government service or an operational improvement, delivery speed is one of the easiest things to measure.
Speed matters. Customers benefit from products reaching the market sooner, organisations respond faster to change, and teams maintain momentum. But delivery speed only tells part of the story.
Product management starts long before development begins and continues well after a product is launched. The biggest decisions often happen before a single line of code is written or before a factory begins production. Likewise, the real measure of success isn't that a product shipped. It's whether it solved the right problem and created lasting value.
Throughout my career, I've worked across both physical and digital products. While the environments are very different, I've found the fundamentals remain the same. Every successful product relies on understanding customer needs, making informed decisions, bringing the right people together and measuring outcomes that matter.
I tend to think about product impact across five connected areas:
Discovery and research
Strategy and design
Delivery and execution
Stakeholders and governance
Commercial outcomes
Each area has its own measurements. Together, they tell a much richer story than delivery speed ever can.
by Lucas Gabriel ©2026
A note on the "product management role"
Product management does not have a single definition. The role changes depending on the organisation, product maturity, industry, scale and the needs of the business.
Some product managers focus heavily on discovery and strategy, while others may spend more time supporting delivery, operations, stakeholder management or project coordination. In some organisations, the role may overlap significantly with project management.
The important thing is understanding the environment you operate in, where decisions are made and how you create value. The five areas outlined in this article are not a checklist or a fixed role description. They are a way to think about the different areas that contribute to product impact.
Discovery and research
Discovery and research form the foundation of every successful product. Before teams build anything, they need confidence that they're solving the right problem for the right people.
This stage is about reducing uncertainty. That means understanding customers, identifying pain points, exploring market opportunities, validating assumptions and recognising technical, commercial or operational constraints.
For physical products, this might involve supplier research, manufacturing capability or retail requirements. For digital products, it often includes user research, analytics, technical feasibility and competitor analysis.
Skipping discovery doesn't save time. It simply shifts the cost further into the project, where mistakes become far more expensive to fix.
What gets measured?
Number and diversity of customer interviews or research sessions
Quality of customer and market insights
Validation of assumptions through prototypes, samples, MVPs, mock-ups, pilot runs or experiments
Competitor and market analysis
Time invested in discovery compared to delivery
Confidence in the problem definition before development begins
What product managers influence
Product managers decide where the team should focus its research and which assumptions carry the greatest risk. They bring together customer insights, business objectives and technical knowledge to build a shared understanding of the problem before proposing solutions.
They don't aim to remove every uncertainty. They reduce enough uncertainty for the team to make informed decisions with confidence.
What the measurements reveal
Strong discovery metrics suggest a team understands both the customer and the problem they're trying to solve. Decisions are backed by evidence rather than opinion, reducing the risk of expensive changes later.
Weak discovery often shows up as feature creep, changing priorities, poor adoption or products that technically work but fail to deliver meaningful value.
Digital example
Imagine a government planning platform designed to support local councils and urban planners. Before writing any software, the product team spends months interviewing planners, infrastructure specialists, emergency services, government agencies and community representatives. They map existing workflows, identify common frustrations and validate assumptions using early prototypes.
The result isn't simply a better interface. It's a product that reflects how people genuinely work, reducing rework during development and uncovering opportunities the original project team hadn't considered.
Physical product example
A toy company is preparing to launch a new construction set aimed at children aged eight to twelve. Early testing reveals that younger children struggle with the assembly instructions, while parents are more concerned about durability than originally expected. Retailers also provide feedback on packaging size and shelf presentation before production begins.
Rather than treating this as late-stage feedback, the product team adjusts the design, simplifies the instructions and redesigns the packaging before committing to manufacturing. These relatively small changes improve customer satisfaction while avoiding significant production costs after tooling has begun.
Strategy and design
Discovery tells us what problem to solve. Strategy and design determine how we'll solve it.
This stage turns research into a clear product direction. It connects customer needs with business objectives and translates both into a roadmap that teams can execute. While designers shape the experience and engineers define the technical solution, product managers bring these perspectives together to ensure everyone is working towards the same outcome.
For digital products, strategy may focus on user experience, platform capability and scalability. For physical products, it also considers manufacturing, sourcing, compliance, packaging, logistics and retail requirements. Although the constraints differ, the goal remains the same: build the right product in the right way.
What gets measured?
Clarity of the product vision and objectives
Alignment between the roadmap and business strategy
Customer and user experience through testing and feedback
Number and quality of design iterations
Prioritisation of high-value features or product improvements
Confidence from stakeholders before delivery begins
What product managers influence
Product managers define priorities, balance competing needs and keep teams focused on solving the original problem. They work closely with designers, engineers, marketers, manufacturers and business stakeholders to ensure decisions support both customer value and organisational goals.
Rather than designing every screen or engineering every component, they define what success looks like and create the conditions for great solutions to emerge.
What the measurements reveal
Strong strategy and design metrics show the team has a clear direction and is making deliberate decisions rather than reacting to changing opinions. Teams spend less time revisiting earlier decisions because priorities are understood and aligned.
Poor results often appear as unclear priorities, unnecessary features, design rework or products that meet technical requirements but fail to meet customer expectations.
Digital example
A product team is developing a planning platform that helps councils assess development applications. Early usability testing reveals that planners spend too much time navigating between maps, documents and reporting tools. Rather than adding more functionality, the roadmap shifts towards simplifying workflows and reducing the number of steps required to complete common tasks.
The strategy remains focused on improving productivity rather than increasing feature count, resulting in higher adoption and greater user satisfaction.
Physical product example
A manufacturer is developing a new range of reusable drink bottles. Customer research shows buyers value durability and ease of cleaning over additional accessories. At the same time, production teams identify opportunities to simplify manufacturing by reducing the number of moulded components.
The product manager balances customer expectations, manufacturing capability, cost targets and retail pricing to produce a product that delivers greater value while remaining commercially viable.
Delivery and execution
Delivery and execution is where product strategy becomes a real customer experience.
In digital products, this may involve development, testing, deployment and release. In physical products, it may involve manufacturing, quality assurance, packaging, distribution and retail launch.
But delivery does not end when a product is released or reaches the shelf. A product only creates value when customers understand it, engage with it and choose to use it.
This is where product management connects with launch planning, customer onboarding, communication and feedback loops. A technically successful product can still fail if customers do not understand its value, struggle to adopt it or have no clear pathway to provide feedback.
For digital products, this may mean onboarding journeys, training, support content, analytics and continuous improvements based on user behaviour. For physical products, it may mean brand positioning, packaging design, retail presentation, instructions and customer feedback that influence future improvements.
What gets measured?
Delivery speed, including cycle time and release frequency
Product quality through testing, defect rates and customer issues
Launch readiness and customer adoption
Onboarding completion and engagement
Customer feedback and satisfaction
Speed of responding to issues and opportunities after launch
What product managers influence
Product managers help teams move from building a product to creating a successful customer experience. They coordinate delivery teams while also ensuring customers understand the product, know how to use it and have opportunities to provide feedback.
They work closely with designers, engineers, marketers, manufacturers, sales teams and customer support to ensure the product delivers value beyond its initial launch.
What the measurements reveal
Strong delivery metrics show a team can execute effectively, but adoption and feedback reveal whether the product is creating real value.
A product that ships quickly but struggles with adoption may have a delivery problem, but it may also indicate gaps in positioning, onboarding, communication or customer understanding.
Digital example
A government platform launches a new digital service designed to simplify planning workflows. Although the technology performs well, early adoption is lower than expected. User research reveals that customers need clearer guidance and examples before changing existing processes.
The product team introduces improved onboarding materials, training sessions and feedback channels. Adoption increases because the team measured success beyond the technical release.
Physical product example
A consumer product company launches a new children's product into retail stores. The product quality is strong, but customer feedback shows that the packaging does not clearly explain how the product works or why it is different from competing products.
The product team works with brand, packaging and marketing teams to improve the customer experience at the point of purchase. The next production run includes updated packaging and clearer messaging, improving customer understanding and sales performance.
The product was not only designed and manufactured. It was communicated, experienced and improved.
Stakeholders and governance
No product succeeds in isolation. Every product exists within an organisation, and every organisation has people with different priorities, responsibilities and expectations.
Stakeholders and governance are about creating alignment. Product managers spend much of their time connecting teams, facilitating decisions and ensuring the right people have the right information at the right time. This isn't simply about communication. It's about helping organisations make informed decisions that keep products moving in the right direction.
In digital environments, governance may involve engineering, cybersecurity, privacy and executive approvals. For physical products, it might include manufacturing, procurement, quality assurance, compliance, logistics and retail partners. Regardless of the environment, product managers act as the bridge between strategy and execution.
What gets measured?
Stakeholder engagement and satisfaction
Speed and quality of decision making
Alignment between business objectives and delivery priorities
Frequency and effectiveness of communication
Resolution of risks, issues and dependencies
Number of escalations or project delays
What product managers influence
Product managers create alignment between teams with different goals and perspectives. They facilitate discussions, clarify priorities and provide enough evidence for stakeholders to make confident decisions.
They don't own every decision, but they often create the conditions for good decisions to happen. By identifying risks early, resolving competing priorities and maintaining transparency, they help teams spend less time waiting and more time delivering value.
What the measurements reveal
Strong stakeholder and governance metrics indicate an organisation is working together rather than in silos. Decisions are made efficiently, risks are managed proactively and delivery maintains momentum.
Poor governance often appears as delayed approvals, conflicting priorities, duplicated effort or teams solving different versions of the same problem.
Digital example
A government agency is implementing a digital planning platform used by multiple departments and local councils. Each stakeholder group has different priorities, from policy compliance to technical integration and operational efficiency. Regular governance meetings, transparent reporting and clearly defined decision pathways help maintain alignment throughout delivery.
Rather than becoming a reporting exercise, governance enables faster decisions, removes blockers and builds confidence across the organisation.
Physical product example
A consumer products company is preparing to launch a new seasonal product range. Marketing wants additional features to improve shelf appeal, manufacturing is concerned about production timelines and procurement identifies supply risks for a key component.
The product manager works with each team to assess trade-offs, balance priorities and agree on a solution that protects the launch date while delivering the greatest value for customers and the business.
Commercial outcomes
The ultimate measure of a product isn't whether it was delivered on time. It's whether it created meaningful value.
Commercial outcomes connect product decisions to organisational success. For commercial businesses, this may include revenue, profitability or market share. For government, education and not-for-profit organisations, success may be measured through adoption, operational efficiency, community outcomes or improved service delivery.
This is where product management moves beyond building products and begins demonstrating impact.
What gets measured?
Revenue growth or cost savings
Customer acquisition, retention and satisfaction
Product adoption and active usage
Market share or audience growth
Operational efficiency and productivity improvements
Return on investment (ROI)
Achievement of strategic organisational objectives
What product managers influence
Product managers continuously evaluate whether the product is delivering the intended outcomes. They analyse customer behaviour, monitor business performance and identify opportunities to improve value over time.
While many commercial outcomes depend on sales, marketing and operations, product managers influence the decisions that shape those outcomes from the earliest stages of discovery through to ongoing product improvement.
What the measurements reveal
Strong commercial outcomes demonstrate that the product is solving meaningful problems while supporting organisational objectives. They validate that the investment in discovery, strategy, delivery and stakeholder alignment has translated into measurable value.
Weak commercial outcomes often indicate a disconnect between what was built and what customers or organisations genuinely needed. Sometimes the product was delivered successfully, but the underlying problem was never the right one to solve.
Digital example
A government digital platform is launched to improve planning and infrastructure decision-making across multiple agencies. Rather than measuring success purely through system uptime or completed releases, the product team tracks adoption, reductions in manual processes, faster planning decisions and lower support requests.
These measures demonstrate that the platform is improving how government operates, not simply that new software has been delivered.
Physical product example
A retailer introduces a redesigned home organisation product based on customer research and manufacturing improvements. The updated design reduces production costs, increases shelf availability and receives stronger customer reviews than the previous version. Sales increase, product returns decline, and retailers expand the product range into additional stores.
The commercial success wasn't driven by one decision. It was the result of better product management across every stage of the product lifecycle.
Delivery speed will always matter. Products that reach customers sooner can create a competitive advantage, respond to changing needs and generate value earlier. But speed is only one measure of success, and often not the most important one.
The products that make the greatest impact are rarely the ones built the fastest. They're the ones built with a clear understanding of the problem, a well-defined strategy, strong collaboration and a relentless focus on outcomes after launch.
Across both physical and digital products, I've found the principles remain remarkably consistent. The tools, technologies and constraints may differ, but the role of the product manager does not. We're there to reduce uncertainty, make informed decisions, bring people together and maximise value throughout the product lifecycle.
If we measure product managers only by how quickly they deliver, we risk rewarding activity over impact. When we also measure the quality of discovery, the strength of strategy, the effectiveness of governance and the commercial outcomes achieved, we gain a far more complete picture of product success.
The best product managers don't just deliver products.
They deliver outcomes that matter.
