Unit 2: The product trio: PM, design, engineering

Learning objectives

By the end of this unit, you should be able to describe the distinct contributions of each role in the product trio, understand how the trio collaborates during discovery and delivery, and recognize how AI is changing the dynamics between these three roles.

Video script

Reading material

How the trio actually works

In a well-functioning product trio, the three members share ownership of discovery. They jointly conduct customer interviews, review research together, and collaborate on problem definition. The PM doesn't go off and do discovery alone and then present findings to the team. Everyone is in the room (or on the call) with the customer.

This matters because each person notices different things. The PM notices when the customer describes a problem that aligns with a business opportunity. The designer notices when the customer struggles with a workflow or uses unexpected terminology. The engineer notices when the customer describes a problem that has a simpler technical solution than what the team was considering.

During delivery, the roles diverge more. The designer refines the experience, the engineer builds the solution, and the PM coordinates with stakeholders and monitors progress toward the outcome. But even here, daily collaboration matters. A standup where the trio reviews what they learned yesterday and adjusts today's work is very different from a standup where individuals report status on their tasks.

Common dysfunctions

The PM as product owner (backlog manager). In many agile implementations, the PM becomes the "product owner" whose main job is grooming the backlog and writing acceptance criteria. This reduces the PM to an order-taker and breaks the trio dynamic because the PM is operating downstream of the real decisions.

The designer as pixel-pusher. When design is brought in after decisions are made, the designer's job is reduced to making things look good. They can't influence the solution direction because the direction is already set. Good designers have deep insight into user behavior and should be shaping what gets built, not just how it looks.

The engineer as implementer. When engineering is treated as a build-to-spec function, you lose the most creative technical perspectives. Engineers often see elegant solutions that the PM and designer would never think of, but only if they're involved early enough to understand the problem.

The trio in an AI world

AI changes the trio dynamic in a few specific ways.

The prototype gap shrinks. AI tools let each member of the trio create rough versions of the others' work. A PM can generate a mockup to communicate an idea. A designer can create a functional prototype. An engineer can draft product copy. This means conversations start with something tangible instead of abstract descriptions, which makes collaboration more productive.

The analysis burden lightens. AI can handle data synthesis that used to be manually distributed across the trio. Customer interview summaries, usage analytics, competitive research, these can be processed by AI, freeing the trio to focus on interpretation and decision-making.

The quality bar rises. When AI handles routine execution, the trio's human contributions need to be more thoughtful. A designer who just produces layouts is competing with AI that can do the same thing. A designer who brings deep understanding of user behavior and interaction design principles is irreplaceable. The same applies to every role in the trio.

Practical exercise

Exercise: Trio simulation

Pick a product you use daily (a messaging app, a task manager, a note-taking tool, or anything else). Now imagine you're part of the product trio for that product.

From the PM perspective: What's the biggest unmet need for users of this product? What business outcome would solving it drive?

From the design perspective: What's the most frustrating user experience in the current product? How would you redesign it?

From the engineering perspective: What technical constraint or opportunity do you notice? Is there something the product could do that it doesn't because of a technical limitation or assumption?

Now combine the three perspectives: where do they overlap? Where do they conflict? Write a brief (one paragraph) product opportunity that synthesizes all three viewpoints.

The goal isn't to get the "right" answer. It's to practice looking at the same product through three different lenses and finding the synthesis.