Product trio

The Product Trio is the core collaborative partnership of Product Manager, Product Designer, and Tech Lead (or Engineering Lead) who work together on product discovery and key decisions. Rather than the PM deciding what to build and handing requirements to design and engineering, the trio collaborates on understanding problems and finding solutions together. Each brings a different essential perspective that improves decisions.

Why it matters

Product development suffers when functions work in silos. PMs who decide alone miss technical constraints and design possibilities. Designers who design alone create experiences that can't be built efficiently. Engineers who build alone create technically elegant solutions to the wrong problems.

The trio model integrates these perspectives early, when it matters most. Better decisions emerge from the intersection of user needs (PM), user experience (design), and technical feasibility (engineering). Problems are caught sooner. Solutions are more creative. Buy-in is built through participation.

The three perspectives

Each trio member brings a distinct lens.

Product Manager brings the value perspective. What problems are worth solving? What do users need? What does the business require? The PM ensures the team works on things that matter and understands why.

Product Designer brings the usability perspective. How should the solution work? What experience does the user have? The designer ensures solutions are usable, intuitive, and delightful.

Tech Lead brings the feasibility perspective. What's technically possible? What are the constraints? What are the implementation trade-offs? The tech lead ensures solutions can actually be built sustainably.

All three perspectives are necessary. Products that are valuable but not usable fail. Products that are usable but not feasible don't ship. Products that are feasible but not valuable waste effort.

How the trio works

The trio collaborates throughout discovery and delivery.

Problem understanding involves all three. When exploring user needs and defining problems, each perspective contributes insight. The designer sees experience problems; the engineer sees technical problems; the PM sees business context.

Solution exploration benefits from diverse thinking. Brainstorming with all three perspectives produces more creative options than any individual could generate.

Trade-off decisions require all perspectives at the table. Should we ship a simpler solution faster or a more complete solution later? The answer depends on user needs, experience impact, and technical effort - all three lenses.

Backlog refinement is richer when the trio participates. Stories and requirements improve when technical and design considerations inform them early.

Trio dynamics

Healthy trio collaboration requires certain conditions.

Equal partnership means no role dominates. The PM doesn't dictate to design and engineering; the trio decides together. Each perspective is valued equally.

Regular collaboration keeps the trio connected. This might be daily standups, weekly discovery sessions, or regular joint working time. Collaboration can't happen in occasional meetings.

Respectful disagreement is healthy. Trios should debate; that's how good decisions emerge. But disagreement should be about ideas, not egos.

Shared context keeps everyone informed. If the PM learns something from stakeholders, the trio should know. If the engineer discovers a constraint, the trio should know. No information hoarding.

The trio and the broader team

The trio isn't the whole team - it's the core decision-making partnership.

Other engineers build alongside the tech lead. The tech lead represents engineering perspective in trio discussions but doesn't do all the implementation.

Other designers may exist for larger products. The product designer in the trio represents design perspective in decisions.

User research, data, QA and other functions contribute to the team. The trio incorporates their input into decisions.

The trio serves as the hub for discovery and direction; the broader team executes and contributes.

When trios struggle

Several patterns undermine trio effectiveness.

Handoff mode occurs when roles operate sequentially rather than collaboratively. PM decides, hands to design, design hands to engineering. This isn't a trio; it's a relay race.

PM dominance happens when the PM makes decisions and expects others to comply. This loses the benefit of multiple perspectives.

Absence or partial participation undermines the model. If design never joins discovery sessions, their perspective is missing when it matters most.

Decision avoidance emerges when trios can't resolve disagreements. At some point, decisions must be made; endless debate is dysfunction.

Implementing the trio model

Organizations adopting the trio model should:

Co-locate trio members (or ensure strong virtual collaboration for remote teams). Physical or digital proximity enables natural collaboration.

Include all three in discovery activities - customer interviews, prototype testing, experiment design. Shared experience builds shared understanding.

Establish decision-making norms. How does the trio resolve disagreements? What decisions require consensus versus rough agreement?

Protect trio time. If trio members are pulled into separate meetings and processes, collaboration suffers. Ensure time for joint work.

Trios and customer feedback

Customer feedback is a trio input. When all three members hear directly from customers - through interviews, feedback review, or support observation - they build shared empathy that improves collaboration.

Tools like Klero help trios access customer feedback together, reviewing user input as a team rather than filtered through one role. Shared exposure to customer reality aligns the trio around user needs.