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
"Personas and journeys are all models we use in UX to manage complexity."
Scott PlewesWhy Isn't Your UX Approach Going Viral?: A Mathematical Model
March 28, 2023
"If people just got in the room and I did nothing except take a seat, everything would be fine."
Alison Rand Sarah BrooksScaling Impact with Service Design
March 25, 2021
"Research should prioritize participant and researcher well-being over institutional convenience."
Rachael Dietkus, LCSWThe power to heal and harm
March 13, 2025
"Today's problems come from yesterday's solutions."
Sheryl CababaLiving in the Clouds: Adopting a Systems Thinking Mindset
June 6, 2023
"I think the world we’re in is definitely not antagonistic to research, there’s a huge opportunity right now."
Renee BouwensLanding Product Impact: Aligning Research as a Foundational Driver for Delivering the World’s Best Products
December 15, 2023
"User research is interdisciplinary; only two thirds of people who do research describe their job as primarily research."
JP Allen Holly HoldenNavigating the UX Tools Landscape
October 1, 2021
"If you have a question for a speaker, put it in the thread for their talk, not in the general chat."
Bria AlexanderOpening Remarks
November 18, 2022
"DeepFakes can look too realistic and might introduce new privacy risks if donor faces come from real people."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"Conjoint analysis was used by Apple and Samsung to determine the financial value of specific product features."
Ricardo MartinsUnlocking the power of advanced quantitative methods
March 12, 2025
Latest Books All books
Dig deeper with the Rosenbot
What challenges exist for experienced designers transitioning into academia, especially philosophy?
How can design operations demonstrate their value when their work is often invisible until failure?
How should a design ops team define and use lead measures and scorecards to track progress effectively?