Which part of the LMC actually wrecked you? For me it was lean principles

Lean principles got me too, honestly. I work full time and have two kids so I was studying in like 20-minute chunks whenever I could — lunch breaks, after bedtime, sometimes just sitting in my car before work. The vocabulary wasn't the hard part. It was understanding why the principles connected to each other, not just memorizing definitions. I failed the first time because I could recite the eight wastes but couldn't apply them to a scenario I hadn't seen before.

Second time around I stopped trying to cram and just spent a week doing nothing but practice questions on lean principles specifically. Didn't touch the other sections until I felt solid there. That actually worked. If you're studying part-time like I was, don't try to cover everything evenly — find your weak spot and live there for a bit before moving on.

Lean principles got me too, honestly. I'm a project manager with two kids and I was squeezing in maybe 45 minutes before bed most nights, so I didn't have time to really sit with the philosophy side of it. The technical stuff I could memorize. Takt time, cycle time, the eight wastes -- fine. But when they ask you to apply the thinking to a scenario you haven't seen? That's where I kept blanking. Failed my first attempt by four points.

What finally helped was stopping the flashcard grind and just walking through practice questions out loud, explaining my reasoning like I was teaching someone. Sounds weird but it forced me to actually understand it instead of pattern-matching answers. If you're studying part-time around a job, give yourself more time than you think you need on the conceptual stuff. The diagrams are the easy part.

Same boat honestly. I work full-time in manufacturing and was studying in like 20-minute chunks whenever I could grab them -- lunch breaks, waiting for my kid at practice, that kind of thing. The lean principles section hit different when you're exhausted because it's not just memorization, it's conceptual, and your brain has to actually connect the ideas. I'd read the same paragraph three times and still couldn't tell you what I just read.

What finally clicked for me was explaining the concepts out loud to nobody in particular while I was driving. Sounds ridiculous but it forced me to actually process it instead of just scanning words. The first time I couldn't explain why waste elimination ties back to customer value without stumbling, I knew I hadn't actually learned it yet. Once I could talk through it naturally, the questions on the real exam felt way more manageable. Don't underestimate how much the fatigue factor plays into it when you're studying part-time -- it's not just the content, it's that your brain is already half-fried before you even open the book.

Just passed mine two weeks ago so this is hitting close to home. Lean principles got me too — specifically the whole "respect for people" pillar. I went in thinking it was just a soft, feel-good concept they throw in at the end, but the exam hit it hard in scenario questions where you had to distinguish between waste reduction that was also respectful versus waste reduction that just looked efficient on paper. That distinction tripped me up constantly.

What finally clicked for me was stop memorizing the eight wastes as a list and start thinking about which ones are "time" wastes versus "effort" wastes. Defects, overproduction, waiting — those are time. Unused talent is the outlier that breaks the pattern, and of course that's the one that shows up in like three different question framings. Once I started categorizing them that way instead of just reciting DOWNTIME, the scenario questions got way more manageable.

Also second everything said about kaizen vs. kaikaku. I almost blew past that distinction in my review because it felt like a vocabulary nitpick, but there were at least two or three questions where getting that wrong would've cascaded into a wrong answer on the follow-up. The exam is sneaky about testing whether you actually understand the philosophy or just memorized the terms.

Just passed mine three weeks ago, second attempt too, so this hits close to home. Lean principles absolutely wrecked me the first time — not because the concepts are hard to understand in isolation, but because the exam loves to give you scenarios where two or three principles are in tension and you have to pick the "most lean" response. That's where I kept losing points without even realizing why.

The thing that actually clicked for me on the second go was forcing myself to think in terms of the customer first, always. Like whenever I hit a tricky question I'd ask "which answer eliminates the most waste from the customer's perspective" before anything else. Sounds obvious but I was overcomplicating it by jumping straight into tool-specific thinking — kanban, 5S, whatever — instead of anchoring back to value. Doing a ton of scenario questions on an lmc practice test helped me build that reflex faster than re-reading the material did.

Value stream mapping I actually ended up fine on too. The diagrams look intimidating but the exam questions are more conceptual than technical — they're not asking you to calculate takt time from scratch, they want to know if you can identify where waste is hiding in a process flow. Once I stopped dreading the VSM stuff and just practiced reading maps for bottlenecks, it felt manageable. Lean principles though — yeah, that's the real beast.

Passed mine about two years ago now, and lean principles absolutely wrecked me too — but honestly, looking back, I think it's because we go in expecting it to be a philosophy and the exam treats it like a technical framework. The stuff that really got me wasn't value stream mapping either. It was the difference between muda, mura, and muri when they show you a scenario and want you to classify it. On paper those distinctions feel obvious. In a timed question with four plausible answers, not so much.

The hindsight take: what actually matters most for passing is understanding *why* lean tools exist, not just what they are. I could draw a VSM in my sleep going in. Couldn't tell you why you'd choose a kaizen event over a kaikaku approach for a particular situation. That's where the exam lives — in the judgment calls, not the definitions. If I'd spent half the time I spent memorizing the seven wastes on just doing practice scenarios instead, I probably would've passed the first time.

Also the pull systems vs push systems questions are deceptively tricky. Everyone thinks they get it until the scenario involves a partially hybrid environment. That one still bugs me and I passed.

Wait, so it wasn't value stream mapping? That's actually a relief to hear because I've been dreading that section. I'm still in the middle of studying and lean principles have been kicking my teeth in — specifically the whole pull vs push system stuff and how it connects to JIT. Like I understand the concept in the abstract but the moment a question puts it in a manufacturing context with actual numbers I completely blank.

Can I ask what specifically about lean principles tripped you up? Was it the waste identification (the 7 or 8 muda types, depending on which version you're studying), or more the philosophical side like takt time calculations and how they tie into customer demand? Because I feel like I'm memorizing definitions without actually understanding how to apply them under exam conditions.

Also — did you find the first attempt useful at all for knowing where to focus the second time, or did you feel like you were almost starting over? Trying to figure out if I should just push through and take it now to see where I land or wait until I feel more solid.