Article
October 6, 2026
8 min read
What Makes a Great Product Team
Great product teams combine specialist depth with shared responsibility for customer usefulness, from the first question through delivery and learning in use.
By Cristiano Pierry
The principles behind a team of builders.
Consider a recommendation feature that earns more clicks while leaving customers struggling to find something they actually want. The experiment looks promising in one measure. Someone still has to ask what happened after the click, whether the experience improved, and what the team should change. That question belongs to everyone who helped build the feature.
A great product team brings people close enough to a customer problem to help shape the solution and stay responsible for what happens when customers use it. Its members have different areas of expertise, and they draw on that depth together. Everyone can exercise judgment, challenge an assumption, and help move an idea toward a useful result.
That is the foundation of a team of builders. For an aspiring product manager, learning to participate in this work is an important part of learning the job. A prototype can make a question concrete enough for others to inspect. An investigation can reveal what a requirement actually means for the system. The PM contributes to that work and helps keep it connected to the customer problem.
The customer experience belongs to the whole team
The team should be able to explain whose problem it is solving and what a substantially better experience would look like. Ambition begins here: helping someone accomplish something that was previously difficult, or removing a frustration they had learned to tolerate. Customer trust needs to be earned through the decisions that follow, including how the product behaves when something goes wrong.
In the recommendation example, more clicks could reflect curiosity, confusion, or a useful discovery. The team needs evidence about what followed. People should examine measures of engagement alongside customer satisfaction and the commercial outcomes the product is meant to support. A product manager helps make those relationships explicit so people can explain what they are optimizing and why. Customer value and a sustainable business need to be considered together.
That perspective extends to the whole organization. A decision can create work for an upstream partner, increase costs elsewhere, or leave another team managing a problem after launch. People should bring attention to issues beyond their immediate scope and help the appropriate owner resolve them. Clear ownership gives collaboration structure and makes the gaps between teams easier to address. A team that optimizes its own result while passing the cost to others has more work to do.
The design also needs to consider people beyond the first launch. Language, accessibility, regional differences, and eligibility constraints can affect whether an experience works at all. A local implementation should reflect an understanding of the broader audience and the requirements that future expansion will bring. A PM should raise those considerations early enough for them to influence the design.
Choose the important problem and investigate it properly
Shared responsibility requires focus. A team needs the courage to give up worthwhile opportunities so the most important work has a chance to succeed. Those choices must change how people spend their time. The familiar task can be appealing because people know how to do it well. Ruthless prioritization means confronting the difficult, consequential problem even when easier work would produce a more comfortable status update. The team also needs to decide which uncertainty deserves its next experiment and make room for the people needed to resolve it.
Focus should support ambitious goals. Suppose a product needs to become substantially faster without requiring a much larger operating budget. Improving the current implementation may be insufficient. The team may need to change the architecture, eliminate work, or develop a capability that serves several needs. An ambitious goal can force a reconsideration of the approach and an investigation of tradeoffs that had seemed unavoidable. The PM helps keep the customer outcome clear while the team works through what a different approach would require.
This kind of work demands depth. When a result contradicts expectations, the team audits the evidence and examines the details. Suppose the feature earns more clicks, yet people repeatedly restart their search. The team needs to inspect the path after the click. Perhaps the customer discovers that a promising result is unavailable, or the measurement counts a failed attempt as engagement. Check the underlying records and the measurement before deciding what to change. A PM needs enough understanding to participate in that investigation and recognize when specialist judgment is needed. No relevant task becomes beneath someone's attention because of their title.
The investigation should improve the system that produced the result. Recurring defects may point to a missing check, an unclear handoff, or a process that cannot scale. Fix the immediate issue and change what allows it to recur. Build prompt feedback into the process so the team can see whether the improvement holds. Lasting progress includes making the next problem easier to prevent or detect.
Customer feedback belongs in that loop. A working prototype gives people something concrete to inspect and challenge together. Research and experiments help establish whether the proposed experience is useful to customers. The team bases launch decisions on evidence of customer value or explicit business priorities. Measures should evolve as the team learns: an early indicator that helps validate an idea may be insufficient once the product is used more widely. A PM helps establish what evidence would justify continuing, changing direction, or stopping.
Simplification applies to both the product and the way it is built. Customers should be able to accomplish their task with as little unnecessary effort, delay, and navigation as possible. Internally, each process should earn the time it takes. Repetitive manual work is an opportunity to improve the workflow and automate where that serves a clear goal. Removing complexity should make the experience easier for the people who use, build, and support it.
Care with resources requires understanding the full cost of a decision. Skipping an investment in testing or tooling may create repeated work that costs far more over time. A saving should hold up after its consequences are included. A product manager needs to understand those consequences with the people who will bear them.
AI tools can give more people a way to explore an idea directly in working software. A PM might test whether a simpler flow still respects an eligibility constraint, then bring that experiment to the people qualified to review it. Agreed scope and appropriate access help the team use those experiments responsibly. Where machine learning shapes the customer experience, human expertise also helps address cases the system does not yet handle well and improve its performance. The builders remain responsible for judging the behavior and deciding what is suitable for use.
Make disagreement useful
Relevant knowledge should carry weight regardless of who holds the most senior title. People need to challenge openly, explain their evidence, and listen to competing views. Preserving social harmony is a poor reason to leave a consequential concern unexamined. When a disagreement can be explored in working software, the team can try alternatives and examine what each reveals. Product managers help clarify the decision and communicate the reasoning well enough for others to engage with it. Influence grows through useful insights and clear explanation.
Once a decision is made, everyone commits to helping it succeed. People who argued for another approach bring the same effort to execution as those who supported it. The team continues to observe the result and agrees on what evidence would warrant reopening the decision. Full commitment includes giving the chosen approach a serious test and being honest about what that test reveals.
Learning requires people to set ego aside. Seek the best ideas from inside and outside the team's disciplines. Acknowledge mistakes without rationalizing them and accept that growth can involve criticism, vulnerability, and failure. Leaders have particular responsibility for making that candor possible through their own behavior. An aspiring PM can contribute by asking for feedback, showing uncertainty where it exists, and changing a position when the evidence warrants it.
Carry the work through and develop the people doing it
Urgency comes from recognizing that delay has consequences. A customer problem left unresolved or a decision repeatedly deferred can carry real costs. Take calculated risks, assess what can be learned through action, and move without waiting for a perfect answer or protection from blame. When a dependency blocks progress, identify what is needed, engage the right people, and actively look for a path forward.
Delivery means producing a timely, high-quality result and checking that it works in use. Long hours and visible effort cannot establish whether the customer problem was solved. The people making early choices should stay involved through the review, testing, and follow-up those choices require. A builder team needs time and support to carry a promising idea beyond the demo and learn from its use.
Excellence needs to be visible in the work. Define what good looks like, examine weak reasoning and recurring defects, and keep raising the standard as the team's capabilities improve. Constructive feedback should lead to better work. Hiring and promotion decisions should raise the team's capability too, with attention to long-term needs. Exceptional talent deserves an investment in development through coaching, meaningful responsibility, and opportunities to grow into new areas, including roles elsewhere in the organization.
An aspiring product manager can contribute before having authority to set the team's direction. Bring a customer question into the work, help make an idea concrete enough to test, and learn from the people who understand the system. Stay involved when the result challenges the original assumption or needs more work than expected. In the recommendation example, that means staying with what customers do after the click and carrying what the team learns into the next decision.
This writing reflects my personal perspectives on product management, AI, and content discovery. It does not represent the official position of my employer or any affiliated organization.