Download as PDF, PPTX
Uploaded byuxpin
Three's a Party: How Trifectas Help Product, Engineering, and Design Work Together
The document discusses the concept of trifectas in product organizations, emphasizing the collaboration of product management (PM), user experience (UX), and engineering roles to enhance project execution and organizational health. It outlines the responsibilities of product and domain trifectas in steering projects and driving decision-making while promoting agility and accountability. Additionally, it highlights the importance of monitoring team dynamics, communication, and project outcomes to ensure successful collaboration across different roles.
More Related Content
Similar to Three's a Party: How Trifectas Help Product, Engineering, and Design Work Together
Three's a Party: How Trifectas Help Product, Engineering, and Design Work Together
- 1. Davis Neable Three’s aParty: How Trifectas Help Product, Engineering, and Design Work Together
- 2. It takes twoto make a thing go right three
- 3.
- 4.
- 5. What is atrifecta?
- 6. - David O.Russel “The trifecta of directing is character emotion, camera movement, and music. When you hit those three, that's magical.”
- 7.
- 8. Product Engineering UserExperience
- 9.
- 10. Product Trifecta responsibilities areassumed within small teams PM UX ENG
- 11. One trifecta guidesa small number of projects Project teams Product PM UX ENG
- 12. Product and domaintrifectas steer large organizations Project teams Domain Product PM UX ENG
- 13. Product managers A snapshotof the current Shopify Plus RnD organization Developers UX folks (Design, user research, content strategy, front-end development) = 4 6% 65% 29%
- 14. • Freedom andautonomy for project teams to move quickly • A defined pool for resource sharing at scale • Stability for building rich domain expertise and role specificity • Foundation for spinning up new domains and projects Trifecta model provides:
- 15. Trifectas provide structure, vision,and flexibility so product organizations can execute efficiently and effectively.
- 16. • Only forproduct organizations • Just balanced skill representation • A gatekeeper (even though it can feel like that sometimes) • Easy What a trifecta is not:
- 17. Trifectas have clear responsibilitiesand should demand accountability. 1
- 18. Dreams in years,acts in quarters. ● Resourcing ● Identifying new investment areas ● Organization design ● Set strategic priorities ● (re)Prioritizing the roadmap Product trifecta Responsible for the outcome of the entire product offering
- 19. Dreams in quarters, actsin months. ● Lead a team of teams ● Alignment and health of project teams ● Maintenance decisions ● Kick off new projects ● Release planning ● Define project type ● Milestone changes Domain trifecta Responsible for the outcome of a set of projects, typically grouped by a product theme
- 20. Dreams in months, actsin weeks. ● Executing against the project brief and vision ● Keeping domain trifecta informed ● Sprint planning ● Retrospectives ● Demos ● Milestone reviews Project teams Responsible for an individual project’s outcomes.
- 21. Product Trifecta DomainTrifecta Project Team Roadmap definition Project kickoff Execution Maintenance decisions Milestone change Project involvement varies across layers Actor Stakeholder
- 22. 2 Trifectas canbe leveraged as organizational structures.
- 23. Trifectas used tomodel the organization of projects PM UX ENG Project teams Domain Product
- 24. Trifectas used tomodel the organization of projects PM UX ENG Project teams Domain Product Shopify Plus Automation Shopify Flow Plus Services Migration Billing OnboardingShopify Scripts
- 25. Trifectas can alsodouble as clear reporting structures UX Project teams Domain Product Director level Senior leads & leads Individual contributors
- 26. Trifectas help gaininsight into organizational health. 3
- 27. Identify missing roles PM UX ENG Projectteams Domain Product
- 28. PM UX ENG Improve communication efficiencies Projectteams Domain Product
- 29.
- 30. Team Have we assembled the rightteam? Alignment Do we agree on the goals and metrics? Quality Does it solve customer problems and will it delight them? Scrappiness Are we being opinionated and saying “no” to the right things? Keep score Can we tell if the project and team are hitting their goals? Asking effective questions
- 31. • Project rituals,such as spring planning, demos and retros (weekly) • Project milestone reviews with trifecta (varies) • Organization-wide project leads synch (weekly) • Cross-domain trifecta synch (weekly) • ... Leverage trifectas to gain context:
- 32.
- 33. Photo by CynthiaAndres Organization changes should come after a trifecta has been stabilized to minimize thrash.
- 34. It takes timeto build the trust necessary for a trifecta to be wholly effective. Photo by Sebastian Grochowicz
- 35. Photo by CynthiaAndres As the organization grows, identify the magnitude of the change and respond appropriately.
- 36. Scaling product groupsis hard work
- 38.
- 39.