This video is only accessible to conference ticket holders.
Log in Create account
For 90 days after a conference, only paid ticket holders can watch conference videos. After that, all Gold members have access.
Contact Support if you are having any issues.
Summary
Before taking the Continuous Discovery Habits course, we were already experimenting with Design Sprints to solve tough problems and build momentum—but the course gave us the structure and language to reinforce a deeper culture of learning across product and design. In this talk, I’ll share how I used DesignOps thinking to translate a course into company-wide behavior change. Building on our sprint foundation, I introduced new rituals, rhythms, and infrastructure to help teams shift from validation to true discovery—from asking “Will this work?” to “What might we learn?”
Key Insights
-
•
Discovery is often the first casualty under deadline pressure, but it’s essential for building the right product and reducing rework.
-
•
Without shared rituals and connective processes, learning remains invisible and doesn’t drive action across teams.
-
•
Design sprints can align cross-functional teams and surface assumptions but don’t create sustained discovery habits on their own.
-
•
Training teams on discovery methods is necessary but insufficient; teams also need scaffolding—lightweight, repeatable structures and rituals—to make habits stick.
-
•
Scaffolding provides temporary support, safety, and clarity so teams can practice discovery confidently without feeling buried by process.
-
•
Flexible approaches that focus on outcomes rather than prescriptive processes help teams adopt discovery in ways that fit their culture and work style.
-
•
Rituals like biweekly product reviews and discovery weeklies increase visibility, alignment, and feedback speed among product trios and stakeholders.
-
•
Embedding discovery as a continuous rhythm leads to faster decisions, fewer false starts, and more impactful feature launches.
-
•
Scaling discovery does not require added headcount or massive budgets but thoughtful scaffolding and alignment across teams.
-
•
Successful discovery habits evolve through iteration, retrospection, and adapting scaffolding to the unique needs of each team and organization.
Notable Quotes
"Discovery doesn’t usually come with a launch party or even its own Jira ticket, but it’s what turns speed into progress."
"When discovery is missing, teams might move fast, but often in the wrong direction."
"Hope is not a strategy, and mandates don’t build culture. What works is scaffolding."
"Scaffolding is the temporary structure that provides support, safety, and access while the real work happens underneath."
"Instead of prescribing a meeting, we focused on how people should feel at the end and what outcomes to achieve."
"We built scaffolding that teams could climb, not cages they had to sit in."
"Discovery habits don’t stick because of training. They stick because of scaffolding."
"Start small, add scaffolding, and let momentum do the rest."
"The role of leaders is to provide just enough guidance so teams don’t feel lost but avoid bureaucracy."
"Teams started shipping multiple new features every few weeks, not because they cut corners, but because of fewer false starts."
Or choose a question:
More Videos
"You build trust by showing you understand what it takes to get something shipped and by knowing the subject matter."
Peter MerholzThe Trials and Tribulations of Directors of UX
July 13, 2023
"Our file is a visual representation of our entire workflow and mirrors the structure of our board."
John Paul de Guzman10k Screens Later: How We Became a Data-Driven Design Organization
September 24, 2024
"Measuring ops impact by how much people are using the research and embedding feedback loops is much more valuable than just looking at money saved."
Brigette MetzlerScaling ResearchOps: Helping Researchers do Their Best Work
March 30, 2020
"Bias is fueled by over-engineering without enough participation from non-technical roles that could reduce it."
Joel BranchHumanizing AI: Filling the Gaps with Multi-faceted Research
March 11, 2021
"Involving designers means treating them like precious individuals who value autonomy and collaboration, not imposing rules."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"We’re an older company by tech standards—older than Facebook, Twitter, LinkedIn, and even Google by one year."
Chris MosesStretching the Definition of DesignOps with Product Development
November 7, 2018
"You don't want to hide away for six months and try to build the perfect documentation. It won't work."
Gabrielle VerderberDocumentation Your Team Will Actually Use
October 3, 2023
"People don’t actually hate innovation; they like their jobs and feel threatened by change."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"One designer said collaborating across Salesforce has been the best experience they’ve had at the company after five years."
Melissa TsangFrom Insights to Action: Driving Business Values through DesignOps
January 8, 2024
