{"id":704,"date":"2025-12-01T13:03:21","date_gmt":"2025-12-01T13:03:21","guid":{"rendered":"https:\/\/www.montrealindustry.com\/?p=704"},"modified":"2026-01-26T12:23:03","modified_gmt":"2026-01-26T12:23:03","slug":"how-to-run-kaizen-meetings-that-generate-real-weekly-savings","status":"publish","type":"post","link":"https:\/\/www.montrealindustry.com\/en\/how-to-run-kaizen-meetings-that-generate-real-weekly-savings\/","title":{"rendered":"How to run kaizen meetings that generate real weekly savings"},"content":{"rendered":"\n\n<div class=\"tldr-hybrid\"> <p><strong>Most continuous improvement programs fail because they focus on gathering ideas rather than hunting for visible, quick savings.<\/strong><\/p> <ul> <li>The secret is not the \u201csuggestion box,\u201d but the Gemba walk to identify \u201cdollars on the floor.\u201d<\/li> <li>Every improvement, however small, must be valued for its financial impact and implemented with maximum velocity.<\/li> <\/ul> <p><em><strong>Recommendation:<\/strong> Systematically integrate a finance representative into your improvement loops to accelerate savings validation and demonstrate a continuous return on investment (ROI) to management.<\/em><\/p> <\/div><p>As a continuous improvement facilitator, you know the drill: meetings full of good intentions, colorful post-its on a board, a suggestion box that\u2019s overflowing\u2026 only to eventually see most of these suggestions fizzle out without ever being implemented. This frustration is the daily reality for many manufacturing SMEs in Montreal and elsewhere. People often confuse Lean methodology, a global system for waste hunting, with its fundamental philosophy: Kaizen, the mindset of continuous improvement carried by every employee. The problem is not a lack of ideas, but the absence of a system designed to transform them into measurable results.<\/p> <p>Classic approaches hit a wall of bureaucracy, slowness, and demotivation. Teams are asked to find solutions, but they aren\u2019t given the tools to quantify the impact of their findings, nor the speed of execution that feeds engagement. The result is a graveyard of good intentions where the best initiatives die for lack of follow-through. But what if the real key wasn\u2019t to collect more ideas, but to create a culture of rapid action, focused on the detection and immediate resolution of quantifiable problems? What if every improvement was seen not as a task, but as a \u201cdollar on the floor\u201d that just needs to be picked up?<\/p> <p>This article proposes a \u201cblack belt\u201d approach\u2014pragmatic and results-oriented. We will deconstruct the myth of the suggestion box, structure Gemba walks that generate value, learn how to balance small wins and major projects, and above all, integrate financial validation not as an obstacle, but as an accelerator for your Kaizen process. The goal: to generate visible savings, every week.<\/p><p>To guide you through this transformation, this article is structured to address each performance lever. We will begin by diagnosing the flaws in traditional systems and then build, step by step, an efficient and profitable Kaizen machine.<\/p> <div class=\"summary-block\"><h2>Summary: Your Roadmap for Profitable Kaizen<\/h2> <ul> <li> <a href=\"#46.1\">Why the classic suggestion box system is a graveyard for motivation?<\/a><\/li> <li> <a href=\"#46.2\">How to organize a productive Gemba walk with management?<\/a><\/li> <li> <a href=\"#46.3\">A 2-second improvement or a major project: what to value to create momentum?<\/a><\/li> <li> <a href=\"#46.4\">The risk of the phrase \u201cwe\u2019ve always done it this way\u201d for your survival<\/a><\/li> <li> <a href=\"#46.5\">When to validate the savings of a Kaizen project with the finance department?<\/a><\/li> <li> <a href=\"#15.1\">Why your current Excel spreadsheets are unusable for Artificial Intelligence?<\/a><\/li> <li> <a href=\"#40.3\">How much do customer returns and production scrap really cost you?<\/a><\/li> <li> <a href=\"#30\">How to manage your factory remotely using cloud-based dashboards?<\/a><\/li> <\/ul> <\/div> <h2 id=\"46.1\">Why the classic suggestion box system is a graveyard for motivation?<\/h2> <p>The suggestion box, whether physical or digital, starts with good intentions: giving employees a voice. However, in practice, it most often turns into an administrative black hole. Ideas go in, but few come out as concrete actions. This phenomenon is not inevitable; it is the consequence of a fundamentally passive design. The employee submits a suggestion and waits, often without feedback, creating a cycle of frustration and disengagement. It is no coincidence that a study reveals nearly 80% of improvement resolutions are abandoned after only a few weeks. The system is not designed for speed.<\/p> <p>The main flaw of this model is the <strong>disconnection between the idea and the action<\/strong>. The suggestion is extracted from its context, analyzed coldly by a committee that lacks field reality, and put on hold. This delay kills the initial enthusiasm. An operator who identifies a micro-waste wants to see it corrected quickly, not in six months after three validation meetings. The absence of immediate feedback sends a clear message: \u201cyour idea is not a priority.\u201d<\/p> <p>By creating a <strong>culture of suggestion<\/strong> rather than a culture of action, the suggestion box institutionalizes slowness. It separates those \u201cwho think\u201d (management) from those \u201cwho do\u201d (operators), the exact opposite of the Kaizen philosophy which aims to empower every person to improve their own workstation. To break this deadlock, the logic must be reversed: stop waiting for ideas and start actively hunting them on the shop floor.<\/p>  <h2 id=\"46.2\">How to organize a productive Gemba walk with management?<\/h2> <p>The Gemba walk is the antidote to the suggestion box. The Japanese term \u201cGemba\u201d means \u201cwhere the truth is found,\u201d i.e., the workshop, the production line, the place where value is created. Organizing a Gemba walk involves bringing management and support teams to the field, not to inspect, but to <strong>observe, listen, and understand<\/strong> real challenges. The goal is not to find culprits, but to identify improvement opportunities\u2014those famous \u201cdollars on the floor\u201d waiting to be picked up. A productive Gemba is short, focused, and leads to immediate actions.<\/p> <p>To be effective, a Gemba walk must be prepared. It is not an improvised visit. The protocol is simple but rigorous: define a theme (e.g., waiting times on line X), form a multidisciplinary team, and remember the golden rules: ask open questions (\u201cWhy do we do it this way?\u201d), propose no solutions on the spot, and above all, show humility. The expert is the operator. The involvement of a union representative can be a major asset, transforming the process into a common quest for productivity and ergonomic improvement.<\/p> <figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/www.montrealindustry.com\/wp-content\/uploads\/2025\/12\/observation-gemba-usine-aeronautique-montreal.webp\" alt=\"Dirigeants observant les op\u00e9rations de production dans une usine a\u00e9rospatiale montr\u00e9alaise lors d'une marche Gemba\"><\/figure>\n<p>After observation comes the most important phase: the debriefing. This is where observations are shared and transformed into an action plan. Every identified problem must be associated with a simple metric (seconds lost, unnecessary meters traveled) and converted into a potential cost. This quantification is what will speak to management and justify the allocation of resources for resolution. A successful Gemba walk always ends with a list of clear actions, with an owner and a short deadline.<\/p> <div class=\"actionable-list\"> <h3>Your Action Plan for an Effective Gemba Audit<\/h3> <ol> <li>Contact Points: List all stations and processes involved in the Gemba walk scope.<\/li> <li>Collection: Inventory observed waste (waiting, unnecessary movements, overproduction) with specific examples and photos if possible.<\/li> <li>Consistency: Compare observed processes against official work standards. Gaps are opportunities.<\/li> <li>Memorability\/Emotion: Identify the most \u201cshocking\u201d or simplest waste to solve to create a quick first win.<\/li> <li>Integration Plan: Assign each action to a lead with a follow-up date within less than a week.<\/li> <\/ol> <\/div>  <h2 id=\"46.3\">A 2-second improvement or a major project: what to value to create momentum?<\/h2> <p>A common mistake in improvement programs is to only value large projects with a high financial impact. However, true Kaizen culture feeds on a multitude of small daily improvements. The question is not to choose between a \u201c2-second improvement\u201d (like moving a tool box closer) and a re-engineering project, but to understand that both are two sides of the same coin. Small victories create <strong>momentum and engagement<\/strong>, while major projects bring structural performance gains.<\/p> <p>The key to motivation is the <strong>velocity of improvement<\/strong>. An employee who sees their idea, even a tiny one, implemented in less than 24 hours feels heard and valued. This effect is far more powerful than an annual bonus. Publicly celebrating these quick wins\u2014a \u201cKaizen of the Week\u201d board, a mention in the team meeting\u2014anchors the idea that every second gained counts. According to Kaizen experts, these gradual and continuous adjustments, once accumulated, have a significant impact on the company\u2019s overall performance.<\/p> <blockquote> <p class=\"citation-content\">We aren\u2019t just trying to fix a problem. We are designing a new process in which that problem no longer exists.<\/p> <cite>\u2013 Patrick Choquette, Industrial Engineer and Senior Advisor, BDC Advisory Services<\/cite> <\/blockquote> <p>The winning strategy is to create a two-speed system. On one hand, an ultra-fast circuit for small improvements that require no investment and can be implemented by the team itself. On the other, a structured process (like DMAIC) for more complex projects that require in-depth analysis and budgetary validation. By valuing both, you show that every contribution, regardless of size, is essential to collective performance.<\/p>  <h2 id=\"46.4\">The risk of the phrase \u201cwe\u2019ve always done it this way\u201d for your survival<\/h2> <p>The phrase \u201cwe\u2019ve always done it this way\u201d is more than just resistance to change; it is a symptom of complacency that can prove fatal for a company. In a globalized competitive environment, stagnation is not an option. The industrial history of Montreal and Quebec is a brutal reminder of this. Entire sectors, once flourishing, declined in the face of international competition. Indeed, local industrial history recalls that the textile and footwear industries disappeared in Quebec, partly due to an inability to innovate and optimize their processes continuously.<\/p> <p>These companies did not disappear for lack of expertise, but for lack of agility. They continued doing \u201cas before\u201d while the world around them changed. The Kaizen approach offers exactly the protection needed against this risk. By encouraging permanent questioning and giving teams the means to adapt their work methods, you establish a culture of evolution. It\u2019s not about revolutionizing everything every day, but accepting that every process can and must be improved.<\/p> <div class=\"case-study-block\"> <p class=\"case-study-block-title\">Case Study: The Toyota Method as a Survival Model<\/p> <p>Born in Toyota factories in the 1950s, the Kaizen method became the key to the competitiveness of the Japanese model. Unlike the Western approach of \u201cre-engineering\u201d which advocates radical and discontinuous changes, the Toyota approach favors small, fast, and regular changes. This strategy avoids the \u201cYo-Yo\u201d effect of large reorganizations and sustains improvements over time, making adaptation a core competence of the company rather than a one-off project.<\/p> <\/div> <p>Today, for a manufacturing SME in Montreal, ignoring this principle is not just a brake on productivity; it is a threat to its <strong>industrial survival<\/strong>. The question is no longer \u201cshould we change?\u201d but \u201chow fast can we improve to stay relevant?\u201d. The answer lies in your ability to transform the phrase \u201cwe\u2019ve always done it this way\u201d into \u201chow could we do it better tomorrow?\u201d.<\/p>  <h2 id=\"46.5\">When to validate the savings of a Kaizen project with the finance department?<\/h2> <p>One of the biggest brakes on improvement velocity is the bottleneck often represented by the finance department. In many organizations, finance is perceived as a final judge, a censor who validates (or invalidates) projects after the fact. For an effective Kaizen process, this role must be radically transformed: finance must become an <strong>early strategic partner<\/strong>, a coach who helps teams quantify the value of their ideas from the start.<\/p> <p>The key is to establish clear ground rules and transparent validation thresholds. Not every improvement needs to pass through the CFO\u2019s office. A delegation system based on the amount of projected annual savings allows teams to be empowered and considerably speeds up the process. An improvement that generates $500 in annual savings does not justify the same level of validation as a $50,000 project.<\/p> <figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/www.montrealindustry.com\/wp-content\/uploads\/2025\/12\/reunion-validation-kaizen-finance-montreal.webp\" alt=\"\u00c9quipe finance analysant les \u00e9conomies d'un projet Kaizen sur tableau de donn\u00e9es dans un bureau moderne de Montr\u00e9al\"><\/figure>\n<p>The implementation of a simple validation matrix, known to all, is a powerful tool for decentralizing decision-making. This approach holds supervisors and department managers accountable, as they become the primary validators of their teams\u2019 gains. The role of finance then focuses on training teams in ROI calculation methods, auditing the most significant projects, and consolidating global gains for management.<\/p> <table class=\"table-data\"> <caption>Financial Validation Thresholds for Kaizen Projects<\/caption> <thead> <tr> <th>Annual Savings Amount<\/th> <th>Required Validation Level<\/th> <th>Average Approval Time<\/th> <\/tr> <\/thead> <tbody> <tr> <td>Less than $500\/year<\/td> <td>Field Team<\/td> <td>Immediate<\/td> <\/tr> <tr> <td>$500 to $5,000\/year<\/td> <td>Direct Supervisor<\/td> <td>1-2 days<\/td> <\/tr> <tr> <td>$5,000 to $50,000\/year<\/td> <td>Departmental Management<\/td> <td>1 week<\/td> <\/tr> <tr> <td>Over $50,000\/year<\/td> <td>CFO and Executive Committee<\/td> <td>2-4 weeks<\/td> <\/tr> <\/tbody> <\/table> <p>By transforming financial validation from a closed door into a series of open and adapted doors, you don\u2019t just save time: you demonstrate that the company trusts its teams and is serious about improving performance.<\/p>  <h2 id=\"15.1\">Why your current Excel spreadsheets are unusable for Artificial Intelligence?<\/h2> <p>All factories run on Excel. It is a fantastic tool for quick calculations and managing small lists. However, the way 90% of these files are built makes them completely unusable for advanced data analysis or for feeding Artificial Intelligence (AI) algorithms. Your spreadsheets are often documents designed for the human eye, not for a machine. They are filled with \u201cdirty digital ink\u201d that blocks any attempt at automation and intelligent management.<\/p> <p>The problem lies in a series of common practices that, while visually practical, are a nightmare for data analysis. Every time a human uses visual formatting to convey information, they create unstructured data. AI cannot interpret a red cell as \u201cUrgent\u201d if that information is not encoded in a \u201cStatus\u201d column. Similarly, merged cells to center a title destroy the tabular structure that algorithms need to function.<\/p> <p>To prepare your factory for Industry 4.0 and data-driven management, basic discipline in managing your spreadsheets is indispensable. You must move from a <strong>\u201cReport\u201d Excel<\/strong> to a <strong>\u201cDatabase\u201d Excel<\/strong>. This means adopting strict rules: one piece of information per cell, no merged cells, standardized date and number formats, and a ban on using color as the only vector for information. Here are the most common errors that prevent the exploitation of your data:<\/p> <ul> <li>Merged cells preventing automatic data reading<\/li> <li>Unstructured free-text comments and annotations<\/li> <li>Use of colors as the only status indicator<\/li> <li>Lack of standardized formats for dates and amounts<\/li> <li>Mixing raw data and calculation formulas in the same columns<\/li> <\/ul> <p>Cleaning up these practices is not just about cleanliness; it is the sine qua non for being able to one day analyze your production trends, predict breakdowns, and optimize your flows in real-time using more powerful tools.<\/p>  <h2 id=\"40.3\">How much do customer returns and production scrap really cost you?<\/h2> <p>When evaluating the cost of poor quality, we tend to limit ourselves to the material value of the discarded or returned product. This is a dangerously incomplete view. The real cost of production scrap or a customer return is an iceberg: the visible part (the cost of the product) hides a much larger mass of <strong>hidden costs<\/strong> that weigh heavily on your profitability. The Kaizen approach aims precisely to melt this iceberg by tackling the root causes of poor quality.<\/p> <p>Think about everything surrounding a single defective product: the time an operator spent producing it, the cost of raw materials, the energy consumed, the inspection time to detect it, the administrative time to manage the customer return, the transport costs to retrieve it, the cost of its replacement, and the potentially devastating impact on your reputation. Each of these elements represents \u201cdollars on the floor.\u201d The Kaizen method allows for a radical increase in the Quality Rate with a sharp drop in scrap and waste by attacking the roots of the problem.<\/p> <div class=\"case-study-block\"> <p class=\"case-study-block-title\">Case Study: ROI Calculation in Aerospace<\/p> <p>The example of Vulture Aerospace perfectly illustrates the calculation of Return on Investment (ROI) for Lean improvements. Faced with recurring quality issues, the company invested 80 million euros in automation and continuous improvement. This investment allowed them to increase production by 10 aircraft per month. With each additional unit generating 3.5 million euros in profit, the investment was quickly recouped. The analysis revealed that the hidden costs of poor quality included not only scrap but also extra inspections and overstocking required to compensate for defects.<\/p> <\/div> <p>Calculating the <strong>Cost of Poor Quality (COPQ)<\/strong> is an essential exercise to justify your improvement initiatives. By putting a precise figure on each waste, you transform an abstract \u201cquality problem\u201d into a concrete financial loss that management cannot ignore. This is the most powerful argument for unlocking the resources needed for your Kaizen projects.<\/p> <div class=\"key-takeaways\"> <p>Key Takeaways<\/p> <ul><li>Replace the passive suggestion box with active Gemba walks to identify problems at the source.<\/li><li>Quantify every improvement opportunity in \u201cdollars on the floor\u201d to create a common language with management.<\/li><li>Involve finance upstream in the process to speed up savings validation and transform that department into an ally.<\/li><\/ul> <\/div> <h2 id=\"30\">How to manage your factory remotely using cloud-based dashboards?<\/h2> <p>Once your Kaizen culture is in motion, ideas are transformed into actions, and gains are validated, the ultimate step is to make this performance visible and manageable in real-time. Cloud-based dashboards are the perfect tool for this. They allow for the centralization of Key Performance Indicators (KPIs), making them accessible to everyone\u2014from management to operators\u2014and allowing the factory to be managed remotely. This is the nervous system of your continuous improvement process.<\/p> <blockquote> <p class=\"citation-content\">It is important to manage one\u2019s organization using performance indicators to measure results.<\/p> <cite>\u2013 Manager GO, KAIZEN Method Guide<\/cite> <\/blockquote> <p>A good Kaizen dashboard doesn\u2019t just track classic production indicators like Overall Equipment Effectiveness (OEE). It must, above all, measure the <strong>health and momentum of your improvement process<\/strong> itself. Tracking the number of ideas submitted is good, but tracking the average implementation time is better. Measuring potential savings is one thing, but displaying actual savings validated by finance is what proves the ROI of your program.<\/p> <p>The power of the cloud is to make this data live and accessible. A manager can check the week\u2019s performance from their phone; a supervisor can lead their morning team meeting in front of a screen displaying live KPIs. This transparency creates healthy competition and anchors the data culture at all levels. To be effective, your dashboard should focus on a handful of actionable indicators:<\/p> <ul> <li>Number of Kaizen ideas submitted per week<\/li> <li>Average implementation time for improvements<\/li> <li>Weekly savings generated and validated<\/li> <li>Employee participation rate in initiatives<\/li> <li>Cumulative ROI of Kaizen projects over a rolling 12-month period<\/li> <\/ul> <p>Implementing such a tool, powered by clean data (as seen previously), is the final brick in building a true learning factory, capable of adapting and improving continuously, with results visible to all.<\/p>  <p>Your factory is full of potential savings. The next step isn\u2019t to look for more ideas, but to apply a rigorous method to reveal and realize them. Start today by organizing your next Gemba walk with these principles in mind to transform your improvement culture.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most continuous improvement programs fail because they focus on gathering ideas rather than hunting for visible, quick savings. The secret is not the \u201csuggestion box,\u201d but the Gemba walk to identify \u201cdollars on the floor.\u201d Every improvement, however small, must&#8230;<\/p>\n","protected":false},"author":1,"featured_media":653,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[],"class_list":["post-704","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-innovation-digital-transformation"],"_aioseop_title":"","_aioseop_description":"","_links":{"self":[{"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/posts\/704","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/comments?post=704"}],"version-history":[{"count":3,"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/posts\/704\/revisions"}],"predecessor-version":[{"id":717,"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/posts\/704\/revisions\/717"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/media\/653"}],"wp:attachment":[{"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/media?parent=704"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/categories?post=704"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.montrealindustry.com\/en\/wp-json\/wp\/v2\/tags?post=704"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}