Triz Case

I understand that the penetration of TRIZ was not easy. Even we say 'TRIZ is a wonderful method for inventive thinking', people say (or think) 'It's doubtful. There cannot be any method of easy invention'. I have worked with various software tools and technology led inventive problem solving methodologies but a limited number of corporation were able to use them. Of course, with advent of cloud computing most of high-end, capital intensive technological platforms with all bells and whistles are readily available through SAAS with no capital outlay and with minimal recurring expense to all types of companies big, medium, small.

I have recently come to know about software tools TechOptimizer. It is a very useful which was built by a group of Altshuller's former students who emigrated from Russia to USA. If you read the book, it Fundamentals has chapters devoted to each of the major problem solving and problem analysis modules (not the Internet Assistant). They are sequenced more by frequency of use than by order of use. The first half of the book takes you through the solution generating modules; the latter half, the problem analysis modules:

Chapter 1 outlines a stereotypical, multiphase methodology for design, and why one is needed. It introduces the "Innovation Roadmap"-a useful flowchart that describes sequencing of TechOptimizer modules in-use. It includes the gathering of background data, the sequencing of use of problem statement tools (function analysis and trimming, feature transfer), the use of problem solving tools (effects,

Page | 3

prediction, principles), and validation & reporting. Connection between the design methodology and Roadmap are implied; few details are given here (or elsewhere)explicitly defining how the steps in the Innovation Roadmap feed into particular design phases.

Chapter 2 describes the Effects Knowledge Base. It includes an explanation of how the input, output and control parameters can be used to relate several effects using the Connect feature. This is helpful if you add your own effects to the library.

Chapter 3 describes how the Prediction module contributes to helping set R&D directions, predicting the evolution of technological systems, and improving interactions between parts of your system.

Chapter 4 on Principles gives the origins & background on technical contradictions and coaches you upon how to set up technical contradictions using the three-line template TechOptimizer uses. Although mentioned, treatment of physical contradictions is too light (as it is in the software) for the tastes of most TRIZ users; the opportunity is missed to point out TechOptimizer' s single window on Physical Contradiction and Separation Principles, which has the corresponding 40 principles aligned to the separation principles.

Page | 4

Chapter