Balanced Breakthrough
An idea that passes all three lenses simultaneously: Desirability, Feasibility, and Viability — the only location in the model where a genuine breakthrough lives.
An idea that passes two lenses is not a breakthrough. It is a trap with a blind spot — and the one that passes two is usually harder to kill than the one that passes none.
What it is
Not a checklist. A diagnostic — three overlapping questions that together define the only zone worth building in.
Balanced Breakthrough is the condition that must be true for an innovation idea to be worth building: it must be desirable (people genuinely want it), feasible (the organisation can reliably deliver it), and viable (the economics work sustainably). These are not three independent tests passed one after another. They are three simultaneously active lenses, each capable of making an idea unworkable regardless of how strongly the others hold. A breakthrough lives only at the centre, where all three overlap.
The model was developed at IDEO and codified in Design Thinking as the three-circle framework that organises human-centred innovation work. Its core insight is that the most dangerous ideas are not the ones that fail all three lenses — those are easy to stop. The most expensive ideas are the ones that pass two. An idea that is desirable and feasible but not viable will be built with confidence and love, attract real users, and then fail when the economics catch up. An idea that is desirable and viable but not feasible will be sold, funded, and committed to — and then fail in delivery.
The three lenses are named for a reason. Desirability is not the same as expressed interest or survey approval; it is genuine human need, confirmed through research rather than assumed. Feasibility is not theoretical buildability; it is the real operational and technical capability of this organisation to deliver this thing consistently. Viability is not optimistic projection; it is sustainable unit economics under realistic assumptions. The discipline the model demands is applying each lens with honesty, not using it to validate a direction the team has already decided to pursue.
Explore the seven zones. Only one is the breakthrough.
Each zone has a name, a failure mode, and an example. The centre is the only place worth building.
Click any region of the Venn to see what kind of idea lives there and what happens when teams build in that zone without recognising it. Most promising ideas sit in one of the overlap zones, not the centre — close enough to feel like breakthroughs, far enough to be traps.
When to deploy it
Before committing investment. The DFV check is most valuable when the stakes of getting it wrong are still low enough to change direction.
Use it when
- →You are evaluating which ideas to take forward from a set of candidates — and need to distinguish genuine opportunities from exciting traps.
- →A promising concept is generating momentum and you want to ensure the enthusiasm is not masking a fatal gap in one of the lenses.
- →You are preparing to commit resources — funding, headcount, operational capacity — and need to verify that all three lenses are genuinely solid before doing so.
- →A cross-functional team needs a shared language for evaluating ideas across their different domains of expertise.
Do not lean on it when
- ×The team treats it as a validation tool rather than a diagnostic one — using it to confirm a direction already decided, not to test it honestly.
- ×The inputs to each lens are hypothetical rather than evidenced. An assessment run on assumptions alone produces structured-looking conclusions built on nothing.
- ×The analysis is used to declare an idea a breakthrough before each lens is genuinely tested. Labelling something viable because it is feasible and desirable is the most common way the model fails.
- ×You need a tool for generating ideas rather than evaluating them — Balanced Breakthrough is an evaluative lens, not an ideation method.
The honest limit: Balanced Breakthrough is a diagnostic frame, not a decision engine. It tells you which zone an idea sits in and what the implication of that zone is. It does not tell you whether to stop or reshape, how to bridge a gap, or which trade-off to accept. Those decisions require context, organisational judgment, and information the model itself cannot provide.
How it works
Five moves, from naming the idea to identifying precisely where it sits and what to do about it.
Name the idea clearly enough to test it.
Before checking any lens, the team needs to agree on what the idea actually is — specifically enough that each lens can be applied without ambiguity. A vague idea produces vague lens checks. A clearly stated idea (what is it, for whom, delivered how, at what economics) makes the three questions answerable. Spend time on this before moving to the lenses.
Check Desirability with evidence from real people.
Desirability is confirmed or denied by real human research, not by assumption, survey approval ratings, or the team's intuition about what customers want. It requires direct contact with the people the idea is designed for — observing their behaviour, understanding their unmet needs, and testing whether the proposed idea genuinely addresses something they care about. The Desirability check is weak if the team has not spoken to, or observed, real intended users.
Check Feasibility with operational honesty.
Feasibility is about what this organisation can actually do — not what is theoretically possible or what comparable organisations have achieved. It requires an honest assessment of current capabilities, the gap to what delivery would require, and the cost and timeline of bridging that gap. Feasibility checks often require input from operations, technology, and people with hands-on delivery experience rather than only from the strategists and designers who conceived the idea.
Check Viability with real financial modelling.
Viability requires actual unit economics: the real cost to serve, the realistic price ceiling, the volume at which the model works, and the competitive dynamics that affect margin over time. Optimistic projections, analogues from adjacent industries, or "this will work at scale" assumptions do not constitute a viability check. The model must hold at realistic entry scale, not just at a hypothetical future state. If the numbers only work at a scale that is years away, the viability check is not yet passed.
Locate the idea in the Venn and decide what the location means.
With evidence in each lens, the team can identify which zone the idea occupies. Centre means the idea passes all three and is worth building. Pairwise overlap means a specific lens is missing and the team must decide: is the gap bridgeable (can we acquire the capability, change the model, or shift the price point?), or does it make the idea not viable in this form? Single-circle means the idea is not ready and the team should either radically change direction or stop. The location is diagnostic; the decision is human.
Best practices
What separates a genuine three-lens check from the appearance of one.
When it works well
- ✓Each lens is checked with genuine evidence — real user research for Desirability, operational self-assessment for Feasibility, real unit economics for Viability.
- ✓The team includes people who can speak with authority to all three lenses — not just the people who had the idea.
- ✓The analysis is used to locate the idea honestly, including when the location is uncomfortable.
- ✓When a lens fails, the team treats it as a specific, addressable question ("what would need to be true about the economics for this to work?") rather than as a final verdict.
- ✓The tool is applied iteratively as each lens is tested — the picture updates as evidence comes in rather than being set once at the start.
The failure modes, and how to avoid them
Using it as a validation tool, not a diagnostic one.
The most common failure: the team has already decided to pursue the idea and uses the DFV framework to confirm, not challenge. The lens that is weakest gets the most optimistic treatment. Run the analysis before the team has committed to a direction, or explicitly ask "what would make us stop?" for each lens.
Running the analysis without real inputs.
A DFV analysis built on assumptions produces structured-looking conclusions built on nothing. If the research has not been done, the Desirability check is not real. If the financial model has not been built, the Viability check is not real. The framework cannot generate the evidence it requires; it only structures the evidence you already have.
Treating all three lenses as equally certain.
Teams often have strong evidence for one or two lenses and much weaker evidence for the third. The analysis should name the confidence level for each lens, not collapse them into a single verdict. "Strong Desirability signal, operational Feasibility confirmed, Viability based on analogues — needs real modelling" is more honest and more useful than a single thumbs-up.
Only including people who designed the idea in the analysis.
The Desirability lens is weakened if no one who has spoken to real users is in the room. The Feasibility lens is weakened if no one from operations or delivery is present. The Viability lens is weakened without someone who has built financial models. The DFV check requires cross-functional input by design.
Treating a failed lens as a project-ending verdict.
A lens that fails is a specific question: what would need to change for this lens to hold? The answer sometimes leads to a different model, a different price point, a different target user, or a different operational approach. The failure of one lens rarely means the idea is worthless — it means the current form of the idea has a specific gap that needs to be addressed or accepted.
Logistics
The tool is simple. The inputs are not — and that distinction matters.
Running a DFV analysis requires a cross-functional team that can speak to all three lenses, evidence (not assumptions) for each, and enough time to have an honest conversation about what the evidence actually says. The framework itself is three questions. The work that makes it real is the research, modelling, and operational assessment that must happen before — or alongside — the conversation.
Assemble a genuinely cross-functional team
The Desirability lens needs someone who has done real user research and can speak to what customers actually want. The Feasibility lens needs someone from operations or delivery who understands what the organisation can and cannot do. The Viability lens needs someone with financial and commercial expertise. If any of these voices is missing, one lens will default to assumption.
Gather evidence before the session, not during it
The DFV conversation is most productive when the team has real evidence for each lens going in — not when they are constructing the evidence during the session itself. User research, financial modelling, and operational assessment should be done before the DFV discussion, so the session can focus on interpreting what the evidence means rather than generating it from first principles.
Name the confidence level for each lens explicitly
Not all lenses will be equally evidenced. Making the confidence level explicit — "we have strong evidence on Desirability, moderate on Feasibility, and Viability is still primarily assumption" — keeps the analysis honest and points directly to what needs to be done next. A falsely even presentation of all three lenses hides exactly the work that still needs doing.
Ask the kill question for each lens
For each lens, the team should ask: what would make us kill this idea? What result from user research would tell us Desirability is not real? What operational constraint would make Feasibility impossible? What unit economics finding would make Viability unachievable? Pre-defining the kill criteria reduces the risk of motivated reasoning when the results come in.
Return to the framework as evidence accumulates
The DFV analysis is not a one-time check. As each lens is tested through research, prototyping, and financial modelling, the picture updates. Teams that run one DFV session and treat it as final are applying the framework incorrectly. The model is most valuable when it is revisited each time a significant piece of evidence changes the picture in any lens.
AI and this method
AI shifts the weight of the three lenses unevenly — and cannot integrate them.
Toggle between modes to see how AI contributes differently to each of the three lenses — most strongly to Viability, moderately to Feasibility, and least to Desirability, where the limit of language-based analysis matters most. The integrating judgment at the centre remains irreducibly human.
In-depth example
The premium cleaning service: a D+F idea that looked like a breakthrough until the numbers arrived.
A founding team runs a rigorous DFV check on a premium on-demand cleaning service and discovers the idea sits in the Desirability + Feasibility overlap, not the centre. Strong customer love, clear operational feasibility — fatal unit economics. Toggle to see what a hypothetical AI-run DFV analysis might produce and why the false balance it generates is more dangerous than no analysis at all.
Checking each lens explicitly
DESIRABILITY
Strong ✓
Research with fifteen professional households confirmed genuine unmet need. Participants described the pain clearly: existing cleaning services were inconsistent on quality, required micromanagement, and created friction rather than relieving it. Willingness to pay at the proposed price point was high, and the concept of a reliably premium service with no supervisory overhead resonated strongly.
FEASIBILITY
Conditional ✓
The team could recruit and train cleaning professionals to the required quality standard. The logistics and scheduling systems were buildable. The conditional: sustaining quality at scale would require robust QA processes and low staff turnover — both achievable but demanding ongoing investment. Feasibility held, but only with operational discipline.
VIABILITY
FATAL ✗
This is where the idea broke. At the price point customers would pay — even the premium end — the labour cost to deliver a high-quality clean at premium service levels exceeded revenue per visit. Labour is the dominant cost, and the unit economics were structurally negative. Volume did not fix it; it amplified the loss. The team modelled every pricing and cost scenario and could not find a path to positive unit economics.
Where this idea lives — and what the team did
Desirability + Feasibility, not Viability — Love Without Sustainability
The idea sits in the D+F overlap, not the centre. People love it and the team can deliver it, but the economics are fatal. A year of building this would have created something beloved and unsustainable — the most common and most expensive trap in the DFV model.
The team stopped before building
Because the DFV check surfaced the viability gap before significant investment, the team paused. This was not a comfortable conversation — the concept was genuinely exciting and the team was attached to it. But the discipline of checking all three lenses before committing prevented a much larger loss.
Reframing, not abandoning
The team explored whether the viability gap could be bridged by changing the model — higher-tier positioning with fewer clients, B2B rather than B2C, or a technology-mediated quality layer that reduced the labour cost per visit. Each variant required re-checking all three lenses. The desirability and feasibility findings remained useful inputs to any reformulation.
What the analysis gave them
A clear diagnosis rather than a vague sense that something was wrong. Knowing the idea sat in D+F rather than centre pointed precisely to what needed to change: the economic model, not the concept itself. That specificity made the conversation about next steps much more productive than a general "the numbers don't work" conclusion.
Frameworks
Where Balanced Breakthrough shows up.
The DFV lens appears at the evaluation and gate moments of the major innovation frameworks — when teams need to decide whether a concept is genuinely worth building, not just promising. It is the common language across frameworks that otherwise differ significantly in their approach and vocabulary.
Related methods
What to pair with Balanced Breakthrough — and where in the DFV model each method operates.
Balanced Breakthrough is the integrating lens. The methods below operate within specific circles — generating evidence for Desirability, testing Feasibility in practice, or mapping the dimensions of Viability. The DFV framework names the question each method is answering.
Sources & further reading
The work behind this method.
Change by Design
Tim Brown (2009)
Brown's account of Design Thinking at IDEO places the Desirability-Feasibility-Viability framework at the centre of human-centred innovation practice. His treatment of the three circles is not a checklist but a dynamic tension: the most interesting work in innovation happens at the intersections and the gaps, and the task of the designer is to navigate toward the centre by understanding why the balance is currently off. Brown's framing of the framework as a diagnostic rather than a gate is the account that most clearly captures how the model is meant to function in practice.
The Innovator's Dilemma
Clayton M. Christensen (1997)
Christensen's account of why good companies fail illuminates the Viability trap in particular: incumbents optimise for the viability of their existing business model, which leaves them blind to desirable new offerings that would undermine that model. The DFV framework, read through Christensen, reveals that Viability is not a single fixed lens — it depends on whose economics you are measuring and over what time horizon. The book is the best account of what happens when the Viability lens is applied only to the existing model and not to the emerging one.
Ten Types of Innovation
Larry Keeley, Ryan Pikkel, Brian Quinn, and Helen Walters (2013)
Keeley and colleagues provide the most systematic treatment of Viability as a multi-dimensional lens. The ten types — spanning profit model, network, structure, process, product performance, product system, service, channel, brand, and customer engagement — show that Viability is not simply "does the product make money?" but a composite of business model dimensions, most of which are not product features at all. Teams using the DFV framework benefit from the Ten Types as a tool for finding Viability routes when the obvious model fails.