{"id":20,"date":"2026-06-04T20:03:15","date_gmt":"2026-06-04T20:03:15","guid":{"rendered":"https:\/\/elcinsight.com\/?page_id=20"},"modified":"2026-08-14T09:36:09","modified_gmt":"2026-08-14T09:36:09","slug":"ogledalo-firme","status":"publish","type":"page","link":"https:\/\/elcinsight.com\/en\/ogledalo-firme\/","title":{"rendered":"Company Mirror"},"content":{"rendered":"<style id=\"elc-og-zaglavlje\">\n.elc-site-header .elc-brand{display:none !important;}\n@media(max-width:820px){.elc-site-header{display:none !important;}}\n.trp-floating-switcher{display:none !important;}\n.elc-og-hero{padding:46px 24px 42px !important;}\n.elc-og-hero h1{font-size:clamp(32px,4vw,52px) !important;}\n.elc-og-hero p{font-size:19px !important;margin-top:14px !important;}\n.elc-og-wrap{margin:40px auto 60px !important;}\n.elc-og-cta{max-width:1180px;margin:0 auto;padding:22px 24px 0;font-family:Arial,Helvetica,sans-serif;}\n.elc-og-cta .kutija{border-left:5px solid #D4182A;background:#f7f7f7;padding:18px 22px;font-size:17px;line-height:1.6;color:#1a1a1a;}\n.elc-og-cta a{color:#D4182A;font-weight:800;text-decoration:none;}\n.elc-og-btn{display:inline-block;background:#D4182A;color:#fff !important;text-decoration:none;font-weight:700;font-size:17px;padding:14px 30px;margin-top:12px;}\n.elc-og-btn:hover{background:#A5111C;}\n@media(max-width:781px){.elc-og-btn{display:block;text-align:center;}}\n<\/style>\n<style>body.page-id-20 .wp-block-post-title,body.page-id-20 .wp-block-group:has(.wp-block-post-title){display:none!important}body.page-id-20 .wp-block-group.banner,body.page-id-20 .page-banner,body.page-id-20 .inner-banner{display:none!important}.elc-ogledalo{font-family:Arial,Helvetica,sans-serif;color:#111;background:#fff}.elc-og-hero{background:radial-gradient(circle at 20% 0%,rgba(237,28,36,.22),transparent 34%),#101010;color:#fff;border-bottom:6px solid #ed1c24;padding:92px 24px 86px;text-align:center}.elc-og-hero h1{margin:0;font-size:clamp(44px,5vw,74px);line-height:1.02;font-weight:900;letter-spacing:0}.elc-og-hero p{max-width:760px;margin:22px auto 0;font-size:22px;line-height:1.45;color:#f1f1f1}.elc-og-wrap{max-width:1180px;margin:72px auto 90px;padding:0 24px;display:grid;grid-template-columns:300px minmax(0,1fr);gap:54px;align-items:start}.elc-og-toc{position:sticky;top:30px;border:1px solid #ddd;background:#fff;padding:26px}.elc-og-toc h3{margin:0 0 18px;color:#ed1c24;font-size:16px;letter-spacing:.08em;font-weight:900;text-transform:uppercase}.elc-og-toc a{display:grid;grid-template-columns:38px 1fr;gap:12px;text-decoration:none;color:#111;font-weight:800;line-height:1.25;padding:14px 0;border-top:1px solid #eee;font-size:15px}.elc-og-toc a span{color:#ed1c24;font-size:15px}.og-section{padding-bottom:58px;border-bottom:1px solid #e5e5e5;margin-bottom:58px}.og-num{color:#ed1c24;font-weight:900;font-size:17px;margin-bottom:18px}.og-section h2{font-size:clamp(34px,4vw,54px);line-height:1.05;margin:0 0 28px;font-weight:900;letter-spacing:0;color:#070707}.og-section p{font-size:21px;line-height:1.72;margin:0 0 22px;color:#111;max-width:860px}@media(max-width:900px){.elc-og-wrap{grid-template-columns:1fr;margin-top:44px}.elc-og-toc{position:relative;top:auto}.elc-og-hero{padding:64px 20px}.og-section p{font-size:19px}}<\/style>\n<div class=\"elc-ogledalo\"><header class=\"elc-og-hero\"><h1>Company Mirror<\/h1><p>What LEAN really looks like in practice. No beautification. No theory that sounds nice but doesn't work in the works.<\/p><\/header><div class=\"elc-og-cta\"><div class=\"kutija\">Ovo je vodi\u010d, ne prodajni tekst. Ako vam se \u017euri do rezultata, isti pristup je spakovan u gotove alate na strani <a href=\"\/en\/digitalni-proizvodi\/\">Digital products<\/a>.<\/div><\/div>\n<div class=\"elc-og-wrap\"><nav class=\"elc-og-toc\"><h3>Contents<\/h3><a href=\"#predgovor\"><span>01<\/span>Preface<\/a><a href=\"#sta-je-zapravo-lean-razbijanje-mita\"><span>02<\/span>What is LEAN: breaking the myth<\/a><a href=\"#kako-je-lean-nastao-istina-koju-mnogi-preskacu\"><span>03<\/span>How LEAN came about: the truth that many people skip<\/a><a href=\"#osnovni-elementi-lean-a-kuca-koja-se-ne-gradi-powerpointom\"><span>04<\/span>The basics of LEAN: a house that isn't built with PowerPoint<\/a><a href=\"#vazni-lean-alati-i-koncepti\"><span>05<\/span>LEAN tools and concepts<\/a><\/nav><main><section class=\"og-section\" id=\"predgovor\"><div class=\"og-num\">01<\/div><h2>Preface<\/h2><p>Due to increasingly difficult business conditions, lack of resources, unpredictable market dynamics and the dwindling number of quality staff available, companies today have little choice: they will either optimize their processes and empower people, or they will suffocate in daily firefighting.<\/p><p>This practical guide was created for this very reason: as a tool to help businesses become resilient, organized, and stable; not through theory, but through the actual application of the LEAN approach in practice.<\/p><p>This guide is not academic literature. He summarizes the years spent in factories, among machines, in conversation with people who know what it means to fight for a piece and for a watch. It was made to be used, not to be read once and forgotten. It does not contain complicated expressions and unnecessary English terms and detailed solutions: but a roadmap to solutions that work in both small and large companies, in our country, here, in real conditions.<\/p><p>Who's it for? This guide is for young and ambitious executives who want to set things right and know how to do it.<\/p><p>For business owners who want a system that is not based on luck. For directors who no longer want to listen to justifications but to see the result.<\/p><p>For those who want to become leaders. and to be honest, it is not for those who know best. Wait for the next audit.<\/p><p>If you have a clear strategy, if you don't mind looking at yourself and the system, and if you want a team that knows what they're doing and why, this guide will help you achieve it. and remember:<\/p><p>&amp; # 8222; our only security is our ability to change.&amp; # 8220;\u2013 John C. Lilly<\/p><\/section>\n<section class=\"og-section\" id=\"sta-je-zapravo-lean-razbijanje-mita\"><div class=\"og-num\">02<\/div><h2>What is LEAN: breaking the myth<\/h2><p>According to McKinsey research, only 30% of companies that try to implement LEAN achieve lasting results. The other 70% give up, make-up processes, or return to the organization's old system.<\/p><p>Why? Because they think LEAN is\"something you can buy, learn in a seminar and finish in three months\". Today, the concept is practiced, where companies send their employees to various seminars and receive certain belts (yellow, green, black belt&#8230;) and then it is considered that the company got a LEAN expert, who will be \"in charge\" of LEAN.<\/p><p>The same situation has been happening for years when the responsible persons for security were determined; when you go through shopfloor and talk to one of the production managers about security-related topics, they will tell you that a Marko is in charge and responsible for these tasks. The situation is changing from the root when world trends are changing, in Europe, and even in our country, where through legal regulations, on the example of security, it is clearly indicated that there is no \"responsible person\" for security, but an advisor or associate for security affairs. This clearly implies that this sda person is obliged to teach other colleagues in the company security and that everyone is responsible for security in his or her scope of work. It's the same with LEAN.<\/p><p>Lean is a management philosophy that focuses on maximizing value for the customer by eliminating loss in the process. It sounds smart and seems useful. But to be honest, how many people who say that actually know what loss means? and how many of them have ever stayed longer than 10 minutes with an operator who assembles 800 pieces a day of a product and thus observed the process. In most cases, the process is analyzed through standard tools, such as bottleneck analysis, VSM, and similar tools learned in seminars, but without a deeper connection to reality in the field.<\/p><p>Based on my many years of experience, we could define one definition of LEAN, but from the prism of practical work and working with people in the field:<\/p><p>LEAN is a brutally honest mirror of the firm: it shows what's wrong, every day, and asks leaders to have the courage to fix it, along with the people, not through them.<\/p><p>Here are a few examples to make a difference:<\/p><p>At LEAN, the CEO doesn't sit in the office all day, he goes to shopfloor once a day: not to control, but to see, ask, and learn. Lead by example during the Tour carries all the prescribed equipment as well as the workers that he visits and adheres to all the rules.<\/p><p>In a LEAN firm, the manager does not make plans in Excel that have nothing to do with reality, but plans according to the rhythm of the production and voice of the operator.<\/p><p>In a LEAN firm, when there is a problem: the first question is: \"what is not supported by the system?\u201d , and not \" who's to blame?\u201d<\/p><p>At LEAN, the executive does not set goals out of his head: he uses data from the field, from production, and aligns it with the real capacities of people and machines.<\/p><p>In a LEAN firm, problems are not hidden for&#8222;after an audit &amp; # 8220; but are marked immediately, because it is a shame to hide and an honor to solve.<\/p><p>At LEAN, a daily meeting lasts a maximum of 10 minutes, standing, with a single board and a clear focus: safety, quality, and what must not stop today.<\/p><p>At LEAN, the best worker is not the one who works the fastest, but the one who sees the problem and says, \u201cthis doesn't make sense: let's change.\u201d<\/p><p>At the LEAN firm, the head of the line does not yell \u201cfaster!\", but asks: \"Why Are We late? What do you need to run smoothly?\u201d<\/p><p>In a LEAN firm, the kaizen proposal is not a dead box \u2013 rather, the idea of the worker is resolved within 5 days and the person who proposed receives feedback.<\/p><p>In a LEAN firm, when new equipment comes in, it is not only the engineering that decides, but the operators make comments because they will work with it every day.<\/p><p>Before we go deeper into the analysis, a few words about me as the person who made an effort to put together this little script by looking at things from a slightly different, practical and above all unusual angle.<\/p><p>My Name Is Nemanja Krsti\u0107 and for more than 17 years I have been working on improvement of production processes, safety at work and implementation of LEAN principles in various industries: from food, textile and electrical, construction to chemical and purpose-oriented production. I hold a master's degree in engineering, and I built my practical knowledge through direct work on shopfloor, with people and machines, in real conditions where every hour and every piece means the difference between profit and loss.<\/p><p>I worked as a LEAN, EHS, QA Manager, HR Manager, Logistics and Planning Manager, Production Director, Facility specialist in domestic and international companies, at the beginning of my career I volunteered in a large multinational company InBev. Later, I moved into consulting through my own company EHS &amp; LEAN Consulting.<\/p><p>My practice is not based on school examples, but on real challenges in factories that have been beset by chaos, paperwork, subjective decisions, and lack of systems. My goal has never been to implement LEAN so that the company has a nice report, but to create an environment where people can work without wasting time, without stress and with clarity at every step. Through years of work, I have developed my own methodologies for connecting teams, building mutual trust and providing lasting results that are not dependent on one person or one system, but on daily learning and stable process management.<\/p><p>This script is not a theoretical guide. This is the result of fieldwork, conversations with workers, my and common failures and UPS and downs, attempts, and ultimately results. I'm writing this to help executives who have the opportunity to really make a difference, but need the right framework to know where to start.<\/p><\/section>\n<section class=\"og-section\" id=\"kako-je-lean-nastao-istina-koju-mnogi-preskacu\"><div class=\"og-num\">03<\/div><h2>How LEAN came about: the truth that many people skip<\/h2><p>Today, many people talk about LEAN as a modern method of management that comes from the West. However, the truth is completely different. LEAN was not born in the offices of wealthy businessmen, it did not originate in the laboratories of American universities or as a result of research by multinational companies. LEAN grew out of poverty, and out of despair; in postwar Japan, where there was neither money, nor resources, nor time for mistakes.<\/p><p>After World War II, Japan was devastated. The industry is collapsing, the materials are gone, and the labor force is exhausted. Toyota, then still a small and local company, could not compete with the big Western giants who produced in large batches and had huge stocks. Therefore, they had to come up with a different mode of production. Not faster, stronger, but smarter.<\/p><p>Thus, they began developing what would later become known as the Toyota Production System (TPS); a system that is based on common sense, respect for people, and everyday problem solving. What's special about Toyota is not just the system, but a culture where everyone has the right to stop the line if they see a mistake, where the leader is placed not because of the title, but because he can listen, see, and ask \u201cwhy\u201d five times if he has to.<\/p><p>LEAN wasn't called LEAN. They didn't call him that. even today in Toyota, the term is hardly used. That name came much later, when Western experts tried to&#8222; pack &amp; # 8220; What they saw in Toyota into some universal method.<\/p><p>The term&#8222; Lean production &amp; # 8220; was first used in 1988. the author of the book &#8222;The Machine That Changed the world&#8220; This book presents Toyota as the best example of efficient manufacturing in the world, and the word lean is chosen to describe a system that uses less everything: less inventory, less space, less defects, less time, but with more value for the customer.<\/p><p>Unfortunately, what happened after that was that many took LEAN as a tool, as a project, as something that can be &#8222;implemented&#8220; through four workshops and 3 tables. and here comes the fall. Because LEAN was never a reporting system; it was a way of thinking and behaving at every moment, at every place.<\/p><p>So, when someone says today, \"let's introduce LEAN,\" my first question is, \" Are you ready to rethink everything you're doing right now \u2013 including your own habits, attitudes, and decisions-are you ready to change as top of the hill-as management?\"&#8220;<\/p><p>If management is not ready, it is better not to introduce it. it's just another PowerPoint file in the recycle bin.<\/p><\/section>\n<section class=\"og-section\" id=\"osnovni-elementi-lean-a-kuca-koja-se-ne-gradi-powerpointom\"><div class=\"og-num\">04<\/div><h2>The basics of LEAN: a house that isn't built with PowerPoint<\/h2><p>LEAN is not a theoretical model of the book. and it's not the \"Toyota house\" from the slide. In the real world, where products are created, LEAN builds from chaos. And the foundation of that house is neither Just-in-time, nor Kanban (for which everyone gets caught first), nor jidoka for quality management; they come later, as an upgrade. The real foundation of LEAN, from my many years of experience, is 5s and safety. These are the elements that management must immediately enable, and in addition, open up space for workers to actively participate in the optimization of the process, which is Kaizen.; I see kaizen (the process of proposing ideas) as the insulation of the foundations of a stable building, which serves to make the foundations \u201cnot crack\u201d in the future.<\/p><p>Anyone who doesn't understand this is free to use belts, certificates, flow diagrams and analysis of bottlenecks.... All this remains a dead letter on paper if the basic three elements (5s, safety and Kaizen) do not exist, and if they are not carried by the sincere empathy of leadership. These three principles are not technical matters, but the basis of the company's culture. When it is the foundation the house can grow.<\/p><p>I always start from a simple truth: it is the operators of machines who bring the money to the companies. They're the heart. Everything else, including us from management, HR, quality control, planning, logistics, and even sales, are just support. Service. and like any service, we can speed up that money flow, unburden it, or just ruin it.<\/p><p>If the worker does not know where his tool is, if there is no room to turn normally, if the wheel is under his foot, the cable hangs over his head, and he has to stick his hands in the machine without protection: there is no LEAN. there is improvisation. And improvisation is the most expensive item in the company, it just doesn't usually measure right away.<\/p><p>Therefore, my LEAN house looks like this kaon a Figure 1.<\/p><p>Figure 1: LEAN house from my perspective<\/p><p>This LEAN House is not a drawing for presentation, but a mirror of one serious organization. Each layer has its own role, and they all work together as a system that is capable of withstanding the pressures of daily production, the unpredictability of the market and the increasingly frequent internal crises in firms.<\/p><p>The foundation of the house consists of three deep-rooted layers. The first is the company's long-term strategy, vision and mission. It is not a letter on paper for a site, as is usually true text in one firm because they consider it \"pro forme\", but a clear direction that gives meaning to all everyday decisions. If a company changes course every six months, that'S where LEAN can't come to life because everything people make is undone by the first change of priorities. The long-standing strategy and key policies are defined by the ownership structure with clearly defined development points. A vision is the end point where a company should reach when it achieves that strategy, and a mission is the path along which to reach a strategic point. The mission is defined by the director with his team, through operational goals, procedures and plans.<\/p><p>At this strategic layer lies 6S, a blend of 5s methodology and Occupational Safety. Without order, Organization and security, there is no stable process. If the worker does not know where his tool is, if the cables cross under his feet, if he does not know whether he is allowed to touch the machine, the system is not under control.<\/p><p>What connects stability and everything above it is Kaizen, everyday, common sense improvement. It's not a big project. Kaizen's question is: \"Does this make sense?\"Kaizen is the insulation between the foundation and the wall. You can't see it, but without it, the system quickly starts to crack from the inside.<\/p><p>The house then rises on three pillars. The first is management and leadership. The two concepts are well understood because they don't relate to each other. You can be a leader without leadership, and then people fear you, but they don't follow you. You can be a leader without a function and then people listen to you because they believe, not because they have to. The real pillar comes when management knows that it is not there to command, but to serve. That's called leadership.<\/p><p>The second pillar is people and teamwork. Without engaged people there is no LEAN culture-without mutual trust, any change is perceived as a threat.  If there's \"them up\" and \"us down\" in the firm, the house is in half.<\/p><p>The third pillar is always LEAN. Only here come visualization (visual management), VSM, A3, takt time, standard work, SMED, JIT, KANBAN and others. They are important, but they are not essential. Without the previous two pillars, the tools become another PowerPoint file in the archive.<\/p><p>All pillars are connected by a layer of KPI, targets, triggers, and DMAIC processes. Without a doubt, everything is subjective. Goals without numbers are just wishes. The KPI must be clear, honest and functional, not to punish, but to know where to help. KPI is the formula used to obtain a single measurement scale. To this scale, we add a point that we define as a target, the so-called target, and precisely define the process that we measure. What I demand in practice, which is very rare to see in companies because everyone deals only with goals, is a lower value point on the KPI scale, the so-called trigger. This triggers the DMAIC research process when the value on a KPI falls to a critical value. DMAIC (Define, Measure, Analyze, Improve, and Control) is a very powerful LEAN tool that enables Team research into nonconformities. It includes Ishikawa, 5 Why, brainstorm, and other approaches.<\/p><p>In the end, the roof is satisfied customers and quality. That's what you can see from the outside. If the customer is satisfied and the quality is stable, it means that all the layers below work.<\/p><p>At the top is a guiding star. It's Business Excellence, Business Excellence. This is what we strive for in every process. Companies can define KPIs to measure business success: efficiency, effectiveness, OEE, and others. For them, the top management defines targets for each year. For example, for process efficiency, the goal may be around 75 percent, but for a firm to achieve business excellence, efficiency must be at least 95 percent, quality 99 percent, and effectiveness at least 90 percent. This means that the total OEE must be at least 85 percent.<\/p><\/section>\n<section class=\"og-section\" id=\"vazni-lean-alati-i-koncepti\"><div class=\"og-num\">05<\/div><h2>LEAN tools and concepts<\/h2><p>LEAN is not a tool. LEAN is a philosophy. But like any good philosophy, no practical tools remain just a PowerPoint story. In my practice, I use concrete basic tools that work, but of course, much more demanding tools can be applied. I'll give you the basics:<\/p><p>5S + Safety = 6S (workspace arrangement to speed up the process and reduce risk)<\/p><p>The 5S is not just a Japanese exotic or \"some methodology for cleanliness\"; it's the first thing a serious firm has to introduce before they even say the word LEAN.<\/p><p>The name 5S comes from five Japanese words that describe the sequence of activities:<\/p><p>Seiri (sorting): removing anything not needed from the workplace. Screws that are never used, tools that are just in case: all this creates confusion and takes up space. On the field, this means: what you don't need to remove. At this stage, we stick worm tags on all the equipment and tools that we do not need and after a period of time they are disposed of in the 5s zone and removed from work positions.<\/p><p>Seiton (systematic deployment): when we have removed everything that we do not need from the workplace,then we analyze what we use (frequency of Use) and then we arrange tools and equipment so that the things we use the most are at hand (close to us) and preferably in the Golden Area (Golden area \u2013 from belt to chest);<\/p><p>Seiso (Cleaning): Cleaning the workspace, not for gloss, but for control and maintenance. When we wash machines, we see leaks, for example. When we clean, we actually check.<\/p><p>Seiketsu (standardization): when we have arranged and cleaned everything to be standardized (we paint what the workplace should look like, lay out the contours behind the equipment that is hung, and make a visual standard for each work position). A visual standard is essentially a poster that shows where what should stand in that working position.<\/p><p>Shitsuke (self-discipline): maintenance and habit. For 5S to live, you have to live it every day. If you ignore it for a day or two, the system breaks down. If you repeat it then it becomes natural. That is why we do cross-checks through CHECK lists so that a constant one job position over a period of time is reviewed by multiple levels of employees<\/p><p>In my practice, I never talk about 5S without adding a sixth s: Safety. Security is not an addition. Safety is the foundation of everything. If a man has to jump over boxes to get to the machine, if the cable hangs over his head, or if the screwdriver gets stuck in the table: it's not messy, it's dangerous. And anything dangerous, one day it becomes expensive.<\/p><p>5S + Safety means that when you complete a 5s inspection, you not only say \"it looks nice\", but also \"it's safe for a man to spend eight hours here\". and there's a difference between a company that plays LEAN and a company that lives LEAN.<\/p><p>In some companies I have seen that 5S exists \"on paper\" \u2013 they have beautiful before and after photos, everything is great one day. And then everything goes back to the way it was before. Why? Because they did not have a leader who would first take to \u201clay down the tool\u201d (start a project and lead by example), and they did not have a culture in which order is maintained because everyone believes it should, not because it is inspected for pro forma or audit.<\/p><p>Therefore, 5S and Safety are not tools. They're a habit. Habits are built every day. If you miss it, No Lean, no production.  There's just a struggle to catch up to what you've made difficult for yourself.<\/p><p>Bottleneck Analysis<\/p><p>Bottleneck analysis is a fundamental step in understanding the capacity of a production system. There is always a point in the process that limits the flow and it is determined not arbitrarily, but by precise measurement. In my practice, I rely on the time study methodology, through which I define standard times for each operation in the process. By comparing these times and analyzing the frequency of the downtime, it is possible to clearly identify where the downtime occurs. The bottleneck does not have to be located only on the line, but can also arise in the stages of preparation, control, logistics or planning. Therefore, it is important that the analysis is comprehensive and carried out periodically. When a bottleneck is identified, it is approached to be removed, which does not always imply new investments. In a large number of cases, minor operational adjustments are sufficient: changes to the work schedule, adjustment of clock time or reallocation of tasks. A properly conducted bottleneck analysis allows the firm to increase overall capacity without additional resource stress and without complicated reorganizations.<\/p><p>It often happens in practice that managers of production, not knowing this analysis, allocate more workers to some process of the production line (a certain point) where there is an absolute surplus and unnecessary and in another place there is a shortage of workers. In conversation with them, before analysis, such a possibility is impossible and they categorically reject it. The goal of these analyses is not to \u201cpush\u201d and get justice, but to prove with an engineering approach that the process is not well-adjusted and that the company has an unnecessary loss.<\/p><p>GEMBA (tours of production plants and controls via check lists)<\/p><p>Gemba walking is a Lean practice in which the manager goes directly to the place where the work is actually done; where value is created (shopfloor) it is not about supervision or control, but about learning through observation and conversation. In my practice, a Gemba walk involves a structured observation of processes with the help of check lists, which are used for cross-control: not only 5S and security, but also all key processes in the work. This checks whether the work is actually being carried out in accordance with standards, whether there are hidden obstacles and where time or quality is wasted.<\/p><p>The walk should have a clear focus and should not take more than a few minutes per location. The most important thing is to ask the right questions: what makes it difficult for you to work, where the process is not clear, what bothers you every day. This is the only way to get to the real problems, but also to the real proposals for promotion. The gemba walk is most effective when it becomes routine and when people realize that the manager does not come to look for mistakes, but to remove obstacles. We find workers who do their jobs differently; regardless, we always first praise what they do well (even if it is only 10%; before that, \"break the ice\" with some positive story), then we ask open questions to clarify the way we work and never leave the place and conversation until we get a promise (through a smile) that the worker and the process will improve.<\/p><p>Heijunka (production planning optimization<\/p><p>Heijunka is a method of balancing production aimed at reducing variation in line load, material flow, and people's engagement. In practice, this means that production is planned so as to avoid working in waves; days with overload and days with falling activity. For example: instead of making ten thousand pieces of one item and not making that item for days, Heijunka implies rhythmic, evenly distributed production of different items in accordance with the real needs of customers.<\/p><p>The biggest challenge with Heijunka in domestic companies is planning; often a plan is made that looks good on paper, but does not follow the actual pace of production, available resources, or process capacities. Because of this, the plan puts pressure on people, makes supplies, or leads to interruptions. In my work I use a combination of Lean tools and realistic shopfloor feedback to bring Heijunka down to the level of operational planning; it not only exists as Excel, but as a living system. The first thing I do is to introduce one of the principles of the WCSC concept (world class supply chain) that production planning and realization of production are separated into separate sectors and that the sales sector cannot directly communicate with the production sector, nor that the production sector can make a plan for itself (which is a kind of conflict of interest). Therefore, the systematization and organizational structure are reformed and the ligostics sector with the function of planning as a buffer zone between sales and production and to balance the demands of each other.<\/p><p>Balancing not only means an even number of pieces per shift, but also includes stability in delivery time, quality and machine load. Once this is achieved, firms manage resources more easily, reduce worker stress, and eliminate the need for unplanned overtime or constant shifting of people from position to position.<\/p><p>Hoshin Kanri (taking business strategy to the lowest layers of the hierarchy<\/p><p>Hoshin Kanri is a method by which a firm's strategy translates into concrete goals and activities at all levels of the organization. The point is to ensure that there is a balance between what the administration plans and what is happening in the operation. In practice, this means that the strategy does not remain a document in the drawer (for example, the ISO policy of a pro forma company), but that each sector knows its part of the way, how it measures progress and what to do if a deviation occurs.<\/p><p>The biggest advantage of Hoshin Kanri is that it introduces two-way communication. The goals do not come down unilaterally. The question is whether they are achievable, whether resources are provided, and what are the possible obstacles. In companies where this does not exist, it often happens that goals are defined, but no one at the plant knows what they are or why they are important.<\/p><p>In my application of this tool, I use a simple format: for each strategic direction there are related goals, clear indicators, task owner and control mechanism. The key to success is keeping the pace of the review and linking KPI results to concrete actions, not just presentations. When people understand where the company is going and see how their role contributes to that direction, then the strategy also makes sense and really lives on in everyday work.<\/p><p>Just in time (production planning principle)<\/p><p>Just in time is the principle of production and delivery based on the real needs of the customer, without surpluses and inventories that unnecessarily take up space, tie money and create additional pressure on the system. The idea is simple: produce only what is needed, in the amount that is needed, at the time it is needed. Often in practice, we have a situation that ignoring the needs of the customer, the production director himself plans what is done and how it suits him, so we have large batches, which age delays, excessive supplies and shortages.that is why it is described above that we work on the principle of WCSC-na and that logistics plans production and material.<\/p><p>In practice, for JIT to function, all parts of the system must be stable. There is no room for improvisation. The Plan must be realistic (based on realized efficiency from production and current realistic capacities), material available. As soon as a part of the chain fails, the entire system suffers. Therefore, JIT cannot be introduced declaratively. Technical precision, organizational discipline and a clear chain of communication between planning, procurement, production and logistics are required.<\/p><p>In firms that are used to&#8222; playing safe &amp; # 8220; making large stocks, the introduction of JIT requires a change of thinking. It's not about risk, it's about relying on facts and accurate planning. In the systems I set up, JIT was always phased in: first through internal logistics and the withdrawal of materials to the line at actual consumption, then through the Kanban system, and only later through the planning of production to order.<\/p><p>Just in time brings the most benefits when combined with standardized work and leveling planning. Then the need for constant emergency deliveries and overloaded storage ceases, and the process becomes transparent, predictable and financially sound. Most companies are immediately \u201ccaught \" for JIT and its implementation, but this is something that is introduced when the entire management is stalked, there are precise scrum meetings at exactly a certain time (it is very important to solve the team's problems immediately), if the logistics separate from production and independently operate and plan, etc..<\/p><p>Takt Time (remaining time until delivery \/ number of ordered pieces)<\/p><p>Tact Time is the basic rhythm of production that defines how often a product needs to be finished in order to meet the customer's demand. It is calculated as the ratio of available production time and quantity demanded, and is the basis for balancing work, planning capacity and organization of the line. This means that sales cannot agree delivery times if the clock time is shorter than the cycle time, i.e. the actual time required to make one piece of the product. If this does not apply, then we often have situations where there is always a customer who is late, that production plans change during the day, that loading plans change, etc.and this creates a huge decline in employee morale, confusion and a drop in productivity.<\/p><p>If the tact is not known or ignored, production is planned blindly, by feel. This most often leads to overcrowded operations, surpluses, delays, and constant haste. When clock time is taken as a basis, it is clear how many operators are needed, where the deadlock occurs and what the work sequence should look like.<\/p><p>In companies that have a wide range of products and frequent changes, tact is used flexibly, while estimating the load by product groups or lines. It is important that tact is not seen as pure mathematics, but as a tool for harmonizing requirements and real possibilities. Tact does not force the system to work faster, but to work smarter and give the customer clear and accurate feedback when exactly on the day they can store their goods.<\/p><p>Kaizen (process of proposing ideas<\/p><p>Kaizen represents a way of thinking that has proven to me over the years as the most stable framework for improving work. It does not make sudden changes, does not rely on large investments and does not require complicated projects. Kaizen involves asking a simple question every day: whether something in our process can be done easier, simpler, safer, or with fewer errors.<\/p><p>I am implementing it by setting up a simple and transparent system in which anyone can propose improvements. We use a form in which a description of the problem and a proposal of a solution are entered, and the whole process is followed by a team and approved and rewarded. Each proposal has an owner, a defined deadline, and mandatory feedback to whoever made the proposal. It has been shown to me that people enter the system honestly and willingly only if they see that someone is listening to them and that ideas are not ignored. Therefore, it is a rule that no proposal must go unanswered, whether applied immediately, postponed until later, or rejected with reasoning.<\/p><p>Kaizen is not only used in production. Practice has shown me that useful ideas often come from the support sector (service), from people who are seemingly not directly in the process, but feel its consequences on a daily basis. Kaizen is successful only if its implementation does not come down to the initiative of one man. When respect is shown for each proposal, a culture is built in which people really want to contribute.<\/p><p>Kanban (based on the principle of supermarket)<\/p><p>Kanban is a materials and information management tool that in my practice has proven to be most effective in situations where it is important that the system itself signals that something is needed, without calls, requests or chasing. His greatest strength is in simplicity. In practice, a Kanban card, box, color, or physical signal are used that clearly indicate that action needs to be supplemented, prepared, or taken. For example, if we have separated production into two segments \u2013 basic production and finishing \u2013 instead of finishing constantly communicating with basic production when and what it needs, we do a preliminary analysis and define that four pallets of semi-finished products are needed for daily production. The functional location of the handover is determined, pallet points are marked, and then the head of the basic production with a glance at that Inter-warehouse knows what needs to be produced. The goal is that all pallet spaces are always filled, and that the finishing takes what it needs at a given moment.<\/p><p>When set up correctly, the Kanban eliminates unnecessary ordering, overcrowded supplies, and empty walks. Introduction starts where most of the time is lost due to waiting for material, tools or semi-finished products. We set a rule: once the signal is out of the zone, the logistics respond without further questions. The system is adjusted using a defined minimum and maximum quantity, which has been previously tested on real flow.<\/p><p>In companies that have a chaotic material flow, Kanban often seems like too much of a change. That's why I'm phasing it in. First into internal logistics, especially for packaging, consumables and tools. Later, when the team sees how it works, Kanban becomes part of the everyday system and no one wants to go back to the way it was. The key to success is not to make the cards beautiful, but to make people respect them and to make the system react on time.<\/p><p>KPI (determining the formula for measuring the value for each process)<\/p><p>KPIs, or key performance indicators, are a measurement framework that allows workflows to be monitored, analyzed and improved based on facts. They are not a tool for controlling people, but an instrument for understanding the system. A properly set KPI indicates where the system is functioning stably and where the deviation occurs. In our approach, we use KPIs as a basis for operational and strategic management, and their monitoring is an integral part of the Lean table and daily meetings.<\/p><p>In addition to the target value, which is most often defined in all companies, we introduce mandatory determination of trigger value (lower limit below which the analysis of causes is initiated). We do this through a DMAIC approach, in which the process is decomposed, the cause is sought, and measures are proposed. Trigger is not a penalty, but a signal that we jointly agreed to help us react in a timely manner.<\/p><p>Each KPI must be clear, measurable and functional. We link it to specific tasks and responsibilities, so that teams have clear information on which to make decisions. If the result is below the goal, we are looking not for the culprit, but for the cause. If it is above expectations, it is a signal that we have the opportunity to standardize what works well.<\/p><p>OEE (complete efficiency of the production process)<\/p><p>OEE is a key indicator by which we measure the actual utilization of equipment, and is the product of three components: availability (effectiveness), performance (efficiency) and quality. It shows not only how much the machine worked, but how much of the planned time it really turned into a good product. Through OEE we get a picture of where the system is losing capacity: whether due to downtime, slow operation or bad pieces. It is important to understand the difference between effectiveness and efficiency. The expected production time is 430 minutes, we have determined by time Study methodology that with all the microstores and the typical nature of our process, we need 100 seconds for one piece (that is in ideal conditions and at 100% of the norm), the director has determined the target for this year at 75% efficiency and that is 133.3 seconds about one piece. The worker works during the day and exceeds the target of 75% STP is excellent, but only works for 350 minutes (for example, prolonged breaks, late start of production, inefficient keeping of machines, etc..). That's why we use OEE which gives us the bigger picture, not just efficiency.<\/p><p>In practice, we use OEE as a basis for daily assessment of process efficiency. Each component is viewed privately. If the availability is low, we analyze why the machine is standing. If performance is below expectations, we measure cycle time and compare it with clock time. If the quality is below the norm, we proceed to the investigation of defects. In this way, we do not draw conclusions based on the total number, but understand which part of the system requires intervention.<\/p><p>We use OEE not only for measurement, but as a tool for dialogue between production, maintenance, planning and quality. When all sectors look at the same metric, it's easier to agree on priorities. This is why OEE is displayed on the Lean dashboard, with daily and monthly results, with clear trigger values that drive analysis and corrective actions.<\/p><p>In companies that strive for Business Excellence, the target value for OEE is at least 85%. Below this may mean that the system is still in the stabilization stage or that there are structural constraints in the processes. Regardless of the current value, it is crucial for the team to know how the OEE is calculated, what it represents, and how to react when one of its elements falls below the expected level.<\/p><p>PDCA cycle (defining agreed actions<\/p><p>The PDCA cycle (Plan\u2013Do-Check-Act) is the basic theoretical framework for change management and problem solving in the Lean system. Although the method is simple and logical, in practice it has proved to me that it is rarely applied consistently. Most often, a plan is made, something is implemented, but the verification and Correction are skipped or remain in the mail correspondence. Therefore, instead of the classic PDCA model, in practice, we rely on a simpler and more transparent tool \u2013 action log organized according to the Kanban principle.<\/p><p>Each sector, each project has its own action plan, which is in the form of a coded and standardized document in Excel, and it is good that top management, auditors and everyone who requests can easily and quickly be convinced of the business of one sector and a couple of years back. Actions are defined by the team, the owner of the action determines the deadline by which he will do the action, and his supervisor eventually corrects that deadline.<\/p><p>Poka Yoke (bug elimination tool<\/p><p>Poka Yoke is an approach that aims to make an error physically disabled or immediately spotted before reaching the next stage of the process. In translation, it is a form of protection against human error, not through punishment, but through a smart solution. In firms that do not have stable processes, most problems arise precisely from repeated errors that the system has missed. Poka Yoke is a way to cut it.<\/p><p>If, for example, we look at the textile industry and the problem that some workers skip to sew the label on the sweater that they put on the counter for the next production process, then we introduce that the sweater does not leave the nap ult, but when they finish their operations in which the sewing of the label is the last, they must hang the same sweater on the label on the moving trolley for the landing stage: there is no label \u2013 I can't hang it<\/p><p>In some companies where we have introduced this practice, the most important shift has occurred in the understanding that a mistake must not be repeated if it has already happened once. The Poka Yoke system forces us to modify the process so that the error can either not occur, or stop immediately. This builds trust in the system and contributes significantly to quality.<\/p><p>Root Cause Analysis (5 Why)<\/p><p>Root cause analysis, most commonly known as the \"5 why\" method, is used when we want to get to the true source of the problem rather than extinguish the consequences. By asking a series of \"why did it happen\" questions, we go deeper into the process each time until we get to the point that is the cause, not just the symptom. In most cases, the problem we see is only the result of something deeper that the system does not solve. If we do not understand how this works, we can recall a simple example with children: when a child asks \"Why does a bird fly\" , and we answer \"because it has wings\", a new \"and why does it Have Wings\" follows&amp; # 8230; and so on until we get to the point. This process can also be seen as a battle with weeds. If we just mow it with a trimmer, it'll grow back, probably even stronger. But if we pull it out of the root, and before it releases the seed, we solved the problem at the right time.<\/p><p>In our application of this tool, we approach with a basic rule: one seeks not the culprit, but the cause. We do the analysis within the team that is closest to the process, with the involvement of operators, managers and support (if the problem is located in only one sector we use the basic 5 why pattern, and if the problem permeates several sectors I use DMAIC). We do not use pre-prepared forms that no one understands, but concrete questions, on a concrete situation, with a clear record and conclusion. In some cases, five questions are not answered, and sometimes the cause is already in the third. It is important that there is honesty and willingness to look at one's own failure in the organization, and not to shift the problem to someone else.<\/p><p>SMED (optimization of product change time-changeover)<\/p><p>SMED (Single-Minute Exchange of Die) is a method used to reduce the time it takes to change a tool, format, or machine position, with the goal of completing the entire replacement within less than 10 minutes. This does not mean that it must last exactly one minute, but that it does not exceed one digit; thus a maximum of nine minutes and 59 seconds.<\/p><p>In practice, SMED begins by observing the actual flow of replacement and separating the activities: what can be done while the machine is still running, and what must only be done when it stops. The greatest losses occur due to searching for tools, waiting for documentation, or poor preparation. When everything can be done in advance, the change itself becomes faster and simpler.<\/p><p>The method is especially useful in companies that often change articles or batches. In addition to saving time, SMED brings stability, less stress and more control over planning. When the system is well set up, it is possible to work shorter batches without making stock, and the machine is used more efficiently.<\/p><p>This process is accelerated by sorting the formatted parts as part of the 5s project.<\/p><p>Standardized work (multifunctional work procedures and instructions)<\/p><p>Standardized work is the agreed-upon best currently known way to perform a particular job. It serves not to limit workers, but to provide stability, clear division of steps, and measurability of processes. When everyone is doing the same job in different ways, it is difficult to find out where the mistake is made, and even more difficult how to improve something.<\/p><p>In practice, standardization begins by defining the key steps in the operation, the order of operation, the tools required, and the duration time. We document all of this through simple visual standards that are clearly highlighted in the workplace. The goal is not to write the instructions for the inspection, but to make a clear agreement to the worker and the team: how it is done, why exactly, and what is the sign that something is deviating.<\/p><p>When introducing standardized work, we always include operators because they are the ones who know best where the deviations are and where they need to be facilitated. Then each function gives its own inputs depending on the need, and so for the work procedures in production goes the following sequence:<\/p><p>suggestions and vegetable information of the operators on the machines are our<\/p><p>technology (engineering) gives a description of the process steps<\/p><p>The LEAN sector or technology provides standard times for operations<\/p><p>quality requirements are provided by the quality sector<\/p><p>safety and security requirements are provided by the HS sector<\/p><p>Lotto (Lock out Tag Out) and machine maintenance requirements are defined by the technical service<\/p><p>And logistics around production and material planning<\/p><p>Once the standard is set, it does not remain fixed. It changes whenever someone offers a better solution that we test and confirm. In this way, the standard is not an obstacle to improvement, but the basis on which Kaizen builds.<\/p><p>TPM (maintenance of machinery and equipment)<\/p><p>Total productive maintenance (TPM) is an approach in which everyone in an organization participates in maintaining the stability of equipment. Unlike the classic model where the operator works until there is a failure and then calls the master, TPM involves the operator in daily activities that prevent the failure. These are not complex repairs, but simple actions: cleaning, visual control, basic checks. In this way, maintenance becomes part of daily work, not an emergency reaction. The technical team no longer deals with small interventions, but analyzes and improves the system.<\/p><p>In practice, we are introducing the TPM:<\/p><p>we choose critical machines.,<\/p><p>we define the day-to-day checkpoints,<\/p><p>we use simple check-lists and<\/p><p>we're going through the Lean table.<\/p><p>TPM does not replace conventional maintenance, but gives it an advantage because it allows earlier detection of problems, reduces the number of emergency interventions and extends the service life of the equipment. Most importantly: the worker no longer waits for something to break, but knows how to prepare the machine every day for stable operation.<\/p><p>VSM (process flow mapping<\/p><p>VSM, Value Stream Mapping, is a tool that we use to visually show the entire flow of a product, from order to delivery. By mapping each step, including supplies, waits, transfers, and transportation, we get a clear picture of where time is wasted, where material is piled up, and where interruptions occur. The goal is not to make the draft look neat, but to reveal inefficiencies that are not visible in everyday work.<\/p><p>In practice, we start by going through the actual process with the team, directly in the field, step by step, and first through the Time Study analysis, we measure each operation and then enter the time between operations; we put it all on that dotted line (timeline). We do not rely on theoretical flows, but draw what really exists: how many pieces stand between operations, how long the wait lasts, whether there is a parallel flow, how quality control is performed. On this basis, we separate activities that create value from those that only occupy space and time (then there is elimination).<\/p><p>When the map is finished, it is used to make concrete decisions: where we can merge the steps, where to reduce the stock, where to set the signal, where to introduce a standard. VSM does not work to be hung on the wall. It works to trigger change. When we do VSM we have Cycle time (the time it takes to do one piece and by comparing it with Takt time we can give customers feedback when exactly to expect goods, and we can plan material and make the basis for JIT).<\/p><p>Visual factory (Visual Management<\/p><p>The visual factory implies that all important information is available where the work is done, in real time and without the need for additional explanations. Instead of asking employees what to do, where they are, or what is currently happening, the system shows them through colors, labels, lines, boards, signal cards, or light indicators.<\/p><p>In practice, this means that the layout of the workplace is clearly marked, that the tools and materials are in place, that the status of the order is visible without opening the computer, and that any change in the process is immediately recognizable. We use, for example, a Lean board with sections for safety, quality, manufacturing and Kaizen activities, and visual contours for tools, material flow signs, marked passages and signaling for downtime.<\/p><p>The goal of visual management is not aesthetics, but efficiency. Good visual organization reduces decision time, reduces verbal communication, and prevents mistakes. Once established, it becomes the basis for Standardization and transparency in every sector. The basis of VM is 5S. best practices are to install large monitors on the worklines that display KPIs (dashboards) and all important and relevant information on shopfloor.<\/p><p>LEAN tabla<\/p><p>Lean table is something that is the product of my many years of work and understanding the need for important information in one place and a unique way of communication. It is the focal point of shopfloor where key information on Team Work, Production, Quality, Safety and improvements are displayed. Its purpose is not to\" look good\", but to let the team know at all times what is important, what is happening and where to react. The board must be up-to-date, accessible to everyone, and organized to provide a clear overview without the need for additional interpretation.<\/p><p>In practice, we divide the Lean board by functions: security (e.g. incidents, protective equipment), quality (defects, complaints, samples), production (plan, implementation, downtime), and improvements (Kaizen suggestions, action log). In the middle there is often an action section \u2013 where through the Kanban approach, the status of each open activity is monitored: planned, ongoing, completed. This is done by using PDCA logic without any additional paperwork.<\/p><p>Meetings in front of the board are short (scrum principle), with a clear order and guided by questions rather than drawing up reports. When the board is used consistently, it becomes a decision-making tool, not just an information board. The value of the Lean table is not in the plasticized columns, but in that it triggers conversation, shared responsibility, and a quick reaction when something deviates.<\/p><p>Andon (stopping the line due to nonconformity)<\/p><p>Andon is a tool that allows the operator to stop a line or signal a problem as soon as they spot it, in order to prevent error, failure or loss of quality. The bottom line is that the problem does not go further through the process, but to be solved immediately, while it is still small. This is the tool that elevated Toyota the most, just because the then CEO trusted a \u201ccrazy\u201d worker (the creator of the LEAN concept \u2013 to whom colleagues laughed) to put their ideas into action. At first, there were more delays than before, but the production lines were advancing more and more!<\/p><p>In practice, this is difficult to implement because many production managers try to keep everything under control, do not allow the line to stop without their consent and keep the decisions to themselves, are micromanagers. Andon demands confidence: that the operator has the right to react, and that the team leader responds without condemnation. When there is fear or micromanagement, the system is formally introduced but not used. In firms that have truly embraced it, Andon becomes a fundamental reflex in preventing larger problems.<\/p><p>This is only part of the LEAN tools we use in practice; there is a wider range, but I think that this is provided for just ordered systems and that it is absolutely enough to create a five-year strategy and meaningful growth enough to implement these tools alone.<\/p><p>How to do LEAN analysis-looking through the eyes of the worker<\/p><p>LEAN analysis never starts from the office. We don't look at reports first, we don't open spreadsheets, and we don't listen to executives ' statements. We start by standing at the entrance of production and trying to look at everything with the eyes of the workers. It's like we're going into the company for the first time and we have to do a task, and no one has explained anything to us.<\/p><p>We look at where the worker enters (what is the entrance, whether it is safe, whether it is necessary to hold it, whether it is adequately marked with vertical and horizontal signaling), where he changes, whether he knows where he is going, how long it takes him to get to the workplace. Are the tools ready yet, or does he have to look for them? Does he know where his documents are, how often he has to ask someone something? We watch him move: whether he bypasses things that bother him, whether he bends, turns, carries something in his hands that can be driven. We observe how much \"unconscious effort\" there is: what he no longer sees because he is used to it, but we notice because we look fresh.<\/p><p>On the example we used: a new worker comes into the production space and tries to start work. It does not have a clear arrangement of tools, it has to ask a colleague where the next part stands, it is guided by the logic \"we have been doing this for years\". The table is not set in height, the cable hangs over his head, and for each step he has to bend or stretch a little. At that point, we already have the first ten potential losses. and that without the product even starting to fold.<\/p><p>Practically, we use a pre-prepared form that does not look like an audit list, but like a map for observation: what the worker is looking for with a glance, how clear he is what next, whether everything is in place, whether he feels safe. We record observations without condemnation and without comment: just facts. When we come back later, together with the team, we go through each point and ask the question: Why is it like this and what we could change to make it not like this.<\/p><p>This approach does not require special technology, only open eyes, empathy, and a desire to see things as they are seen by the one who really does the job. When we start with the analysis, not the numbers, then the solutions we propose make sense and a chance to survive.<\/p><p>If we have executives who insist on the \u201cbe as I say\u201d approach, without observing the process and listening to the people who do the work on a daily basis, then we do not introduce the system but impose authority. In practice, it happens that problems only move, but they are not solved. Mistakes are hidden, ideas do not come to the fore, and workers begin to retreat to a minimum of engagement, because they feel that what they say does not change anything. This directly affects the quality, safety and speed of operation. In the end, the line works, but far below its potential (which we encounter quite a lot in practice) \u2013 and the losses build up over time.<\/p><p>Lean analysis is not a challenge to one's ego, but an opportunity to see what one can never understand from the office. Being a manager doesn't mean you know more: it means you're entrusted with a greater responsibility to see things more broadly. When an executive is the first to stand up, ask, observe, write down, and ask for the opinion of workers, then a culture is created in which people want to cooperate. When, by contrast, everything comes down to orders (\"do as I say\" and\u201d I'm in charge here\"), tables, and criticism, the system enters a state of resistance; this is a disastrous situation for the company, because the main gear brakes and snaps, and very often, almost always, it is brake precisely by those who have been given the confidence by the ownership structure and the director (sometimes including him) to \u201clubricate\u201d that gear and adjust it properly.<\/p><p>The most successful teams are not those in which everyone is silent while the boss is talking, but those in which people express themselves freely because they know that someone is really listening to them. And Lean analysis, if it is honestly conducted, shows exactly that: where the system brakes people, not where people Brake the system.<\/p><p>LEAN vs ISO standards-two worlds, two logics<\/p><p>One of the most common misconceptions in companies is the belief that if there is an ISO standard, then all processes are already sufficiently regulated and there is no need for Lean. In practice, however, it falls into the water very quickly. ISO is an excellent framework for establishing a management system, but it is focused on proving compliance rather than efficiency. His goal is to have documentation, to have a procedure, and to have a record. ISO does not ask how much time is lost, whether the worker understands the process, or whether there is unnecessary movement and waiting in production. This is in the best line when ISO is fully alive and implemented, and you can now see what is the situation in most companies where ISO standard was introduced \u201cpro forme\u201d, there is \u201csome employee who is in charge of ISO\u201d and it all comes down to a campaign to collect documentation before the upcoming certification\ud83d\ude0a.<\/p><p>LEAN, on the other hand, starts with the question: Where is the time, money, energy and motivation wasted? Where is the job more difficult than it should be? Where does the system slow down a man instead of supporting him? Lean does not care if there is a document: he cares if what a worker does every day makes sense, rhythm and support.<\/p><p>That is why it is quite possible, and very often happens, that a company has ISO 9001, ISO 14001, ISO 45001, and that it still has chaos in the process, downtime, dissatisfied people, high costs and overworked executives. ISO does not solve these problems because it is not intended to do so. It seeks records, procedures and controls, but does not go into the depth of the daily workflow. Lean does just that: it goes to the place where value is created, observes the flow, engages people, and removes the superfluous.<\/p><p>In our work we do not contradict ISO and Lean. On the contrary: we use the best of both worlds to show customers and customers that our system works efficiently and that they have nothing to worry about. ISO gives structure, Lean gives life. When they come together, we get a system that doesn't exist just for the certificates, but a system that works because people know what they're doing, why they're doing it, and how to do it better every day.<\/p><p>Who can't run LEAN \u2013 and why every company can't do it<\/p><p>LEAN In theory seems simple. The tools are familiar, the processes can be mapped, the visual system can be introduced relatively quickly. But it's just a form. The bottom line is people, and that's where most companies fall. Not because of the tool, but because it is being run by those who see the organization as their own territory, and not as a living system that must grow and develop with people, not without them. It often happens, what many ask \u201cin the hallways\u201d of the company why this person is engaged if it seems to the majority that it is not a good solution. Companies do this because they do not choose executives by their ability to develop the system, but by their ability to act decisively. In a culture where authority is identified with volume and control with pressure, people who shout, order and \"order\" are easily perceived as capable managers. They are often visible, always involved, reactive, and the first to \"take action\", and leave the impression of action at first sight.<\/p><p>But there lies the trap, because such people do not run the system, they compensate it. Everything that is not solved through structure, they try to solve through themselves. and as long as they are present and have everything under their hands, the system somehow works. But when they don't, chaos ensues. and even worse, they know it, and that is why they are increasingly centralizing control.<\/p><p>On the other hand, quieter, more poised, system-oriented people, who would probably better run the firm in the long run, often lack \"stage power\". They don't make noise. They ask, they listen, they introduce things through people. and that is why many misjudge them as \"weak\". In a culture where a quick result, a clear order, and someone who takes responsibility are demanded, such people are often ignored or bypassed, because they act as if they are \"not leaders\".<\/p><p>The bottom line is that companies still reward control more than building a system. And Lean is exposing that model, because it shows that the real strength of the firm is not in the energy of the individual, but in the stability of a system that does not depend on the individual.<\/p><p>It is also a misconception that Lean can be led by anyone who is \"flexible enough\" and \"loves people\". In practice, the other extreme also happens: that the person who runs Lean has no authority, cannot set boundaries, avoids conflict, and constantly retreats in the face of resistance. Then Lean becomes a theoretical story, it is filled with tasks, meetings are held, but essentially nothing changes. People quickly recognize that there is no decision behind words and the system begins to break down from within.<\/p><p>Therefore, Lean cannot be led by someone who is afraid to ask a question, to ask for change, to resent. But also, it cannot be led by someone who commands without understanding the process and connecting with people. We need a balance. It takes a person with the character to withstand resistance and humility to know that the system is not there for them, but for the team and the customer. Only then can Lean come to life: not as a project, but as a way of working.<\/p><p>The person who runs Lean must know that he is not at the center, but on the side, in the service of the process. It can't be run by someone who doesn't go down, who doesn't know how to listen to the operator, and who believes that problems are solved from the command office. Even more difficult, it cannot be led by someone who keeps everything to himself, who does not delegate, who does micromanagement, and who thinks Lean means \"I'm the one who knows it right\".<\/p><p>Micromanagement is the biggest enemy of Lean. it suppresses initiative, turns executives into passive executors, and sends a message that nothing changes without permission. In such a system, people do not propose because they know they will be ignored, and Kaizen becomes a box that collects dust. Instead of the Lean system developing people, the opposite happens-the system depends on one man who \"pulls\" everything. And that never lasts long.<\/p><p>That's why every company fails. Not because there is no means, tools or support, but because there is no person who knows how to let the system breathe, and how to guide through others rather than through them.<\/p><p>That's why it's important for the Lean person to know how to build a team and how to make decisions through collaboration. In my practice, we use an approach based on the Scrum model, inspired by the rugby team (American football). Unlike traditional sport where a player gets the ball, so everyone waits for him to make a move, in rugby the whole team pushes together, at the same time, with the same force, in the same direction and these agreed actions last very short and effectively. There is no waiting for a command, no looking at who is the leader: everyone knows their role and moves together, because they know that the goal is achieved only if no one stops.<\/p><p>We convey that in the way we run the team and the meetings: everyone is participating, everyone knows where the obstacle is, and everyone is part of the solution. The Scrum team does not function as a chain of command, but rather as a dynamic unit that self-organizes, adapts, and makes micro-decisions every day without the need for \"top-down\"approval. That's why this model not only accelerates work, but strengthens responsibility and mutual trust, which are the foundations of any Lean system that really works.<\/p><p>Lean is not a system, Lean is a mirror.<\/p><p>Lean is not a project. It is not a table, a tool, or an audit report. Lean is a mirror, and it's the most honest thing a company can set itself. And each mirror can show two images: what we are proud of, and what we hide.<\/p><p>In companies that are not ready to look into that mirror, Lean remains a plasticized panel on the wall. Executives deal with numbers they don't understand, meetings become reading problems without the courage to step into them, and workers learn to keep quiet and do their own thing. The system still works, but it squeaks, loses, consumes people, annoys partners, and ultimately costs money. Not on paper, but in profit. In time. In the health of the team.<\/p><p>But in companies that dare to look at things honestly, Lean changes everything. Not overnight, not as an advertisement, but from the ground up. It changes the rhythm. It changes the logic. the most important thing is to change the relationship between people. In a company like this, people don't scream, they listen. They don't solve everything on their own, they make others think. and they're not looking for reports to \"have cover\" but to know where to help.<\/p><p>Many are looking for a\u201d solution \" like in modern medicine: quickly, to relieve the symptom. Lean doesn't do that. Lean does not cure symptoms. Lean digs to the cause. And that takes patience, discipline and character. That's why it can't be run by anyone. That's why it doesn't work everywhere. But where it succeeds: the company not only survives, it becomes an example to others.<\/p><p>Finally: if you are a CEO, owner, or someone entrusted with a company, the process to run or the people: Lean is not an expense, but an investment in common sense. A system that does not depend on one person. In a culture where work makes sense. and to firms that no longer work \"under pressure\", but with a goal.<\/p><p>If you're willing to rethink everything, including yourself, Lean can be the healthiest thing you've ever introduced.<\/p>\n<div class=\"elc-og-cta\"><div class=\"kutija\"><strong>\u0160ta sad?<\/strong> Ako \u017eelite da vidite gde va\u0161a firma stvarno stoji, po\u010dnite od Excel procene sistema sa 45 pitanja. Ako \u017eelite da o tome porazgovaramo, prvi razgovor je besplatan, telefonom ili onlajn.<br><a class=\"elc-og-btn\" href=\"\/en\/digitalni-proizvodi\/\">Pogledajte gotova re\u0161enja<\/a><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>Ogledalo firme Kako zaista izgleda LEAN u praksi. Bez ulep\u0161avanja. Bez teorije koja lepo zvu\u010di, a ne radi u pogonu. Ovo je vodi\u010d, ne prodajni tekst. Ako vam se \u017euri do rezultata, isti pristup je spakovan u gotove alate na strani Digitalni proizvodi. Sadr\u017eaj 01PREDGOVOR02\u0160ta je zapravo LEAN: razbijanje mita03Kako je LEAN nastao: istina koju [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-20","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/pages\/20","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/comments?post=20"}],"version-history":[{"count":6,"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/pages\/20\/revisions"}],"predecessor-version":[{"id":485,"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/pages\/20\/revisions\/485"}],"wp:attachment":[{"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/media?parent=20"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}