product-trio

## Core Principle The Product Trio is the minimum viable team for building great digital products: a **Product Manager**, a **Designer**, and a **Software Engineer** working collaboratively from beginning to end, rather than passing work sequentially through handoffs. Unlike traditional waterfall approaches where PM writes requirements → Designer creates mockups → Engineers build, the trio works together throughout discovery and delivery, bringing their unique perspectives to every decision. ## When to Use Deploy the Product Trio model when you need to: - **Break down silos** between product, design, and engineering teams - **Accelerate discovery** through parallel exploration instead of sequential phases - **Reduce rework** from late-stage feasibility or usability issues discovered after handoffs - **Build missionary teams** that own outcomes rather than mercenary teams executing orders - **Scale product development** while maintaining quality and team autonomy Particularly critical during product discovery phases where fast iteration on assumptions requires tight collaboration. ## How It Works ### Trio Roles and Responsibilities **Product Manager (Business Viability)** - Defines problems worth solving based on business goals and customer needs - Prioritizes opportunities using data and strategic alignment - Ensures solutions create value for users and the business - Manages stakeholder communication and expectations **Designer (Desirability & Usability)** - Translates user needs into intuitive, delightful experiences - Prototypes solutions for rapid testing and iteration - Validates assumptions through user research and testing - Advocates for user experience in all decisions **Engineer (Feasibility & Scalability)** - Assesses technical feasibility of proposed solutions - Identifies constraints, opportunities, and tradeoffs - Contributes technical innovation to solve problems - Ensures solutions are buildable within constraints ### Collaborative Discovery Process **Step 1: Define Opportunity Together** - Trio reviews customer data, user research, and business goals as a team - Collectively identifies problems worth solving - Creates shared understanding of success metrics - **Output**: Aligned opportunity framing with clear success criteria **Step 2: Generate Solutions Collaboratively** - All three roles contribute ideas based on their expertise - Designer sketches concepts, Engineer identifies technical approaches, PM evaluates business fit - Avoid premature constraints ("we can't build that") in divergent phase - **Output**: Diverse solution concepts evaluated from all three perspectives **Step 3: Rapid Prototyping and Testing** - Designer creates low-fidelity prototypes - Engineer validates technical assumptions (spikes, proof-of-concepts) - PM tests value proposition with customers and stakeholders - **Output**: Validated or invalidated assumptions with evidence **Step 4: Make Decisions Together** - Evaluate tradeoffs between desirability, feasibility, and viability - Reach consensus on approach that balances all three constraints - Document decisions and reasoning for future reference - **Output**: Shared commitment to solution with understood tradeoffs **Step 5: Build and Iterate** - Engineer implements with ongoing design and product input - Designer refines experience based on implementation realities - PM adjusts scope and priorities based on learnings - **Output**: Shipped product increment with team ownership ### Anti-Patterns to Avoid **Handoff-Driven Work**: PM defines everything upfront, hands to design, design hands to engineering. This delays feedback and creates rework. **Hero Culture**: One person (usually PM or senior engineer) makes all decisions while others execute. Wastes expertise and creates bottlenecks. **Sequential Validation**: Test feasibility after design, or test usability after building. Front-load validation by working together. **Meeting-Heavy Collaboration**: Don't replace work with status meetings. Work together in shared tools, with focused sync points. **Unbalanced Voice**: All three perspectives must carry weight. If engineer is just "order taker" or designer is "pixel pusher," you don't have a trio. ## Practical Examples **Example 1: New Feature Discovery** Context: Team exploring payment options for SaaS product - **PM** brings data: 40% of churned trials cite "billing too complex" - **Designer** conducts user interviews revealing confusion around upgrade paths - **Engineer** identifies Stripe API capabilities that enable one-click upgrades - **Trio Decision**: Build simplified upgrade flow using Stripe Checkout instead of custom billing - **Outcome**: Reduced engineering effort, better UX, faster time-to-market **Example 2: Technical Debt vs Feature Work** Context: Core search feature slow, but roadmap has new features planned - **Engineer** demonstrates 5-second search latency causing user drop-off - **Designer** shares research showing users abandon after 3 seconds - **PM** analyzes impact: search used in 80% of sessions, affecting retention - **Trio Decision**: Reprioritize roadmap to fix search performance before new features - **Outcome**: Data-driven tradeoff balancing tech health with feature delivery **Example 3: Scaling to Multiple Trios** Context: Product growing beyond single team capacity - Define clear ownership boundaries (e.g., by user journey or product area) - Each trio owns outcomes for their domain end-to-end - Cross-trio coordination through shared rituals (demo days, architecture reviews) - Avoid centralizing functions (all designers reporting to design lead) ## Expected Outcomes - **Faster Time to Market**: Parallel exploration eliminates sequential bottlenecks - **Higher Quality Decisions**: Three perspectives catch issues early (business, user, technical) - **Reduced Rework**: Feasibility and usability validated before full implementation - **Increased Team Ownership**: Collective decisions create missionary, not mercenary teams - **Better Work-Life Balance**: Distributed decision-making reduces hero culture and burnout Success metric: Teams can articulate why they're building something (not just what) and make autonomous decisions without escalation. ## Complementary Practices Combine Product Trio with: - **Continuous Discovery Habits** (Teresa Torres) for weekly customer touchpoints - **Dual-Track Agile** to run discovery and delivery in parallel - **Opportunity Solution Trees** for structured decision documentation - **Empowered Product Teams** (Marty Cagan) for autonomous team structure --- **Concept Origin**: Marty Cagan (SVPG), Teresa Torres (Product Talk) **Key Resources**: - Inspired: How to Create Tech Products Customers Love (Cagan, 2017) - Continuous Discovery Habits (Torres, 2021) - Product Talk: Core Concept - The Product Trio