Ullman’s Diagram depicted above is utilised to make design related decisions.<\/p>\n\n\n\n
How to use the Morphological Box?<\/strong> <\/p>\n\n\n\nStep 1<\/strong>: Using a small team, brainstorm and identify the attributes of the system (product, process or service) you are examining. These attributes are parts, functions, properties, qualities or design elements of the system of interest.<\/p>\n\n\n\nFor example:<\/p>\n\n\n\n
The attributes of a pen could be: material, retraction method, ink type, flow control, quality, colour, size, feel, weight and price.<\/li> The attributes of a hotel would be type, style, service level, star rating, price, location, facilities.<\/li><\/ul>\n\n\n\nIn generating the attributes, it is crucial to define each clearly. For example, what is meant by \u201chotel-type\u201d? What is meant by \u201chotel-style\u201d?<\/p>\n\n\n\n
Step2<\/strong>: Construct the Morphological Box using these attributes as column headings.<\/p>\n\n\n\nStep 3<\/strong>: For each attribute column, brainstorm and write down as many variations of the attribute as possible.<\/p>\n\n\n\nIf you are struggling to generate options\/variations, consider changing the attribute<\/li> If you find the same options\/variation appearing in another column, consider combining the attribute columns<\/li><\/ul>\n\n\n\nThe table, the Morphological Box, should now show all possible variations of each attribute.<\/p>\n\n\n\n
Step 4<\/strong>: Select one entry from each column to create a whole system concept solution. This can be done systematically (every combination!), randomly or by selecting different combinations. It is at this point the team can create truly imaginative system concepts.<\/p>\n\n\n\nStep 5<\/strong>: The aim is to arrive at a single practical but innovative system concept solution. It will require a mix of evaluation and improvement of the various system concepts. It is often critical, at this point, to be disciplined in the approach using decision tools like N\/3, Decision Matrix or Pugh Matrix. <\/p>\n\n\n\nCar Development<\/strong><\/p>\n\n\n\nFor developing a new car, for example, all the relevant parameters (e.g. Design Approach, Material etc.) are noted, and as many attributes as possible are assigned to each parameter. It requires expertise and imagination, as the aim is to create something new out of something that already exists. The result, in this case, is a two-dimensional table (although a morphological box can have up to four dimensions).<\/p>\n\n\n\nThe limitations of Morphological Box:<\/strong><\/p>\n\n\n\nPoorly thought through attributes.<\/strong> The attributes are crucial in constructing a Morphological Box. They must be relevant and clearly defined. I will typically think about customer\/user requirements as the attributes. <\/li>Not exploring possible whole system concepts. <\/strong>Morphological Box works, but we often do not explore the more extreme possibilities.<\/li><\/ul>\n\n\n\nSince finding the parameters from experience is perceived as the most complex step, here are some more tips:<\/p>\n\n\n\n
The parameters must be logically independent of each other so that they can be combined freely.<\/li> The parameters must apply to all conceivable solutions and not be valid for a subset of the problem.<\/li> The parameters should have conceptual relevance and not describe insignificant details of the solution sought.<\/li><\/ul>\n\n\n\nThe creation time for complex morphologies can be very long and can take several days or even weeks.<\/p>\n\n\n\n
Author: Piyush<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"Morphological Box is a Creative Thinking tool for generating complete solutions to complex problems. For this, we logically decompose the problem into several variables\/factors and try to identify solutions or…<\/p>\n","protected":false},"author":1,"featured_media":477,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_analytify_skip_tracking":false,"footnotes":""},"categories":[21],"tags":[],"_links":{"self":[{"href":"https:\/\/qubotics.io\/wp-json\/wp\/v2\/posts\/479"}],"collection":[{"href":"https:\/\/qubotics.io\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qubotics.io\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qubotics.io\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/qubotics.io\/wp-json\/wp\/v2\/comments?post=479"}],"version-history":[{"count":0,"href":"https:\/\/qubotics.io\/wp-json\/wp\/v2\/posts\/479\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/qubotics.io\/wp-json\/wp\/v2\/media\/477"}],"wp:attachment":[{"href":"https:\/\/qubotics.io\/wp-json\/wp\/v2\/media?parent=479"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qubotics.io\/wp-json\/wp\/v2\/categories?post=479"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qubotics.io\/wp-json\/wp\/v2\/tags?post=479"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"\"](\"https:\/\/qubotics.io\/wp-content\/uploads\/2022\/01\/Ullmans-diagram.png\")
<\/a><\/figure><\/div>\n\n\n\n