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
"Screen reader users scored significantly lower in usability tests, reflecting the most effort in interpreting content."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"You don’t want so much governance that people can’t be creative, but you need just enough to help their process."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"Going from 100 to 200 people, suddenly product managers started hearing from a dozen people a week with conflicting requests."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Your career is a design project. It’s the only one you own, so own it like you would a product."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The chief of staff is the bridge between our executive leadership team and the design ops practitioners."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Self-service was a model with the most unknowns but possibly the biggest rewards."
Amy EvansHow to Create Change
September 25, 2024
"Flight is about adaptability – being ready to switch gears and pivot quickly in a global and changing environment."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"If you do anything with other people, you’re creating culture."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"You have to push against 200,000 years of human evolution to get researchers to create reusable knowledge."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
Latest Books All books
Dig deeper with the Rosenbot
What are effective first steps for starting research operations in a large organization with limited resources?
What responsibilities should design ops take on regarding frameworks like onboarding and career growth templates?
What are successful strategies to overcome resistance to UX research within product teams?