Operating with Purpose
Summary
Key Insights
-
•
Onboarding 80% of MailChimp’s CX and design department over four weeks creates a strong cultural foundation.
-
•
A clear sense of purpose significantly improves work engagement and personal well-being.
-
•
Purpose-driven messaging encourages better habits, such as hospital workers improving hand hygiene.
-
•
Mentorship during onboarding benefits both new hires and mentors by reigniting passion for work.
-
•
Remote work exacerbates loneliness, making intentional one-on-one connections vital for team health.
-
•
Tailored microlearning and flexible scheduling help employees continue growing without added stress.
-
•
Work-life boundaries are essential for mental health, especially when working from home.
-
•
Celebrating efforts, not only successes, fosters persistence and connection among teammates.
-
•
Managers setting examples by openly prioritizing mental health encourages healthier team environments.
-
•
Understanding teammates’ personal and career goals helps align individual purpose with company objectives.
Notable Quotes
"I’ve onboarded 80% of the design and CX department, and it really shapes their trajectory and connection to culture."
"When you feel your work connects to a greater purpose, you’re more invested and perform better."
"Hospital workers were 45% more likely to wash hands properly when told it helped patients rather than themselves."
"Mentoring new hires actually reignites the mentor’s own passion for their work."
"My manager says never ask me to take a day off, just tell me — it’s a huge cultural shift."
"Onboarding isn’t a one-time activity, it’s an ongoing event that helps people connect and find their place."
"People coming from agencies sometimes need help dropping bad habits like working at 2am or stressful environments."
"It’s important to create space outside work for people to connect to meaningful activities and communities."
"Celebrating efforts, even when they’re not wins, helps people keep moving forward."
"If your purpose is just getting through 2020, that’s okay — survival can be the goal right now."
Or choose a question:
More Videos
"If you want to scale, incorporate global UX research from day one and test your assumptions broadly."
Nancy DouyonWe'll Figure That Out in the Next Launch: Enterprise Tech's Nobility Complex
June 15, 2018
"All behavior your component is capable of, including responsive and interaction states, will work inside UXPin."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
"The whole should be greater than the sum of the parts, but achieving that requires intentional design and leadership."
Jorge ArangoMeeting of the Waters: Designing for Successful Inorganic Growth
August 12, 2021
"We are not just doing research to find stuff out; we need to show a return on investment on everything."
Jon White Erin MayUnsticking Research for Better Information Flow
March 11, 2026
"Designing in enterprise means facilitating conversations and educating your teams because many stakeholders don’t speak design."
Jessamyn EdwardsSurviving Your UX Career in Enterprise Design
December 2, 2021
"An agency developing shared technical infrastructure must market to itself why change is preferred, not just rely on top-down mandate."
Stefanie OwensOptimizing for Outcomes: Transformation Design in Systems at Scale
December 4, 2024
"Every problem is a research problem."
Ron BronsonDesign, Consequences & Everyday Life
November 18, 2022
"Slack is growing steadily for us, but it’s hard to moderate and expensive at scale."
Louis RosenfeldThe Rosenbot and the Rosenverse: An AMA with Lou Rosenfeld
June 5, 2024
"We're at a pivotal moment where technology can truly make a difference in sustainability."
Ash BrownSilver Linings: What DesignOps Learned in the Shift to WFH
October 23, 2020
Latest Books All books
Dig deeper with the Rosenbot
What role does posture play when introducing informal sketches in collaborative discussions?
What is continuity architecture and why is it important across AI-driven journeys?
How can organizations prevent design system knowledge from being an undocumented API surface reliant on specific individuals?