Stop Talking, Start Doing
Summary
Karin recounts her experience leading design transformation at Intuit between 2003 and 2014. She begins with the origin of Quicken by Scott Cook and Tom Pru, emphasizing early user-centered design that led to market dominance. However, as Intuit grew, product silos and complexity diluted customer focus, and usability benchmarking revealed the company was only average compared to competitors. Karin pressed leadership, including then-CEO Steve Bennett, to prioritize ease of use, which improved task success but did not boost net promoter scores or revenue growth. Steve challenged the team to find what lies beyond ease, prompting Karin and the tiger team to study companies like Apple and Nike, leading to the Design for Delight (D for D) initiative. Despite initial enthusiasm and executive support, the initiative stagnated due to leadership transitions and weak design leadership. Karin and her core design partners resolved to be bolder and pushed to embed design deeply into Intuit’s culture. They gained the new CEO Brad Smith’s full support and created immersive empathy experiences for executives, shifting the company’s focus from usability to delight and financial impact for customers. The Innovation Catalysts program spread design thinking across teams beyond designers, sparking measurable improvements across departments. Karin also highlights the importance of scaling design talent and leadership, showing that respected design-driven companies maintain at least a 2:1 designer-to-product manager ratio. By establishing formal design ladders, increasing senior leadership roles for designers, and embedding design in company operations, Intuit became recognized externally as a design-driven organization. Karin closes with four keys to lasting impact: articulate a clear vision, engage hearts and minds through emotion and data, give design work away to empower others, and scale design sustainably through organizational mechanisms.
Key Insights
-
•
Quicken's early success stemmed from deeply observing real users and setting concrete usability goals.
-
•
Despite a strong customer-focus legacy, Intuit became average in usability relative to competitors over time.
-
•
Improving ease of use alone increased task success but did not raise net promoter scores or revenue growth.
-
•
Studying companies with brand loyalty (Apple, Nike, Harley-Davidson) revealed the critical role of customer delight.
-
•
Design for Delight (D for D) needed executive sponsorship, emotional storytelling, accountability, and a structured process.
-
•
Initial D for D efforts failed due to shifting leadership, lack of design leadership, and insufficient cultural embedding.
-
•
Creating immersive empathy experiences for executives shifted strategic focus to solving deeper customer problems.
-
•
Innovation Catalysts helped spread design thinking beyond designers, empowering broader organizational change.
-
•
A ratio of at least two designers per product manager strongly correlates with better user experiences.
-
•
Embedding design into hiring, training, leadership ladders, and everyday operations creates lasting cultural impact.
Notable Quotes
"Legacy is about having an impact that lasts, not just short term but years or even decades."
"Scott Cook noticed his wife’s frustration balancing their checkbook and realized millions more probably felt the same pain."
"We benchmarked usability and found Intuit was average compared to competitors — not good enough anymore."
"Steve Bennett asked, what’s beyond ease, leading us to study companies known for delighting their customers."
"Design for Delight wasn’t about fun — it was deliberately designing for delight to engage customers emotionally."
"Ron Johnson from Apple and Paul English from Kayak inspired us by sharing how their companies build customer loyalty."
"After a year of D for D, nothing had changed. The initiative looked like just another check box."
"Our CEO Brad Smith said, I’m all in on Design for Delight, but no new content — it has to reinforce what we already do."
"When executives met customers’ real stories during the recession, they said, holy crap, now we get the pain."
"Companies with strong user experiences had twice as many designers as product managers, often with senior design strategists."
Or choose a question:
More Videos
"Everything is an experiment."
Erin WeigelReal-world lessons to improve your conversion rates
June 26, 2024
"There's no way to deny it: every industry needs to adapt to AI, but nobody really knows how yet."
Daniel KorczynskiWhy AI Is Bad at Research (and how to make it actually useful)
March 10, 2026
"Asynchronous communication means you’re not going to get an answer quickly, and you have to embrace that."
Kim LenoxLeading Distributed Global Teams
May 20, 2019
"That night at 11:59 PM the entire nation of New Zealand would move into what was called a level 4 lockdown."
Brendan JarvisFraming Tomorrow by Questioning Today
June 8, 2022
"Good trouble is part of our craft—it's about making the right amount of disruption to improve healthcare."
Carol MassaDesigning Health: Integrating Service Design, Technology, and Strategy to Transform Patient and Clinician Experiences
December 3, 2024
"As the product journey progressed, research cadence got faster with prototypes and quicker feedback loops."
Dr Chloe SharpUsing Evidence and Collaboration for Setting and Defending Priorities
November 29, 2023
"Civic action as proof of concept to get government moving, to get the wheels turning was really interesting."
Sarah Auslander Betsy Ramaccia Gordon RossInsights Panel
November 18, 2022
"Never assume and always ask why."
Susan Simon-DanielsWar Stories LIVE! Susan Simon-Daniels
March 30, 2020
"Sharing your automation scripts and articles can get four times more attention than traditional case studies."
Farid SabitovAutomatization for Large Enterprise Teams
January 8, 2024
Latest Books All books
Dig deeper with the Rosenbot
How does Rosenfeld Media ensure high quality and relevance across its Rosenverse offerings?
What steps can a team take to make sure their vision gets included in the product roadmap?
What human oversight processes are necessary to ensure the accuracy and relevance of AI-enhanced research repositories?