Collaboration Flows in Product Development
Summary
Mark Interrante, the SVP of Engineering at Hewlett-Packard Enterprise, has an extensive history of building out design and product teams in technology. Listen as he shares tips and tools to improve collaboration between multi-disciplinary teams.
Key Insights
-
•
Organizational silos often manifest visibly in product design, reflecting internal boundaries rather than customer needs.
-
•
Bringing in external UX experts like Jakob Nielsen can reveal uncomfortable truths about organizational alignment.
-
•
Assuming positive intent when working across teams dramatically improves collaboration and conflict resolution.
-
•
Mapping horizontal workflows across teams helps identify bottlenecks, usually caused by delays and waiting time rather than workload.
-
•
Writing the fences — explicitly defining cross-team boundaries and interaction protocols — increases trust and collaboration between departments.
-
•
Small, incremental changes in team habits compound to transform culture much more effectively than large sweeping reforms.
-
•
Clarifying the deeper goals behind tasks using four simple outcome questions prevents wasted effort and uncovers better solutions.
-
•
A concise proposal framework (side-pav) that states situation, complication, position, action, and benefit dramatically increases approval rates for change initiatives.
-
•
Large organizations benefit from treating teams as having APIs—clear, documented interfaces for interaction and requests.
-
•
Focusing on optimizing workflow latency delivers far greater productivity returns than increasing work hours or additional headcount.
Notable Quotes
"You can see our organization through the homepage of our site — we each owned a rectangle."
"Culture is what you tolerate — if you tolerate rudeness or tardiness, it becomes part of who you are."
"Assume positive intent from their point of view — they’re trying to have a good day, not work against you."
"Up to 90% of time in work streams is delay or waiting time, not active work."
"If you want to get faster output, optimize the work and workflow first — not add more hours."
"We started to build an API for how other teams could interact with us like a contract."
"Use four simple questions to find out what people really want and why — it avoids misaligned efforts."
"Side-pav proposals answer what’s going on, why it matters now, what you propose, what action to take, and what benefit comes from it."
"Small micro changes every week add up — ask your team what tiny improvements they’ve made recently."
"Making issues visible, sharing models, and iterating versions of workflows helps uncover blockages and solutions."
Or choose a question:
More Videos
"Technical difficulties happen, so please use hashtag.deo help within our Slack channel or email for support."
Bria AlexanderOpening Remarks
September 29, 2021
"People said, ‘I get it’ when a peer explained how their day actually changed—not from top-down communication."
Matt StoneScaling Empathy, A Case Study in Change Management
June 11, 2021
"Design portfolios are filled with slop when people lean too much on AI; you lose the human effort that makes design meaningful."
Paul FordNew work, new words: A glossary for AI
June 9, 2026
"When I talk about We, am I talking about You and Me, or the company itself? The word We can get really confusing."
Indra KlavinsA Design Ops Girl in a Dev Ops World
October 23, 2019
"Relational design privileges relationships and reciprocity not only between people but also with rivers, mountains, and animals."
Meghan Hellstern Joanne DongThe Next 100 Years of Civic Design: How Might We Better Rise to Meet the Challenges of Today and Tomorrow?
December 10, 2021
"Don’t do remote contextual inquiry just because you can; you lose so much context."
Sarah RinkRemote User Research: Dos and Don'ts from the Virtual Field
June 11, 2020
"Mobile screen readers can confirm basic accessibility but desktop testing is still needed due to differences across tools."
Sam ProulxMobile Accessibility and You
June 9, 2022
"Staff and principal designers need to balance zooming in on execution and zooming out to define strategic vision and minimize risk."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"Templates don’t have to be masterpieces; even simple reusable checklists and diagrams can save time and effort."
Michelle ChinThe DesignOps Starter Kit
September 29, 2021