Summary
Constantly improving processes and embracing an iterative mindset can be difficult. In this session, I’ll share unexpected hurdles I faced while leading large-scale changes and how you can avoid them. We'll dive into key moments where I hit roadblocks and more importantly, I'll share the valuable lessons I learned the hard way. Let’s turn my “list of things I wish I knew” into actionable best practices that you can apply to lead change more effectively.
Key Insights
-
•
Doubling a team’s size can drastically reduce process maturity and create new challenges in scaling tools and workflows.
-
•
Failing to thoroughly vet feedback before acting can lead to choosing suboptimal solutions that cause more disruption.
-
•
Piloting changes on a smaller scale helps uncover issues early and builds stakeholder buy-in before full implementation.
-
•
Assessing the urgency of feedback involves understanding who it impacts, if it blocks critical work, and possible temporary workarounds.
-
•
Feedback should be viewed as data, recognizing whether it reflects the majority or a small subset to avoid biased decisions.
-
•
Locking processes from change for 1-2 months creates stability and sustainability, especially when managing multiple teams.
-
•
Documentation of changes, including rationale, approvals, alternative options, and pilot outcomes, prevents repeating past mistakes.
-
•
Engaging trusted colleagues can help mitigate personal bias when assessing feedback.
-
•
Using anecdotal team feedback helps leaders appreciate the human impact of change and the importance of pacing.
-
•
Managing change frequency is a balance that requires gauging team health through surveys and direct human connection.
Notable Quotes
"If you dug deeper into feedback, you'd find ways to address issues without a big change."
"Leading change is like shopping—take time to find the right store before you buy."
"Piloting your ideas before committing helps prevent disruption and saves energy in the long run."
"Processes are never perfect, but thoughtful testing limits disruption for your team."
"We forget a lot of details over time; documentation saves us from repeating mistakes."
"Assessing feedback urgency means understanding if the issue blocks critical work or if there are workarounds."
"Using pilots can get buy-in from stakeholders who might resist broad change initially."
"Anecdotal feedback from team members helps leaders understand the real impact of change."
"More frequent change isn't always better; good communication and team pulse are key."
"Not everything that is faced can be changed, but nothing can be changed until it is faced."
Or choose a question:
More Videos
"Evals are really your intellectual property—they define what good looks like in your domain."
Peter Van DijckBuilding impactful AI products for design and product leaders, Part 2: Evals are your moat
July 23, 2025
"One of the core questions of research strategy is how do you decide what research to do when demand exceeds resources."
Chris Geison Cristen Torrey Eric MahlstedtWhat is Research Strategy?: A Panel of Research Leaders Discuss this Emergent Question
March 4, 2021
"Using Merge we’re closing the loop of documentation and empowering stakeholders to communicate via common jargon and components."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
"Target’s internal teams varied in design maturity from totally nonexistent to full design strategy, so we had to meet them where they were."
Abbey Smalley Sylas SouzaScaling UX Past the Size of Your Team
January 8, 2024
"Who needs a designer when we have generative AI?"
Jon FukudaTheme One Intro
October 2, 2023
"Design is the rendering of intent — bringing ideas into form that solve the problem."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
"Healthy teams are the foundation of a healthy organization."
John Calhoun Rachel PosmanMeters, Miles, and Madness: New Frameworks to Measure the (Elusive) Value of DesignOps
September 24, 2024
"They had no idea who we were or what value we provided, so first was hello, we exist."
Jacqui Frey Dan WillisPanel Discussion: Integrating DesignOps
November 7, 2018
"Design takes on a new role as governance practitioner, overseeing branding, content, and accessibility."
Amy EvansHow to Create Change
September 25, 2024
Latest Books All books
Dig deeper with the Rosenbot
What responsibilities should design ops take on regarding frameworks like onboarding and career growth templates?
Is it effective to evaluate entire multi-turn chatbot sessions or individual steps? What is recommended?
What lessons did Sean and Sarah share about sustaining knowledge management beyond the closure of a government design team?