Key Takeaways
Borrow proven ideas across industries, but let domain experts make them real.
Look beyond your field. TRIZ, short for the Theory of Inventive Problem Solving, starts from a practical observation: similar problems and solution patterns recur in different industries. Rather than beginning from scratch, describe a specific problem in general terms, find a relevant existing approach, then adapt it to your circumstances. This passage between a real problem, an abstract model, and a practical answer is called the Prism of TRIZ.
Dyson’s bagless vacuum, for example, adapted cyclone separation, a method used in sawmills to separate dust from air. The analogy supplied a direction, not a finished product. Turning it into a working vacuum still required technical knowledge and invention. TRIZ can focus expertise and stretch it, but cannot substitute for understanding how the system works.
The method resembles analogical transfer: a solution travels between fields when the underlying relationship is similar, even though the objects differ. That is a more useful model of creativity than the myth of an idea appearing from nowhere. The crucial work is checking what transfers and what does not. A clever analogy can mislead when important conditions differ, so domain experts need to test the borrowed principle against materials, users, regulations, and operating conditions. TRIZ is strongest as a search guide, not as a guarantee that a successful solution in one setting will succeed unchanged in another.
When improvement creates a tradeoff, search for a way to break the link.
Name the conflict. A Technical Contradiction occurs when improving one feature makes another worse, such as adding material to strengthen a car while increasing its weight. A Physical Contradiction occurs when the same thing must have opposite properties, such as an umbrella being large in rain and compact when carried. TRIZ treats these conflicts as clues to inventive opportunities, rather than reasons to settle immediately for a compromise.
Researchers distilled 40 broad Inventive Principles from patterns in patents, after analyzing 50,000 records. For a technical contradiction, the Contradiction Matrix connects 39 engineering parameters to principles that have helped solve similar conflicts. For a physical contradiction, ask whether the opposites can be separated in time, space, condition, or system. The prompt is conceptual; practical ideas still depend on the problem solver.
This framework changes the question from which benefit to sacrifice to which assumption is making the benefits incompatible. That shift echoes design approaches that change system architecture rather than optimize a single component. Yet the matrix reflects patterns in patent records, not a universal law of invention. Its suggestions are starting points, and the problem’s framing affects what it returns. Treating the list as prompts rather than prescriptions preserves its creative value and leaves room for solutions that the original patent sample did not capture.
Define the outcome first, then judge solutions by benefits, costs, and harms.
Separate what from how. A benefit is an outcome someone wants; a function describes how that outcome is delivered; a solution is a particular system that performs the function. Confusing these levels can lock a team into one familiar design. Someone asking for a large car, for instance, may actually want status, space for passengers, or both. Each benefit could be met in different ways.
The Ideal Outcome is a list of desired benefits before deciding how to achieve them. To compare real options, TRIZ uses Ideality: benefits considered against all inputs and unwanted outputs. Costs include time, effort, materials, and money. Harms include waste and unwanted effects, even if they seem neutral, such as noise or heat. Imagining an ideal result broadens the search; assessing costs and harms brings the decision back to reality.
This separation resembles requirements engineering, where teams distinguish user needs from product specifications. It helps prevent a proposed feature from quietly becoming the goal itself. Counting harms also improves on a narrow cost-benefit calculation by making side effects visible. The challenge is that benefits and harms vary across stakeholders: a feature that saves staff time may create work for customers. Ideality is therefore best treated as a structured conversation, not a precise score that can conceal disagreement behind arithmetic.
Treat nearby waste, time, and environmental conditions as design materials.
Search before adding. Resource thinking asks what is already available in or around a system that could deliver a needed function. Resources can include components, empty space, staff knowledge, time, natural forces, and even a harmful output. First identify the benefit and function you need, then look for resources that could supply that function. This keeps the search focused and can avoid adding cost or complexity.
At Schiphol Airport, targets were placed in urinals, turning users’ tendency to aim at a target into a cleaning aid. The book reports an 80 percent reduction in spillage and a 20 percent reduction in cleaning costs. Another example is self-cleaning glass that uses rain to carry dirt away. These solutions make an existing behavior or environmental condition do useful work instead of introducing a separate mechanism.
This way of thinking connects naturally to circular design, which looks for useful roles for materials and outputs that a linear process would discard. It can reveal low-cost interventions precisely because it broadens the definition of a resource beyond equipment. Still, available does not always mean free: using a natural resource can have environmental costs, and relying on people’s behavior can introduce uneven results. A resource should be evaluated in context, including who supplies it and who bears any new burden.
Read a product’s evolution before competitors make its next version obsolete.
Track the trajectory. TRIZ describes eight Trends of Technical Evolution, patterns that successful systems often follow. They include increasing Ideality, an S-curve of development, greater automation, more segmentation, greater flexibility, better coordination between components, movement from complexity back to simplicity, and closer matching to changing needs. These are directions to investigate, not rules that every product must obey or calendars that predict when change will arrive.
An S-curve describes slow early progress, rapid improvement, and eventual maturity. Digital cameras began as expensive, bulky alternatives that produced worse images than film, but improvements eventually made them dominant. Kodak had developed digital technology yet remained tied to film. Studying a product’s history, components, and surrounding market can help a team anticipate possible next steps and prepare for technologies that may initially look inferior.
The S-curve is useful because it distinguishes a product’s current performance from its future improvement potential. A mature product may still outperform a young alternative today, while the newer technology has more room to advance. This is a valuable correction to decisions based only on current comparisons. The framework is less reliable as a timetable: regulation, customer trust, infrastructure, and business incentives can slow or redirect a technical trend. Strategic foresight therefore needs both product analysis and attention to the larger environment.
Stretch time, scale, and assumptions to escape familiar answers.
Interrupt the mental rut. Psychological Inertia is TRIZ’s term for being stuck in a habitual direction of thought, often because assumptions feel like facts. Expertise helps people solve familiar problems quickly, but the same shortcuts can make unfamiliar problems look like old ones. Tools that deliberately change perspective can expose alternatives.
The 9 Boxes map a situation across three time periods, usually past, present, and future, and three scales: the system, its larger environment, and its component details. A separate creativity exercise, Size-Time-Cost, pushes a problem toward extremes, such as no budget or unlimited time, before translating the resulting ideas into practical options. Smart Little People asks problem solvers to imagine tiny helpful or troublesome agents inside a problem area, then turn their actions into real design ideas.
These techniques make assumptions visible by changing the frame in which a problem is considered. That resembles cognitive debiasing practices that prompt people to generate alternatives before committing to an initial explanation. Extreme imagining can also lower the pressure to produce a sensible answer immediately. Its limit is important: imagination expands the candidate set, but does not establish feasibility. The move back to practical testing is not a concession to dull thinking. It is what distinguishes useful creativity from an entertaining list of impossibilities.
Draw the system’s interactions before deciding which part to fix.
Map what happens. Function Analysis breaks a system into Subject-Action-Object relationships. The subject performs an action that changes the object. Each interaction can be useful, insufficient, excessive, or harmful. Mapping components and their interactions reveals where the system works, where it falls short, and where it creates unwanted effects.
In an intensive care unit, monitors and staff conversations provide essential information and care, but their noise can disturb patients’ sleep. A map makes both sides visible, helping the team avoid a blunt fix that removes something necessary. The map should focus on one level of the system at a time, include relevant environmental factors, and identify the system’s main purpose. The resulting problem list can then be tackled interaction by interaction, and the improved system can be mapped again.
A function map acts like a shared model of a socio-technical system: it makes relationships visible to people who may understand different parts of the whole. That shared picture can improve diagnosis before any intervention is chosen. But a map is still a model, and its boundaries determine which effects appear. An ICU analysis that omits patients’ families, for example, may overlook relevant interactions. The value lies not in producing a perfect diagram, but in making assumptions discussable and revising the map when evidence changes.
Match each problem type to a proven solution prompt, not random brainstorming.
Choose the right prompt. TRIZ organizes solution tools around different kinds of problems. Contradictions point to the 40 Inventive Principles; product development can use the Trends; questions about how to produce a function can be explored through the Effects Database, which organizes scientific and engineering effects by what they do. The 76 Standard Solutions address harmful actions, insufficient actions, and difficult measurement or detection problems.
This classification turns a vague search into a targeted one. If a useful action is too weak, consider changing a component, adding an action, or using the environment. If an action causes harm, consider removing its cause, blocking the harm, converting it into something useful, or correcting its effects. For difficult measurement, ask whether the system can be changed so measurement is unnecessary, or whether a proxy can be measured instead.
The tool-selection logic is a form of structured search: problem categories reduce the number of directions a team must explore at once. That is especially helpful when open brainstorming produces many ideas but little traction. The categories also encourage a useful diagnostic pause: is the problem a tradeoff, an unwanted effect, a weak function, or a measurement challenge? No taxonomy can anticipate every messy situation, however. When a problem fits more than one category, trying multiple prompts is often more productive than forcing a single label.
Remove components without surrendering the functions people need.
Simplify by transferring functions. Trimming is a method for removing a system component while keeping its useful actions. A function map identifies what the component contributes, including both benefits and harms. Then ask whether the object, another component, an available resource, or a temporary action could perform the useful function instead. Removing the component can reduce costs and harms without reducing the benefits.
Dyson’s bagless vacuum offers a clear illustration. The dust bag was removed, but its useful role, separating dust from air, remained through a cyclone system. Trimming can begin with small changes far from a system’s main purpose, then move toward more radical redesign. Repeating the map-and-trim cycle may reveal a different system altogether. It can also expose missing functions that need to be added before further simplification makes sense.
Trimming is a powerful counterweight to the common assumption that improvement means adding features. It also aligns with lean design, where removing unnecessary steps can lower cost and complexity. The important distinction is between removing a component and removing its function: the first can improve a system, while the second may simply make it fail. A successful trim depends on understanding dependencies and testing the redesigned system. Without that discipline, elegant simplification can become disguised underinvestment.
Share imperfect ideas early, then improve them with the people who must act.
Make collaboration part of the method. TRIZ’s problem-solving sequence moves from understanding and scoping the issue, to defining needs, modeling the problem, finding solution prompts, generating options, and ranking and implementing them. Ideas can arise throughout, but capturing them rather than arguing over them too soon helps the group keep working on the problem.
The book calls these early proposals “bad solutions” to signal that they are incomplete and open to improvement. A visible idea park lets everyone contribute, including quieter participants. The people who own the problem and must implement a change should be involved: they bring practical knowledge and can identify obstacles while there is still time to address them. Rank options by how well they meet desired benefits, then consider costs and harms. Treat implementation problems as new problems to solve, not automatic reasons to quit.
This approach combines structured problem solving with psychological safety. A team can disagree about an idea without treating its proposer as the problem, which makes it easier to surface half-formed suggestions and practical objections. Involving implementers also connects invention to organizational reality, where a technically sound answer may fail if it creates extra work for someone else. Participation does not guarantee agreement or execution, though. Clear ownership, authority, and capacity still matter, so the process should end with explicit decisions and responsibilities.
Analysis
TRIZ’s central move is to make creativity less dependent on personal inspiration. It turns recurring patterns in inventive work into prompts, then asks problem solvers to translate those prompts into their own technical or organizational setting. The method’s most valuable contribution may be this division of labor: abstraction widens the search, while expertise and testing decide what can work. Its tools also correct a familiar sequence error. Teams often choose a solution before agreeing on the desired outcome or understanding the whole system. TRIZ delays that commitment by separating benefits from functions and by mapping interactions before selecting interventions.
The framework is unusually coherent because Ideality links its many tools. Contradictions seek more benefit without accepting a forced tradeoff; resource thinking seeks benefit without adding inputs; Trends anticipate how systems may improve; and Trimming removes components while preserving useful functions. Each is a different route toward a better balance of benefits, costs, and harms. This gives the toolkit a shared purpose rather than leaving it as a collection of unrelated creativity games.
Its evidence base also deserves careful interpretation. Patent analysis can reveal recurring technical strategies, but patents reflect what was documented and protected, not every creative act or every failed attempt. The framework therefore supports disciplined exploration, not statistical certainty that a suggested principle is best. Likewise, a system map clarifies interactions only within the boundaries its users choose. Missing stakeholders or delayed environmental effects can make an apparently ideal solution harmful elsewhere.
The practical discipline is to keep the cycle intact: state what is wanted, describe the system plainly, model the conflict or failure, use a suitable prompt, generate alternatives, and test the strongest options. This is neither pure brainstorming nor mechanical rule-following. It is a way to make creative search auditable, collaborative, and revisable, while preserving the human judgment required to turn a conceptual suggestion into a working solution.
Review Summary
TRIZ For Dummies receives positive reviews, with readers praising its clear introduction to TRIZ methodology. Reviewers appreciate the book's well-structured content and its ability to explain complex concepts simply. Some find it helpful for determining whether to pursue further TRIZ training. The book is seen as a valuable resource for those interested in design, innovation, and problem-solving. While most reviewers find it informative, some suggest that the structure could be improved and additional examples would enhance understanding.
People Also Read
Glossary
TRIZ
Inventive problem-solving toolkitAn acronym for the Russian phrase meaning Theory of Inventive Problem Solving. TRIZ combines a problem-solving process with tools based on patterns identified in patents and scientific literature. It helps people model a specific problem in general terms, use prompts drawn from prior solutions, and adapt those prompts with relevant expertise.
Prism of TRIZ
Specific to abstract to specificThe movement between a real-world problem, an abstract description of its essential structure, and a practical solution in the original setting. Abstraction makes it easier to recognize similarities with problems from other fields. The final step requires adapting the general prompt using knowledge of the real system.
Ideality
Benefits relative to downsidesTRIZ’s way of assessing how good a system is by considering its desired benefits in relation to its costs and harms. Costs include inputs such as time, materials, effort, and money. Harms are unwanted outputs, including effects that may seem neutral. Improving Ideality means increasing benefits, reducing costs, reducing harms, or some combination.
Ideal Outcome
A solution-free wish listA description of all desired outcomes, expressed as benefits rather than features or proposed solutions. It gives problem solving a direction while allowing people to consider what they want before judging what seems practical. The benefits can then be translated into functions and evaluated against real-world constraints.
Technical Contradiction
One improvement worsens anotherA conflict in which improving one characteristic of a system makes another characteristic worse. Adding material may strengthen a product but also increase its weight. TRIZ uses a Contradiction Matrix to connect such conflicts, expressed through engineering parameters, with Inventive Principles that can prompt alternative solutions.
Physical Contradiction
One thing needs opposite statesA conflict in which the same feature must have opposite properties to meet different needs. An umbrella needs to be large for protection and small for carrying. TRIZ suggests separating the opposing requirements in time, space, condition, or system rather than compromising between them.
40 Inventive Principles
Prompts for resolving contradictionsA set of 40 general solution concepts distilled from inventive patent examples. Principles include changing a parameter, segmenting a system, acting in advance, or making a component flexible. They do not provide finished designs. They prompt problem solvers to develop context-specific ideas for resolving contradictions.
Psychological Inertia
Habitual limits on thinkingTRIZ’s term for being stuck in a familiar direction of thought. Past experience, assumptions, technical language, and attachment to existing solutions can make alternatives difficult to see. Creativity tools such as extreme scenarios, time-and-scale mapping, and Smart Little People help change the frame and expose hidden constraints.
9 Boxes
A time-and-scale mapA grid for examining a system across three time periods, commonly past, present, and future, and three levels of scale: the system, its broader environment, and its component details. It helps clarify context, identify causes, anticipate change, and search for solutions beyond the most obvious place or moment.
Function Analysis
A map of system interactionsA method for describing a system through Subject-Action-Object relationships. It maps useful, insufficient, excessive, and harmful actions between system components and relevant environmental elements. The resulting Function Map makes interactions visible, produces a list of problems, and supports targeted improvement or redesign.
Standard Solutions
Prompts for defined problem typesA collection of 76 solution prompts organized around harmful actions, insufficient actions, and difficulties with measurement or detection. They are applied to a defined action or function, often modeled as a Subject-Action-Object relationship. The prompts suggest directions to explore, rather than ready-made solutions.
Trimming
Remove a component, keep its functionA method for improving a system by removing a component while preserving the useful actions it performed. Problem solvers first map the system’s functions, then consider whether another component, the object itself, a resource, or a temporary action can take over. Removing a component can reduce costs and harms while retaining benefits.
Effects Database
Scientific effects organized by functionA reference resource that organizes scientific and engineering effects according to what they can do. A problem solver states a needed function, such as cleaning a surface or measuring a property, and searches for effects that could provide it. The results are conceptual leads that must be adapted to the specific system.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.