Collaborating Effectively Across Engineering, Product, and Design
Designed for Engineers, Product Managers, Designers, and cross-functional team leads working on shared product initiatives to spark real collaboration and high-energy learning.
A practical workshop for cross-functional teams that want clearer decisions, shared priorities, visible alignment, and smoother delivery across Engineering, Product, Design, Customer Success, and Marketing.
Everyone Agreed Until Delivery
Participants review notes from a product planning meeting where everyone appeared aligned. They predict whether delivery progressed smoothly, then learn that each team interpreted the agreed plan differently, creating rework and repeated clarification meetings. Collaborating Effectively Across Engineering, Product, and Design
Tap to view the full activity.
Why this works
The prediction error makes the difference between agreement in a meeting and shared understanding during execution visible.
One Feature, Different Priorities
Each group receives the same feature request but is secretly assigned a different role: Engineering, Product, Design, Customer Success, or Marketing. Every team prepares recommendations from its perspective before sharing them and identifying the shared goals beneath the differences. Collaborating Effectively Across Engineering, Product, and Design
Tap to view the full activity.
Why this works
The hidden roles show that functions often optimize for different outcomes even when they are discussing the same feature.
The Context That Missed the Room
Participants role-play a planning session. One participant receives confidential customer feedback, another knows a technical limitation, and another understands an upcoming business priority. The team must make a decision using only what is shared, then reveal the context that never reached the room. Collaborating Effectively Across Engineering, Product, and Design
Tap to view the full activity.
Why this works
The hidden context shows why important information must be surfaced early instead of being treated as something everyone else already knows.
Which Conversation Comes First
Teams receive twelve collaboration activities, including customer research, technical discovery, design review, stakeholder alignment, effort estimation, prototype testing, roadmap discussion, and implementation planning. They arrange them into the sequence that creates the strongest foundation. Collaborating Effectively Across Engineering, Product, and Design
Tap to view the full activity.
Why this works
Forced sequencing makes collaboration quality visible and helps teams see how a late conversation can create expensive rework.
Two Planning Sessions
Participants compare two planning meetings for the same initiative. One focuses on individual updates and isolated decisions. The other encourages shared problem-solving, clarifies assumptions, and confirms ownership before moving forward. Participants identify which practices create stronger collaboration. Collaborating Effectively Across Engineering, Product, and Design
Tap to view the full activity.
Why this works
The comparison shows how meeting design can create shared ownership rather than simply placing people on the same calendar.
Through Another Team's Lens
Participants temporarily step into another function's role. Engineers think like Product Managers, Product Managers approach the discussion as Designers, and Designers evaluate decisions as Engineers. They revisit a product decision from the new perspective before comparing insights. Collaborating Effectively Across Engineering, Product, and Design
Tap to view the full activity.
Why this works
Role reversal helps people understand the constraints, responsibilities, and success measures of partner teams before judging their choices.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.