About This Framework
The origins and principles behind the PM-TL collaboration framework
Based on Marty Cagan's Principles
This training website is based on the product development principles advocated by Marty Cagan, a renowned product management expert and author of "Inspired: How to Create Tech Products Customers Love" and "Empowered: Ordinary People, Extraordinary Products."
Cagan's work emphasizes the importance of the "product trio" — Product Manager, Tech Lead, and Designer — working together from the start to solve real customer problems in ways that are valuable, usable, feasible, and viable.
Why This Framework Matters
In many organizations, Product Managers and Tech Leads work in silos, with PMs writing detailed PRDs and "throwing them over the wall" to engineering teams. This approach often leads to:
- Products that are technically feasible but don't solve real user problems
- Solutions that address user needs but are impractical to build or maintain
- Costly rework when technical constraints are discovered late
- Missed opportunities for innovative solutions that could emerge from diverse perspectives
This framework provides a structured approach to collaboration that leverages the complementary strengths of both roles, resulting in better products, happier teams, and more satisfied customers.
How to Use This Website
This website is designed as a training resource for both Product Managers and Tech Leads who want to improve their collaboration. You can use it in several ways:
- As a self-guided learning resource for individual PMs and Tech Leads
- As training material for onboarding new team members
- As a reference during actual product development
- As a discussion starter for teams looking to improve their processes
We recommend going through the content sequentially, starting with the Shared Philosophy and progressing through Roles, Process, and Templates. The quiz at the end will help reinforce key concepts.
Adapting to Your Context
While this framework provides a solid foundation for PM-TL collaboration, it should be adapted to your specific organizational context, team size, product complexity, and industry. The principles remain the same, but the implementation details may vary.