Working With Product Managers & Stakeholders

Working With Product Managers & Stakeholders 🔗 **Source:** [Working With Product Managers & Stakeholders](https://www.youtube.com/watch?v=affXyQg--qQ) > [!note]+ Document Notes > tags: [engineering-management, product-management, stakeholder-collaboration] > author: [Ladybug Podcast] > source: [YouTube] > reference: [https://www.youtube.com/watch?v=affXyQg--qQ] > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: Working With Product Managers & Stakeholders >  ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - The episode explains how engineering managers work with PMs, design, and other stakeholders. - Cross-functional trust and early collaboration reduce rework and conflict. - Stakeholders include product, design, support, sales, marketing, and adjacent engineering teams. - Tradeoffs involve capacity, technical debt, security risk, and customer impact. - Bottom line: align on business goals, communicate early, and define roles clearly. Source: [YouTube](https://www.youtube.com/watch?v=affXyQg--qQ). ## 📖 Main Content - The hosts stress a product mindset for engineers. Think from the customer back. - PM partnership works best as paired leadership. Meet daily and share context. - Technical debt must map to business risk. Tie upgrades to security and revenue. - Design collaboration improves outcomes. Share rationale and iterations early. - Early EPD triads cut rework. Include ICs who will build the thing. - Communicate top-line first when managing up. Offer details on request. Source: [YouTube](https://www.youtube.com/watch?v=affXyQg--qQ). ### 🗒️ Notes #### ⏱️ [00:00](https://www.youtube.com/watch?v=affXyQg--qQ&t=0) Product mindset for engineers - Engineers should think about customer experience, not only tasks. - Ask how customers will interface with features. #### ⏱️ [02:23](https://www.youtube.com/watch?v=affXyQg--qQ&t=143) Cross-functional agendas - Different roles have different goals. Acknowledge conflicts early. - Daily PM collaboration reduces friction. #### ⏱️ [06:57](https://www.youtube.com/watch?v=affXyQg--qQ&t=417) Role boundaries - PMs should not direct engineering execution. - Engineering sets estimates and sequencing. #### ⏱️ [09:00](https://www.youtube.com/watch?v=affXyQg--qQ&t=540) Technical debt as risk - Tie upgrades to security and compliance risk. - Explain velocity gains from platform work. #### ⏱️ [11:01](https://www.youtube.com/watch?v=affXyQg--qQ&t=661) Design system gaps - Startups often lack robust design systems. - Scope creeps when components change mid-stream. #### ⏱️ [15:06](https://www.youtube.com/watch?v=affXyQg--qQ&t=906) Share design rationale - Designers who show iterations build trust. - Engineers push back less when reasoning is clear. #### ⏱️ [18:33](https://www.youtube.com/watch?v=affXyQg--qQ&t=1113) Team rituals matter - Standups and retros with PM and design build rapport. - Reorgs require tight coordination across teams. #### ⏱️ [20:08](https://www.youtube.com/watch?v=affXyQg--qQ&t=1208) Broader stakeholders - Interface with support, sales, marketing, and CS. - Negotiate capacity for cross-team dependencies. #### ⏱️ [23:42](https://www.youtube.com/watch?v=affXyQg--qQ&t=1422) Shared business goals - Conflicts often reflect context gaps. - Align on the business objective first. #### ⏱️ [25:20](https://www.youtube.com/watch?v=affXyQg--qQ&t=1520) EPD from day one - Bring product, engineering, and design together early. - Include ICs who hold key technical context. #### ⏱️ [28:59](https://www.youtube.com/watch?v=affXyQg--qQ&t=1739) Translate technical concepts - Explain constraints in plain language. - Let engineers practice stakeholder communication. #### ⏱️ [32:26](https://www.youtube.com/watch?v=affXyQg--qQ&t=1946) Managing up - Lead with the headline. Offer details as needed. - Senior leaders want the TL;DR first. #### ⏱️ [35:53](https://www.youtube.com/watch?v=affXyQg--qQ&t=2153) Season arc and resources - Upcoming topics cover hiring, performance, and harder conversations. - Resource callouts include product leadership reading. ## 📚 References - Ladybug Podcast: *Working With Product Managers & Stakeholders* (YouTube) — [video](https://www.youtube.com/watch?v=affXyQg--qQ). - Neo4j Nodes conference mentioned in ad — [neo4j.com/nodes](https://neo4j.com/nodes). - Simon Sinek, *Start With Why* — overview page (verification recommended). - Marty Cagan, *Inspired* — overview page (verification recommended). Note: External book links not verified here; use trusted publisher pages. ## 🗣️ Paraphrase - The episode argues that strong EPD collaboration prevents delays and rework. - Teams should align capacity plans with design scope and security risks. ## 📰 Newsletter - Engineers thrive when they think from the customer back. This episode shows how. - Pair with PMs. Share context. Map technical debt to clear business risk. - WordPress folks: apply EPD rituals to Core, Themes, and Plugins. - Try design reviews that show iterations, not only outcomes. - Resource roundup: Ladybug episode video, Neo4j Nodes, product leadership books. Links: [Video](https://www.youtube.com/watch?v=affXyQg--qQ), [Nodes](https://neo4j.com/nodes). ## ✅ Action Items - DevRel - Developer advocacy: Run “customer-back” demos using real support tickets. Track adoption lift. - Education: Offer EPD role primers. Add office hours for PMs and designers. - Developer experience: Publish examples-first templates for RFCs, PRDs, and API mocks. - Developer marketing: Ship a funnel that attributes docs-driven conversions. - Community management: Define Code of Conduct escalation runbooks. Survey trust quarterly. - Internal/external/cross-project: Create SLAs for cross-team reviews and release gates. - OSPO - Policy & Governance: Codify decision rights for PM, Eng, and Design in charters. - License Compliance: Schedule quarterly scans. Teach SPDX basics. - Security Management: Define vuln intake, embargo handling, and signing keys. - Software Inventory: Maintain SBOM freshness SLOs and component owners. - Developer Support: Stand up consultation hours with legal and security. - Community Engagement: Draft MoUs and upstream funding guidelines. - Strategic Alignment: Report KPIs to executives with trend lines and risk notes. - Community - Maintainers: Host roadmap clinics. Enforce release hygiene checklists. - Contributors: Rotate “first issue” pairings. Track retention at 30/90 days. - Sponsors: Share milestone reports and transparent budgets. - Ecosystem: Run incident drills with coordinated disclosures. - WordPress - Core: Triage issues weekly. Enforce performance budgets in CI. - Core Performance: Publish profiling dashboards. Fund perf bounties. - Core AI: Define evaluation sets and responsible AI guardrails. - Core Program: Align team rituals and cross-dependencies. - Mobile: Prioritize offline UX and telemetry review. - Playground: Build browser labs and reproducible bug templates. - Community: Update meetup kits. Expand speaker mentorship. - Training: Ship structured learning paths and certification pilots. - Marketing: Plan campaigns with clear narratives and editorial calendars. - Support: Close knowledge base gaps and set response SLAs. - Design: Standardize tokens and run UX audits. - Documentation: Fill DevHub/HelpHub gaps. Use examples-first patterns. - Photos: Strengthen taxonomy and moderation guidelines. - TV: Improve captions and content indexing. - Polyglots: Run translation sprints and glossary alignment. - Accessibility: Track issues heatmap. Schedule regular audits. - Meta: Stabilize .org APIs and contributor tools reliability. - CLI: Expand command coverage and smoke tests. - Hosting: Share cross-host reliability checklists and telemetry. - Tide: Improve scoring transparency and review loops. - Openverse: Harden ingestion pipelines and moderation policy. - Themes: Increase review throughput with lints and mentoring. - Plugins: Add provenance checks and security liaisons. - The WPCC - Programs: Launch fellowship tracks and maintainer stipends. - Projects: Offer governance clinics and doc sprints. - Funding experiments: Pilot matched grants and milestone payouts with ledgers. - FAIR - Technical independence: Require local metadata, provenance, and signature checks. - Policies and covenants: Enforce transparency, sunset clauses, and anti-capture. - Productized governance artifacts: Publish charters, operator agreements, and scorecards. ## 🧪 Hypotheses - Triad kickoffs reduce rework by at least 20%. - Mapping debt to risk increases platform work allocation by 15%. - Designers sharing iterations lowers change requests by 25%. - Capacity sheets with shared inputs cut planning churn by 30%. ### 📊 Methodology - Run A/B across projects with and without triad kickoffs. - Track percentage of sprint capacity assigned to platform work. - Measure post-review design change volume and severity. - Log planning cycles and meeting counts per initiative. ### ❓ Questions - Which artifacts most improve shared context: PRDs, RFCs, or live mocks? - How do we quantify “customer-back” thinking in code reviews? - What cadence best balances design exploration and delivery? ### 🔮 Future Research - Study how design systems maturity changes engineering velocity. - Evaluate security attestations’ impact on sales cycle time. ### 💡 Implications - Practice: Run triad kickoffs and publish capacity sheets. - Policy: Clarify decision rights and escalation paths. - Security: Tie upgrades to attestations and compliance. - Education: Teach stakeholders to translate risk to impact. - Funding: Justify platform work with risk-adjusted ROI. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ~10 (heuristic, not computed). - Visual learners - Present: Verbal descriptions; some mental models. - Improve: Add diagrams of stakeholder flows and RACI charts. - Aural learners - Present: Podcast audio; conversational style. - Improve: Provide a 3-minute audio summary and TTS highlights. - Verbal learners - Present: Definitions and analogies for risk and capacity. - Improve: Add plain-language callouts and glossaries. - Kinesthetic learners - Present: Few labs. - Improve: Offer checklists and sandbox exercises with mocks. - Logical learners - Present: Capacity spreadsheets and roadmaps. - Improve: Add decision trees and error budgets. - Social learners - Present: Team rituals and cross-team meetings. - Improve: Cohort guides and peer-review rubrics. - Solitary learners - Present: Long-form listening option. - Improve: Reflection prompts and self-check quizzes. - Naturalistic learners - Present: Not addressed. - Improve: Tie to sustainability impacts of platform choices. ### 📊 Accessibility Assessment - Screen reader semantics - Present: YouTube headings and captions. - Improve: Provide full transcript download and descriptive alt text. - Keyboard navigation - Present: Standard YouTube controls. - Improve: Ensure visible focus and skip links around embeds. - Contrast and readability - Present: Platform defaults meet 4.5:1 typically. - Improve: Verify large-text thresholds and line-height guidance. - Text resizing and reflow - Present: Responsive player. - Improve: Support prefers-reduced-motion for animations. - Media and captions - Present: Auto-captions likely exist; accuracy varies. - Improve: Human-edited captions and downloadable transcript. - Forms and interactions - Present: N/A. - Improve: N/A. - Standards reference - Map gaps to WCAG 2.2 AA success criteria. ### 🌍 DEIB Assessment - Cultural breadth - Present: General tech workplace context. - Improve: Global examples and translation links. - Inclusive language - Present: Mostly neutral terms. - Improve: Add plain-language summaries and define jargon. - Neurodiversity support - Present: Structured conversation and recap. - Improve: More chunking and icon+text labels in materials. - Representation - Present: Hosts share experiences. - Improve: Bring voices from varied identities and roles. - Psychological safety - Present: Encourages empathy and respect. - Improve: Publish community guidelines for discussions. ### ✅ Logical Validity - Strong reasoning - Inductive link between technical debt and business risk. Clear and actionable. - Causal claim that triad kickoffs reduce rework. Plausible and widely practiced. - Fallacies - None apparent. Claims remain tentative and experience-based. - Tone of voice - Conversational, practical, and candid. Examples support claims. ### 🛡️ DARVO Analysis - Deny - None. The speakers acknowledge tradeoffs and friction. - Attack - None. No undermining of other roles. - Reverse victim/offender - None. The episode frames conflicts as process issues. ## 🎯 Conclusion - Align on goals, start collaboration early, and translate risk to impact. - Define roles clearly. Share context across product, design, and engineering. - Next, pilot triad kickoffs, publish capacity sheets, and track rework rates.