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
"Tags are a balance; project tags are wild and flexible, global tags must be controlled to avoid chaos."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"Anticipation involves preparatory actions to manage uncertainty about future conditions."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"Innovation is not a spice that you sprinkle on and suddenly magical new things come out."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"Meeting designers where they spend their time, like integrating accessibility plugins into Figma, is the most effective way to make progress."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"It’s the individuals who choose whether and how they take advantage of the opportunities you create."
Tess DixonC'mon Get Happy
September 29, 2021
"Soft skills often are a multiplier on your hard skills—they’re just as valuable, if not more so."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"Careers as ladders are what HR wants, but careers aren’t linear; they should be a jungle gym."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"At Atlassian, many confident non-researchers were already doing lots of research, which was an opportunity and a challenge."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"Without a design ops function, teams make their own flavors that dilute brand and accessibility."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
