Constraint Relaxation
Constraint Relaxation: Every problem has constraints β some real (physics, law, budget), many assumed ("we always do it this way", "customers won't pay for that"). List your constraints explicitly, then ask for each: "Is this a hard constraint or an assumption?" Relax the assumptions temporarily and ask: "What becomes possible now?" The best solutions often hide behind constraints that weren't actually fixed.
What Is Constraint Relaxation?β
Constraint Relaxation is a technique from artificial intelligence, operations research, and design thinking that improves problem-solving by making implicit constraints explicit and then testing which of them are truly fixed. It is related to reframing and lateral thinking but is more systematic: it explicitly inventories constraints and tests each for elasticity.
Problems are almost always solved within a bounded space defined by constraints. Some constraints are truly fixed β physical laws, legal requirements, absolute budget limits. Others are assumed fixed without being genuinely so β "we only sell direct," "our software must run on-premises," "we don't work with that type of customer." These assumed constraints are inherited from past decisions, conventional wisdom, or unstated norms β and they often eliminate large sections of the solution space without justification.
The discipline of constraint relaxation: (1) make all constraints visible by listing them explicitly; (2) categorise each as truly fixed vs. assumed; (3) for assumed constraints, ask "what would become possible if this constraint were removed?"; (4) identify which relaxations reveal high-value options worth pursuing.
This doesn't mean ignoring real constraints β it means not treating assumed constraints with the same weight as real ones. The goal is to see the full solution space and consciously choose which constraints to operate within, rather than unconsciously limiting the space without examination.
How It Worksβ
Step 1: Define the problem clearly
β What outcome are you trying to achieve?
Step 2: List all current constraints explicitly
β What are we assuming we cannot change?
β What has been ruled out before this discussion?
β Include: budget, time, personnel, technology, customer requirements,
regulatory, geographic, organisational
Step 3: Categorise each constraint
β Truly Fixed: physical, legal, contractual, ethical
β Assumed Fixed: conventional, historical, internal policy, unexplored
Step 4: For each assumed constraint, ask:
β "What becomes possible if we relax this?"
β "What would we build/do if this constraint didn't exist?"
β "What would the solution look like with 10x more/less [resource]?"
Step 5: Evaluate relaxed-constraint solutions
β Which options reveal high-value approaches?
β Which assumed constraints are worth challenging in reality?
Step 6: Selectively remove or renegotiate assumed constraints
β Some relaxations require renegotiating internal policies
β Some require new resources; some are free
Three Real-World Examplesβ
Netflix: Removing the "Physical Media" Constraintβ
Traditional video rental assumed: customers must physically access media (cassettes, DVDs). This constraint drove everything β store locations, inventory management, late fees. When Reed Hastings founded Netflix, the business still operated within this constraint β mail-order DVDs. The 1997 pivot to streaming required relaxing the assumption that media had to be physical. Once that constraint was removed, the entire business model changed: no inventory, no shipping, no physical stores, global scale.
The "physical media" constraint felt real because it had been true for decades. It was actually an assumed constraint β one that technology rendered optional.
Engineering: "Software Must Run on Customer Hardware"β
Enterprise software companies assumed their software must run on customer hardware β physical servers in customer data centres. This constraint was treated as essentially legal/security (customer data must not leave the premises). Salesforce's Marc Benioff relaxed this constraint in 1999 with Salesforce CRM β software delivered entirely in the cloud. Most enterprise IT departments initially rejected this as a violation of a "fixed" security constraint.
The constraint turned out to be assumed β not all customers required on-premises; security could be achieved in the cloud; and enough customers were willing to accept a new model. Relaxing one assumed constraint launched a multi-trillion dollar industry.
Strategy: "We Only Serve [Customer Type]"β
A professional services firm believed it could only serve enterprise clients β this was a stated constraint based on their historical positioning. Constraint relaxation exercise: "What would the firm look like if we also served mid-market clients?" Revealed: a potential productised service line at lower price points, delivered by more junior staff, that didn't compete with the enterprise business. The assumed constraint (enterprise only) had been protecting margin identity but was not an actual requirement of the business model. The relaxation revealed a separate growth lever.
When to Use Itβ
β Constraint Relaxation is most valuable for:
- Innovation challenges where obvious solutions have been exhausted
- Problems where past approaches have consistently failed
- Strategic pivots where business model assumptions need examination
- Design sprints where fresh perspectives on "rules" are needed
β Use with caution for:
- Truly fixed constraints (relaxing legal or safety requirements is not creative, it's dangerous)
- When the constraint is the right answer (some constraints exist for very good reasons)
- Without follow-up reality-testing (relaxed-constraint ideas still need validation)
| Pairs well with | Why |
|---|---|
| Reframing | Reframing changes the problem; constraint relaxation changes the solution space |
| First Principles | First Principles identifies which constraints are fundamental; constraint relaxation removes the rest |
| Lateral Thinking | Lateral thinking and constraint relaxation are complementary creativity techniques |
| Chesterton's Fence | Before relaxing a constraint, understand why it exists (Chesterton) β then decide whether to keep it |
Common Misuses and Limitationsβ
Relaxing real constraints. Physics can't be relaxed. Legal requirements can't be ignored. Safety standards can't be reframed away. The technique's value is in identifying assumed constraints β not in disregarding genuinely fixed ones. Constraint relaxation requires honest categorisation.
Generating solutions without reality-testing them. Constraint relaxation generates options; it doesn't validate them. "What if we had an unlimited budget?" produces ideas β but those ideas still need to be tested against real constraints once the exploration is done.
Using it as a one-time brainstorm rather than an ongoing discipline. Organisations accumulate assumed constraints over time as policies, conventions, and inherited decisions solidify. Regular constraint audits β quarterly reviews of "rules we operate by" β are more valuable than one-time brainstorm sessions.
Related Modelsβ
| Model | Relationship |
|---|---|
| Reframing | Complementary: reframing changes the problem frame; constraint relaxation changes the solution space |
| First Principles | First principles identifies truly fundamental constraints |
| Chesterton's Fence | Understand why a constraint exists before relaxing it |
| Thought Experiment | "What if this constraint were removed?" is a thought experiment |
Frequently Asked Questionsβ
How do you identify which constraints are assumed vs truly fixed?
Ask: "Has anyone done this differently? Is it physically possible to not have this constraint? Could a well-resourced competitor operate without it? Does this constraint exist because of law/physics, or because of historical decisions?" If the answer to the last question is "historical decisions," the constraint is probably assumed. If a competitor has already relaxed a constraint and is operating successfully, it's definitely assumed. If no law, physical principle, or contractual requirement mandates it, it should be examined.
What is the "10x / 1/10x" constraint relaxation exercise?
Ask: "What would we build if we had 10x the budget? 10x the time? 10x the team?" Then: "What would we build if we had 1/10th the budget? 1/10th the time?" The extremes reveal which constraints are actually binding and which aren't. Often, the 1/10th exercise reveals a simpler, more focused approach that's actually better than the original β not because of the reduced resources but because the forced simplification removed complexity that wasn't adding value.
Is constraint relaxation the same as brainstorming without limits?
No. Unconstrained brainstorming ("imagine anything is possible") is often less productive than targeted constraint relaxation because it provides no structure for where to look. Constraint relaxation is structured: you've inventoried the specific constraints, categorised them, and are specifically asking what becomes possible when each assumed one is removed. This is more focused and typically more productive. You're not imagining a world without constraints; you're asking which specific constraints can actually be changed.
Further Readingβ
- de Bono, E. (1970). Lateral Thinking β the connection between constraint relaxation and creative problem-solving
- Syed, M. (2019). Rebel Ideas β how removing assumption constraints drives innovation
- Christensen, C. (1997). The Innovator's Dilemma β how assumed constraints create disruption opportunities
Apply with AIβ
π Run a constraint relaxation exercise with MindMax β
This page is part of the MindMax Mental Models Knowledge Base.