Quality https://tigosoftware.com/ en 3 Levels of Quality in KANO Analysis Model https://tigosoftware.com/3-levels-quality-kano-analysis-model <span class="field field--name-title field--type-string field--label-hidden">3 Levels of Quality in KANO Analysis Model </span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">admin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Mon, 11/14/2022 - 13:33</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p><strong>Customers do know what they want but may not be proficient at describing their needs.</strong> The KANO model identifies three types of customer needs. By understanding the three types of customer needs and how to reveal them with the KANO model, the project team can use this information to guide the improvement process.</p> <h2><strong>The development of the KANO model Six Sigma</strong></h2> <p>Noriaki Kano, a Japanese researcher and consultant, published a paper in 1984 with a <strong>set of ideas and techniques that help us determine our customers’ satisfaction with product features</strong>. These ideas are commonly called the KANO Model. The KANO model Six Sigma shows that there is a basic level of quality that consumers assume the product will have. When listening to Voice of Customer, the team might classify the data into three categories. The categories are <strong>Must-be, Primary Satisfiers, and Delighters</strong>. This classification is called a KANO Analysis.</p> <ul><li>A <strong>must-be requirement</strong> can dissatisfy, but cannot increase satisfaction. It is a basic requirement of the customer; they will not do business without it.</li> <li>A <strong>Primary Satisfier requirement</strong> is one where the more of these requirements that are met, the more satisfied the customer</li> <li>A <strong>delighter</strong> does not cause dissatisfaction if not present, but it will delight clients if present</li> </ul><p>The team must ensure that the process meets the must-be’s, increases the primary satisfiers, and potentially adds delighters.</p> <p><img alt="Customer satisfaction types" data-entity-type="file" data-entity-uuid="b6d6e2a6-43a4-4a84-aafd-f9246c570ab9" src="/sites/default/files/inline-images/customer_satisfaction_types.png" /></p> <h2><strong>Example</strong></h2> <p>Please have a look at an example of a KANO model. This is what the diagram looks like.</p> <p><img src="https://i.imgur.com/8M7huJd.png" /></p> <h2><strong>How does it work?</strong></h2> <p>The KANO model shows that <strong>there is a basic level of quality that customers assume the product will have</strong>. For example, all cars have windows and tires. If asked, customers don’t even mention the basic quality items, they take them for granted. However, if this quality level isn’t met the customer will be dissatisfied.</p> <h3><strong>Basic and Expected Quality</strong></h3> <p>Note that the entire ‘Basic Quality’ curve lies in the lower half of the chart, representing dissatisfaction. <strong>Providing basic quality is not enough to create a satisfied customer.</strong> The ‘Expected Quality’ line represents those expectations which customers explicitly consider. The model shows that <strong>customers will be dissatisfied if their quality expectations are not met;</strong> satisfaction increases as more expectations are met.</p> <h3><strong>Exciting quality</strong></h3> <p>The ‘Exciting Quality’ curve lies entirely in the satisfaction region. This is the effect of innovation. <strong>Exciting quality represents unexpected quality items.</strong> The customer receives more than they expected. Competitive pressure will constantly raise customer expectations. <em><strong>Today’s exciting quality is tomorrow’s basic quality.</strong></em></p> <h3><strong>Reverse Quality</strong></h3> <p>These attributes refer to a high degree of achievement resulting in dissatisfaction and to the fact that not all customers are alike. For example, some customers prefer high-tech products, while others prefer the basic model of a product and will be dissatisfied if a product has too many extra features.</p> <p>Examples:</p> <ul><li>A restaurant so crowded that it generates huge queues, may be good for the owner, but displeasing to customers.</li> <li>In a similar way, the smaller the internal space, the lower the satisfaction of vehicle owners.</li> <li>The fewer options and variety on the menu of an airline, the lower the satisfaction of its customers.</li> <li>In a callcenter, using a lot of jargon, using excessive pleasantries, or using excessive scripts while talking to customers might be off-putting for them.</li> <li>In a hotel, producing elaborate photographs of the facilities that set high expectations which are then not satisfied upon visiting can dissatisfy the customers.</li> </ul><h3><strong>Keeping up with changing customer expectations</strong></h3> <p>Firms that seek to lead the market must innovate constantly. Conversely, firms that seek to offer standard quality must constantly research customer expectations to determine the currently accepted quality levels. It is not enough to track competitors since expectations are influenced by outside factors as well. For example, the quality revolution in manufacturing has raised expectations for service quality as well.</p> <h2><strong>Quality changes with the times</strong></h2> <p>Lastly, I would like to add that quality changes with the times.<br /><br /> Especially in the modern era, people's behavior and way of thinking are greatly affected by the continuous evolution of technology, and the world is changing at a rapid pace. In fact, there is a growing trend to demand more business value from software and systems than ever before. For example, even if a information system is developed that works well, if not many people use it, it won't be evaluated.<br /><br /> In other words, we are entering an era where people believe that if no one uses the system, its quality is low. Therefore, it is becoming more and more important for developers to proceed with development more speedily, keeping in mind the business impact and value creation.</p> <p>In this day and age where everyone is using digital devices such as smartphones in their daily lives, the expectations for software quality are becoming higher and higher.</p> <h2><strong>Instructions to prepare KANO model</strong></h2> <p><strong>Here are the instructions to prepare KANO model:</strong></p> <ol><li>Generate a list of customer requirements. Don’t guess what they are – talk to your customers</li> <li>Review the KANO model</li> <li>Identify the appropriate category for each requirement. Work through the list of requirements one by one.</li> <li>Mark each product or service attribute as to whether it is a: disatisfier/basic requirement, satisfier/more is better or a delighter. Add a fourth category – not relevant. These are attributes that the customer does not care about.</li> <li>Determine priorities</li> </ol><p><strong>How to determine priorities in a KANO model?</strong></p> <ul><li>First look at anything labeled as dissatisfiers or basic requirement. These represent customers’ minimal expectations, assess whether your organization is currently filling these requirements or not</li> <li>Perform the same assessment on the satisfiers. Are you doing them at all? Can you do more?</li> <li>If you aren’t meeting the basic requirements and have a lot of work to do on the satisfiers, don’t worry about the delighters yet. If you have all the basic requirements covered, and most of your satisfiers are done well, evaluate the delighters</li> </ul><h2><strong>Final Words</strong></h2> <p>Based on the five categories of the Kano model, a product can be assessed based on the basic features, delighters, satisfiers and dissatisfiers to help determine what might be the best mix of features to attract customers. While the model itself is straightforward, it requires careful consideration for customer needs and wants. In order to be effective and accurate in performing a Kano analysis that truly reflects aspirations of customers and the unique selling point that can help make a product stand out.</p> <p><em>Via <a href="http://en.tigosolutions.com/post/4418/3-levels-of-quality-in-kano-analysis-model">TIGO Solutions</a></em></p> </div> <div class="field field--name-field-blog-category field--type-entity-reference field--label-inline clearfix"> <div class="field__label">Category</div> <div class="field__item"><a href="/taxonomy/term/215" hreflang="en">Quality Management</a></div> </div> <div class="field field--name-field-tags field--type-entity-reference field--label-inline clearfix"> <h3 class="field__label inline">Tags</h3> <ul class="links field__items"> <li><a href="/taxonomy/term/530" hreflang="en">Quality</a></li> </ul> </div> <section class="field field--name-comment field--type-comment field--label-above comment-wrapper"> </section> Mon, 14 Nov 2022 06:33:41 +0000 admin 1517 at https://tigosoftware.com https://tigosoftware.com/3-levels-quality-kano-analysis-model#comments TQM vs. Kaizen vs. Six Sigma: what’s the difference? https://tigosoftware.com/tqm-vs-kaizen-vs-six-sigma-whats-difference <span class="field field--name-title field--type-string field--label-hidden">TQM vs. Kaizen vs. Six Sigma: what’s the difference?</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">admin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Fri, 09/09/2022 - 10:52</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>TQM, Kaizen, and Six Sigma are all unique management approaches that have a shared focus on processes rather than projects and value continuous improvement— let’s examine where they differ.</p> <h3><strong>Six Sigma</strong></h3> <p>Six Sigma focuses almost exclusively on the number of defects per million and reducing them. The percentile success rate is the north star. It lays out a concrete framework for finding production problems.</p> <p><img alt="Six Sigma" data-entity-type="file" data-entity-uuid="7504478a-f517-4776-b6ff-b9aa482859dc" src="/sites/default/files/inline-images/2022-09-09_11-15-18.jpg" /></p> <p>First, you must recognize that the issue exists. Your managers may have an idea that production is too slow. Next, you prove that the problem exists using measurement and data. Then you figure out the solution by running different numbers and using that to find a practical approach.</p> <h3><strong>Kaizen</strong></h3> <p>The Kaizen approach has more in common with TQM as it also aims to improve the work environment as a whole, rather than honing in on defects. Neither Kaizen nor TQM limits itself to fixing mistakes in the production line. The difference is that Kaizen focuses on bottom-up culture-based changes.</p> <h3>TQM</h3> <p>TQM is almost more of a cultural initiative than a management framework with concrete steps. You can see that in the high-level principles like fact-based decision-making where you involve every employee. Where it differs from Kaizen is the focus on high-level management involvement for decisions like standardizing frameworks and tools throughout the company.</p> <p>Via monday.com</p> </div> <div class="field field--name-field-blog-category field--type-entity-reference field--label-inline clearfix"> <div class="field__label">Category</div> <div class="field__item"><a href="/category/quan-tri-chat-luong-toan-dien-tqm" hreflang="en">Total Quality Management</a></div> </div> <div class="field field--name-field-tags field--type-entity-reference field--label-inline clearfix"> <h3 class="field__label inline">Tags</h3> <ul class="links field__items"> <li><a href="/taxonomy/term/530" hreflang="en">Quality</a></li> <li><a href="/taxonomy/term/106" hreflang="en">Quality Management</a></li> <li><a href="/taxonomy/term/519" hreflang="en">Quality Control</a></li> </ul> </div> <section class="field field--name-comment field--type-comment field--label-above comment-wrapper"> </section> Fri, 09 Sep 2022 03:52:19 +0000 admin 1371 at https://tigosoftware.com https://tigosoftware.com/tqm-vs-kaizen-vs-six-sigma-whats-difference#comments Difference between Quality and Grade https://tigosoftware.com/difference-between-quality-and-grade <span class="field field--name-title field--type-string field--label-hidden">Difference between Quality and Grade</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">admin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Wed, 08/31/2022 - 15:05</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>The terms "quality" and "grade" are often used interchangeably. In this post, let's understand the difference between these two terms</p> <h2 id="t-1661933063841"><strong>Difference between Quality and Grade:</strong></h2> <p>Quality is an attribute that describes how well something works. It is often measured by its performance against specifications. In contrast, the grade is a measure of the relative value of different products or services.</p> <h2 id="t-1661933063842"><strong>What is Quality?</strong></h2> <p>Quality is the degree to which a product or service meets customer expectations at any given time. A quality system focuses on meeting those expectations to maintain or improve customer satisfaction.</p> <p>The formal definition of quality as per ISO 9000 2015 is:</p> <p><em>"Quality:  degree to which a set of inherent characteristics of an object fulfils requirements".</em></p> <h2 id="t-1661933063843"><strong>What is a Grade?</strong></h2> <p>Think of grade as a category of the product. Different grades of the products have the same functional use but different technical characteristics.</p> <p>Here is the formal definition of grade according to <a href="https://www.qualitygurus.com/link/iso90012015/" target="_blank" title="iso90012015">ISO 9001</a> 2015:</p> <p><em>Grade: "category or rank given to different requirements for an object having the same functional use". Example: Class of airline ticket and category of hotel in a hotel brochure.</em></p> <h2 id="t-1661933063844"><strong>Examples</strong></h2> <p>For example, a $1 Raymond pen and $1000 Montblanc pen are both used to write. As long as both are serving this purpose satisfactorily, both have good quality.</p> <p>However, the Montblanc pen is a separate category of luxury products. Hence it is a different grade or product.</p> <p>So next time, when you have to compare the quality of the $1 Raymond pen and $1000 Montblanc pen, don't say that the Montblanc pen is of better quality. It is just a different grade or category. You can not compare apples and oranges.</p> <figure role="group" class="caption caption-img"><img alt="Quality vs Grade" data-entity-type="file" data-entity-uuid="6f2291d6-e8f6-4176-9915-1fc0832d3284" src="/sites/default/files/inline-images/2022-08-31_15-07-13.png" /><figcaption>Bad Quality, Good Quality and Grade</figcaption></figure><p>Also, high grade does not imply high quality.</p> <p><em>Via <a href="https://en.tigosolutions.com/post/4382/difference-between-quality-and-grade">TIGO Solutions</a></em></p> </div> <div class="field field--name-field-blog-category field--type-entity-reference field--label-inline clearfix"> <div class="field__label">Category</div> <div class="field__item"><a href="/category/quan-tri-chat-luong-toan-dien-tqm" hreflang="en">Total Quality Management</a></div> </div> <div class="field field--name-field-tags field--type-entity-reference field--label-inline clearfix"> <h3 class="field__label inline">Tags</h3> <ul class="links field__items"> <li><a href="/taxonomy/term/106" hreflang="en">Quality Management</a></li> <li><a href="/taxonomy/term/530" hreflang="en">Quality</a></li> </ul> </div> <section class="field field--name-comment field--type-comment field--label-above comment-wrapper"> </section> Wed, 31 Aug 2022 08:05:47 +0000 admin 1339 at https://tigosoftware.com https://tigosoftware.com/difference-between-quality-and-grade#comments