{"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-09-17T17:17:53","modified_gmt":"2026-09-17T17:17:53","slug":"ogledalo-firme","status":"publish","type":"page","link":"https:\/\/elcinsight.com\/en\/ogledalo-firme\/","title":{"rendered":"Company Mirror"},"content":{"rendered":"\n<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.elc-vrh{display:flex;justify-content:space-between;align-items:center;gap:14px;margin:0 0 20px;padding:0 0 12px;border-bottom:1px solid #e8e8e8;}.elc-nazad{font-size:15px;font-weight:700;color:#111;text-decoration:none;}.elc-nazad:hover{color:#D4182A;}.elc-jezik{display:inline-flex;border:1px solid #d8d8d8;overflow:hidden;flex:0 0 auto;}.elc-jezik a,.elc-jezik b{font-size:13px;font-weight:800;letter-spacing:.06em;padding:7px 13px;text-decoration:none;line-height:1;}.elc-jezik a{color:#555;background:#fff;}.elc-jezik a:hover{color:#fff;background:#A5111C;}.elc-jezik b{color:#fff;background:#D4182A;}<\/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\"><div class=\"elc-vrh\"><a class=\"elc-nazad\" href=\"\/\"><span class=\"elc-sr-t\">\u2190 Po\u010detna<\/span><span class=\"elc-en-t\" data-no-translation>\u2190 Home<\/span><\/a><span class=\"elc-jezik elc-sr-t\"><b>SR<\/b><a href=\"\/en\/ogledalo-firme\/\" data-no-translation>EN<\/a><\/span><span class=\"elc-jezik elc-en-t\"><a href=\"\/ogledalo-firme\/\" data-no-translation>SR<\/a><b>EN<\/b><\/span><\/div><style>html[lang^=\"en\"] .elc-og-hero:not(.og-en-x),html[lang^=\"en\"] .elc-og-wrap:not(.og-en-x){display:none !important}.og-en{max-width:860px;margin:0 auto;padding:10px 0 50px;font-family:Arial,Helvetica,sans-serif;color:#111}.og-en h1{font-size:40px;line-height:1.15;margin:12px 0 18px}.og-en p,.og-en li{font-size:18px;line-height:1.65}.og-en ul{margin:0 0 22px;padding-left:22px}.og-en li{margin-bottom:6px}.elc-og-hero{background:none !important;color:#111 !important;border-bottom:0 !important;padding:22px 0 4px !important;text-align:left !important;max-width:1180px;margin:0 auto}.elc-og-hero h1{color:#111 !important;font-size:clamp(32px,3.4vw,46px) !important}.elc-og-hero p{color:#333 !important;margin-left:0 !important;font-size:19px !important}@media(max-width:820px){.elc-ogledalo{max-width:100% !important;margin-left:0 !important;margin-right:0 !important}.elc-og-wrap{padding-left:0 !important;padding-right:0 !important}.elc-og-wrap>*{min-width:0 !important}}@media(max-width:560px){.og-en h1{font-size:30px}.og-en p,.og-en li{font-size:17px}}<\/style><header class=\"elc-og-hero\"><h1>Ogledalo firme<\/h1><p>Kako zaista izgleda LEAN u praksi. Bez ulep\u0161avanja. Bez teorije koja lepo zvu\u010di, a ne radi u pogonu.<\/p><\/header><header class=\"elc-og-hero og-en-x elc-en-t\" data-no-translation><h1>Company Mirror<\/h1><p>What LEAN really looks like in practice. No sugarcoating. No theory that sounds good but does not work on the shop floor.<\/p><\/header><div class=\"elc-og-cta\"><div class=\"kutija\"><span class=\"elc-sr-t\">Ovo je vodi\u010d, ne prodajni tekst. Ako vam se \u017euri do rezultata, isti pristup je spakovan u gotove alate na strani <a href=\"\/digitalni-proizvodi\/\">Digitalni proizvodi<\/a>.<\/span><span class=\"elc-en-t\" data-no-translation>This is a guide, not a sales text. If you are in a hurry for results, the same approach is packed into ready-made tools on the <a href=\"\/en\/digitalni-proizvodi\/\">Digital products<\/a> page.<\/span><\/div><\/div>\n<div class=\"elc-og-wrap\"><nav class=\"elc-og-toc\"><h3>Sadr\u017eaj<\/h3><a href=\"#predgovor\"><span>01<\/span>PREDGOVOR<\/a><a href=\"#sta-je-zapravo-lean-razbijanje-mita\"><span>02<\/span>\u0160ta je zapravo LEAN: razbijanje mita<\/a><a href=\"#kako-je-lean-nastao-istina-koju-mnogi-preskacu\"><span>03<\/span>Kako je LEAN nastao: istina koju mnogi preska\u010du<\/a><a href=\"#osnovni-elementi-lean-a-kuca-koja-se-ne-gradi-powerpointom\"><span>04<\/span>Osnovni elementi LEAN-a: ku\u0107a koja se ne gradi PowerPointom<\/a><a href=\"#vazni-lean-alati-i-koncepti\"><span>05<\/span>Va\u017eni LEAN alati i koncepti<\/a><\/nav><main><section class=\"og-section\" id=\"predgovor\"><div class=\"og-num\">01<\/div><h2>PREDGOVOR<\/h2><p>Usled sve te\u017eih uslova poslovanja, nedostatka resursa, nepredvidive tr\u017ei\u0161ne dinamike i sve manjeg broja dostupnih kvalitetnih kadrova, firme danas nemaju mnogo izbora: ili \u0107e optimizovati svoje procese i osna\u017eiti ljude, ili \u0107e se gu\u0161iti u svakodnevnom ga\u0161enju po\u017eara.<\/p><p>Ovaj prakti\u010dan vodi\u010d nastao je upravo zbog toga: kao alat koji poma\u017ee firmama da postanu otporne, organizovane i stabilne; ne kroz teoriju, ve\u0107 kroz stvarnu primenu LEAN pristupa u praksi.<\/p><p>Ovaj vodi\u010d nije akademska literatura. On je sa\u017eetak godina provedenih po fabrikama, me\u0111u ma\u0161inama, u razgovoru sa ljudima koji znaju \u0161ta zna\u010di boriti se za komad i za sat. Napravljen je da se koristi, ne da se \u010dita jednom i zaboravi. U njoj se ne nalaze komplikovani izrazi i nepotrebni engleski termini i detaljna re\u0161enja: ve\u0107 putokaz do re\u0161enja koja funkcioni\u0161u i u malim i u velikim firmama, kod nas, ovde, u realnim uslovima.<\/p><p>Kome je namenjen? Ovaj vodi\u010d je za mlade i ambiciozne rukovodioce koji \u017eele da postave stvari kako treba i da znaju kako to da urade.<\/p><p>Za vlasnike firmi koji \u017eele sistem koji nije zasnovan na sre\u0107i. Za direktore koji vi\u0161e ne \u017eele da slu\u0161aju opravdanja nego da vide rezultat.<\/p><p>Za menad\u017eere koji \u017eele transformaciju u lidere. I da budemo iskreni: nije za one koji znaju sve najbolje. Oni neka sa\u010dekaju slede\u0107i audit.<\/p><p>Ako imate jasnu strategiju, ako vam nije problem da pogledate i sebe i sistem, i ako \u017eelite tim koji zna \u0161ta radi i za\u0161to, ovaj vodi\u010d \u0107e vam pomo\u0107i da to ostvarite. I zapamtite:<\/p><p>&#8222;Na\u0161a jedina sigurnost je na\u0161a sposobnost da se menjamo.&#8220; (John C. Lilly)<\/p><\/section>\n<section class=\"og-section\" id=\"sta-je-zapravo-lean-razbijanje-mita\"><div class=\"og-num\">02<\/div><h2>\u0160ta je zapravo LEAN: razbijanje mita<\/h2><p>Prema McKinsey istra\u017eivanju, samo 30% firmi koje poku\u0161aju da implementiraju LEAN posti\u017eu trajne rezultate. Ostalih 70% odustane, \u0161minka procese ili se vra\u0107a na stari sistem organizacije.<\/p><p>Za\u0161to? Jer misle da je LEAN \u201ene\u0161to \u0161to se mo\u017ee kupiti, nau\u010diti na seminaru i zavr\u0161iti za tri meseca\u201d. Danas se praktikuje koncept, gde firme \u0161alju svoje zaposlene na razne seminare i dobijaju odre\u0111ene pojaseve (yellow, green, black belt&#8230;) i tada se smatra da je firma dobila LEAN stru\u010dnjaka, koji \u0107e biti \u201ezadu\u017een\u201c za LEAN.<\/p><p>Ista situacija se de\u0161avala i godinama unazad kada su se odre\u0111ivala odgovorna lica za bezbednost; kada pro\u0111ete shopfloor-om i pri\u010date sa nekim od rukovodioca proizvodnje o temama vezanim za bezbednost, re\u0107i \u0107e vam da je za te poslove zadu\u017een i odgovoran neki Marko. Situacija se menja iz korena kada se svetski trendovi menjaju, u Evropi, pa i kod nas, gde se kroz zakonsku regulativu, na primeru bezbednosti, jasno ukazuje da ne postoji \u201eodgovorno lice\u201c za bezbednost ve\u0107 savetnik ili saradnik za poslove bezbednosti. Ovo jasno implicira da je ta osoba du\u017ena nau\u010diti druge kolege u firmi bezbednosti i da je svako odgovoran za bezbednost u svom delokrugu rada. Isti je princip i sa LEAN konceptom.<\/p><p>Da se vratimo na neku od zvani\u010dnih LEAN definicija koje svi citiraju: \u201eLean je filozofija upravljanja koja se fokusira na maksimizaciju vrednosti za kupca kroz eliminaciju gubitaka u procesu\u201d. Zvu\u010di pametno i deluje korisno. Ali da budemo iskreni: koliko ljudi koji to izgovore, zapravo znaju \u0161ta zna\u010di &#8222;gubitak&#8220;? i koliko njih se ikada zadr\u017ealo du\u017ee od 10 minuta kraj operatera koji sklapa 800 komada dnevno nekog proizvoda i na taj na\u010din posmatrali proces. U ve\u0107ini slu\u010dajeva proces se analizira kroz standardne alate, kao \u0161to su analiza uskih grla, VSM, i sli\u010dni alati nau\u010deni na seminarima, ali bez dublje povezanosti sa realno\u0161\u0107u na terenu.<\/p><p>Na osnovu mog dugogodi\u0161njeg iskustva mogli bismo odrediti jednu definiciju LEAN-a, ali iz prizme prakti\u010dnog rada i rada sa ljudima na terenu:<\/p><p>LEAN je brutalno iskreno ogledalo firme: pokazuje \u0161ta ne valja, svakog dana, i tra\u017ei od lidera da imaju hrabrosti da to poprave, zajedno sa ljudima, a ne preko njih.<\/p><p>Evo nekoliko uop\u0161tenih primera da bismo znali napraviti razliku:<\/p><p>U LEAN firmi, direktor ne sedi ceo dan u kancelariji ve\u0107 jednom dnevno ide na shopfloor: ne da kontroli\u0161e, ve\u0107 da vidi, pita i u\u010di. Vodi primerom prilikom obilaska nosi svu propisanu opremu kao i radnici koje oblazi i pridr\u017eava se svih pravila.<\/p><p>U LEAN firmi, menad\u017eer ne pravi planove u Excelu koji nemaju veze sa stvarno\u0161\u0107u, ve\u0107 planira u skladu sa ritmom proizvodnje i glasa operatera.<\/p><p>U LEAN firmi, kada do\u0111e do problema: prvo se pita: \u201c\u0160ta sistem nije podr\u017eao?\u201d, a ne \u201cKo je kriv?\u201d<\/p><p>U LEAN firmi, rukovodilac ne postavlja ciljeve iz glave: ve\u0107 koristi podatke sa terena, iz proizvodnje, i uskla\u0111uje ih sa realnim kapacitetima ljudi i ma\u0161ina.<\/p><p>U LEAN firmi, problemi se ne kriju za &#8222;posle audita&#8220;, ve\u0107 se obele\u017eavaju odmah, jer je sramota sakriti, a \u010dast re\u0161iti.<\/p><p>U LEAN firmi, dnevni sastanak traje najvi\u0161e 10 minuta, stoje\u0107i, sa jednom tablom i jasnim fokusom: bezbednost, kvalitet, i \u0161ta danas ne sme stati.<\/p><p>U LEAN firmi, najbolji radnik nije onaj koji najbr\u017ee radi, ve\u0107 onaj koji vidi problem i ka\u017ee: \u201cOvo nema smisla: hajde da promenimo.\u201d<\/p><p>U LEAN firmi, \u0161ef linije ne vi\u010de \u201cbr\u017ee!\u201d, nego pita: \u201cZa\u0161to kasnimo? \u0160ta ti treba da bi i\u0161lo glatko?\u201d<\/p><p>U LEAN firmi, kaizen predlog nije mrtva kutija, ve\u0107 se ideja radnika re\u0161ava u roku od 5 dana i osoba koja je predlo\u017eila dobija povratnu informaciju.<\/p><p>U LEAN firmi, kada nova oprema dolazi, ne odlu\u010duje samo in\u017eenjering, ve\u0107 operateri daju komentare jer oni \u0107e s njom raditi svaki dan.<\/p><p>Pre nego \u0161to nastavimo dublje u analizu, nekoliko re\u010di o meni kao osobi koja se potrudila da sastavi ovu malu skriptu sagledavaju\u0107i stvari iz malo druga\u010dijeg, prakti\u010dnog i pre svega nesvakida\u0161njeg ugla\ud83d\ude0a.<\/p><p>Zovem se Nemanja Krsti\u0107 i ve\u0107 vi\u0161e od 17 godina se bavim unapre\u0111enjem proizvodnih procesa, bezbedno\u0161\u0107u na radu i implementacijom LEAN principa u razli\u010ditim industrijama: od prehrambene, tekstilne i elektro, gra\u0111evinske do hemijske i namenski orijentisane proizvodnje. Nosilac sam master diplome iz in\u017eenjerstva, a svoje prakti\u010dno znanje izgradio sam kroz direktan rad na shopfloor-u, sa ljudima i ma\u0161inama, u realnim uslovima gde svaki sat i svaki komad zna\u010de razliku izme\u0111u profita i gubitka.<\/p><p>Radio sam kao LEAN, EHS, QA menad\u017eer, HR menad\u017eer, menad\u017eer Logistike i planiranja, direktor proizvodnje, Facility specialista u doma\u0107im i me\u0111unarodnim kompanijama, na po\u010detku karijere sam volontirao u velikoj multinacionalnoj kompaniji Inbev. Kasnije sam pre\u0161ao u konsultantske vode kroz sopstvenu firmu EHS &amp; LEAN Consulting.<\/p><p>Moja praksa se ne zasniva na &#8222;\u0161kolskim primerima&#8220;, ve\u0107 na stvarnim izazovima u fabrikama koje su bile optere\u0107ene haosom, papirologijom, subjektivnim odlukama i nedostatkom sistema. Moj cilj nikada nije bio da implementiram LEAN da bi firma imala &#8222;lep izve\u0161taj&#8220;, ve\u0107 da stvorim ambijent u kojem ljudi mogu raditi bez gubljenja vremena, bez stresa i sa jasno\u0107om u svakom koraku. Kroz godine rada sam razvio sopstvene metodologije za povezivanje timova, izgradnju me\u0111usobnog poverenja i obezbe\u0111ivanje trajnih rezultata koji nisu zavisni od jedne osobe ili jednog sistema, ve\u0107 od svakodnevnog u\u010denja i stabilnog upravljanja procesima.<\/p><p>Ova skripta nije teorijski vodi\u010d. Ovo je rezultat rada na terenu, razgovora sa radnicima, mojih i zajedni\u010dkih neuspeha i uspona i padova, poku\u0161aja, i kona\u010dno rezultata. Pi\u0161em ovo kako bih pomogao rukovodiocima koji imaju priliku da zaista naprave razliku, ali im treba pravi okvir da bi znali odakle da krenu.<\/p><\/section>\n<section class=\"og-section\" id=\"kako-je-lean-nastao-istina-koju-mnogi-preskacu\"><div class=\"og-num\">03<\/div><h2>Kako je LEAN nastao: istina koju mnogi preska\u010du<\/h2><p>Danas mnogi pri\u010daju o LEAN-u kao o nekoj modernoj metodi menad\u017ementa koja dolazi sa Zapada. Me\u0111utim, istina je potpuno druga\u010dija. LEAN nije ro\u0111en u kancelarijama bogatih poslovnih ljudi, nije nastao u laboratorijama ameri\u010dkih univerziteta niti kao rezultat istra\u017eivanja multinacionalnih kompanija. LEAN je nastao iz siroma\u0161tva, i iz o\u010daja; u posleratnom Japanu, gde nije bilo ni novca, ni resursa, ni vremena za gre\u0161ke.<\/p><p>Nakon Drugog svetskog rata, Japan je bio razoren. Industrija u kolapsu, materijala nema, a radna snaga iscrpljena. Toyota, tada jo\u0161 mala i lokalna kompanija, nije se mogla takmi\u010diti sa velikim zapadnim gigantima koji su proizvodili u velikim serijama i imali ogromne zalihe. Zato su morali da smisle druga\u010diji na\u010din proizvodnje. Ne br\u017ee, ja\u010de, nego pametnije.<\/p><p>Tako su po\u010deli da razvijaju ono \u0161to \u0107e kasnije postati poznato kao Toyota Production System (TPS); sistem koji se zasniva na zdravom razumu, po\u0161tovanju ljudi i svakodnevnom re\u0161avanju problema. Ono \u0161to je posebno kod Toyote nije samo sistem, ve\u0107 kultura u kojoj svako ima pravo da zaustavi liniju ako vidi gre\u0161ku, gde se lider ne postavlja zbog titule, ve\u0107 zato \u0161to ume da slu\u0161a, vidi, i zna da pita \u201cza\u0161to\u201d i pet puta ako treba.<\/p><p>LEAN se nije zvao LEAN. Oni ga nisu tako zvali. I dan-danas u Toyoti taj izraz gotovo da se ne koristi. Taj naziv je nastao mnogo kasnije, kada su zapadni stru\u010dnjaci poku\u0161ali da &#8222;upakuju&#8220; ono \u0161to su videli u Toyoti u neki univerzalan metod.<\/p><p>Prvi put termin &#8222;Lean production&#8220; upotrebljen je 1988. godine, u okviru istra\u017eivanja MIT-a koje je dovelo do knjige &#8222;The Machine That Changed the World&#8220;. U toj knjizi Toyota je predstavljena kao najbolji primer efikasne proizvodnje u svetu, a re\u010d &#8222;lean&#8220; je odabrana da opi\u0161e sistem koji koristi manje svega: manje zaliha, manje prostora, manje defekata, manje vremena, ali sa vi\u0161e vrednosti za kupca.<\/p><p>Na\u017ealost, ono \u0161to se desilo posle toga je da su mnogi uzeli LEAN kao alatku, kao projekat, kao ne\u0161to \u0161to se mo\u017ee &#8222;implementirati&#8220; kroz \u010detiri radionice i 3 tabele. I tu kre\u0107e pad. Jer LEAN nikada nije bio sistem za izve\u0161taje; on je bio na\u010din razmi\u0161ljanja i pona\u0161anja u svakom trenutku, na svakom mestu.<\/p><p>Zato, kada danas neko ka\u017ee: &#8222;Hajde da uvedemo LEAN&#8220;, moje prvo pitanje je:&#8220;A jeste li spremni da preispitate sve \u0161to trenutno radite, uklju\u010duju\u0107i i sopstvene navike, stavove i odluke; da li ste spremni da se menjate vi kao vrh brega-vi kao menad\u017ement?&#8220;<\/p><p>Ako menad\u017ement nije spreman bolje je da ga ne uvodi. I sam po\u010detak bi\u0107e vam samo jo\u0161 jedan PowerPoint fajl u recycle bin-u.<\/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>Osnovni elementi LEAN-a: ku\u0107a koja se ne gradi PowerPointom<\/h2><p>LEAN nije teorijski model iz knjige. I nije ona \u201eToyota ku\u0107a\u201c sa slajda. U stvarnom svetu, tamo gde se stvaraju proizvodi, LEAN se gradi iz haosa. A temelj te ku\u0107e nisu ni Just-in-Time, ni Kanban (za koje se svi prvi uhvate), ni Jidoka za upravljanje kvalitetom; oni dolaze kasnije, kao nadogradnja. Pravi temelj LEAN-a, iz mog dugogodi\u0161njeg iskustva, jesu 5S i bezbednost. To su elementi koje menad\u017ement mora odmah da omogu\u0107i, i da pored toga otvori prostor radnicima da aktivno u\u010destvuju u optimizaciji procesa a to je Kaizen; ja na kaizen (proces predlaganja ideja) gledam kao izolaciju temelja stabilne gra\u0111evine, koja slu\u017ei da temelji \u201cne pucaju\u201d u budu\u0107nosti.<\/p><p>Ko to ne razume, d\u017eabe mu pojasevi, sertifikati, dijagrami tokova i analiza uskih grla\u2026. Sve to ostaje mrtvo slovo na papiru ako osnovna tri elementa (5S, bezbednost i Kaizen) ne postoje, i ako nisu no\u0161eni iskrenom empatijom rukovodstva. Ta tri principa nisu tehni\u010dke stvari, ve\u0107 osnov kulture firme. Kada je to temelj ku\u0107a mo\u017ee da raste.<\/p><p>Uvek polazim od jedne jednostavne istine: operateri na ma\u0161inama su ti koji firmi donose novac. Oni su srce. Sve ostalo, uklju\u010duju\u0107i nas iz menad\u017ementa, HR, kontrolu kvaliteta, planiranje, logistiku, pa i samu prodaju, samo su podr\u0161ka. Servis. I kao svaki servis, mo\u017eemo taj protok novca da ubrzamo, da ga rasteretimo, ili da ga jednostavno upropastimo.<\/p><p>Ako radnik ne zna gde mu je alat, ako nema prostora da se normalno okrene, ako mu stoji to\u010dak pod nogom, kabl mu visi iznad glave, a mora da gura ruke u ma\u0161inu bez za\u0161tite: tu nema LEAN-a. Tu postoji improvizacija. A improvizacija je najskuplja stavka u firmi, samo se obi\u010dno ne meri odmah.<\/p><p>Zato, moja LEAN ku\u0107a izgleda ovako kao na slici 1.<\/p><p>Slika 1: LEAN ku\u0107a iz moje perspektive<\/p><p>Ova LEAN ku\u0107a nije crte\u017e za prezentaciju, ve\u0107 ogledalo jedne ozbiljne organizacije. Svaki sloj ima svoju ulogu, a svi zajedno funkcioni\u0161u kao sistem koji je sposoban da izdr\u017ei pritisak svakodnevne proizvodnje, nepredvidivosti tr\u017ei\u0161ta i sve \u010de\u0161\u0107ih unutra\u0161njih kriza u firmama.<\/p><p>Temelj ku\u0107e \u010dine tri duboko ukorenjena sloja. Prvi je dugoro\u010dna strategija firme, vizija i misija. To nije slovo na papiru za sajt, kao \u0161to se obi\u010dno i pravi tekst u jednoj firmi jer smatraju da je to \u201epro forme\u201c, ve\u0107 jasan pravac koji daje smisao svim svakodnevnim odlukama. Ako firma menja kurs na svakih \u0161est meseci, tu LEAN ne mo\u017ee da za\u017eivi jer se sve \u0161to ljudi naprave poni\u0161tava prvom promenom prioriteta. Dugogodi\u0161nju strategiju i klju\u010dne politike defini\u0161e vlasni\u010dka struktura sa jasno definisanim razvojnim ta\u010dkama. Vizija je krajnja ta\u010dka gde firma treba da stigne kada ostvari tu strategiju, a misija je put kojim se ide do strate\u0161ke ta\u010dke. Misiju defini\u0161e direktor sa svojim timom, kroz operativne ciljeve, procedure i planove.<\/p><p>Na tom strate\u0161kom sloju nalazi se 6S, spoj 5S metodologije i bezbednosti na radu. Bez reda, organizacije i bezbednosti nema stabilnog procesa. Ako radnik ne zna gde mu je alat, ako mu se kablovi prepli\u0107u pod nogama, ako ne zna da li sme da dotakne ma\u0161inu, sistem nije pod kontrolom.<\/p><p>Ono \u0161to povezuje stabilnost i sve iznad nje jeste Kaizen, svakodnevno, zdravorazumsko unapre\u0111enje. To nije veliki projekat. Kaizen je pitanje: \u201eIma li ovo smisla?\u201c Kaizen je izolacija izme\u0111u temelja i zida. Ne vidi se, ali bez nje sistem ubrzo kre\u0107e da puca iznutra.<\/p><p>Ku\u0107a se potom podi\u017ee na tri stuba. Prvi je menad\u017ement i liderstvo. Svesno su oba pojma tu, jer se ne podrazumevaju jedno sa drugim. Mo\u017ee\u0161 biti rukovodilac bez liderstva i tada te se ljudi boje, ali te ne prate. Mo\u017ee\u0161 biti lider bez funkcije i tada te ljudi slu\u0161aju jer veruju, ne zato \u0161to moraju. Pravi stub nastaje kada menad\u017ement zna da nije tu da komanduje, nego da slu\u017ei. To se zove liderstvo.<\/p><p>Drugi stub su ljudi i timski rad. Bez anga\u017eovanih ljudi nema kulture LEAN-a. Bez me\u0111usobnog poverenja, svaka promena se do\u017eivljava kao pretnja. Ako u firmi postoje \u201eoni gore\u201c i \u201emi dole\u201c, ku\u0107a puca na pola.<\/p><p>Tre\u0107i stub su LEAN alati. Tek ovde dolaze vizuelizacija (vizuelni menad\u017ement), VSM, A3, takt time, standardni rad, SMED, JIT, KANBAN i ostalo. Oni su va\u017eni, ali nisu su\u0161tina. Bez prethodna dva stuba, alati postaju jo\u0161 jedan PowerPoint fajl u arhivi.<\/p><p>Sve stubove povezuje sloj KPI, ciljeva, trigera i DMAIC procesa. Bez merenja, sve je subjektivno. Ciljevi bez brojki su samo \u017eelje. KPI mora biti jasan, po\u0161ten i funkcionalan, ne da bi se ka\u017enjavalo, ve\u0107 da bi se znalo gde treba pomo\u0107i. KPI predstavlja formulu pomo\u0107u koje dobijamo jednu mernu skalu. Na tu mernu skalu dodajemo ta\u010dku koju defini\u0161emo kao cilj, takozvani target, i precizno defini\u0161emo proces koji merimo. Ono \u0161to zahtevam u praksi, a \u0161to je jako retko videti u firmama jer se svi bave samo ciljevima, jeste donja vrednosna ta\u010dka na KPI skali, takozvani triger. To je okida\u010d koji pokre\u0107e proces istra\u017eivanja DMAIC kada vrednost na nekom KPI-u padne na kriti\u010dnu vrednost. DMAIC (Define, Measure, Analyze, Improve, and Control) je vrlo mo\u0107an LEAN alat koji omogu\u0107ava timsko istra\u017eivanje neusagla\u0161enosti. Obuhvata Ishikawu, 5 Why, brainstorm i druge pristupe.<\/p><p>Na kraju, krov su zadovoljni kupci i kvalitet. To je ono \u0161to se vidi spolja. Ako je kupac zadovoljan i kvalitet stabilan, to zna\u010di da svi slojevi ispod funkcioni\u0161u.<\/p><p>Na samom vrhu nalazi se zvezda vodilja. To je poslovna izvrsnost, Business Excellence. To je ono \u010demu te\u017eimo u svakom procesu. Firme mogu definisati KPI-eve kojima \u0107e meriti poslovni uspeh: efikasnost, efektivnost, OEE i druge. Za njih najvi\u0161e rukovodstvo defini\u0161e targete za svaku godinu. Na primer, za efikasnost procesa cilj mo\u017ee biti oko 75 odsto, ali da bi firma dostigla poslovnu izvrsnost, efikasnost mora biti minimalno 95 odsto, kvalitet 99 odsto, a efektivnost najmanje 90 odsto. To zna\u010di da ukupni OEE mora biti najmanje 85 odsto.<\/p><\/section>\n<section class=\"og-section\" id=\"vazni-lean-alati-i-koncepti\"><div class=\"og-num\">05<\/div><h2>Va\u017eni LEAN alati i koncepti<\/h2><p>LEAN nije jedan alat. LEAN je filozofija. Ali kao svaka dobra filozofija, bez prakti\u010dnih alata ostaje samo pri\u010da za PowerPoint. U mojoj praksi koristim konkretne osnovne alate koji funkcioni\u0161u, ali se naravno mogu primenjivati i mnogo zahtevniji alati. Nave\u0161\u0107u osnovne:<\/p><p>5S + Safety = 6S (ure\u0111enje radnih prostora radi ubrzanja procesa i smanjenja rizika)<\/p><p>5S nije samo japanska egzotika niti \u201eneka tamo metodologija za \u010disto\u0107u\u201c; to je prva stvar koju ozbiljna firma mora da uvede pre nego \u0161to uop\u0161te izgovori re\u010d LEAN.<\/p><p>Naziv 5S dolazi od pet japanskih re\u010di koje opisuju redosled aktivnosti:<\/p><p>Seiri (Sortiranje): uklanjanje svega \u0161to nije potrebno sa radnog mesta. \u0160rafovi koji se nikad ne koriste, alati koji su za svaki slu\u010daj: sve to stvara konfuziju i oduzima prostor. Na terenu ovo zna\u010di: ono \u0161to ti ne treba skloni. U ovoj fazi lepimo crvene tagove na svu opremu i alate koji nam ne trebaju i nakon nekog perioda se odla\u017eu u 5S zonu i sklanjaju sa radnih pozicija.<\/p><p>Seiton (Sistematsko raspore\u0111ivanje, re\u0111anje): kada smo sve otklonili \u0161to nam ne treba sa radnog mesta,tada analiziramo \u0161ta Koliko koristimo (frekvencija upotrebe) i tada raspore\u0111ujemo alat i opremu tako da nam stvari koje najvi\u0161e koristimo budu pri ruci (blizu nas) i po mogu\u0107nosti u zlatnoj zoni (Golden Area: od pojasa do grudi);<\/p><p>Seiso (\u010ci\u0161\u0107enje): \u010di\u0161\u0107enje radnog prostora, ne radi sjaja, ve\u0107 radi kontrole i odr\u017eavanja. Kad peremo ma\u0161ine vidimo i curenja na primer. Kad \u010distimo, u stvari proveravamo.<\/p><p>Seiketsu (Standardizacija): kada smo sve pore\u0111ali i o\u010distili da se ija tada standardizujemo (slikamo kako treba da izgleda radno mesto, postavljamo konture iza opreme koja je oka\u010dena i pravimo vizuelne standard za svaku radnu poziciju). Vizuelni standard je u su\u0161tini poster koji pokazuje gde \u0161ta treba da stoji na toj radnoj poziciji.<\/p><p>Shitsuke (Samodisciplina): odr\u017eavanje i navika. Da bi 5S \u017eivelo, mora\u0161 da ga \u017eivi\u0161 svaki dan. Ako ga ignori\u0161e\u0161 dan-dva, sistem se raspada. Ako ga ponavlja\u0161 tada postaje prirodan. Zato radimo unakrsne kontrole putem CHECK listi da bi konstantno jednu radnu poziciju tokom perioda pregledalo vi\u0161e nivoa zaposlenih<\/p><p>U mojoj praksi, nikada ne pri\u010dam o 5S bez da dodam i \u0161esti S: Safety. Bezbednost nije dodatak. Bezbednost je preduslov svega. Ako \u010dovek mora da preska\u010de kutije da bi do\u0161ao do ma\u0161ine, ako mu kabl visi iznad glave ili ako \u0161rafciger ostane zaglavljen u stolu: to nije neuredno, to je opasno. A sve \u0161to je opasno, jednog dana postaje i skupo.<\/p><p>5S + Safety zna\u010di da kad zavr\u0161i\u0161 5S inspekciju, ne ka\u017ee\u0161 samo \u201elepo izgleda\u201c, nego i \u201ebezbedno je da \u010dovek ovde provede osam sati\u201c. I tu je razlika izme\u0111u firme koja igra LEAN i firme koja \u017eivi LEAN.<\/p><p>U nekim firmama sam vi\u0111ao da 5S postoji \u201ena papiru\u201c: imaju lepe fotografije pre i posle, sve je sjajno jedan dan. A posle toga se sve vrati kao pre. Za\u0161to? Jer nisu imali lidera koji \u0107e prvi uzeti da \u201cslo\u017ei alat\u201d (pokrene projekat i vodi primerom), i nisu imali kulturu u kojoj se red odr\u017eava zato \u0161to svi veruju da to treba, a ne zato \u0161to je inspekcija radi pro forme ili audita.<\/p><p>Zato, 5S i Safety nisu alat. Oni su navika. A navike se grade svakog dana. Ako to propusti\u0161: nema Lean-a. Nema ni proizvodnje. Ima samo borba da stigne\u0161 ono \u0161to si sam sebi zakomplikovao.<\/p><p>Usko grlo (Bottleneck Analysis)<\/p><p>Analiza uskog grla je osnovni korak u razumevanju kapaciteta jednog proizvodnog sistema. Uvek postoji ta\u010dka u procesu koja ograni\u010dava protok i ona se ne odre\u0111uje proizvoljno, ve\u0107 preciznim merenjem. U svojoj praksi oslanjam se na time study metodologiju, kroz koju defini\u0161em standardna vremena za svaku operaciju u procesu. Upore\u0111ivanjem tih vremena i analizom u\u010destalosti zastoja mogu\u0107e je jasno identifikovati gde dolazi do zadr\u017eavanja. Usko grlo se ne mora nalaziti samo na liniji, ve\u0107 mo\u017ee nastajati i u fazama pripreme, kontrole, logistike ili planiranja. Zbog toga je va\u017eno da analiza bude sveobuhvatna i da se sprovodi periodi\u010dno. Kada se usko grlo identifikuje, pristupa se njegovom otklanjanju, \u0161to ne podrazumeva uvek nova ulaganja. U velikom broju slu\u010dajeva dovoljna su manja operativna pode\u0161avanja: promene rasporeda rada, prilago\u0111avanje takt vremena ili preraspodela zadataka. Ispravno sprovedena analiza uskog grla omogu\u0107ava firmi da pove\u0107a ukupni kapacitet bez dodatnog stresa na resurse i bez komplikovanih reorganizacija.<\/p><p>\u010cesto se doga\u0111a u praksi da menad\u017eeri proizvodnje, ne poznaju\u0107i ovu analizu, rasporede vi\u0161e radnika na neki proces proizvodne linije (odre\u0111enu ta\u010dku) gde je apsolutni vi\u0161ak i nepotrebno a na drugom mestu nedostaje radnika. U razgovoru sa njima, pre analize, takva mogu\u0107nost je nemogu\u0107a i kategori\u010dki je odbijaju. Cilj ovih analiza nije da se \u201cnate\u017eemo\u201d i isterujemo pravdu, ve\u0107 da in\u017eenjerskim pristupom doka\u017eemo da proces nije dobro pode\u0161en i da firma ima nepotreban gubitak.<\/p><p>GEMBA (obilasci proizvodnih pogona i kontrola putem CHECK listi)<\/p><p>Gemba \u0161etnja je Lean praksa u kojoj rukovodilac odlazi direktno na mesto gde se posao stvarno obavlja; tamo gde nastaje vrednost (shopfloor) Ne radi se o nadzoru ili kontroli, ve\u0107 o u\u010denju kroz posmatranje i razgovor. U mojoj praksi, Gemba \u0161etnja uklju\u010duje strukturisano posmatranje procesa uz pomo\u0107 check listi, koje se koriste za unakrsnu kontrolu: ne samo 5S i bezbednosti, ve\u0107 i svih klju\u010dnih procesa u radu. Time se proverava da li se posao zaista odvija u skladu sa standardima, da li postoje skrivene prepreke i gde se gubi vreme ili kvalitet.<\/p><p>\u0160etnja mora imati jasan fokus i ne sme trajati du\u017ee od nekoliko minuta po lokaciji. Najva\u017enije je postavljati prava pitanja: \u0161ta ti ote\u017eava rad, gde ti proces nije jasan, \u0161ta ti smeta svakog dana. Samo tako dolazimo do pravih problema, ali i do stvarnih predloga za unapre\u0111enje. Gemba \u0161etnja je najefikasnija kada postane rutina i kada ljudi shvate da menad\u017eer ne dolazi da tra\u017ei gre\u0161ke, ve\u0107 da ukloni prepreke. Nailazimo na radnike koji razli\u010dito rade svoj posao; bez obzira na to uvek prvo pohvalimo ono \u0161to dobro radi (makar to bilo i samo 10%; pre toga \u201cprobijemo led\u201d sa nekom pozitivnom pri\u010dom), pa onda postavljamo otvorena pitanja da nam se pojasni na\u010din rada i nikada ne odlazimo sa mesta i razgovora dok ne dobijemo obe\u0107anje (kroz osmeh) da \u0107e se radnik i proces popraviti.<\/p><p>Heijunka (optimizacija planiranja proizvodnje)<\/p><p>Heijunka je metod uravnote\u017eenja proizvodnje \u010diji je cilj da se smanji variranje u optere\u0107enju linije, materijalnog toka i anga\u017eovanja ljudi. U praksi, to zna\u010di da se proizvodnja planira tako da se izbegne rad u talasima; danima sa preoptere\u0107enjem i danima sa padom aktivnosti. Na prmer: umesto da se pravi deset hiljada komada jednog artikla pa se danima taj artikal ne radi, Heijunka podrazumeva ritmi\u010dnu, ravnomerno raspore\u0111enu proizvodnju razli\u010ditih artikala u skladu sa realnim potrebama kupaca.<\/p><p>Najve\u0107i izazov kod Heijunke u doma\u0107im firmama jeste planiranje; \u010desto se pravi plan koji &#8222;lepo izgleda&#8220; na papiru, ali ne prati stvarni takt proizvodnje, raspolo\u017eive resurse ni kapacitete procesa. Zbog toga plan stvara pritisak na ljude, pravi zalihe ili dovodi do prekida. U svom radu koristim kombinaciju Lean alata i realnog shopfloor feedbacka da bih Heijunku spustio na nivo operativnog planiranja; ne samo da postoji kao Excel, ve\u0107 kao sistem koji \u017eivi. Prvo \u0161to radim jeste uvo\u0111enje jednog od na\u010dela WCSC koncepta (world class supply chain) da se planiranje proizvodnje i realizacija proizvodnje razdvoje u zasebne sektore i da sektor prodaje ne mo\u017ee direktno komunicirati sa sektorom proizodnje, niti da sektor proizvodnje mo\u017ee sam praviti sebi plan (\u0161to je svojevrsni sukob interesa). Zato se reformi\u0161e sistematizacija i organizaciona struktura i postavlja sektor logistike sa funkcijom planiranja kao tampon zona izme\u0111u prodaje i proizvodnje i da balansira me\u0111usobne zahteve.<\/p><p>Uravnote\u017eenje ne zna\u010di samo ravnomeran broj komada po smeni, ve\u0107 uklju\u010duje i stabilnost u vremenu isporuke, kvalitetu i optere\u0107enju ma\u0161ina. Kada se to postigne, firme lak\u0161e upravljaju resursima, smanjuju stres kod radnika i elimini\u0161u potrebu za neplaniranim prekovremenim radom ili stalnim prebacivanjem ljudi s pozicije na poziciju.<\/p><p>Hoshin Kanri (preno\u0161enje poslovne strategije do najni\u017eih slojeva hijerarhije)<\/p><p>Hoshin Kanri je metod kojim se strategija firme prevodi u konkretne ciljeve i aktivnosti na svim nivoima organizacije. Su\u0161tina je u tome da se obezbedi uskla\u0111enost izme\u0111u onoga \u0161to uprava planira i onoga \u0161to se de\u0161ava u operativi. U praksi, ovo zna\u010di da strategija ne ostaje dokument u fioci (na primer ISO politika firme koja se pravi pro forme), ve\u0107 da svaki sektor zna svoj deo puta, kako meri napredak i \u0161ta treba da preduzme ako se javi odstupanje.<\/p><p>Najve\u0107a prednost Hoshin Kanrija je \u0161to uvodi dvosmernu komunikaciju. Ciljevi se ne spu\u0161taju jednostrano. Postavlja se pitanje da li su dosti\u017eni, da li su resursi obezbe\u0111eni i \u0161ta su mogu\u0107e prepreke. U firmama gde ovo ne postoji, \u010desto se de\u0161ava da su ciljevi definisani, ali niko u pogonu ne zna ni \u0161ta su, ni za\u0161to su va\u017eni.<\/p><p>U mojoj primeni ovog alata, koristim jednostavan format: za svaki strate\u0161ki pravac postoje povezani ciljevi, jasni pokazatelji, vlasnik zadatka i kontrolni mehanizam. Klju\u010d uspeha je u odr\u017eavanju ritma pregleda i povezivanju KPI rezultata sa konkretnim akcijama, a ne samo s prezentacijama. Kada ljudi razumeju gde firma ide i vide kako njihova uloga doprinosi tom pravcu, onda i strategija dobija smisao i stvarno se \u017eivi u svakodnevnom radu.<\/p><p>Just in Time (princip planiranja proizvodnje i materijala)<\/p><p>Just in Time je princip proizvodnje i isporuke zasnovan na stvarnim potrebama kupca, bez vi\u0161kova i zaliha koje nepotrebno zauzimaju prostor, vezuju novac i stvaraju dodatni pritisak na sistem. Ideja je jednostavna: proizvesti samo ono \u0161to je potrebno, u koli\u010dini koja je potrebna, u trenutku kada je potrebno. \u010cesto u praksi imamo situaciju da zanemaruju\u0107i potrebe kupca direktor proizvodnje sam planira \u0161ta se radi i kako njemu odgovra, pa imamo velike serije, koje staraju ka\u0161njenja, prekomerne zalihe i nedostatke\u2026Zato je ve\u0107 gore opisano da radimo po principu WCSC-na i da Logistika planira proizvodnju i materijal.<\/p><p>U praksi, da bi JIT funkcionisao, svi delovi sistema moraju biti stabilni. Nema mesta improvizaciji. Plan mora biti realan (zasnovan na ostvarenoj efikasnosti iz proizvodnje i trenutnim realnim kapacitetima), materijal dostupan. \u010cim neki deo lanca zaka\u017ee, ceo sistem trpi. Zato JIT ne mo\u017ee da se uvede deklarativno. Potrebna je tehni\u010dka preciznost, organizaciona disciplina i jasan lanac komunikacije izme\u0111u planiranja, nabavke, proizvodnje i logistike.<\/p><p>U firmama koje su navikle da &#8222;igraju na sigurno&#8220; prave\u0107i velike zalihe, uvo\u0111enje JIT-a zahteva promenu razmi\u0161ljanja. Ne radi se o riziku, ve\u0107 o oslanjanju na \u010dinjenice i ta\u010dno planiranje. U sistemima koje sam postavljao, JIT je uvek bio fazno uveden: prvo kroz internu logistiku i povla\u010denje materijala na liniju po stvarnoj potro\u0161nji, zatim kroz Kanban sistem, a tek kasnije kroz planiranje proizvodnje po narud\u017ebini.<\/p><p>Just in Time donosi najvi\u0161e koristi kada se kombinuje sa standardizovanim radom i niveli\u0161u\u0107im planiranjem. Tada prestaje potreba za stalnim hitnim isporukama i preoptere\u0107enim skladi\u0161tem, a proces postaje pregledan, predvidiv i finansijski zdrav. Ve\u0107ina firmi se odmah \u201cuhvati\u201d za JIT i njegovu implementaciju, ali je ovo ne\u0161to \u0161to se uvodi kada se ceo menad\u017ement uhoda, postoje precizni scrum sastanci ta\u010dno u odre\u0111ena vremena (jako bitno da bi se timski odmah re\u0161avali problemi), ako se Logistika odvoji od proizvodnje i nezavisno deluje i planira itd..<\/p><p>Takt Time (preostalo vreme do isporuke \/ broj poru\u010denih komada)<\/p><p>Takt Time je osnovni ritam proizvodnje koji defini\u0161e koliko \u010desto proizvod treba da bude gotov kako bi se zadovoljila potra\u017enja kupca. Ra\u010duna se kao odnos raspolo\u017eivog proizvodnog vremena i tra\u017eene koli\u010dine, i predstavlja bazu za balansiranje rada, planiranje kapaciteta i organizaciju linije. Ovo zna\u010di da prodaja ne mo\u017ee da ugovara rokove isporuke ako je takt vreme kra\u0107e od cycle time-a, odnosno od stvarnog vremena potrebnog da se izradi jedan komad proizvoda. Ako se ovo ne primenjuje onda \u010desto imamo situacije da je uvek neki kupac u ka\u0161njenju, da se u toku dana menjaju planovi proizvodnje, da se menjaju planovi utovara i sl i to stvara ogroman pad morala kod zaposlenih, konfuziju i pad produktivnosti.<\/p><p>Ako takt nije poznat ili se ignori\u0161e, proizvodnja se planira naslepo, po ose\u0107aju. To naj\u010de\u0161\u0107e dovodi do prenatrpanih operacija, vi\u0161kova, ka\u0161njenja i stalnih \u017eurbi. Kada se takt vreme uzme kao osnov, jasno se vidi koliko operatera je potrebno, gde dolazi do zastoja i kako treba da izgleda sekvenca rada.<\/p><p>U firmama koje imaju \u0161irok asortiman i \u010deste izmene, takt se koristi fleksibilno, uz procenu optere\u0107enja po grupama proizvoda ili linijama. Va\u017eno je da se takt ne posmatra kao \u010dista matematika, ve\u0107 kao alat za uskla\u0111ivanje zahteva i stvarnih mogu\u0107nosti. Takt ne tera sistem da radi br\u017ee, ve\u0107 da radi pametnije i da se kupcu daju jasne i ta\u010dne povratne informacije kada ta\u010dno u dan mo\u017ee o\u010dekivati svoju robu.<\/p><p>Kaizen (proces predlaganja ideja)<\/p><p>Kaizen predstavlja na\u010din razmi\u0161ljanja koji mi se kroz godine pokazao kao najstabilniji okvir za unapre\u0111enje rada. Ne donosi nagle promene, ne oslanja se na velike investicije i ne zahteva komplikovane projekte. Kaizen podrazumeva svakodnevno postavljanje jednostavnog pitanja: da li ne\u0161to u na\u0161em procesu mo\u017ee da se uradi lak\u0161e, jednostavnije, bezbednije ili sa manje gre\u0161aka.<\/p><p>Primenjujem ga tako \u0161to sam postavio jednostavan i transparentan sistem u kome svako mo\u017ee da predlo\u017ei pobolj\u0161anje. Koristimo obrazac u koji se unosi opis problema i predlog re\u0161enja, a ceo proces se poceduralno i timski prati i odobrava i nagra\u0111uje. Svaki predlog ima vlasnika, definisan rok i obaveznu povratnu informaciju onome ko je predlog dao. Pokazalo mi se da ljudi u sistem ulaze iskreno i sa voljom samo ako vide da ih neko slu\u0161a i da se ideje ne ignori\u0161u. Zbog toga je pravilo da nijedan predlog ne sme ostati bez odgovora, bilo da se primenjuje odmah, odla\u017ee za kasnije ili odbija uz obrazlo\u017eenje.<\/p><p>Kaizen ne primenjujemo samo u proizvodnji. Praksa mi je pokazala da korisne ideje \u010desto dolaze iz sektora podr\u0161ke (servisa), od ljudi koji naizgled nisu direktno u procesu, ali svakodnevno ose\u0107aju njegove posledice. Kaizen je uspe\u0161an samo ako se njegovo sprovo\u0111enje ne svodi na inicijativu jednog \u010doveka. Kada se poka\u017ee po\u0161tovanje prema svakom predlogu, gradi se kultura u kojoj ljudi zaista \u017eele da doprinesu.<\/p><p>Kanban (proizvodnja po principu marketa-samoposluge)<\/p><p>Kanban je alat za upravljanje materijalima i informacijama koji se u mojoj praksi pokazao kao najefikasniji u situacijama kada je va\u017eno da sistem sam daje signal da je ne\u0161to potrebno, bez poziva, molbi ili jurnjave. Njegova najve\u0107a snaga je u jednostavnosti. U praksi se koriste Kanban kartica, kutija, boja ili fizi\u010dki signal koji jasno pokazuju da je potrebno dopuniti, pripremiti ili preduzeti akciju. Na primer, ako imamo razdvojenu proizvodnju na dva segmenta (osnovnu proizvodnju i zavr\u0161nu obradu), umesto da zavr\u0161na obrada stalno komunicira sa osnovnom proizvodnjom kada joj i \u0161ta treba, radimo prethodnu analizu i defini\u0161emo da je za dnevnu proizvodnju potrebno \u010detiri palete poluproizvoda. Odre\u0111uje se funkcionalno mesto primopredaje, obele\u017eavaju se paletna mesta, i tada rukovodilac osnovne proizvodnje jednim pogledom na taj me\u0111u-magacin zna \u0161ta treba da se proizvodi. Cilj je da sva paletna mesta uvek budu popunjena, a da zavr\u0161na obrada uzima ono \u0161to joj je potrebno u datom trenutku.<\/p><p>Kada je ispravno postavljen, Kanban elimini\u0161e nepotrebno naru\u010divanje, prepunjene zalihe i prazne hodove. Uvo\u0111enje po\u010dinjem tamo gde se gubi najvi\u0161e vremena zbog \u010dekanja na materijal, alate ili poluproizvode. Postavljamo pravilo: kada signal iza\u0111e iz zone, logistika reaguje bez dodatnih pitanja. Sistem se pode\u0161ava uz pomo\u0107 definisane minimalne i maksimalne koli\u010dine, koja je prethodno testirana na realnom protoku.<\/p><p>U firmama koje imaju haoti\u010dan protok materijala, Kanban \u010desto deluje kao prevelika promena. Zato ga uvodim fazno. Prvo u internu logistiku, posebno za ambala\u017eu, potro\u0161ni materijal i alate. Kasnije, kad tim vidi kako funkcioni\u0161e, Kanban postaje deo svakodnevnog sistema i vi\u0161e niko ne \u017eeli da se vrati na staro. Klju\u010d uspeha nije u tome da kartice budu lepe, ve\u0107 da ih ljudi po\u0161tuju i da sistem reaguje na vreme.<\/p><p>KPI (odre\u0111ivanje formula za merenje vrednosti za svaki proces)<\/p><p>KPI, odnosno klju\u010dni pokazatelji performansi, predstavljaju merni okvir koji omogu\u0107ava da se radni procesi prate, analiziraju i unapre\u0111uju na osnovu \u010dinjenica. Oni nisu alat za kontrolu ljudi, ve\u0107 instrument za razumevanje sistema. Ispravno postavljeni KPI pokazuje gde sistem funkcioni\u0161e stabilno, a gde dolazi do odstupanja. U na\u0161em pristupu, KPI koristimo kao osnovu za operativno i strate\u0161ko upravljanje, a njihovo pra\u0107enje je sastavni deo Lean table i dnevnih sastanaka.<\/p><p>Pored ciljne vrednosti, koja se naj\u010de\u0161\u0107e defini\u0161e u svim firmama, uvodimo i obavezno odre\u0111ivanje triger vrednosti (donje granice ispod koje se pokre\u0107e analiza uzroka). To radimo kroz DMAIC pristup, u kojem se proces razla\u017ee, tra\u017ei uzrok i predla\u017eu mere. Triger nije kazna, ve\u0107 signal koji smo zajedni\u010dki dogovorili da bi nam pomogao da reagujemo pravovremeno.<\/p><p>Svaki KPI mora biti jasan, merljiv i funkcionalan. Povezujemo ga sa konkretnim zadacima i odgovornostima, kako bi timovi imali jasnu informaciju na osnovu koje mogu da donose odluke. Ako je rezultat ispod cilja, ne tra\u017eimo krivca, ve\u0107 uzrok. Ako je iznad o\u010dekivanja, to je signal da imamo priliku da standardizujemo ono \u0161to funkcioni\u0161e dobro.<\/p><p>OEE (kompletna efikasnost proizvodnog procesa)<\/p><p>OEE je klju\u010dni pokazatelj kojim merimo stvarnu iskori\u0161\u0107enost opreme, i predstavlja proizvod tri komponente: dostupnosti (efektivnost), performansi (efikasnost) i kvaliteta. Ne pokazuje samo koliko je ma\u0161ina radila, ve\u0107 koliko je od planiranog vremena zaista pretvoreno u dobar proizvod. Kroz OEE dobijamo sliku gde nam sistem gubi kapacitet: da li zbog zastoja, sporog rada ili lo\u0161ih komada. Za ovaj concept jako je bitno znati razliku izme\u0111u efektivnosti i efikasnosti. Predvi\u0111eno proizvodno vreme je 430 minuta, odredili smo Time Study metodologijom da nam je uz sve mikrozastoje i tipi\u010dnost na\u0161eg procesa 100 sekundi potrebno za jedan komad (to je u idealnim uslovima i na 100% norme), direktor je odredio target za ovu godinu na 75% efikasnosti i to je 133.3 sekundi o jednom komadu. Radnik radi u toku dana i prema\u0161uje target od 75% \u0161tp je odli\u010dno, ali radi samo 350 minuta (recimo produe pauze, kasno krenu sa proizvodnjom, neefikasno dr\u017eavanje ma\u0161ina itd..). Zato koristimo OEE koji nam daje \u0161iru sliku, a ne samo efikasnost.<\/p><p>U praksi, koristimo OEE kao osnovu za svakodnevnu procenu efikasnosti procesa. Svaka komponenta se posmatra zasebno. Ako je dostupnost niska, analiziramo za\u0161to ma\u0161ina stoji. Ako su performanse ispod o\u010dekivanja, merimo cycle time i upore\u0111ujemo sa takt vremenom. Ako je kvalitet ispod norme, kre\u0107emo u istragu defekata. Na taj na\u010din ne donosimo zaklju\u010dke na osnovu ukupnog broja, ve\u0107 razumemo koji deo sistema tra\u017ei intervenciju.<\/p><p>OEE ne koristimo samo za merenje, ve\u0107 kao alat za dijalog izme\u0111u proizvodnje, odr\u017eavanja, planiranja i kvaliteta. Kada svi sektori gledaju istu metriku, lak\u0161e se usaglase oko prioriteta. Zbog toga se OEE prikazuje na Lean tabli, sa dnevnim i mese\u010dnim rezultatima, uz jasne trigger vrednosti koje pokre\u0107u analizu i korektivne aktivnosti.<\/p><p>U firmama koje te\u017ee poslovnoj izvrsnosti, ciljna vrednost za OEE je najmanje 85 odsto. Ispod toga mo\u017ee zna\u010diti da je sistem jo\u0161 u fazi stabilizacije ili da postoje strukturna ograni\u010denja u procesima. Bez obzira na trenutnu vrednost, klju\u010dno je da tim zna kako se OEE ra\u010duna, \u0161ta predstavlja, i kako da reaguje kada neko od njegovih elemenata padne ispod o\u010dekivanog nivoa.<\/p><p>PDCA ciklus (definisanje dogovorenih akcija)<\/p><p>PDCA ciklus (Plan, Do, Check, Act) je osnovni teorijski okvir za upravljanje promenama i re\u0161avanje problema u Lean sistemu. Iako je metod jednostavan i logi\u010dan, meni se u praksi pokazalo da se retko primenjuje dosledno. Naj\u010de\u0161\u0107e se napravi plan, ne\u0161to se sprovede, ali se provera i korekcija presko\u010de ili ostanu u mail prepisci. Zato se umesto klasi\u010dnog PDCA modela u praksi oslanjamo na jednostavniji i transparentniji alat: Action log organizovan po Kanban principu.<\/p><p>Svaki sektor, svaki rojekat ima svoj Akcioni plan koji je u obliku kodiranog i standarduzovanog dokumneta u ekselu i ono \u0161o je dobro da se top menad\u017ement, auditori i svi koji zahtevaju jednostavno i brzo mogu uveriti u poslovanje jednog sektora i par godina u nazad. Akcije se defini\u0161u timski, vlasnik akcije odre\u0111uje rok do kada \u0107e uraditi akciju, a njegov nadre\u0111eni eventualno koriguje taj rok.<\/p><p>Poka Yoke (alat za eliminaciju gre\u0161aka)<\/p><p>Poka Yoke je pristup koji ima za cilj da gre\u0161ka bude fizi\u010dki onemogu\u0107ena ili odmah uo\u010dena pre nego \u0161to stigne do slede\u0107e faze procesa. U prevodu, to je oblik za\u0161tite od ljudske gre\u0161ke, ne kroz ka\u017enjavanje, ve\u0107 kroz pametno re\u0161enje. U firmama koje nemaju stabilne procese, ve\u0107ina problema proizilazi upravo iz ponovljenih gre\u0161aka koje su sistem propustile. Poka Yoke je na\u010din da se to prese\u010de.<\/p><p>Ako na primer posmatramo tekstilnu industriju i problem da neki radnici presko\u010de da u\u0161iju etiketu na d\u017eemper koji odla\u017eu na pult za slede\u0107i proces u proizvodnji, tada uvodimo da d\u017eemper ne ostavljaju nap ult, nego kada zavr\u0161e svoje operacije u Kojima je u\u0161ivanje etikete poslednja, moraju taj isti d\u017eemper oka\u010diti za etiketu na pokretna kolica za slede\u0107u fazu: nema etikete, ne mogu ga oka\u010diti\ud83d\ude0a<\/p><p>U nekim firmama u kojima smo uvodili ovu praksu, najva\u017eniji pomak se dogodio u razumevanju da se gre\u0161ka ne sme ponavljati ako se ve\u0107 jednom desila. Poka Yoke sistem nas tera da proces izmenimo tako da gre\u0161ka ili ne mo\u017ee da se dogodi, ili da se zaustavi odmah. To gradi poverenje u sistem i zna\u010dajno doprinosi kvalitetu.<\/p><p>Root Cause Analysis (5 Za\u0161to)<\/p><p>Analiza osnovnog uzroka, naj\u010de\u0161\u0107e poznata kao metod \u201e5 za\u0161to\u201c, koristi se kada \u017eelimo da do\u0111emo do pravog izvora problema, a ne da gasimo posledice. Postavljanjem niza pitanja \u201eza\u0161to se to desilo\u201c, svaki put dublje ulazimo u proces dok ne do\u0111emo do ta\u010dke koja je uzrok, a ne samo simptom. U ve\u0107ini slu\u010dajeva, problem koji vidimo je samo posledica ne\u010deg dubljeg \u0161to sistem ne re\u0161ava. Ako nam nije jasno kako ovo funkcioni\u0161e, mo\u017eemo se prisetiti jednostavnog primera sa decom: kada dete pita \u201eza\u0161to ptica leti\u201c, pa odgovorimo \u201ezato \u0161to ima krila\u201c, sledi novo \u201ea za\u0161to ima krila\u201c&#8230; I tako dalje, dok ne do\u0111emo do su\u0161tine. Ovaj proces mo\u017eemo posmatrati i kao borbu sa korovom. Ako ga samo pokosimo trimerom, izra\u0161\u0107e ponovo, verovatno jo\u0161 ja\u010di. Ali ako ga i\u0161\u010dupamo iz korena, i to pre nego \u0161to pusti seme, re\u0161ili smo problem u pravom trenutku.<\/p><p>U na\u0161oj primeni ovog alata, pristupamo sa osnovnim pravilom: ne tra\u017ei se krivac, ve\u0107 uzrok. Analizu radimo u okviru tima koji je najbli\u017ei procesu, uz uklju\u010divanje operatera, rukovodioca i podr\u0161ke (ako je problem lociran samo u jednom sektoru koristimo osnovni 5 why obrazac, a ako se problem pro\u017eima u nekoliko sektora koristim DMAIC). Ne koristimo unapred pripremljene forme koje niko ne razume, ve\u0107 konkretna pitanja, na konkretnoj situaciji, sa jasnim zapisom i zaklju\u010dkom. U nekim slu\u010dajevima se ne stane na pet pitanja, a nekad se do uzroka do\u0111e ve\u0107 kod tre\u0107eg. Va\u017eno je da postoji iskrenost i spremnost da se sagleda i sopstveni propust u organizaciji, a ne da se problem prebaci na nekog drugog.<\/p><p>SMED (optimizacija vremena promene proizvoda, changeover-a)<\/p><p>SMED (Single-Minute Exchange of Die) je metod koji se koristi za smanjenje vremena potrebnog za promenu alata, formata ili pozicije ma\u0161ine, sa ciljem da se cela zamena obavi u roku kra\u0107em od 10 minuta. To ne zna\u010di da mora da traje ta\u010dno jedan minut, ve\u0107 da ne prelazi jednu cifru; dakle maksimalno devet minuta i 59 sekundi.<\/p><p>U praksi, SMED po\u010dinjemo tako \u0161to posmatramo stvarni tok zamene i razdvajamo aktivnosti: \u0161ta mo\u017ee da se uradi dok ma\u0161ina jo\u0161 radi, a \u0161ta mora tek kada se ona zaustavi. Najve\u0107i gubici se javljaju zbog tra\u017eenja alata, \u010dekanja dokumentacije, ili lo\u0161e pripreme. Kada se sve \u0161to mo\u017ee obavi unapred, sama promena postaje br\u017ea i jednostavnija.<\/p><p>Metod je posebno koristan u firmama koje \u010desto menjaju artikle ili serije. Osim u\u0161tede vremena, SMED donosi stabilnost, manje stresa i ve\u0107u kontrolu nad planiranjem. Kada je sistem dobro postavljen, mogu\u0107e je raditi kra\u0107e serije bez pravljenja zaliha, a ma\u0161ina se koristi efikasnije.<\/p><p>Ovaj proces maksimalno ubrzavamo sortiranjem formatinih delova u sklopu 5S projekta.<\/p><p>Standardizovani rad (multifunkcionalne radne procedure i uputstva)<\/p><p>Standardizovani rad je dogovoreni najbolji trenutno poznat na\u010din za obavljanje odre\u0111enog posla. On ne slu\u017ei da bi ograni\u010dio radnike, ve\u0107 da bi obezbedio stabilnost, jasnu podelu koraka i merljivost procesa. Kada svi rade isti posao na razli\u010dite na\u010dine, te\u0161ko je otkriti gde se pravi gre\u0161ka, a jo\u0161 te\u017ee kako da se ne\u0161to unapredi.<\/p><p>U praksi, standardizacija po\u010dinje definisanjem klju\u010dnih koraka u operaciji, redosleda rada, potrebnih alata i vremena trajanja. Sve to dokumentujemo kroz jednostavne vizuelne standarde koji su jasno istaknuti na radnom mestu. Cilj nije da se napi\u0161e uputstvo za inspekciju, ve\u0107 da radniku i timu bude jasan dogovor: kako se radi, za\u0161to ba\u0161 tako, i \u0161ta je znak da ne\u0161to odstupa.<\/p><p>Kod uvo\u0111enja standardizovanog rada, uvek uklju\u010dujemo operatere jer upravo oni najbolje znaju gde su odstupanja i gde treba olak\u0161ati. Zatim svaka funkcija daje svoje inpute u zavisnosti od potrebe, a tako za radne procedure u proizvodnji ide slede\u0107i sled:<\/p><p>sugestije i povratne informacije operatera na ma\u0161inama su osnova<\/p><p>tehnologija (in\u017eenjering) daje opis koraka procesa<\/p><p>LEAN sektor ili tehnologija daju standardna vremena za operacije<\/p><p>zahteve za kvalitet daje sektor kvaliteta<\/p><p>zahteve za bezbednost i Z\u017dS daje HS sektor<\/p><p>LOTO (Lock Out Tag Out) i zahteve odr\u017eavanja ma\u0161ine defini\u0161e tehni\u010dka slu\u017eba<\/p><p>I Logistika oko planiranja proizvodnje i materijala<\/p><p>Kada se standard postavi, on ne ostaje fiksiran. Menja se kad god neko ponudi bolje re\u0161enje koje testiramo i potvrdimo. Na taj na\u010din, standard nije prepreka za pobolj\u0161anje, ve\u0107 osnova na koju se Kaizen nadovezuje.<\/p><p>TPM (proces odr\u017eavanja ma\u0161ina i opreme)<\/p><p>TPM, odnosno totalno produktivno odr\u017eavanje, pristup je u kojem svi u organizaciji u\u010destvuju u o\u010duvanju stabilnosti opreme. Za razliku od klasi\u010dnog modela gde operater radi dok ne do\u0111e do kvara, a onda zove majstora, TPM uklju\u010duje operatera u svakodnevne aktivnosti koje spre\u010davaju kvar. To nisu slo\u017eene popravke, ve\u0107 jednostavne radnje: \u010di\u0161\u0107enje, vizuelna kontrola, osnovne provere. Na taj na\u010din, odr\u017eavanje postaje deo svakodnevnog rada, a ne vanredna reakcija. Tehni\u010dki tim se vi\u0161e ne bavi sitnim intervencijama, ve\u0107 analizira i unapre\u0111uje sistem.<\/p><p>U praksi TPM uvodimo postepeno:<\/p><p>biramo kriti\u010dne ma\u0161ine,<\/p><p>defini\u0161emo dnevne ta\u010dke provere,<\/p><p>koristimo jednostavne check-liste i<\/p><p>pratimo stanje kroz Lean tablu.<\/p><p>TPM ne zamenjuje klasi\u010dno odr\u017eavanje, ali mu daje prednost jer omogu\u0107ava ranije otkrivanje problema, smanjuje broj hitnih intervencija i produ\u017eava radni vek opreme. Najva\u017enije: radnik vi\u0161e ne \u010deka da se ne\u0161to pokvari, ve\u0107 zna kako da ma\u0161inu svakog dana pripremi za stabilan rad.<\/p><p>VSM (mapiranje toka procesa)<\/p><p>VSM, Value Stream Mapping, je alat koji koristimo da vizuelno prika\u017eemo ceo tok jednog proizvoda, od narud\u017ebine do isporuke. Mapiranjem svakog koraka, uklju\u010duju\u0107i zalihe, \u010dekanja, prenose i transport, dobijamo jasnu sliku gde se gubi vreme, gde se gomila materijal i gde dolazi do prekida. Cilj nije da nacrt izgleda uredno, ve\u0107 da otkrije neefikasnosti koje nisu vidljive u svakodnevnom radu.<\/p><p>U praksi po\u010dinjemo tako \u0161to sa timom prolazimo kroz stvarni proces, direktno na terenu, korak po korak i prvo kroz Time Study analizu izmerimo svaku operaciju i zatim unosimo vremena izme\u0111u operacija; to sve unosimo na onu isprekidanu liniju (timeline). Ne oslanjamo se na teorijske tokove, ve\u0107 crtamo ono \u0161to stvarno postoji: koliko komada stoji izme\u0111u operacija, koliko traje \u010dekanje, da li postoji paralelni tok, kako se vr\u0161i kontrola kvaliteta. Na osnovu toga odvajamo aktivnosti koje stvaraju vrednost od onih koje samo zauzimaju prostor i vreme (zatim ide eliminacija).<\/p><p>Kada je mapa gotova, ona se koristi za dono\u0161enje konkretnih odluka: gde mo\u017eemo da spojimo korake, gde da smanjimo zalihe, gde da postavimo signal, gde da uvedemo standard. VSM se ne radi da bi bio oka\u010den na zid. Radi se da bi pokrenuo promenu. Kada uradimo VSM imamo Cycle Time (vreme koje nam je potrebno da uradimo jedan komad i upore\u0111uju\u0107i ga sa Takt Time-om mo\u017eemo kupcima davati povratnu informaciju kada ta\u010dno da o\u010dekuju robu, i mo\u017eemo planirati material i npraviti osnovu za JIT).<\/p><p>Vizuelna fabrika (Visual Management)<\/p><p>Vizuelna fabrika podrazumeva da su sve va\u017ene informacije dostupne tamo gde se posao obavlja, u realnom vremenu i bez potrebe za dodatnim obja\u0161njenjima. Umesto da zaposleni pitaju \u0161ta da rade, gde se \u0161ta nalazi ili \u0161ta se trenutno de\u0161ava, sistem im to pokazuje kroz boje, oznake, linije, table, signalne kartice ili svetlosne pokazatelje.<\/p><p>U praksi to zna\u010di da je raspored radnog mesta jasno obele\u017een, da su alati i materijali na svom mestu, da je status narud\u017ebine vidljiv bez otvaranja ra\u010dunara, i da je svaka promena u procesu odmah prepoznatljiva. Koristimo, na primer, Lean tablu sa odeljcima za bezbednost, kvalitet, proizvodnju i Kaizen aktivnosti, i vizuelne konture za alate, znakove za tok materijala, obele\u017eene prolaze i signalizaciju za zastoje.<\/p><p>Cilj vizuelnog menad\u017ementa nije estetika, ve\u0107 efikasnost. Dobra vizuelna organizacija skra\u0107uje vreme odlu\u010divanja, smanjuje verbalnu komunikaciju i spre\u010dava gre\u0161ke. Kada se jednom uspostavi, postaje osnov za standardizaciju i transparentnost u svakom sektoru. Osnova VM je 5S. Najbolje prakse su da se na radnim linijama instaliraju veliki monitori koji prikazuju KPI-eve (dashboard) i sve va\u017ene i relevantne informacijie na shopfloor-u.<\/p><p><span class=\"elc-sr-t\">LEAN tabla<\/span><span class=\"elc-en-t\" data-no-translation>LEAN board<\/span><\/p><p>Lean table je ne\u0161to \u0161to je proizvod mog dugogodi\u0161njeg rada i uvi\u0111anja potrebe za bitnim informacijama na jednom mestu i jedinstvenim na\u010dinom komunikacije. Ona je centralno mesto na shopfloor-u na kome se prikazuju klju\u010dne informacije o radu tima, proizvodnji, kvalitetu, bezbednosti i unapre\u0111enjima. Njena svrha nije da \u201elepo izgleda\u201c, ve\u0107 da tim u svakom trenutku zna \u0161ta je va\u017eno, \u0161ta se de\u0161ava i gde treba da se reaguje. Tabla mora da bude a\u017eurna, dostupna svima i organizovana tako da pru\u017ea jasan pregled bez potrebe za dodatnim tuma\u010denjem.<\/p><p>U praksi, Lean tablu delimo po funkcijama: bezbednost (npr. incidenti, za\u0161titna oprema), kvalitet (defekti, reklamacije, uzorci), proizvodnja (plan, realizacija, zastoji), i unapre\u0111enja (Kaizen predlozi, akcioni log). U sredini se \u010desto nalazi akcioni deo, gde se kroz Kanban pristup prati status svake otvorene aktivnosti: planirano, u toku, zavr\u0161eno. Time se vizuelno obuhvata PDCA logika bez dodatne papirologije.<\/p><p>Sastanci ispred table su kratki (scrum princip), sa jasnim redosledom i vo\u0111eni pitanjima, a ne izvla\u010denjem izve\u0161taja. Kada se tabla koristi dosledno, ona postaje alat za dono\u0161enje odluka, ne samo informativni pano. Vrednost Lean table nije u plastificiranim kolonama, ve\u0107 u tome \u0161to pokre\u0107e razgovor, zajedni\u010dku odgovornost i brzu reakciju kad ne\u0161to odstupi.<\/p><p>Andon (zaustavljanje linije usled neusagla\u0161enosti)<\/p><p>Andon je alat koji omogu\u0107ava operateru da zaustavi liniju ili da signalizira problem \u010dim ga uo\u010di, kako bi se spre\u010dila gre\u0161ka, kvar ili gubitak kvaliteta. Su\u0161tina je da problem ne ide dalje kroz proces, ve\u0107 da se re\u0161ava odmah, dok je jo\u0161 mali. Ovo je alat koji je Toyotu uzdigao najvi\u0161e, samo zato \u0161to je tada\u0161nji direktor dao poverenje \u201cludom\u201d radniku (tvorcu LEAN koncepta, kome su se kolege smejale) da sprovede svoje ideje u delo. U po\u010detku je bilo vi\u0161e zastoja nego pre, ali su proizvodne linije sve vi\u0161e napredovale!<\/p><p>U praksi, ovo je te\u0161ko implementirati jer mnogi menad\u017eeri proizvodnje poku\u0161avaju da dr\u017ee sve pod kontrolom, ne dozvoljavaju da se linija zaustavi bez njihove saglasnosti i zadr\u017eavaju odluke za sebe, mikromenad\u017eeri su. Andon tra\u017ei poverenje: da operater ima pravo da reaguje, a da tim lider odgovori bez osude. Kada postoji strah ili mikromenad\u017ement, sistem se formalno uvede, ali se ne koristi. U firmama koje su ga zaista prihvatile, Andon postaje osnovni refleks u spre\u010davanju ve\u0107ih problema.<\/p><p>Ovo je samo deo LEAN alata koje koristimo u praksi; postoji i \u0161iri spektar, ali smatram da je to predvi\u0111eno za ba\u0161 ure\u0111ene sisteme i da je apsolutno dovoljno za stvarenje petogodi\u0161nje strategije i osetnog rasta dovoljno da se i samo ovi alati implementiraju.<\/p><p>Kako radimo LEAN analizu: posmatranje o\u010dima radnika<\/p><p>LEAN analizu nikada ne po\u010dinjemo iz kancelarije. Ne gledamo prvo izve\u0161taje, ne otvaramo tabele i ne slu\u0161amo izlaganja rukovodilaca. Po\u010dinjemo tako \u0161to stanemo na ulaz proizvodnje i poku\u0161amo da posmatramo sve o\u010dima radnika. Kao da prvi put ulazimo u firmu i treba da obavimo zadatak, a niko nam ni\u0161ta nije objasnio.<\/p><p>Pogledamo gde radnik ulazi (kakav je ulaz, da li je bezbedan, da li neprotrebn zadr\u017eavju, da li je ozna\u010den adekvatno vertikalnom i horizontalnom signalizacijom), gde se presvla\u010di, da li zna gde ide, koliko mu treba da do\u0111e do radnog mesta. Da li su alati ve\u0107 spremni ili mora da ih tra\u017ei? Da li zna gde su mu dokumenti, koliko \u010desto mora da pita nekoga ne\u0161to? Gledamo kako se kre\u0107e: da li zaobilazi stvari koje mu smetaju, da li se savija, okre\u0107e, nosi ne\u0161to u rukama \u0161to mo\u017ee da se vozi. Posmatramo koliko ima \u201enesvesnog truda\u201c: ono \u0161to on vi\u0161e i ne vidi, jer se navikao, ali mi primetimo jer gledamo sve\u017ee.<\/p><p>Na primeru koji smo koristili: novi radnik dolazi u proizvodni prostor i poku\u0161ava da krene s poslom. Nema jasan raspored alata, mora da pita kolegu gde stoji slede\u0107i deo, vodi se logikom \u201etako radimo ve\u0107 godinama\u201c. Sto mu nije pode\u0161en po visini, kabl mu visi iznad glave, a za svaki korak mora da se malo savije ili istegne. U tom trenutku ve\u0107 imamo prvih deset potencijalnih gubitaka. I to bez da je proizvod jo\u0161 po\u010deo da se sklapa.<\/p><p>Prakti\u010dno, koristimo unapred pripremljen formular koji ne li\u010di na audit listu, ve\u0107 kao mapa za posmatranje: \u0161ta radnik tra\u017ei pogledom, koliko mu je jasno \u0161ta dalje, da li je sve na svom mestu, da li se ose\u0107a sigurno. Bele\u017eimo zapa\u017eanja bez osude i bez komentara: samo \u010dinjenice. Kada se kasnije vratimo, zajedno sa timom prolazimo kroz svaku ta\u010dku i postavljamo pitanje: za\u0161to je ovako i \u0161ta bismo mogli da promenimo da ne bude ovako.<\/p><p>Ovaj pristup ne tra\u017ei posebnu tehnologiju, samo otvorene o\u010di, empatiju i \u017eelju da sagledamo stvari onako kako ih vidi onaj koji posao zaista radi. Kada analizu po\u010dnemo od radnika, a ne od brojeva, onda i re\u0161enja koja predlo\u017eimo imaju smisla i \u0161ansu da opstanu.<\/p><p>Ukoliko imamo rukovodioce koji insistiraju na pristupu \u201cbi\u0107e kako ja ka\u017eem\u201d, bez posmatranja procesa i slu\u0161anja ljudi koji posao svakodnevno obavljaju, tada ne uvodimo sistem ve\u0107 name\u0107emo autoritet. U praksi se tada de\u0161ava da se problemi samo pomeraju, ali se ne re\u0161avaju. Gre\u0161ke se prikrivaju, ideje ne dolaze do izra\u017eaja, a radnici po\u010dinju da se povla\u010de u minimum anga\u017eovanja, jer ose\u0107aju da ono \u0161to ka\u017eu ni\u0161ta ne menja. To direktno uti\u010de na kvalitet, bezbednost i brzinu rada. Na kraju, linija radi, ali daleko ispod svog potencijala (\u0161to dosta sre\u0107emo u praksi), a gubici se vremenom gomilaju.<\/p><p>Lean analiza nije izazov za ne\u010diji ego, ve\u0107 prilika da se vidi ono \u0161to iz kancelarije nikada ne mo\u017ee da se razume. To \u0161to je neko rukovodilac ne zna\u010di da zna vi\u0161e: zna\u010di da mu je poverena ve\u0107a odgovornost da stvari vidi \u0161ire. Kada rukovodilac prvi ustane, pita, posmatra, zapisuje i tra\u017ei mi\u0161ljenje radnika, tada se stvara kultura u kojoj ljudi \u017eele da sara\u0111uju. Kada se, nasuprot tome, sve svodi na nare\u0111enje (\u201curadi kako ti ja ka\u017eem\u201d i \u201cja sam ovde glavni\u201d), tabele i kritiku, sistem ulazi u stanje otpora; to je katastrofalna situacija za firmu, jer glavni zup\u010danik ko\u010di i zapinje, i vrlo \u010desto, gotovo uvek \ud83d\ude0a, ga ko\u010de upravo oni kojima je dato poverenje od strane vlasni\u010dke structure i direktora (nekada uklju\u010duju\u0107i i njega) da taj zup\u010danik \u201cpodma\u017eu\u201d i pravilno podese.<\/p><p>Najuspe\u0161niji timovi nisu oni u kojima svi \u0107ute dok \u0161ef pri\u010da, ve\u0107 oni u kojima se ljudi slobodno izra\u017eavaju jer znaju da ih neko stvarno slu\u0161a. A Lean analiza, ako je iskreno sprovedena, upravo to pokazuje: gde sistem ko\u010di ljude, a ne gde ljudi ko\u010de sistem.<\/p><p>LEAN vs ISO standardi: dva sveta, dve logike<\/p><p>Jedna od naj\u010de\u0161\u0107ih zabluda u firmama jeste uverenje da ako postoji ISO standard, onda su svi procesi ve\u0107 dovoljno ure\u0111eni i nema potrebe za Lean-om. U praksi, me\u0111utim, to vrlo brzo padne u vodu. ISO je odli\u010dan okvir za uspostavljanje sistema upravljanja, ali je fokusiran na dokazivanje uskla\u0111enosti a ne na efikasnost. Njegov cilj je da postoji dokumentacija, da postoji procedura i da postoji zapis. ISO ne pita koliko vremena se gubi, da li radnik razume proces ili da li postoji bespotrebno kretanje i \u010dekanje u proizvodnji. To je u najboljoj liniji kada je ISO u potpunosti \u017eiv i implementiran, a mo\u017eete sada sagledati kakva je situacija u ve\u0107ini firmi gde je ISO standard uveden \u201cpro forme\u201d, postoji \u201ctamo neki zaposleni koji je zadu\u017een za ISO\u201d i sve se svodi da se kampanjiski prikupi dokumentacija pred nadolaze\u0107u sertifikaciju\ud83d\ude0a.<\/p><p>LEAN, s druge strane, kre\u0107e od pitanja: gde se gubi vreme, novac, energija i motivacija? Gde je posao su\u0161tinski te\u017ei nego \u0161to bi trebalo da bude? Gde sistem usporava \u010doveka umesto da ga podr\u017eava? Lean ne zanima da li postoji document: zanima ga da li ono \u0161to radnik svakog dana radi ima smisla, ritam i podr\u0161ku.<\/p><p>Zato je sasvim mogu\u0107e, i vrlo \u010desto se de\u0161ava, da firma ima ISO 9001, ISO 14001, ISO 45001, i da i dalje ima haos u procesu, zastoje, nezadovoljne ljude, visoke tro\u0161kove i preoptere\u0107ene rukovodioce. ISO ne re\u0161ava te probleme jer nije tome namenjen. On tra\u017ei evidenciju, proceduru i kontrolu, ali ne ulazi u dubinu svakodnevnog toka rada. Lean upravo to radi: ide do mesta gde nastaje vrednost, posmatra tok, uklju\u010duje ljude i uklanja suvi\u0161no.<\/p><p>U svom radu ne suprotstavljamo ISO i Lean. Naprotiv: koristimo najbolje iz oba sveta da kupcima i klijentima poka\u017eemo da na\u0161 sistem efikasno funkcioni\u0161e i da nemaju razloga za brigu. ISO daje strukturu, Lean daje \u017eivot. Kada se spoje, dobijamo sistem koji ne postoji samo zbog sertifikata, ve\u0107 sistem koji funkcioni\u0161e jer ljudi znaju \u0161ta rade, za\u0161to to rade i kako da to svakog dana rade bolje.<\/p><p>Ko ne mo\u017ee da vodi LEAN i za\u0161to svaka firma to ne uspeva<\/p><p>LEAN u teoriji deluje jednostavno. Alati su poznati, procesi mogu da se mapiraju, vizuelni sistem se mo\u017ee uvesti relativno brzo. Ali to je samo forma. Su\u0161tina le\u017ei u ljudima i tu ve\u0107ina firmi padne. Ne zbog alata, ve\u0107 zato \u0161to ga poku\u0161avaju voditi oni koji organizaciju vide kao sopstvenu teritoriju, a ne kao \u017eivi sistem koji mora da raste i razvija se sa ljudima, ne mimo njih. \u010cesto se de\u0161ava, ono \u0161to se mnogi pitaju \u201cpo hodnicima\u201d firme za\u0161to je ba\u0161 ta osoba anga\u017eovana ako s ve\u0107ini \u010dini da nije dobro re\u0161enje. Firmama se to de\u0161ava jer ne biraju rukovodioce po sposobnosti da razvijaju sistem, ve\u0107 po sposobnosti da &#8222;deluju odlu\u010dno&#8220;. U kulturi gde je autoritet poistove\u0107en s glasno\u0107om, a kontrola s pritiskom, ljudi koji vi\u010du, nare\u0111uju i \u201ezavode red\u201c lako se do\u017eivljavaju kao sposobni menad\u017eeri. Oni su \u010desto vidljivi, uvek uklju\u010deni, reaktivni i prvi koji \u201ene\u0161to preduzimaju\u201c, i na prvi pogled ostavljaju utisak akcije.<\/p><p>Ali tu le\u017ei zamka, jer takvi ljudi ne vode sistem, oni ga kompenzuju. Sve \u0161to se ne re\u0161ava kroz strukturu, oni poku\u0161avaju da re\u0161e kroz sebe. I dokle god su prisutni i sve dr\u017ee pod rukom sistem nekako funkcioni\u0161e. Ali kada ih nema, nastaje haos. I \u0161to je najgore oni to i znaju, i zato sve vi\u0161e centralizuju kontrolu.<\/p><p>S druge strane, ti\u0161i, stalo\u017eeniji, sistemski orijentisani ljudi, koji bi verovatno bolje vodili firmu na du\u017ee staze, \u010desto nemaju \u201escensku mo\u0107\u201c. Ne prave buku. Pitaju, slu\u0161aju, uvode stvari kroz ljude. I zato ih mnogi pogre\u0161no procene kao \u201eslabe\u201c. U kulturi gde se tra\u017ei brz rezultat, jasno nare\u0111enje i neko ko &#8222;preuzima odgovornost&#8220;, takvi ljudi \u010desto budu ignorisani ili zaobi\u0111eni, jer deluju kao da \u201enisu lideri\u201c.<\/p><p>Su\u0161tina problema je \u0161to firme jo\u0161 uvek vi\u0161e nagra\u0111uju kontrolu nego izgradnju sistema. A Lean upravo razotkriva taj model, jer pokazuje da prava snaga firme nije u energiji pojedinca, ve\u0107 u stabilnosti sistema koji ne zavisi od pojedinca.<\/p><p>Zabluda je i da Lean mo\u017ee da vodi bilo ko ko je \u201edovoljno fleksibilan\u201c i \u201evoli ljude\u201c. U praksi, de\u0161ava se i druga krajnost: da osoba koja vodi Lean nema autoritet, ne ume da postavi granice, izbegava sukob i stalno se povla\u010di pred otporima. Tada Lean postaje teorijska pri\u010da, puni se tabla zadacima, dr\u017ee se sastanci, ali se su\u0161tinski ni\u0161ta ne menja. Ljudi brzo prepoznaju da iza re\u010di ne stoji odluka i sistem po\u010dinje da se raspada iznutra.<\/p><p>Zato, Lean ne mo\u017ee da vodi neko ko se boji da postavi pitanje, da zatra\u017ei promenu, da se zameri. Ali isto tako, ne mo\u017ee da ga vodi ni neko ko komanduje bez razumevanja procesa i bez povezivanja sa ljudima. Potreban je balans. Potrebna je osoba koja ima karakter da izdr\u017ei otpor i poniznost da zna da sistem nije tu zbog nje, ve\u0107 zbog tima i kupca. Samo tada Lean mo\u017ee da za\u017eivi: ne kao projekat, ve\u0107 kao na\u010din rada.<\/p><p>Osoba koja vodi Lean mora da zna da nije u centru ve\u0107 sa strane, u slu\u017ebi procesa. Ne mo\u017ee ga voditi neko ko ne silazi u pogon, ko ne zna da saslu\u0161a operatera, i ko veruje da se problemi re\u0161avaju iz komandne kancelarije. Jo\u0161 te\u017ee, ne mo\u017ee ga voditi neko ko sve dr\u017ei za sebe, ko ne delegira, ko se bavi mikromenad\u017ementom, i ko misli da Lean zna\u010di \u201eja sam taj koji zna kako treba\u201c.<\/p><p>Mikromenad\u017ement je najve\u0107i neprijatelj Lean-a. On gu\u0161i inicijativu, pretvara rukovodioce u pasivne izvr\u0161ioce, i \u0161alje poruku da se ni\u0161ta ne menja bez dozvole. U takvom sistemu, ljudi ne predla\u017eu jer znaju da \u0107e biti ignorisani, a Kaizen postaje kutija koja skuplja pra\u0161inu. Umesto da Lean sistem razvija ljude, de\u0161ava se suprotno: sistem zavisi od jednog \u010doveka koji \u201evu\u010de\u201c sve. A to nikada ne traje dugo.<\/p><p>Zato svaka firma ne uspeva. Ne zato \u0161to nema sredstva, alate ili podr\u0161ku, ve\u0107 zato \u0161to ne postoji osoba koja zna kako da pusti sistem da di\u0161e, i kako da vodi kroz druge, a ne preko njih.<\/p><p>Zato je va\u017eno da osoba koja vodi Lean zna kako se gradi tim i kako se donosi odluka kroz saradnju. U mojoj praksi koristimo pristup zasnovan na Scrum modelu, inspirisanom ragbi timom (Ameri\u010dkim fudbalom). Za razliku od tradicionalnog sporta gde igra\u010d dobija loptu, pa svi \u010dekaju da on napravi potez, u ragbiju ceo tim gura zajedno, u isto vreme, istom snagom, u istom pravcu i te dogovoren akcije traju veoma kratko i efikasno. Nema \u010dekanja komande, nema gledanja ko je lider: svi znaju svoju ulogu i kre\u0107u zajedno, jer znaju da se cilj posti\u017ee samo ako niko ne stane.<\/p><p>Upravo to prenosimo i na na\u010din kako vodimo tim i sastanke: svi u\u010destvuju, svi znaju gde je prepreka i svi su deo re\u0161enja. Scrum tim ne funkcioni\u0161e kao lanac komandi, ve\u0107 kao dinami\u010dna jedinica koja se sama organizuje, svakog dana prilago\u0111ava i donosi mikro-odluke bez potrebe za odobrenjem \u201eodozgo\u201c. Zbog toga ovaj model ne samo da ubrzava rad, ve\u0107 ja\u010da odgovornost i me\u0111usobno poverenje, a to su temelji svakog Lean sistema koji zaista radi.<\/p><p>Zaklju\u010dak: Lean nije sistem, Lean je ogledalo<\/p><p>Uvo\u0111enje Lean-a nije projekat. Nije ni tabela, ni alat, ni izve\u0161taj za audit. Lean je ogledalo i to ono najiskrenije koje firma mo\u017ee sebi postaviti. A svako ogledalo mo\u017ee da prika\u017ee dve slike: ono \u010dime se ponosimo, i ono \u0161to skrivamo.<\/p><p>U firmama koje nisu spremne da pogledaju u to ogledalo Lean ostaje plastificirani pano na zidu. Rukovodioci se bave brojkama koje ne razumeju, sastanci postaju \u010ditanje problema bez hrabrosti da se u njih u\u0111e, a radnici nau\u010de da \u0107ute i rade \u201csvoje\u201d. Sistem i dalje funkcioni\u0161e, ali \u0161kripi, gubi, tro\u0161i ljude, nervira partnere i na kraju ko\u0161ta. Ne na papiru, nego u profitu. U vremenu. U zdravlju tima.<\/p><p>Ali u firmama koje se usude da stvari sagledaju iskreno Lean menja sve. Ne preko no\u0107i, ne kao reklama, nego iz temelja. Menja ritam. Menja logiku. I ono najva\u017enije menja odnos me\u0111u ljudima. U takvim firmama rukovodioci ne vi\u010du ve\u0107 slu\u0161aju. Ne re\u0161avaju sve sami ve\u0107 pokre\u0107u druge da misle. I ne tra\u017ee izve\u0161taje da bi \u201cimali pokri\u0107e\u201d ve\u0107 da bi znali gde da pomognu.<\/p><p>Mnogi tra\u017ee \u201cre\u0161enje\u201d kao u savremenoj medicine: brzo, da ubla\u017ei simptom. Lean to ne radi. Lean ne le\u010di simptome. Lean kopa do uzroka. A za to treba strpljenje, disciplina i karakter. Zato ga ne mo\u017ee voditi bilo ko. Zato i ne uspeva svuda. Ali tamo gde uspe: firma ne samo da pre\u017eivi, ve\u0107 postaje primer drugima.<\/p><p>Za kraj: ako ste direktor, vlasnik, ili neko kome je poverena firma, proces da vodite ili ljudi: Lean nije tro\u0161ak, ve\u0107 ulaganje u zdrav razum. U sistem koji ne zavisi od jednog \u010doveka. U kulturu u kojoj rad ima smisla. I u firme koje vi\u0161e ne rade \u201epod pritiskom\u201c, ve\u0107 sa ciljem.<\/p><p>Ako ste spremni da preispitate sve, uklju\u010duju\u0107i i sebe, Lean mo\u017ee biti najzdravija stvar koju ste ikada uveli.<\/p><\/section><\/main><\/div>\n<div class=\"elc-og-wrap og-en-x elc-en-t\" data-no-translation><nav class=\"elc-og-toc\"><h3>Contents<\/h3><a href=\"#en-predgovor\"><span>01<\/span>FOREWORD<\/a><a href=\"#en-sta-je-zapravo-lean-razbijanje-mita\"><span>02<\/span>What LEAN really is: breaking the myth<\/a><a href=\"#en-kako-je-lean-nastao-istina-koju-mnogi-preskacu\"><span>03<\/span>How LEAN came to be: the truth many people skip<\/a><a href=\"#en-osnovni-elementi-lean-a-kuca-koja-se-ne-gradi-powerpointom\"><span>04<\/span>The core elements of LEAN: a house you don&#8217;t build with PowerPoint<\/a><a href=\"#en-vazni-lean-alati-i-koncepti\"><span>05<\/span>Important LEAN tools and concepts<\/a><\/nav><main><section class=\"og-section\" id=\"en-predgovor\"><div class=\"og-num\">01<\/div><h2>FOREWORD<\/h2><p>With business conditions getting tougher, resources running short, market dynamics becoming unpredictable and fewer and fewer good people available, companies today don&#8217;t have many options: either they optimize their processes and empower their people, or they suffocate in daily firefighting.<\/p><p>That is exactly why this practical guide was written: as a tool that helps companies become resilient, organized and stable; not through theory, but through real application of the LEAN approach in practice.<\/p><p>This guide is not academic literature. It is a summary of years spent in factories, among machines, talking with people who know what it means to fight for every piece and every hour. It was made to be used, not read once and forgotten. You won&#8217;t find complicated expressions, unnecessary jargon or detailed ready-made solutions in it: instead, you&#8217;ll find a roadmap to solutions that work in both small and large companies, in real conditions, in the real world.<\/p><p>Who is it for? This guide is for young and ambitious managers who want to set things up the right way and know how to do it.<\/p><p>For business owners who want a system that isn&#8217;t based on luck. For directors who no longer want to listen to excuses, but want to see results.<\/p><p>For managers who want to transform into leaders. And let&#8217;s be honest: it is not for those who know everything best. They can wait for the next audit.<\/p><p>If you have a clear strategy, if you don&#8217;t mind taking a hard look at both yourself and the system, and if you want a team that knows what it&#8217;s doing and why, this guide will help you get there. And remember:<\/p><p>\u201cOur only security is our ability to change.\u201d (John C. Lilly)<\/p><\/section>\n<section class=\"og-section\" id=\"en-sta-je-zapravo-lean-razbijanje-mita\"><div class=\"og-num\">02<\/div><h2>What LEAN really is: 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, put makeup on their processes, or go back to the old way of organizing things.<\/p><p>Why? Because they think LEAN is \u201csomething you can buy, learn at a seminar and wrap up in three months.\u201d The common practice today is for companies to send their employees to various seminars where they earn certain belts (yellow, green, black belt&#8230;), and then the company considers that it has gained a LEAN expert who will be \u201cin charge\u201d of LEAN.<\/p><p>The same thing happened for years with safety, when companies appointed people responsible for it: walk the shop floor, talk to one of the production managers about safety topics, and he&#8217;ll tell you that some guy named Marko is in charge of and responsible for that. The situation changes at the root when global trends change, in Europe and in our region too, where legislation, taking safety as an example, makes it clear that there is no single \u201cresponsible person\u201d for safety, but rather a safety advisor or safety officer. This clearly implies that this person is obliged to teach colleagues in the company about safety, and that everyone is responsible for safety within their own scope of work. The same principle applies to LEAN.<\/p><p>Let&#8217;s go back to one of the official LEAN definitions everyone quotes: \u201cLean is a management philosophy focused on maximizing customer value by eliminating waste in the process.\u201d It sounds smart and seems useful. But let&#8217;s be honest: how many of the people who say it actually know what \u201cwaste\u201d means? And how many of them have ever spent more than 10 minutes standing next to an operator who assembles 800 pieces of a product a day, actually observing the process that way? In most cases the process is analyzed with standard tools, such as bottleneck analysis, VSM and similar tools learned at seminars, but without any deeper connection to the reality on the shop floor.<\/p><p>Based on my many years of experience, we could come up with a definition of LEAN, but through the lens of practical work and working with people on the shop floor:<\/p><p>LEAN is a brutally honest company mirror: it shows what&#8217;s wrong, every single day, and demands that leaders have the courage to fix it, together with their people, not over their heads.<\/p><p>Here are a few general examples so we can tell the difference:<\/p><p>In a LEAN company, the director doesn&#8217;t sit in the office all day, but goes to the shop floor once a day: not to control, but to see, ask and learn. He leads by example: during the walk he wears all the required protective equipment, just like the workers he visits, and follows all the rules.<\/p><p>In a LEAN company, the manager doesn&#8217;t make plans in Excel that have nothing to do with reality, but plans according to the rhythm of production and the voice of the operators.<\/p><p>In a LEAN company, when a problem occurs, the first question is: \u201cWhat did the system fail to support?\u201d, not \u201cWho is to blame?\u201d<\/p><p>In a LEAN company, the manager doesn&#8217;t pull targets out of thin air: he uses data from the floor, from production, and aligns it with the real capacity of people and machines.<\/p><p>In a LEAN company, problems are not hidden until \u201cafter the audit\u201d, but are flagged immediately, because hiding a problem is a disgrace and solving it is an honor.<\/p><p>In a LEAN company, the daily meeting lasts 10 minutes at most, standing, with one board and a clear focus: safety, quality, and what must not stop today.<\/p><p>In a LEAN company, the best worker is not the one who works fastest, but the one who sees a problem and says: \u201cThis makes no sense: let&#8217;s change it.\u201d<\/p><p>In a LEAN company, the line supervisor doesn&#8217;t shout \u201cFaster!\u201d, but asks: \u201cWhy are we behind? What do you need to make it run smoothly?\u201d<\/p><p>In a LEAN company, a Kaizen suggestion doesn&#8217;t die in a box: a worker&#8217;s idea is dealt with within 5 days and the person who suggested it gets feedback.<\/p><p>In a LEAN company, when new equipment arrives, engineering doesn&#8217;t decide alone: operators give their input, because they are the ones who will work with it every day.<\/p><p>Before we go deeper into the analysis, a few words about me, the person who took the trouble to put together this little guide, looking at things from a slightly different, practical and above all unusual angle\ud83d\ude0a.<\/p><p>My name is Nemanja Krsti\u0107, and for more than 17 years I have been working on improving production processes, occupational safety and implementing LEAN principles across different industries: from food, textile, electrical and construction to chemical and defense manufacturing. I hold a master&#8217;s degree in engineering, and I built my practical knowledge through direct work on the shop floor, with people and machines, in real conditions where every hour and every piece makes the difference between profit and loss.<\/p><p>I have worked as a LEAN, EHS and QA manager, HR manager, logistics and planning manager, production director and facility specialist in domestic and international companies, and at the start of my career I volunteered at 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 \u201ctextbook examples\u201d, but on real challenges in factories weighed down by chaos, paperwork, subjective decisions and a lack of systems. My goal was never to implement LEAN so the company would have a \u201cnice report\u201d, but to create an environment where people can work without wasting time, without stress and with clarity at every step. Over the years I have developed my own methods for connecting teams, building mutual trust and securing lasting results that don&#8217;t depend on one person or one system, but on daily learning and stable process management.<\/p><p>This guide is not a theoretical handbook. It is the result of work on the shop floor, conversations with workers, my own failures and shared ones, ups and downs, attempts, and finally results. I am writing this to help managers who have a real chance to make a difference, but need the right framework to know where to start.<\/p><\/section>\n<section class=\"og-section\" id=\"en-kako-je-lean-nastao-istina-koju-mnogi-preskacu\"><div class=\"og-num\">03<\/div><h2>How LEAN came to be: the truth many people skip<\/h2><p>Today a lot of people talk about LEAN as some modern management method that comes from the West. The truth is completely different. LEAN was not born in the offices of wealthy businessmen, it did not come out of American university labs, and it was not the result of research by multinational corporations. LEAN was born out of poverty and desperation, in postwar Japan, where there was no money, no resources and no time for mistakes.<\/p><p>After World War II, Japan was devastated. Industry had collapsed, there were no materials, and the workforce was exhausted. Toyota, at the time still a small local company, could not compete with the big Western giants that produced in large batches and held huge inventories. So they had to come up with a different way of producing. Not faster or harder, but smarter.<\/p><p>That is how they began developing what would later become known as the Toyota Production System (TPS), a system built on common sense, respect for people and solving problems every day. What is special about Toyota is not just the system, but the culture, where everyone has the right to stop the line if they see a defect, and where a leader is chosen not because of a title, but because he knows how to listen, how to see, and how to ask \u201cwhy\u201d five times if needed.<\/p><p>LEAN was not called LEAN. They never called it that. Even today the term is hardly used at Toyota. The name came much later, when Western experts tried to \u201cpackage\u201d what they had seen at Toyota into some universal method.<\/p><p>The term \u201cLean production\u201d was first used in 1988, in MIT research that led to the book \u201cThe Machine That Changed the World\u201d. In that book Toyota was presented as the best example of efficient production in the world, and the word \u201clean\u201d was chosen to describe a system that uses less of everything: less inventory, less space, fewer defects, less time, but with more value for the customer.<\/p><p>Unfortunately, what happened next is that many people took LEAN as a tool, as a project, as something that can be \u201cimplemented\u201d through four workshops and 3 spreadsheets. And that is where the decline starts. Because LEAN was never a reporting system; it was a way of thinking and behaving at every moment, in every place.<\/p><p>So when someone says to me today, \u201cLet&#8217;s implement LEAN\u201d, my first question is: \u201cAre you ready to question everything you are doing right now, including your own habits, attitudes and decisions? Are you ready to change yourselves, as the top of the hill, as management?\u201d<\/p><p>If management is not ready, it is better not to start. Even the beginning will just be one more PowerPoint file in your recycle bin.<\/p><\/section>\n<section class=\"og-section\" id=\"en-osnovni-elementi-lean-a-kuca-koja-se-ne-gradi-powerpointom\"><div class=\"og-num\">04<\/div><h2>The core elements of LEAN: a house you don&#8217;t build with PowerPoint<\/h2><p>LEAN is not a theoretical model from a book. And it is not that \u201cToyota house\u201d from a slide. In the real world, where products are made, LEAN is built out of chaos. And the foundation of that house is not Just in Time, not Kanban (which everyone grabs first), and not Jidoka for quality management; those come later, as an upgrade. The real foundation of LEAN, from my many years of experience, is 5S and safety. These are the elements management must put in place right away, while also opening up room for workers to actively take part in process optimization, and that is Kaizen. I see Kaizen (the process of suggesting ideas) as the waterproofing on the foundation of a stable building, which keeps the foundation from \u201ccracking\u201d in the future.<\/p><p>Whoever doesn&#8217;t understand this can forget about belts, certificates, flow charts and bottleneck analysis. All of it stays a dead letter on paper if the three basic elements (5S, safety and Kaizen) don&#8217;t exist, and if they are not carried by genuine empathy from management. These three principles are not technical matters, they are the basis of the company culture. When that is the foundation, the house can grow.<\/p><p>I always start from one simple truth: the operators on the machines are the ones who bring money into the company. They are the heart. Everything else, including us in management, HR, quality control, planning, logistics, and even sales itself, is just support. A service. And like any service, we can speed up that flow of money, take the load off it, or simply ruin it.<\/p><p>If a worker doesn&#8217;t know where his tools are, if he has no room to turn around normally, if there is a wheel under his feet and a cable hanging over his head, and he has to put his hands into a machine without guarding: there is no LEAN there. There is improvisation. And improvisation is the most expensive item in a company, it just usually isn&#8217;t measured right away.<\/p><p>That is why my LEAN house looks like the one in Figure 1.<\/p><p>Figure 1: The LEAN house from my perspective<\/p><p>This LEAN house is not a drawing for a presentation, it is the mirror of a serious organization. Each layer has its own role, and together they work as a system capable of withstanding the pressure of daily production, market unpredictability and the increasingly frequent internal crises in companies.<\/p><p>The foundation of the house is made up of three deeply rooted layers. The first is the company&#8217;s long-term strategy, vision and mission. That is not words on paper for the website, the way companies usually write that text because they consider it a \u201cformality\u201d, but a clear direction that gives meaning to all everyday decisions. If a company changes course every six months, LEAN cannot take root, because everything people build is wiped out by the first change in priorities. The long-term strategy and key policies are defined by the owners, with clearly defined development milestones. The vision is the end point the company should reach once it achieves that strategy, and the mission is the path taken to reach that strategic point. The mission is defined by the director and his team, through operational goals, procedures and plans.<\/p><p>On top of that strategic layer sits 6S, the combination of the 5S methodology and occupational safety. Without order, organization and safety there is no stable process. If a worker doesn&#8217;t know where his tools are, if cables are tangled under his feet, if he doesn&#8217;t know whether he is allowed to touch the machine, the system is not under control.<\/p><p>What connects stability with everything above it is Kaizen, everyday, common-sense improvement. It is not a big project. Kaizen is the question: \u201cDoes this make sense?\u201d Kaizen is the waterproofing between the foundation and the wall. You can&#8217;t see it, but without it the system soon starts cracking from the inside.<\/p><p>The house then rises on three pillars. The first is management and leadership. Both terms are there on purpose, because one does not automatically come with the other. You can be a manager without leadership, and then people fear you but don&#8217;t follow you. You can be a leader without a position, and then people listen to you because they trust you, not because they have to. The real pillar is formed when management knows it is not there to command, but to serve. That is called leadership.<\/p><p>The second pillar is people and teamwork. Without engaged people there is no LEAN culture. Without mutual trust, every change is experienced as a threat. If a company has \u201cthem up there\u201d and \u201cus down here\u201d, the house splits in half.<\/p><p>The third pillar is LEAN tools. Only here do we get to visualization (visual management), VSM, A3, Takt time, standard work, SMED, JIT, Kanban and the rest. They are important, but they are not the essence. Without the first two pillars, the tools become one more PowerPoint file in the archive.<\/p><p>All the pillars are tied together by the layer of KPIs, targets, triggers and the DMAIC process. Without measurement, everything is subjective. Goals without numbers are just wishes. A KPI must be clear, fair and functional, not so that people can be punished, but so that we know where help is needed. A KPI is a formula that gives us a measuring scale. On that scale we add a point we define as the goal, the so-called target, and we precisely define the process we are measuring. What I insist on in practice, and what you very rarely see in companies because everyone deals only with targets, is a lower value point on the KPI scale, the so-called trigger. It is what sets off the DMAIC investigation process when the value of a KPI drops to a critical level. DMAIC (Define, Measure, Analyze, Improve, and Control) is a very powerful LEAN tool that enables a team investigation of nonconformities. It includes Ishikawa, 5 Why, brainstorming and other approaches.<\/p><p>Finally, the roof is satisfied customers and quality. That is what can be seen from the outside. If the customer is satisfied and quality is stable, it means all the layers below are working.<\/p><p>At the very top is the guiding star. That is Business Excellence. It is what we strive for in every process. Companies can define the KPIs they will use to measure business success: efficiency, effectiveness, OEE and others. Top management sets the targets for them every year. For example, the target for process efficiency might be around 75 percent, but for a company to reach business excellence, efficiency must be at least 95 percent, quality 99 percent, and effectiveness at least 90 percent. That means overall OEE must be at least 85 percent.<\/p><\/section>\n<section class=\"og-section\" id=\"en-vazni-lean-alati-i-koncepti\"><div class=\"og-num\">05<\/div><h2>Important LEAN tools and concepts<\/h2><p>LEAN is not a single tool. LEAN is a philosophy. But like every good philosophy, without practical tools it stays just a story for PowerPoint. In my practice I use specific, basic tools that work, although much more demanding tools can of course be applied as well. Here are the basic ones:<\/p><p>5S + Safety = 6S (organizing workspaces to speed up processes and reduce risk)<\/p><p>5S is not some Japanese exotica or \u201csome methodology for cleanliness\u201d; it is the first thing a serious company has to introduce before it even says the word LEAN.<\/p><p>The name 5S comes from five Japanese words that describe the order of activities:<\/p><p>Seiri (Sort): removing everything that is not needed from the workstation. Screws that are never used, tools kept \u201cjust in case\u201d: all of it creates confusion and takes up space. On the shop floor this means: if you don&#8217;t need it, get rid of it. In this phase we put red tags on all the equipment and tools we don&#8217;t need, and after a certain period they are moved to the 5S zone and taken away from the workstations.<\/p><p>Seiton (Set in order): once we have removed everything we don&#8217;t need from the workstation, we analyze what we use and how often (frequency of use), and then we arrange tools and equipment so that the things we use most are at hand (close to us) and, where possible, in the golden zone (Golden Area: from waist to chest).<\/p><p>Seiso (Shine): cleaning the workspace, not for the shine, but for control and maintenance. When we wash the machines, we also see leaks, for example. When we clean, we are actually inspecting.<\/p><p>Seiketsu (Standardize): once we have arranged and cleaned everything, we standardize it (we photograph how the workstation should look, put outlines behind hanging equipment, and create a visual standard for each workstation). A visual standard is essentially a poster that shows where everything belongs at that workstation.<\/p><p>Shitsuke (Sustain): 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 falls apart. If you repeat it, it becomes natural. That is why we do cross audits with checklists, so that over time each workstation is constantly reviewed by several levels of employees.<\/p><p>In my practice, I never talk about 5S without adding a sixth S: Safety. Safety is not an add-on. Safety is the precondition for everything. If a person has to step over boxes to get to the machine, if a cable hangs above their head, or if a screwdriver stays stuck in the table: that is not messy, that is dangerous. And everything that is dangerous eventually becomes expensive too.<\/p><p>5S + Safety means that when you finish a 5S inspection, you don&#8217;t just say \u201cit looks nice\u201d, but also \u201cit is safe for a person to spend eight hours here\u201d. And that is the difference between a company that plays at LEAN and a company that lives LEAN.<\/p><p>In some companies I have seen 5S exist \u201con paper\u201d: they have nice before and after photos, everything shines for one day. And after that everything goes back to how it was. Why? Because they had no leader who would be the first to \u201cput the tools in order\u201d (launch the project and lead by example), and they had no culture in which order is maintained because everyone believes it should be, not because an inspection is done pro forma or for an audit.<\/p><p>So 5S and Safety are not a tool. They are a habit. And habits are built every day. If you miss that: there is no LEAN. There is no production either. There is only the struggle to catch up with what you made complicated for yourself.<\/p><p>Bottleneck Analysis<\/p><p>Bottleneck analysis is the basic step in understanding the capacity of a production system. There is always a point in the process that limits the flow, and it is not determined arbitrarily, but by precise measurement. In my practice I rely on time study methodology, through which I define standard times for every operation in the process. By comparing those times and analyzing how often stoppages occur, it is possible to clearly identify where things are being held up. The bottleneck does not have to be on the line only; it can also appear in preparation, inspection, logistics or planning. That is why the analysis has to be comprehensive and done periodically. Once the bottleneck is identified, you move on to removing it, which does not always mean new investment. In a large number of cases, smaller operational adjustments are enough: changes to the work schedule, adjusting the takt time, or redistributing tasks. A properly conducted bottleneck analysis allows a company to increase its total capacity without extra stress on resources and without complicated reorganizations.<\/p><p>It often happens in practice that production managers, not knowing this analysis, assign more workers to some process on the production line (a specific point) where they are pure surplus and not needed, while somewhere else workers are missing. When you talk to them before the analysis, they consider this impossible and flatly reject it. The goal of these analyses is not to \u201cwrestle\u201d with anyone or prove who is right, but to use an engineering approach to prove that the process is not set up well and that the company has an unnecessary loss.<\/p><p>GEMBA (shop floor walks and control with checklists)<\/p><p>A Gemba walk is a LEAN practice in which a manager goes directly to the place where the work is actually done: where value is created (the shop floor). It is not about supervision or control, but about learning through observation and conversation. In my practice, a Gemba walk includes structured observation of the process with checklists, which are used for cross audits: not only of 5S and safety, but of all key work processes. This checks whether the work is really being done according to standards, whether there are hidden obstacles, and where time or quality is being lost.<\/p><p>The walk has to have a clear focus and must not last longer than a few minutes per location. The most important thing is to ask the right questions: what makes your work harder, where is the process unclear to you, what bothers you every day. Only that way do we get to the real problems, and also to real improvement suggestions. A Gemba walk is most effective when it becomes a routine and when people realize that the manager does not come to look for mistakes, but to remove obstacles. We come across workers who do their job in different ways; regardless, we always first praise what they do well (even if it is only 10 percent; before that we \u201cbreak the ice\u201d with some positive conversation), then we ask open questions so they can explain how they work, and we never leave the spot and the conversation until we get a promise (with a smile) that the worker and the process will improve.<\/p><p>Heijunka (production planning optimization)<\/p><p>Heijunka is a method of production leveling whose goal is to reduce variation in the load on the line, the material flow and the use of people. In practice, this means planning production so that you avoid working in waves: days of overload and days when activity drops. For example: instead of making ten thousand pieces of one item and then not making that item for days, Heijunka means rhythmic, evenly distributed production of different items in line with real customer demand.<\/p><p>The biggest challenge with Heijunka in local companies is planning; companies often make a plan that \u201clooks nice\u201d on paper but does not follow the actual production takt, the available resources or the process capacities. Because of that, the plan puts pressure on people, creates inventory or leads to stoppages. In my work I use a combination of LEAN tools and real shop floor feedback to bring Heijunka down to the level of operational planning: so that it doesn&#8217;t just exist as an Excel file, but as a system that lives. The first thing I do is introduce one of the principles of the WCSC concept (World Class Supply Chain): production planning and production execution are separated into different departments, the sales department cannot communicate directly with the production department, and the production department cannot make its own plan (which is a kind of conflict of interest). That is why the job structure and the organizational structure are reformed, and a logistics department with a planning function is set up as a buffer zone between sales and production, to balance their demands on each other.<\/p><p>Leveling does not only mean an even number of pieces per shift; it also includes stability in delivery time, quality and machine load. When that is achieved, companies manage resources more easily, reduce stress on workers, and eliminate the need for unplanned overtime or constantly moving people from one position to another.<\/p><p>Hoshin Kanri (cascading business strategy down to the lowest levels of the hierarchy)<\/p><p>Hoshin Kanri is a method for translating a company&#8217;s strategy into specific goals and activities at all levels of the organization. The point is to ensure alignment between what management plans and what happens in operations. In practice, this means the strategy does not stay a document in a drawer (for example, a company&#8217;s ISO policy written pro forma), but every department knows its part of the road, how it measures progress, and what it needs to do if a deviation occurs.<\/p><p>The biggest advantage of Hoshin Kanri is that it introduces two-way communication. Goals are not handed down one way. The question is asked whether they are achievable, whether resources are provided, and what the possible obstacles are. In companies where this does not exist, it often happens that goals are defined, but nobody on the shop floor knows what they are or why they matter.<\/p>\n<p>When I apply this tool, I use a simple format: every strategic direction has linked goals, clear indicators, a task owner and a control mechanism. The key to success is keeping the review rhythm and tying KPI results to concrete actions, not just to presentations. When people understand where the company is going and see how their role contributes to that direction, the strategy starts to make sense and is actually lived in everyday work.<\/p><p>Just in Time (the principle of planning production and materials)<\/p><p>Just in Time is a principle of production and delivery based on the customer&#8217;s real needs, without surpluses and inventory that needlessly take up space, tie up money and put extra pressure on the system. The idea is simple: produce only what is needed, in the quantity that is needed, at the moment it is needed. In practice, we often see the production director ignore the customer&#8217;s needs and plan on his own what gets made and in whatever way suits him, so we end up with large batches that create delays, excess inventory and shortages. That is why I described above that we work on the WCSC principle and that Logistics plans production and materials.<\/p><p>In practice, for JIT to work, every part of the system has to be stable. There is no room for improvisation. The plan has to be realistic (based on the efficiency actually achieved in production and the real capacity available right now), and the material has to be available. As soon as one link in the chain fails, the whole system suffers. That is why JIT cannot be introduced by declaration. It takes technical precision, organizational discipline and a clear chain of communication between planning, purchasing, production and logistics.<\/p><p>In companies used to \u201cplaying it safe\u201d by building large inventories, introducing JIT requires a change in thinking. It is not about taking risks, it is about relying on facts and accurate planning. In the systems I have set up, JIT was always introduced in phases: first through internal logistics and pulling material to the line based on actual consumption, then through a Kanban system, and only later through make-to-order production planning.<\/p><p>Just in Time brings the most benefit when combined with standardized work and level scheduling (Heijunka). Then the constant need for rush deliveries and an overloaded warehouse disappears, and the process becomes transparent, predictable and financially healthy. Most companies immediately \u201cgrab onto\u201d JIT and its implementation, but this is something you introduce only once the whole management team is running smoothly, there are precise scrum meetings at fixed times (very important so the team can solve problems right away), Logistics is separated from production and plans and acts independently, and so on.<\/p><p>Takt Time (time remaining until delivery \/ number of pieces ordered)<\/p><p>Takt Time is the basic rhythm of production that defines how often a product needs to be finished to meet customer demand. It is calculated as the ratio of available production time to the required quantity, and it is the basis for work balancing, capacity planning and line organization. This means sales cannot commit to delivery dates if the takt time is shorter than the cycle time, meaning the actual time needed to make one piece of the product. If this is not applied, we often end up with some customer always being late, production plans changing during the day, loading plans changing and so on, and that causes a huge drop in employee morale, confusion and a drop in productivity.<\/p><p>If takt is unknown or ignored, production is planned blindly, by gut feeling. That most often leads to overloaded operations, surpluses, delays and constant rushing. When takt time is used as the basis, you can clearly see how many operators are needed, where bottlenecks occur and what the work sequence should look like.<\/p><p>In companies with a wide product range and frequent changes, takt is used flexibly, with load estimates by product group or line. What matters is not to treat takt as pure math, but as a tool for aligning demand with real capability. Takt does not push the system to work faster, it pushes it to work smarter and to give the customer clear and accurate feedback on exactly which day they can expect their goods.<\/p><p>Kaizen (the idea suggestion process)<\/p><p>Kaizen is a way of thinking that, over the years, has proven to be the most stable framework for improving work. It does not bring sudden changes, it does not rely on big investments and it does not require complicated projects. Kaizen means asking a simple question every day: can something in our process be done more easily, more simply, more safely or with fewer errors?<\/p><p>I apply it by setting up a simple and transparent system in which anyone can suggest an improvement. We use a form where you enter a description of the problem and a proposed solution, and the whole process is tracked, approved and rewarded by procedure and as a team. Every suggestion has an owner, a set deadline and mandatory feedback to the person who made it. My experience is that people engage with the system honestly and willingly only if they see someone is listening and ideas are not ignored. That is why the rule is that no suggestion may go unanswered, whether it is implemented right away, postponed for later or rejected with an explanation.<\/p><p>We do not apply Kaizen only in production. Practice has shown me that useful ideas often come from support departments (services), from people who seemingly are not directly in the process but feel its consequences every day. Kaizen succeeds only if its implementation does not come down to one person&#8217;s initiative. When every suggestion is treated with respect, you build a culture in which people genuinely want to contribute.<\/p><p>Kanban (production on the supermarket, self-service principle)<\/p><p>Kanban is a tool for managing materials and information that, in my practice, has proven most effective when it matters that the system itself signals that something is needed, without calls, requests or chasing people down. Its greatest strength is its simplicity. In practice, you use a Kanban card, bin, color or physical signal that clearly shows it is time to replenish, prepare or take action. For example, if production is split into two segments (main production and finishing), instead of finishing constantly telling main production what it needs and when, we do an analysis upfront and determine that daily production needs four pallets of semi-finished goods. A functional handover point is defined, pallet spots are marked, and the main production manager knows at a glance at that intermediate storage area what needs to be produced. The goal is for all pallet spots to always be full, and for finishing to take what it needs at any given moment.<\/p><p>When set up correctly, Kanban eliminates unnecessary ordering, overstocked inventory and wasted trips. I start implementation where the most time is lost waiting for materials, tools or semi-finished goods. We set a rule: when a signal leaves the zone, logistics reacts without further questions. The system is tuned using defined minimum and maximum quantities, tested beforehand on the real flow.<\/p><p>In companies with a chaotic material flow, Kanban often looks like too big a change. That is why I introduce it in phases. First in internal logistics, especially for packaging, consumables and tools. Later, once the team sees how it works, Kanban becomes part of the everyday system and nobody wants to go back to the old way. The key to success is not pretty cards, it is people respecting them and the system reacting on time.<\/p><p>KPI (defining formulas to measure value for each process)<\/p><p>KPIs, or key performance indicators, are a measurement framework that makes it possible to track, analyze and improve work processes based on facts. They are not a tool for controlling people, they are an instrument for understanding the system. A properly set KPI shows where the system runs stably and where deviations occur. In our approach, we use KPIs as the basis for operational and strategic management, and tracking them is an integral part of the LEAN board and daily meetings.<\/p><p>Besides the target value, which most companies define, we also introduce a mandatory trigger value (a lower limit below which a root cause analysis is launched). We do this through the DMAIC approach, where the process is broken down, the cause is identified and measures are proposed. The trigger is not a punishment, it is a signal we agreed on together to help us react in time.<\/p><p>Every KPI has to be clear, measurable and functional. We link it to concrete tasks and responsibilities so teams have clear information on which to base decisions. If the result is below target, we do not look for someone to blame, we look for the cause. If it is above expectations, that is a signal we have an opportunity to standardize what is working well.<\/p><p>OEE (overall efficiency of the production process)<\/p><p>OEE is the key indicator we use to measure the real utilization of equipment, and it is the product of three components: Availability (effectiveness), Performance (efficiency) and Quality. It does not just show how long the machine ran, but how much of the planned time was actually turned into good product. OEE gives us a picture of where the system is losing capacity: downtime, slow running or bad parts. For this concept, it is very important to know the difference between effectiveness and efficiency. Planned production time is 430 minutes. Using the Time Study methodology, we determined that, including all micro-stoppages and the specifics of our process, we need 100 seconds per piece (that is under ideal conditions and at 100 percent of the standard). The director set this year&#8217;s target at 75 percent efficiency, which is 133.3 seconds per piece. The worker works during the day and exceeds the 75 percent target, which is excellent, but works only 350 minutes (say, because of extended breaks, starting production late, inefficient machine maintenance and so on). That is why we use OEE, which gives us the wider picture, not just efficiency.<\/p>\n<p>In practice, we use OEE as the basis for the daily assessment of process efficiency. Each component is looked at separately. If availability is low, we analyze why the machine is standing still. If performance is below expectations, we measure cycle time and compare it to takt time. If quality is below standard, we start a defect investigation. That way we do not draw conclusions from the overall number; we understand which part of the system needs intervention.<\/p><p>We do not use OEE only for measurement, but as a tool for dialogue between production, maintenance, planning and quality. When all departments look at the same metric, it is easier for them to agree on priorities. That is why OEE is displayed on the LEAN board, with daily and monthly results and clear trigger values that start the analysis and the corrective actions.<\/p><p>In companies that strive for business excellence, the target value for OEE is at least 85 percent. Anything below that can mean the system is still in the stabilization phase or that there are structural limitations in the processes. Regardless of the current value, the key is that the team knows how OEE is calculated, what it represents, and how to react when one of its elements drops below the expected level.<\/p><p>PDCA cycle (defining agreed actions)<\/p><p>The PDCA cycle (Plan, Do, Check, Act) is the basic theoretical framework for managing change and solving problems in a LEAN system. Although the method is simple and logical, in my experience it is rarely applied consistently. Most often a plan is made, something gets carried out, but the check and the correction are skipped or stay buried in email threads. That is why, instead of the classic PDCA model, in practice we rely on a simpler and more transparent tool: an Action log organized on the Kanban principle.<\/p><p>Every department and every project has its own Action plan, in the form of a coded and standardized Excel document. The good thing about it is that top management, auditors and anyone else who asks can quickly and easily get a clear picture of how a department has been operating, even a couple of years back. Actions are defined as a team, the action owner sets the deadline by which he will complete the action, and his superior adjusts that deadline if needed.<\/p><p>Poka-Yoke (a tool for eliminating errors)<\/p><p>Poka-Yoke is an approach whose goal is to make an error physically impossible, or to have it spotted immediately, before it reaches the next stage of the process. In other words, it is a form of protection against human error, not through punishment, but through a smart solution. In companies without stable processes, most problems come precisely from repeated errors that slipped through the system. Poka-Yoke is the way to cut that off.<\/p><p>Take the textile industry as an example, and the problem of some workers forgetting to sew the label onto a sweater before putting it on the counter for the next production step. In that case we introduce a rule: they no longer put the sweater on the counter. When they finish their operations, the last of which is sewing on the label, they have to hang that same sweater by its label on a mobile rack for the next stage. No label, no way to hang it\ud83d\ude0a<\/p><p>In some companies where we introduced this practice, the most important shift happened in understanding that an error must not repeat once it has already happened. A Poka-Yoke system forces us to change the process so that the error either cannot happen or is stopped 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 \u201c5 Why\u201d method, is used when we want to get to the real source of a problem instead of just putting out the consequences. By asking a series of \u201cwhy did this happen\u201d questions, we go deeper into the process each time until we reach the point that is the cause, not just a symptom. In most cases, the problem we see is only the consequence of something deeper that the system is not solving. If it is not clear how this works, think of a simple example with children: when a child asks \u201cwhy does a bird fly\u201d and we answer \u201cbecause it has wings\u201d, the next question is \u201cand why does it have wings\u201d&#8230; And so on, until we get to the essence. We can also look at this process as a fight against weeds. If we just cut them with a trimmer, they will grow back, probably even stronger. But if we pull them out by the roots, and do it before they go to seed, we have solved the problem at the right moment.<\/p><p>In our application of this tool, we work by one basic rule: we look for the cause, not the culprit. We do the analysis within the team closest to the process, involving operators, managers and support staff (if the problem is located in only one department, we use the basic 5 Why template, and if the problem cuts across several departments, I use DMAIC). We do not use prepared forms that nobody understands, but concrete questions, about a concrete situation, with a clear record and a conclusion. In some cases it does not stop at five questions, and sometimes the cause is found as early as the third. What matters is honesty and the willingness to look at your own organization\u2019s failures, instead of shifting the problem onto someone else.<\/p><p>SMED (optimizing product changeover time)<\/p><p>SMED (Single-Minute Exchange of Die) is a method used to reduce the time needed to change a tool, a format or a machine setup, with the goal of completing the entire changeover in under 10 minutes. This does not mean it has to take exactly one minute, but that it stays in single digits: a maximum of nine minutes and 59 seconds.<\/p><p>In practice, we start SMED by observing the actual changeover and separating the activities: what can be done while the machine is still running, and what has to wait until it stops. The biggest losses come from searching for tools, waiting for documentation, or poor preparation. When everything that can be done in advance is done in advance, the changeover itself becomes faster and simpler.<\/p><p>The method is especially useful in companies that frequently switch products or batches. Besides saving time, SMED brings stability, less stress and more control over planning. When the system is set up well, it is possible to run shorter batches without building up inventory, and the machine is used more efficiently.<\/p><p>We speed this process up as much as possible by sorting the format parts as part of the 5S project.<\/p><p>Standardized work (multifunctional work procedures and instructions)<\/p><p>Standardized work is the agreed, best currently known way of doing a particular job. Its purpose is not to restrict workers, but to provide stability, a clear breakdown of steps and a measurable process. When everyone does the same job in different ways, it is hard to find where the error is made, and even harder to figure out how to improve something.<\/p><p>In practice, standardization starts with defining the key steps in an operation, the work sequence, the tools needed and the duration. We document all of this through simple visual standards that are clearly posted at the workstation. The goal is not to write instructions for an inspector, but to make the agreement clear to the worker and the team: how it is done, why it is done exactly that way, and what signals that something is off.<\/p><p>When introducing standardized work, we always involve the operators, because they know best where the deviations are and where things need to be made easier. Then each function gives its input as needed, so for work procedures in production the sequence is as follows:<\/p><p>suggestions and feedback from the machine operators are the foundation<\/p><p>technology (engineering) provides the description of the process steps<\/p><p>the LEAN department or technology provides the standard times for the operations<\/p><p>the quality department provides the quality requirements<\/p><p>the HS department provides the safety and occupational health requirements<\/p><p>the technical service defines LOTO (Lock Out Tag Out) and the machine maintenance requirements<\/p><p>And logistics, for production and material planning<\/p><p>Once the standard is set, it does not stay fixed. It changes whenever someone offers a better solution that we test and confirm. That way the standard is not an obstacle to improvement, but the foundation that Kaizen builds on.<\/p><p>TPM (the machine and equipment maintenance process)<\/p><p>TPM, or Total Productive Maintenance, is an approach in which everyone in the organization takes part in keeping the equipment stable. Unlike the classic model, where the operator runs the machine until it breaks down and then calls the mechanic, TPM involves the operator in daily activities that prevent breakdowns. These are not complex repairs, but simple tasks: cleaning, visual inspection, basic checks. That 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 introduce TPM gradually:<\/p><p>we choose the critical machines,<\/p><p>we define the daily check points,<\/p><p>we use simple checklists and<\/p><p>we track the condition through the LEAN board.<\/p><p>TPM does not replace classic maintenance, but it gives it an advantage, because it allows problems to be detected earlier, 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 for stable operation every day.<\/p><p>VSM (process flow mapping)<\/p><p>VSM, Value Stream Mapping, is a tool we use to visually show the entire flow of one product, from order to delivery. By mapping every step, including inventory, waiting, handoffs and transport, we get a clear picture of where time is lost, where material piles up and where the flow breaks. The goal is not for the map to look neat, but to reveal inefficiencies that are not visible in everyday work.<\/p>\n<p>In practice, we start by walking through the actual process with the team, right on the shop floor, step by step. First we measure every operation with a Time Study, then we record the times between operations; all of this goes onto that dashed line (the timeline). We don&#8217;t rely on theoretical flows. We draw what actually exists: how many pieces sit between operations, how long the waiting lasts, whether there is a parallel flow, how quality control is done. Based on that, we separate the activities that create value from the ones that only take up space and time (and then comes elimination).<\/p><p>Once the map is done, it is used to make concrete decisions: where we can combine steps, where to reduce inventory, where to put a signal, where to introduce a standard. A VSM is not made to hang on the wall. It is made to drive change. Once we have done the VSM, we have the Cycle Time (the time we need to make one piece). By comparing it with the Takt Time, we can tell customers exactly when to expect their goods, we can plan material, and we can build the foundation for JIT.<\/p><p>The visual factory (Visual Management)<\/p><p>A visual factory means that all important information is available where the work is done, in real time, with no need for extra explanation. Instead of employees asking what to do, where things are or what is happening right now, the system shows them through colors, markings, lines, boards, signal cards or light indicators.<\/p><p>In practice, this means the workplace layout is clearly marked, tools and materials are in their place, order status is visible without opening a computer, and every change in the process is immediately recognizable. For example, we use a LEAN board with sections for safety, quality, production and Kaizen activities, along with shadow boards for tools, signs for material flow, marked aisles and signals for downtime.<\/p><p>The goal of visual management is not looks, it is efficiency. Good visual organization shortens decision time, reduces verbal communication and prevents mistakes. Once it is in place, it becomes the basis for standardization and transparency in every department. The foundation of Visual Management is 5S. Best practice is to install large monitors on the production lines that display KPIs (a dashboard) and all the important, relevant information on the shop floor.<\/p><p><span class=\"elc-sr-t\">LEAN board<\/span><span class=\"elc-en-t\" data-no-translation>LEAN board<\/span><\/p><p>The LEAN board is a product of my many years of work and of seeing the need to have key information in one place and a single way of communicating. It is the central spot on the shop floor that shows key information about the team&#8217;s work, production, quality, safety and improvements. Its purpose is not to \u201clook nice,\u201d but to make sure the team knows at every moment what matters, what is happening and where they need to react. The board has to be up to date, accessible to everyone and organized so that it gives a clear overview with no extra interpretation needed.<\/p><p>In practice, we divide the LEAN board by function: safety (e.g. incidents, protective equipment), quality (defects, customer complaints, samples), production (plan, output, downtime) and improvements (Kaizen suggestions, action log). The middle often holds the action section, where a Kanban approach tracks the status of every open activity: planned, in progress, done. This captures the PDCA logic visually, without extra paperwork.<\/p><p>Meetings in front of the board are short (the scrum principle), with a clear order, and driven by questions, not by pulling up reports. When the board is used consistently, it becomes a decision-making tool, not just a notice board. The value of a LEAN board is not in laminated columns, but in the fact that it starts conversations, builds shared responsibility and drives a fast reaction when something goes off track.<\/p><p>Andon (stopping the line because of a nonconformity)<\/p><p>Andon is a tool that lets an operator stop the line or signal a problem the moment they spot it, to prevent a defect, a breakdown or a loss of quality. The point is that the problem does not travel further down the process, but gets solved right away, while it is still small. This is the tool that lifted Toyota the most, simply because the director at the time put his trust in a \u201ccrazy\u201d worker (the creator of the LEAN concept, whom his colleagues laughed at) to put his ideas into practice. At first there were more stoppages than before, but the production lines kept getting better and better!<\/p><p>In practice, this is hard to implement, because many production managers try to keep everything under control, don&#8217;t allow the line to be stopped without their approval and keep decisions to themselves: they are micromanagers. Andon requires trust: the operator has the right to react, and the team leader responds without blame. Where there is fear or micromanagement, the system gets introduced on paper, but nobody uses it. In companies that have truly embraced it, Andon becomes the basic reflex for preventing bigger problems.<\/p><p>This is only part of the LEAN tools we use in practice. There is a wider range, but I believe that range is meant for really well-organized systems, and that implementing just these tools is absolutely enough to deliver a five-year strategy and noticeable growth.<\/p><p>How we do a LEAN analysis: seeing through the worker&#8217;s eyes<\/p><p>We never start a LEAN analysis from the office. We don&#8217;t look at reports first, we don&#8217;t open spreadsheets and we don&#8217;t listen to managers&#8217; presentations. We start by standing at the production entrance and trying to see everything through the worker&#8217;s eyes. As if we were walking into the company for the first time and had to do a job, and nobody had explained anything to us.<\/p><p>We look at where the worker comes in (what the entrance is like, whether it is safe, whether it holds people up unnecessarily, whether it is properly marked with vertical and horizontal signage), where they change clothes, whether they know where to go, how long it takes them to get to the workstation. Are the tools already ready, or do they have to look for them? Do they know where their documents are, and how often do they have to ask someone something? We watch how they move: do they walk around things that are in their way, do they bend, turn, carry something by hand that could be wheeled? We observe how much \u201cunconscious effort\u201d there is: the things they no longer even see because they have gotten used to them, but that we notice because we are looking with fresh eyes.<\/p><p>In the example we used: a new worker comes into the production area and tries to get started. There is no clear tool layout, they have to ask a coworker where the next part is, and they go by the logic of \u201cthis is how we&#8217;ve done it for years.\u201d The table isn&#8217;t adjusted to their height, a cable hangs over their head, and every step makes them bend or stretch a little. At that point we already have the first ten potential wastes. And that&#8217;s before the product has even started being assembled.<\/p><p>In practical terms, we use a form prepared in advance that doesn&#8217;t look like an audit checklist, but more like an observation map: what the worker searches for with their eyes, how clear the next step is to them, whether everything is in its place, whether they feel safe. We record observations without judgment and without comment: facts only. When we come back later, we go through every point together with the team and ask: why is it like this, and what could we change so it isn&#8217;t like this?<\/p><p>This approach doesn&#8217;t require any special technology, just open eyes, empathy and the will to see things the way the person who actually does the job sees them. When we start the analysis from the worker and not from the numbers, the solutions we propose make sense and have a chance to last.<\/p><p>If we have managers who insist on a \u201cit&#8217;ll be the way I say\u201d approach, without observing the process and without listening to the people who do the job every day, then we are not introducing a system, we are imposing authority. In practice, what happens then is that problems just get moved around, but never solved. Mistakes get covered up, ideas never come to light, and workers start withdrawing to the bare minimum of engagement, because they feel that nothing they say changes anything. This directly affects quality, safety and work speed. In the end, the line runs, but far below its potential (which we see a lot in practice), and the losses pile up over time.<\/p><p>A LEAN analysis is not a challenge to anyone&#8217;s ego, but an opportunity to see what can never be understood from the office. Being a manager doesn&#8217;t mean knowing more: it means being entrusted with a greater responsibility to see the bigger picture. When the manager is the first to get up, ask, observe, take notes and ask for workers&#8217; opinions, that creates a culture in which people want to cooperate. When, on the other hand, everything comes down to orders (\u201cdo it the way I tell you\u201d and \u201cI&#8217;m the boss here\u201d), spreadsheets and criticism, the system goes into resistance. That is a disastrous situation for a company, because the main gear brakes and jams, and very often, almost always \ud83d\ude0a, the ones braking it are exactly the people the owners and the director (sometimes including the director himself) trusted to \u201cgrease\u201d that gear and set it up properly.<\/p><p>The most successful teams are not the ones where everyone stays silent while the boss talks, but the ones where people speak freely because they know someone is really listening. And a LEAN analysis, if it is done honestly, shows exactly that: where the system is holding people back, not where people are holding the system back.<\/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 in place, then all processes are already well enough organized and there is no need for LEAN. In practice, though, that falls apart very quickly. ISO is an excellent framework for setting up a management system, but it is focused on proving compliance, not on efficiency. Its goal is for documentation to exist, for a procedure to exist and for a record to exist. ISO doesn&#8217;t ask how much time is being lost, whether the worker understands the process, or whether there is unnecessary movement and waiting in production. And that is the best case, when ISO is fully alive and implemented. Now picture the situation in most companies where the ISO standard was introduced \u201cpro forma,\u201d there is \u201csome employee over there who is in charge of ISO,\u201d and it all comes down to a last-minute scramble to gather documentation before the upcoming certification \ud83d\ude0a.<\/p>\n<p>LEAN, on the other hand, starts with different questions: where are we losing time, money, energy and motivation? Where is the work fundamentally harder than it should be? Where does the system slow people down instead of supporting them? Lean doesn&#8217;t care whether a document exists: it cares whether what the worker does every single day makes sense, has a rhythm and has support.<\/p><p>That&#8217;s why it is entirely possible, and it happens very often, for a company to hold ISO 9001, ISO 14001 and ISO 45001 and still have chaos in the process, downtime, unhappy people, high costs and overloaded managers. ISO doesn&#8217;t solve those problems because it wasn&#8217;t designed to. It asks for records, procedures and control, but it doesn&#8217;t go deep into the everyday flow of work. That is exactly what Lean does: it goes to the place where value is created, watches the flow, involves the people and removes what isn&#8217;t needed.<\/p><p>In my work, we don&#8217;t set ISO and Lean against each other. Quite the opposite: we use the best of both worlds to show customers and clients that our system works efficiently and that they have no reason to worry. ISO provides the structure, Lean brings it to life. When you combine them, you get a system that doesn&#8217;t exist just for the certificate, but a system that works because people know what they are doing, why they are doing it and how to do it better every day.<\/p><p>Who can&#8217;t lead LEAN, and why not every company pulls it off<\/p><p>In theory, LEAN looks simple. The tools are well known, processes can be mapped, and a visual system can be put in place relatively quickly. But that is only the form. The substance lies in the people, and that is where most companies fail. Not because of the tools, but because it is led by people who see the organization as their own territory, and not as a living system that has to grow and develop together with its people, not around them. It often happens that people in the company ask \u201cin the hallways\u201d why exactly that person was hired when most of them feel it isn&#8217;t the right choice. This happens because companies don&#8217;t pick managers for their ability to develop a system, but for their ability to \u201clook decisive.\u201d In a culture where authority is confused with volume and control with pressure, people who shout, give orders and \u201crestore order\u201d are easily seen as capable managers. They are often visible, always involved, reactive and the first to \u201cdo something,\u201d and at first glance they give the impression of action.<\/p><p>But that is where the trap is, because people like that don&#8217;t lead the system, they compensate for it. Everything that isn&#8217;t solved through structure, they try to solve through themselves. And as long as they are around and keep everything under their hand, the system somehow works. But when they are gone, chaos follows. And worst of all, they know it, which is why they keep centralizing control more and more.<\/p><p>On the other hand, quieter, calmer, system-minded people, who would probably run the company better in the long run, often lack \u201cstage presence.\u201d They don&#8217;t make noise. They ask, they listen, they introduce things through people. And that is why many people wrongly judge them as \u201cweak.\u201d In a culture that wants fast results, clear orders and someone who \u201ctakes charge,\u201d people like that are often ignored or passed over, because they don&#8217;t seem like \u201cleaders.\u201d<\/p><p>The core of the problem is that companies still reward control more than building a system. And Lean exposes exactly that model, because it shows that a company&#8217;s real strength isn&#8217;t in the energy of one individual, but in the stability of a system that doesn&#8217;t depend on any one individual.<\/p><p>It is also a misconception that anyone who is \u201cflexible enough\u201d and \u201clikes people\u201d can lead Lean. In practice, the opposite extreme happens too: the person leading Lean has no authority, can&#8217;t set boundaries, avoids conflict and keeps backing down in the face of resistance. Then Lean turns into theory: the board fills up with tasks, meetings are held, but nothing really changes. People quickly figure out that there is no decision behind the words, and the system starts falling apart from the inside.<\/p><p>So Lean can&#8217;t be led by someone who is afraid to ask a question, to ask for a change, or to make someone unhappy. But it also can&#8217;t be led by someone who gives commands without understanding the process and without connecting with people. You need balance. You need a person who has the character to withstand resistance and the humility to know that the system isn&#8217;t there for them, but for the team and the customer. Only then can Lean take root: not as a project, but as a way of working.<\/p><p>The person leading Lean has to know that they are not at the center, but on the side, serving the process. It can&#8217;t be led by someone who doesn&#8217;t go down to the shop floor, who doesn&#8217;t know how to listen to an operator, and who believes problems get solved from the command office. Even worse, it can&#8217;t be led by someone who keeps everything to themselves, who doesn&#8217;t delegate, who micromanages, and who thinks Lean means \u201cI&#8217;m the one who knows how it should be done.\u201d<\/p><p>Micromanagement is Lean&#8217;s biggest enemy. It kills initiative, turns managers into passive order-takers, and sends the message that nothing changes without permission. In a system like that, people don&#8217;t make suggestions because they know they will be ignored, and the Kaizen box just collects dust. Instead of the Lean system developing people, the opposite happens: the system depends on one person who \u201cpulls\u201d everything. And that never lasts long.<\/p><p>That is why not every company succeeds. Not because it lacks resources, tools or support, but because there is no one who knows how to let the system breathe, and how to lead through other people, not over them.<\/p><p>That is why it matters that the person leading Lean knows 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 a rugby team. Unlike a traditional sport where one player gets the ball and 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 those agreed plays are very short and efficient. Nobody waits for a command, nobody looks around to see who the leader is: everyone knows their role and they move together, because they know the goal is reached only if nobody stops.<\/p><p>That is exactly what we carry over into the way we run the team and meetings: everyone takes part, everyone knows where the obstacle is, and everyone is part of the solution. A Scrum team doesn&#8217;t work like a chain of command, but like a dynamic unit that organizes itself, adapts every day and makes micro-decisions without needing approval \u201cfrom above.\u201d That is why this model doesn&#8217;t just speed up the work, it also strengthens accountability and mutual trust, and those are the foundations of every Lean system that actually works.<\/p><p>Conclusion: Lean is not a system, Lean is a mirror<\/p><p>Implementing Lean is not a project. It isn&#8217;t a spreadsheet, a tool or a report for an audit. Lean is a mirror, and the most honest one a company can hold up to itself. And every mirror can show two pictures: what we are proud of, and what we are hiding.<\/p><p>In companies that aren&#8217;t ready to look into that mirror, Lean stays a laminated board on the wall. Managers deal with numbers they don&#8217;t understand, meetings turn into reading out problems without the courage to dig into them, and workers learn to keep quiet and just do \u201ctheir thing.\u201d The system still works, but it creaks, it loses, it wears people out, it frustrates partners, and in the end it costs. 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 foundation up. It changes the rhythm. It changes the logic. And most importantly, it changes the relationships between people. In companies like that, managers don&#8217;t shout, they listen. They don&#8217;t solve everything themselves, they get others to think. And they don&#8217;t ask for reports to \u201ccover themselves,\u201d but to know where to help.<\/p><p>Many people look for a \u201csolution\u201d the way modern medicine often works: fast, something to relieve the symptom. Lean doesn&#8217;t do that. Lean doesn&#8217;t treat symptoms. Lean digs down to the cause. And that takes patience, discipline and character. That is why not just anyone can lead it. That is also why it doesn&#8217;t succeed everywhere. But where it does succeed, the company doesn&#8217;t just survive, it becomes an example for others.<\/p><p>To wrap up: if you are a director, an owner, or someone who has been trusted to run a company, a process or people, Lean is not a cost, it is an investment in common sense. In a system that doesn&#8217;t depend on one person. In a culture where work has meaning. And in companies that no longer work \u201cunder pressure,\u201d but with a purpose.<\/p><p>If you are ready to question everything, including yourself, Lean may be the healthiest thing you have ever introduced.<\/p>\n<\/section><\/main><\/div>\n<div class=\"elc-og-cta\"><div class=\"kutija\"><span class=\"elc-sr-t\"><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.<\/span><span class=\"elc-en-t\" data-no-translation><strong>What now?<\/strong> If you want to see where your company really stands, start with the Excel system assessment with 45 questions. If you want to talk it through, write to me at solutions@elcinsight.com.<\/span><br><a class=\"elc-og-btn\" href=\"\/digitalni-proizvodi\/\"><span class=\"elc-sr-t\">Pogledajte gotova re\u0161enja<\/span><span class=\"elc-en-t\" data-no-translation>See the digital products<\/span><\/a><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>\u2190 Po\u010detna\u2190 HomeSRENSREN Ogledalo firme Kako zaista izgleda LEAN u praksi. Bez ulep\u0161avanja. Bez teorije koja lepo zvu\u010di, a ne radi u pogonu. Company Mirror What LEAN really looks like in practice. No sugarcoating. No theory that sounds good but does not work on the shop floor. Ovo je vodi\u010d, ne prodajni tekst. Ako vam [&hellip;]<\/p>\n","protected":false},"author":6,"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\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/comments?post=20"}],"version-history":[{"count":14,"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/pages\/20\/revisions"}],"predecessor-version":[{"id":1051,"href":"https:\/\/elcinsight.com\/en\/wp-json\/wp\/v2\/pages\/20\/revisions\/1051"}],"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}]}}