Intuit Design for Delight
Use as a lens · Primary + examples
A principle system for innovation work that becomes useful only when the three ideas are turned into concrete behaviors and decision checks.
Best opened when
Open it when a team wants stronger innovation discipline but does not need a heavy operating model yet.
What to steal first
The three principles are compact enough to travel well across product and innovation teams.
What not to copy
It is not a workshop sequence on its own.
Closest move
Core claim
Design for Delight is Intuit's three-part innovation framework: deep customer empathy, go broad to go narrow, and rapid experimentation. At its best, each principle is a critique standard — a check on whether an innovation review is actually rooted in customer reality, has created enough option breadth before converging, and is closing on evidence rather than confidence.
What transfers is the critique logic each principle implies. Deep customer empathy is not an attitude; it is a question: is this concept grounded in specific things we have observed about real customer behavior? Go broad to go narrow is not an ideation instruction; it is a sequencing norm: are we choosing a direction because we explored genuinely different options, or just because this one arrived first? Rapid experimentation is not a velocity target; it is an evidence question: what is the smallest test that could challenge the most important assumption?
What does not transfer: the three slogans alone, without the behavioral translation. Intuit operationalized these principles inside a culture that expected the questions to be asked in real reviews with consequences for vague answers. Borrowed as a vocabulary set, they become decorative. The leverage is in using them as live critique prompts that change what a review actually demands.
Use it as a lens
The moment when a team is about to narrow to a solution before they have genuinely understood the customer's situation, or before they have gone wide enough to surface better options.
The question it sharpens
Three questions to hold: Have we gone deep enough on what customers actually experience? Have we gone broad enough in generating options before narrowing? Are we running experiments with customers, or defending assumptions internally?
In practice
Use D4D as a stage-gate filter, not a methodology to run. At any decision point where the team is about to commit to a direction, check each principle: Where is the customer signal we are relying on? How many options did we generate before choosing this one? What is the fastest way to get customer reaction to this idea? These three questions slow premature narrowing without requiring a dedicated D4D session.
Where it breaks: The principles become checkbox theater when teams use them as documentation rather than as active prompts. D4D does not help a team that is under pressure to ship and treats empathy as a past activity rather than a present check.
What good looks like
How it worked there
Intuit built Design for Delight inside a product and financial-services culture that needed to shift from feature-building toward customer problem discovery. The principles were not aspirational slogans — they were the criteria by which product concepts were reviewed and funded at senior levels. Leaders asked the empathy and evidence questions in actual sessions.
The principles held because they were backed by real decision pressure. A concept that could not demonstrate customer grounding and option breadth before converging did not advance. In organizations where the equivalent review has no real standards — where a confident presenter and a polished deck are enough to move a concept forward — the principles cannot do the same work. The culture of accountability behind the review is the mechanism; the three phrases are only the description of it.
What not to copy · Failure modes
The three slogans are learned and repeated without changing any actual review behavior. Teams adopt 'deep customer empathy, go broad to go narrow, rapid experimentation' as innovation vocabulary. The phrases appear in decks and strategy documents. But the reviews still start from solutions. The evidence is still thin. The experiments are still multi-month builds. The slogans have been absorbed; the principles have not.
Rapid experimentation gets claimed while the ideas stay protected. A team might run a small test, get ambiguous results, and declare the experiment complete without updating the concept or the roadmap. The principle sounds active but the behavior is the same as before — commitment to a direction is maintained, and the test is used to add confidence rather than to expose risk.
The principle system is treated as complete on its own. Design for Delight is a compact framing, not an operating method. Teams that adopt it without translating each principle into a specific review question, an evidence standard, or a facilitation behavior will find that the system does very little. Three principles with no behavioral translation are three good sentences.
Weak signals to watch for
Closest Waypoint move
Primary route
Use this when the team wants to translate the D4D principles into a local standard it can actually use.
Use this when you need a shared customer-emotional standard and can accept deriving the principles locally rather than importing the full D4D system.
technique
Use it when the principle set exists and now needs operational proof and measurement.
Sources and confidence
Primary + examples
Intuit
Discovery Waypoint
Reviewed by Discovery Waypoint Editorial Team · 2026-04-04
Intuit