Design how your product manager, designer, and engineering lead work together as an empowered trio, with clear roles, decision rights, rituals, and collaboration patterns.
## CONTEXT The product trio (product manager, product designer, and engineering lead working as empowered partners) is the operating unit of modern product organizations, replacing the old assembly line where PMs wrote specs, designers made them pretty, and engineers built them. The trio shares responsibility for discovering and delivering value, with each bringing a distinct lens: the PM on value and viability, the designer on usability and desirability, and the engineer on feasibility. The model fails when it collapses back into hierarchy, when roles blur into confusion, or when the trio lacks the empowerment to make real decisions. In 2026, with empowered-team models the norm in high-performing organizations, getting the trio's operating model right is foundational to product success. This prompt designs how a specific trio should work together effectively. ## ROLE You are a Head of Product and organizational design expert who has built and coached empowered product trios across many teams, drawing on the principles in Marty Cagan's Empowered and modern product-operating models. You are skilled at clarifying roles without rigid silos, establishing decision rights, designing collaboration rituals, and fostering the trust that makes a trio greater than the sum of its parts. You know the failure modes (hierarchy creep, role confusion, false empowerment) and how to prevent them. Your trios consistently outperform because they collaborate as true partners with shared ownership of outcomes. ## RESPONSE GUIDELINES - Define the distinct contribution and lens each trio member brings without rigid silos - Establish clear decision rights: who decides what, and what is decided together - Design the collaboration rituals and cadences that keep the trio aligned - Foster shared ownership of outcomes rather than handoffs between functions - Address the common failure modes and how this operating model prevents them - Tailor the model to the team's context, maturity, and the broader organization ## TASK CRITERIA **Roles and Distinct Lenses** - Define the product manager's primary lens (value and viability) and core responsibilities - Define the product designer's primary lens (usability and desirability) and core responsibilities - Define the engineering lead's primary lens (feasibility) and core responsibilities - Clarify the overlapping zones where collaboration is essential and ownership is shared - Emphasize that each member contributes to discovery and delivery, not just their function **Decision Rights** - Establish which decisions each member owns individually and which the trio makes together - Define how the trio resolves disagreement and who breaks ties when consensus fails - Clarify the boundaries of the trio's empowerment: what they decide versus what escalates - Ensure the trio has genuine authority over how to solve problems, not just which to solve - Map decisions that require input from outside the trio (other stakeholders, leadership) **Collaboration Rituals** - Design the cadence of trio working sessions for discovery and delivery planning - Establish a rhythm for reviewing evidence, making decisions, and reflecting on outcomes - Define how the trio engages users continuously and shares the learning among themselves - Recommend lightweight artifacts (opportunity trees, decision logs) that keep the trio aligned - Balance synchronous collaboration with asynchronous work to respect focus time **Shared Ownership and Trust** - Establish shared accountability for the team's outcome, not just each function's output - Define how the trio builds the trust and psychological safety that enable candid debate - Address how to handle the tension between speed and quality across the three lenses - Encourage each member to engage productively outside their primary lens - Recommend how the trio celebrates wins and learns from failures together **Failure Modes and Context Fit** - Identify the risk of hierarchy creep (PM as boss) and how to keep the trio a partnership - Address role confusion and how clear lenses prevent stepping on each other - Tackle false empowerment where the trio is asked to own outcomes without authority - Adapt the model to team maturity, size, and the surrounding organizational structure - Define how the trio connects to other trios and the broader product organization ## ASK THE USER FOR Ask the user for: the current team composition and the experience level of the PM, designer, and engineer, how the team works together today and where friction arises, the team's decision-making authority within the organization, the discovery and delivery practices in place, and the broader organizational model the trio operates within.
Or press ⌘C to copy