Opening Remarks
Summary
In the opening talk of Design Ops Summit 2023, Lou Rosenfeld warmly welcomes attendees, acknowledging the challenges faced by many in the design operations community this year, especially those feeling isolated due to layoffs or working solo in their roles. Lou encourages participants to connect and build friendships during the summit to combat loneliness. She introduces Bria Alexander, the conference curator and an influential design ops leader at Adobe who is deeply involved in diversity, equity, inclusion, and AI initiatives. Bria shares excitement about the thoughtfully curated program, which is divided into three themes: the changing nature of design ops (curated by John Kuda), practical applications (curated by Bria herself), and the intersection of design ops with other fields (curated by Sar Compre Miller). The talk also highlights logistical details: the conference runs on Pacific Time, features sponsor sessions open to all with no overlap from main programming, and includes digital swag and social events such as networking games and mixers. Attendees are urged to engage primarily via Slack channels dedicated to each session, sponsors, and general discussions, with strong support in place for customer service and a code of conduct ensuring a respectful community atmosphere. Manuel Herrera, a new sketch noter with a rich background in visual education, is introduced as a resource to capture and share conference insights visually, reducing the need for note-taking. Overall, the opening sets a tone of inclusion, support, and community while previewing a high-quality, content-rich conference experience.
Key Insights
-
•
Design ops practitioners often face loneliness, especially when working solo or seeking jobs, making community connection a key focus of the summit.
-
•
This year's summit program is divided into three thematic areas: changing design ops, practical design ops, and design ops plus.
-
•
Sponsor sessions run parallel but separate from the main program and are open for free attendance to anyone, even non-registered guests.
-
•
Slack plays a central role for live interaction, including dedicated channels and threads per session for questions and discussions.
-
•
A new sketch noter, Manuel Herrera, will visually document the conference, allowing attendees to focus more on sessions and less on note-taking.
-
•
The organizers encourage attendees to overcome virtual awkwardness by proactively initiating connections to make lasting design ops friendships.
-
•
The conference operates on Pacific Time by default, but attendees are encouraged to adjust the timezone on the website to avoid missing sessions.
-
•
Social events such as Cozy Juicy Reel games and mixers aim to foster networking and informal bonding among attendees.
-
•
The conference is supported by sponsors who provide significant resources enabling a high-quality experience, but sponsor sessions remain content-driven, not sales pitches.
-
•
A clear code of conduct and customer support infrastructure is emphasized to maintain a supportive and respectful conference environment.
Notable Quotes
"By showing up, you’re doing so not just for yourselves, but for everyone else that’s here."
"Many of you might be the only design ops person in whatever room you’re in for as much as 362 days a year."
"This is a design ops summit. You’re with your people, we get you and we all want you to do well."
"Try to walk away from this conference with at least one new design ops buddy."
"Sponsor sessions are not sales pitches but offer incredibly high quality content, and they’re free for everyone."
"Please post your questions in the thread associated with each presentation so we can see and address them."
"Manuel Herrera is here to take the burden of note-taking off us, so you can focus on the moment."
"If any of those adjectives do not apply to how you’re feeling right now, we wanna know."
"We want the Rosenfeld community, both in person and virtual, to feel as loving, supportive, and informative as possible."
"Please read our code of conduct; it’s on every page of our website and includes ways to get help if needed."
Or choose a question:
More Videos
"We created a pop-up design studio in the cafe to trade coffee and cupcakes for employee input."
Julie BaherCulture Change—My Journey
May 14, 2015
"MidJourney’s dataset reflects stereotyped images because it’s based on internet image results without specific instruction."
Jay BustamanteNavigating the Ethical Frontier: DesignOps Strategies for Responsible AI Innovation
October 2, 2023
"There’s a class distinction in who can or cannot avoid going to the office; 70% of workers never left the office during the pandemic."
Jennifer Bolduc Diane Gregorio Emily DayWhat's involved with getting people back to work?: A panel discussion
July 1, 2021
"We use a structured rubric that evaluates expected impact and how research will be used to inform decisions."
Chris Geison Cristen Torrey Eric MahlstedtWhat is Research Strategy?: A Panel of Research Leaders Discuss this Emergent Question
March 4, 2021
"We protect the time and headspace of everyone on the design team so they can focus more on their craft."
Jilanna WilsonDistributed DesignOps Management
February 26, 2019
"Meaningfulness is linked directly to what your organization cares about in terms of goals and priorities."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"It’s a fake contradiction to say empathy and bureaucracy cannot coexist; we need bureaucracy to have empathy."
Christian BasonInnovating With People: Unleashing the Potential of Civic Design
December 8, 2021
"The proof came from delivering the output — stakeholders stopped questioning the process once they saw the quality research."
Catherine BlizzardUsing Integrated Insight to Drive Growth
March 10, 2022
"Having questions about team happiness broken into person, team and product helps clear up confusion in large organizations."
Tess DixonC'mon Get Happy
September 29, 2021
Latest Books All books
Dig deeper with the Rosenbot
What are effective ways to train AI models to reduce hallucinations and glossing over details in taxonomy building?
What is the difference between AI skills, competencies, and capabilities in a design context?
What does the builder team model with AI in the loop look like compared to traditional product teams?