Asking the Right Questions: Life, Hope and Moving Forward During the Pandemic
Summary
Details to come.
Key Insights
-
•
Starting meetings or classes with a simple warm-up increases attentiveness and presence.
-
•
Remote teaching often results in students keeping cameras off, impacting engagement, but this can be navigated with inclusive strategies.
-
•
Peloton taught the speaker practical leadership lessons including compassion, collaboration, and community support.
-
•
Consistency is critical in leadership and personal growth, exemplified by the speaker's 73-week exercise streak.
-
•
Inclusive leadership requires acknowledging where people are physically and emotionally, offering alternatives accordingly.
-
•
Organizations must consistently provide education and enforce policies addressing discrimination, considering intersectional identities.
-
•
Leadership must listen actively and avoid placing the burden of diversity work solely on marginalized groups.
-
•
Recognizing external stressors such as global events is essential to empathetic leadership and inclusive workplaces.
-
•
Language matters; everyday expressions can unintentionally exclude or offend marginalized communities.
-
•
Inclusion and accessibility should be embedded into every designer's responsibilities, not isolated to specialists.
Notable Quotes
"I had you all do a warm-up before we started to help everyone be present and calm."
"Sometimes working with a bunch of boxes and letters on Zoom was the reality of remote classes."
"Be compassionate with yourself and others. Not everyone likes high fives, and that's okay."
"Collaboration is key. I'm never alone in a Peloton class, even at 4:30 in the morning."
"Consistency is key. I'm on a 73-week streak right now, and that's pretty badass."
"Identity is not monolithic; policies should address layered experiences."
"It is not the responsibility of marginalized groups to do all the educating about their experiences."
"Listen is a skill that is not emphasized enough in leadership."
"Watch your language; terms like 'that's so lame' can be exclusionary or offensive."
"Inclusion and accessibility need to be part of every designer's role, even if today it is one person's job."
Or choose a question:
More Videos
"A lot of accessibility work isn’t just for a small group — designing for the edges gets you the middle for free, as Yuda Trevor says."
Sam ProulxOnline Shopping: Designing an Accessible Experience
November 29, 2023
"Research insights should belong to the team, not just the researcher."
Shipra KayanMake your research synthesis speedy and more collaborative using a canvas
January 24, 2025
"Please read our code of conduct; it’s on every page of our website and includes ways to get help if needed."
Louis Rosenfeld Bria AlexanderOpening Remarks
October 2, 2023
"Expressing gratitude publicly and privately gives people a sense of purpose and acknowledges their contributions."
Michael PolivkaScaling Design through Relationship Maps
November 7, 2017
"We put heavy trust in our stakeholders and co-created the curriculum with them."
Elizabeth Sklar Jessica ShengCo-creating research enablement with your tech org: a case study
March 10, 2026
"Land acknowledgement done as a checkbox is performative; when embedded, it becomes a practice of respect and inclusion."
Zariah CameronStreamlining an Inclusive Design Practice
October 3, 2023
"Managing vendors is a full-time job, and research ops teams often coordinate numerous vendors for tools and recruitment."
Kate TowseyThe State of ResearchOps: More Than Just Theory
June 20, 2019
"A mature design system needs both UI kits and matching developer component libraries; we provide both out of the box."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
"We applied usability test fixes post-launch to get the service out earlier during lockdown."
Tiffany ChengDesigning in a Pandemic: Integrating Speed and Rigor
June 9, 2022
Latest Books All books
Dig deeper with the Rosenbot
How can non-engineers overcome fears and gaps when interacting with engineering codebases for the first time?
How can senior designers coach junior designers to maintain intentional design decisions while using AI?
How can UX designers use AI tools like Kiro to generate shippable code from their designs?