Scope: Product VP's and AVP's
Overview
This growth program is a living document that will continually be updated going forward. In includes an "article cannon" that is helpful references to our own unique Product Operating Model (POM). Each article has a TLDR document, which includes 1) Cody's elitist and condescending perspective 2) an AI summary and 3) the content dump from the article itself.
This POM article cannon needs to be referenced in order to be helpful. There will likely be a GPT you can use to make this easier, but I highly suggest reading the articles at least once too. It is IMPORTANT for a Product leader to identify if they are external / market facing or if they are internal / stakeholder facing. Leveraging Product practices will look different for these groups (heavier for true external customer development). Our P&T orgs largely fall into these identities:
- Customer Solutions (Patrick): member / customer facing, and needs to leverage many of the product practices
- Data Solutions (Greg): this is a hybrid. Data is an indirect value to the Membership as well as Sourcing. When data is being curated for our members, Data Solutions needs to practice a lot of product principles, but when data is needed for Sourcing and RFP's, the product practices can be more lean based on meeting the needs of a captive audience.
- Sourcing Solutions (Strasburger): this is internal facing and the product practices need to be applied appropriately and more efficiently considering there is far less work to get consensus from internal stakeholders.
For shared continued growth, there is also a rounding template that will be used quarterly between Cody and the Product leader, which includes specific homework and expectations done ahead of our meeting.
Lastly, you will find a product job family matrix (PO -> APM -> PM -> Sr PM -> Dir of Prod -> AVP/VP of Prod) as a reference of expectations on the continuum of product.
I. Product Operating Model: Article Canon
Each resource serves as a foundational pillar for the department’s collective mental model. Especially at a leadership level, while the tactics, artifacts, and processes are important, the overall art of thinking of product management and the mental model is most important. Getting lost in the academics or technicalities is a way to miss the mark entirely.
1. Talent Development and Culture (Meta-TLDR)
How are you continuously learning and growing yourself? If you have a team, how are you purposefully growing them? Are you creating a culture where people want to stay because they are growing?
- The Product Manager Assessment (TLDR): A rubric for auditing individual skills and identifying coaching gaps. Also see 1:1 article in section 1 above.
- Managers, Take Your 1:1 Meetings to the Next Level (TLDR): A masterclass in coaching conversations. It provides the specific "Question Banks" for Pillar 4 (Rounding), helping leaders move from status updates to uncovering deep organizational issues. Highly recommend Dossier - The Tactical Guide to Managing Up: 30 Tips read too.
- Nobody is coming to save your career (TLDR) A bit extreme, but the point is to take your growth into your own hands and be unstoppable and relentless. Use your manager as a resource.
2. Delivery and Execution (Meta-TLDR)
How do you know if you are producing value consistently and frequently as efficiently and lean as possible?
- **Stop Starting and Start Finishing** (TLDR): Awesome kanban principles about focus on getting units across the board and delivered. Work your "board" from right to left.
- **Trust but Verify** and **Lesson One: Trust but Verify** (TLDR): Trust is paramount for having productive and empowered teams, but not inspecting consistently is irresponsible and not protecting the team
- **Project Aristotle** (TLDR) the highest performing teams intentionally create psychological safety
- **Tactical milestone execution**(TLDR) this is truly an article on agile. Shift improves estimation accuracy, fosters trust through constant delivery, and feedback influence
3. Product Discovery (Meta-TLDR)
How do you know if you are quickly and cheaply failing on the bad ideas in order to get validation and product-market fit (or stakeholder alignment if internal-only) ahead of development?
- The Opportunity Solution Tree (TLDR): A visual logic map connecting business metrics to customer opportunities.
- High-Integrity Commitments in an Agile Team (TLDR): How to provide predictability to the business without killing agility. How we should be doing product discovery ahead of quarterly commitments.
- The Inconvenient Truth About Product (TLDR): Managing executive expectations regarding failure, discovery, and risk.
- **Bonus Article on Failing Fast through Discovery** Great practice, especially when embarking on a new feature or product, is to document assumptions and then work to validate or invalidate quickly and cheaply up front (timeboxed). The entire purpose is to invalidate your assumptions.
4. Product Leadership and Operating Model (Meta-TLDR)
If you are responsible for a team, how are you running your organization and practicing product principles in a diligent and accountable manner? Are you external-facing (heavier) or are you internal-facing (can be more lean)
- Empowered Product Teams (TLDR): A guide for structuring teams for autonomy and accountability.
- Transformation Theater (TLDR): Distinguishes between "acting" agile and actually delivering value.
- Product vs. Feature Teams (TLDR): The primary diagnostic for whether teams are empowered or just "order takers."
- 12 Signs You’re Working in a Feature Factory (TLDR): A visceral checklist to monitor a team's health.
- Product Operations (TLDR): There are six different models outlined here, which I don't think is worth reading. However, the reason it has remained is to stress the risk of a model where PM's are grown and mentored outside of their direct leader.
- Waterfall to Agile Transition (TLDR): This is primarily applicable for Customer Solutions only. PM vs. PO responsibilities... but if you are market facing, should it be PM and PMM? This is not applicable for internal teams.
5. Product Strategy (Meta-TLDR)
How do you know if you have appropriately created a robust strategy and evangelized it enough?
- Product Roadmaps (TLDR): A critique of traditional pitfalls and date-driven lists.
- The Alternative to Roadmaps (TLDR): Shifting planning toward business outcomes and problems to solve. Most helpful for internal-facing teams.
- OKR and Agile (TLDR): Connecting high-level goals to daily execution without micromanagement.
6. Stakeholder Communication and Influence (Meta-TLDR)
How do you know that you are staying aligned with stakeholders and keeping them fed? Do they feel heard or dismissed? Do they feel valued and are a meaningful contributor? Do they feel current and informed? Do they trust you? With that trust, do they consider you a partner and they value your counsel?
- The Tactical Guide to Managing Up: 30 Tips (TLDR): Provides literal schedules and meeting cadences for 1:1s and product reviews. While written for aligning with your manager, it's a great reference for meeting with stakeholders too.
- Stakeholder Management (TLDR): How to move from being a "servant" to being a "trusted partner" with other executives.
- Missionaries vs. Mercenaries (TLDR): Cultivating a culture of ownership where teams believe in the vision.
7. Product Knowledge and Domain SME (Meta-TLDR)
How do you know if you know your problem space enough? Have you become the defacto source for questions and strategy debate?
- What is a Product? (TLDR): Main point I appreciate is the fact that a product person needs to deeply understand not just the customer, but the business and business stakeholders too
- Product Fail (TLDR): Establishing a culture that learns from failure rather than penalizing it. Also addresses (again) roadmaps.
- A Better Approach to PM Process (TLDR): Establishing "minimally viable consistency" across multiple teams. Just interesting. I will likely remove this article b/c it's a bit academic.
II. Competency Matrix
The product job family from Product Owner to VP or Product. A diagnostic rubric to help leaders better understand what is expected of their staff in a specific role.
If online copy is unaccessible: Product Role Matrix (backup)
III. Rounding and Coaching
Rounding Template: Structured 1:1 and departmental "rounding" template here. This document moves conversations away from status updates and toward strategic alignment and accountability.
Protocol: Rounding is conducted individually on a quarterly basis, keeping the other 1:2 or 1:1 meetings focused on tactical execution.
Homework: Leaders must complete the Product Leader Rounding Template asynchronously ahead of the session.
IV. AI Support as a GPT
Product Coach GPT: An agentic AI trained on the Article Canon and personal leadership principles. It provides just-in-time coaching and feedback for roadmaps, emails, personal growth, team growth, and product strategy development.
V. Bonus References: Contextual Frameworks
- Training
- https://productschool.com/why-product-school
- https://www.svpg.com/product-masterclass/ (cody also has a recording)
- Book: Inspired
- Strong Product Leaders. This seems to be a somewhat popular approach, but i know nothing about it and am only including it as a reference to consider
- Quotes
- “Don’t tell people what to do; tell them what you need accomplished, and you’ll be amazed at the results” - Patton
- “You can have a little now, or everything never” - Anonymous quote on Agile
- “The test of innovation lies not in its novelty, its scientific content, or its cleverness. It lies in its success in the marketplace.” - Peter Drucker
- “I have more respect for the fellow with a single idea who gets there than for the fellow with a thousand ideas who does nothing.” - unknown
- "If you knew you were 30 failures away from your goal, how fast would you want to fail?"