Summary
Join conference curator Christian Crumlish, the conference speakers, and guest commentators for a lively panel discussion reviewing highlights, sharing notable takeaways, and diving deeper into questions inspired by the afternoon’s presentations.
Key Insights
-
•
Shielding product teams too much can stunt their growth; occasional challenges help build resilience.
-
•
PMs risk burnout and becoming bottlenecks if they try to filter all communication between executives and teams.
-
•
Storytelling is a vital, cross-functional skill for conveying value and aligning stakeholders.
-
•
Tailoring strategy communication to audience attention span and priority is key to effective messaging.
-
•
Repeatedly asking about fears and risks surfaces critical unknowns and guides research priorities.
-
•
Translating risks into financial terms facilitates executive-level decision making.
-
•
Different org sizes and maturities require different leadership approaches to information sharing and team autonomy.
-
•
Having one designer supporting many PMs and products is fundamentally insufficient for successful product outcomes.
-
•
Framing product value as a benefit to partner teams aids greater organizational buy-in beyond end-user focus.
-
•
Leaders should name and credit team members for successes but own and investigate failures to instill trust and transparency.
Notable Quotes
"If you don’t have a little earthquake every now and then, you have a real big one after a while."
"If you put yourself between the C-suite and the product teams, you become a bottleneck with no time for actual leadership."
"When something good happens, I want to name the person who did it and say yes, they passed through me. When something bad happens, I say let me and my team go look into it."
"Storytelling helps us speak in the language and context that motivates each team and stakeholder."
"You can build your strategy into eight pages, five, three, one, half a page, then a sentence to adapt to your audience."
"Have you just asked what scares us or keeps us up at night? Those repeated fears highlight the risks we need to avoid."
"I know that a development team of six costs me a million bucks a year, so risk has a dollar value executives understand."
"The idea of one designer to 12 PMs is dead on arrival; either design isn't valued or the company is short on designers."
"You’re not just convincing people of the value but the benefit to them of working with you on the product journey."
"We can design the experience of working with us just like we design for end users."
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
"Design Ops in government requires a lot of diplomacy – it’s about managing relationships and stakeholder expectations."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"VOC wasn’t a replacement for user research, but an enhancer that captured nuggets researchers might miss during discovery."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"A workshop helps people map their skills, identify gaps, and make specific goals for career jumps."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The trusted partnership between the chief of staff and the executive is critically important."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Change is messy and it can be uncomfortable, much like baking bread—it’s hard to imagine sticky dough turning into a perfect loaf."
Amy EvansHow to Create Change
September 25, 2024
"We’re powering a 300 plus organization of designers, researchers, program managers, and strategists."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"Beliefs are habits of action; they are the rules that guide how we decide to act."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"What if the atomic unit of research wasn’t the reports, but it was the insight within those reports?"
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
