Becoming a Changemaker by Leading with Design
Summary
Key Insights
-
•
The role of design leaders has evolved from product delivery to shaping organizational culture at scale.
-
•
Changemakers must assess 'ground conditions' like executive support and resources before accepting leadership roles.
-
•
Rushing into change without understanding the organization's history and culture ('coming in too hot') often generates resistance.
-
•
Building a shared vision requires inclusive collaboration where all stakeholders feel heard and represented.
-
•
Prioritization and focus on a few small wins prevent burnout and enable sustainable change.
-
•
Tools like the impact matrix help teams evaluate effort versus impact to choose projects wisely.
-
•
Vision without execution is futile; delivering tangible outcomes with prototyping and milestones is essential.
-
•
Failure is inevitable in change leadership; embracing mistakes with courage leads to growth and innovation.
-
•
Visual communication techniques enhance stakeholder understanding and trust during complex change efforts.
-
•
Changemakers don’t necessarily need formal design training but must adopt design as a mindset and problem-solving strategy.
Notable Quotes
"The best future leaders will embody the qualities and traits of a DEO — design executive officer — creative business leaders at the intersection of design and business."
"Change is fundamentally a design problem and therefore change can be designed."
"Before you accept a mission as a changemaker, ask yourself do you have a clear directive, champion support, and the right resources?"
"Coming in too hot means running into a burning building like a firefighter, ignoring past work, and rushing without listening."
"Nobody wants to be told to do your thing unless it’s clear that it helps their thing. It’s just human nature."
"Don’t boil the ocean. Get small wins before you go for the big change."
"You need maniacal focus to prioritize, but remain flexible as priorities will always change."
"Vision without execution is hallucination. You must make outcomes tangible and measurable."
"Failure sucks and hurts, but if you haven’t failed, you haven’t taken enough risks."
"When you hit the bottom, that’s where creativity flourishes and it’s time to iterate, evolve, and redesign."
Or choose a question:
More Videos
"Building an emergency backup process ensured research would continue even if key Ops people were unavailable."
Marjorie Stainback Molly Fargotstein Stephanie MarshWhat Research Ops Professionals Have Learned from COVID-19
July 16, 2020
"One design at scale advisor supports about 12 scrum teams, which is rewarding but cognitively demanding."
Nora Tejeda Giovanna AlonsoScaling Design Capabilities at BBVA Through a Self-service Design Model
June 10, 2021
"Around 14 to 20 designers is usually the tipping point where having a dedicated design ops person starts to make sense."
Rachel Posman John CalhounA Closer Look at Team Ops and Product Ops (Two Sides of the DesignOps Coin)
November 19, 2020
"The hustle does suck, and Gen Z is doing this other thing over here, arranging in healthier ways."
Deanna ZandtThe Unspoken Complexity of “Self-Care” with Deanna Zandt
July 21, 2022
"It’s important to ask, before any new release, what are all the things that could possibly go wrong?"
Raven VealDark Metrics: Illuminating the Negative Impact of Digital Health Design
March 12, 2021
"Statistics is another tool in our toolbox, part of a hierarchy of evidence that includes qualitative and quantitative methods."
Caroline Jarrett Erin WeigelHave fun with statistics?
December 12, 2024
"When you set out to build your own design operation strategy, pieces of the puzzle already exist—you don’t have to reinvent the wheel."
Cassandra PiesterDeveloping and Deploying Your Design Operations Strategy
September 24, 2024
"We found patterns that product teams didn’t expect or even want to look for."
Ian JohnsonLatent Scope: Finding structure in unstructured data
June 11, 2025
"UX now has a seat at the table — maybe not next to the CEO, but definitely in the room — thanks in large part to the design system."
Nalini P. KotamrajuAn Organizational Story: Salesforce Lightning Design System
June 9, 2016