
Cross Functional Collaboration
Load curated Lenny-podcast tactics when you need to run product missions with design, eng, data, and domain experts without siloing decisions.
Install
npx skills add https://github.com/refoundai/lenny-skills --skill cross-functional-collaborationWhat is this skill?
- Distills 72 cross-functional collaboration mentions across 57 Lenny podcast guests into one reference skill
- Tactical advice on embedding subject-matter experts (e.g. editors) directly in product missions
- Frames balancing KPIs with expert judgment in creative or content-heavy products
- Captures designer–engineer handoffs such as vibe-coded prototypes promoted to real PRs
- Use as a playbook before staffing or structuring a feature squad, not as an automation script
Adoption & trust: 1.3k installs on skills.sh; 1k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
Recommended Skills
Journey fit
Canonical shelf is Build → PM because cross-functional rituals are defined around shipping product with mixed disciplines, even though the advice applies earlier and later in the journey. PM subphase is where mission structure, stakeholder blend, and editorial-vs-metrics tradeoffs matter most for solo builders wearing multiple hats.
Common Questions / FAQ
Is Cross Functional Collaboration safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Cross Functional Collaboration
# Cross-functional Collaboration - All Guest Insights *57 guests, 72 mentions* --- ## Alex Hardimen *Alex Hardimen* > "Cross-functional missions at the Times... include a lot of the same skill sets that you would find at a tech company, PMs, engineers, designers, data scientists, researchers, product marketers. But the big difference is we also have editors, if it's a product space that directly shapes our journalism." **Insight:** In content-heavy organizations, cross-functional teams should include subject matter experts (like editors) directly in the product mission. **Tactical advice:** - Embed subject matter experts (editors) within product missions - Ensure editors have a 'product-minded' perspective *Timestamp: 00:23:21* --- > "Product managers at the Times really need to understand the blend of art and science. They really need to value expert editorial judgment as they're also looking at individual KPIs, customer research and insights, et cetera." **Insight:** Effective collaboration in creative industries requires balancing data-driven KPIs with expert human judgment. **Tactical advice:** - Value expert editorial judgment alongside data - Balance the 'art' of the product with the 'science' of metrics *Timestamp: 01:02:21* ## Alexander Embiricos *Alexander Embiricos* > "Our designers... have an entire vibe coded side prototype of the Codex app... if we like it, they'll vibe engineer that prototype into an actual PR to land. And then depending on their comfort with the code base... they'll land it themselves or they'll get close and then an engineer can help them land the PR." **Insight:** AI is 'compressing the talent stack,' allowing designers and PMs to contribute directly to production code through AI-assisted 'vibe coding.' **Tactical advice:** - Enable designers to build functional prototypes using AI agents - Create a workflow where non-engineers can submit PRs that engineers then 'polish' or validate *Timestamp: 00:46:24* ## Adam Grenier *Adam Grenier* > "If you approach it with that "Yes, and...", it's often still true. It's like, oh, both of these things can be true at once. You could have a different goal than I have, or you have a system problem local to you that is important to you and it's not important to me. That's okay, both things can exist. So, now that we accept both and can work off of each other, we're more likely to build both a better rapport and energy among ourselves because we're not just saying, "No, no, no, no, you're wrong."" **Insight:** Adopting an improv-based 'Yes, and' mindset helps resolve cross-functional friction by validating different team goals simultaneously. **Tactical advice:** - Acknowledge that conflicting goals between teams can both be valid - Avoid flat denials of other teams' perspectives to maintain rapport and progress *Timestamp: 00:10:24* --- > "If you are CMO and your product leader aren't married at the hip, you're just missing out on just tons of opportunity, and the likelihood of things actually working very well consistently and compounding on each other." **Insight:** In product-led companies, marketing and product must be deeply integrated rather than operating as separate silos. **Tactical advice:** - Ensure marketing leadership and product leadership are 'married at the hip' in planning and execution - Treat product and marketing as one integrated system rather than two different things *Timestamp: 00:43:37* --- > "Honestly, I think learn product development. Go learn agile product development... understanding those skills and those systems will, one, I think make you think differently about how to run your marketing team and, two, make you exponentially better at working with your product organization." **Insight:** Marketing leaders can improve collaboration by mastering the frameworks and language used by product teams, such as Agile and sprints. **Tactical advice:** - Take courses in product-led growth or agile developme