ABS KNOWLEDGE LIBRARY
Interactive scene guides
Find the right resource for your work. Choose a title to open it in ABS; sign in if requested and continue to the same content.
← All content types94 / 94 items
- Leadership TransformationLean Transformation Training (Executive)
- If lean stays a set of tool projects, conversion stops at the shop floor
- Follow one order to find the time: waiting far outweighs processing
- A target is not a result: every level’s gap needs an owner
- Close a ticket only on a measured result; if missed, go back to the root cause
- When leaders change their behavior, the site changes its practice
- The system checks targets; leaders go to the site
- Leadership TransformationLean Transformation Training (Middle Management)
- A cycle touching takt cannot absorb a single abnormality
- Cut walking by layout, then stay about 10% under takt
- Report every deviation; escalate up the line when you cannot restore
- Four team factors multiply: one zero makes the whole zero
- Formulas and response chains to the system; floor judgment stays with the team leader
- Logistics pullLean Supply Chain
- Set the NDA, participants and benefit sharing before going on site
- Three work points illustrate how preconditions affect handoffs
- Pick the right supplier, then seat the key people
- Settle the NDA and the benefit split before the event
- Count back 45 days across 21 actions
- What the three days must deliver
- Route tools by site conditions
- Aim high, with metrics people accept
- Turn “later” into dates
- After you leave, walks and countermeasures hold it
- Eight items, 90 days later, to whom
- The system holds the gates; people keep the negotiation and the floor
- GrowthLean Software Development
- The bigger the batch, the later the problem shows
- Cut the batch small; every increment goes to a user
- Build a team that delivers alone, then adopt in four steps
- Write stories to user value; estimate together
- Commit to capacity, not to full load
- Stand up at the board daily; two flat days, investigate
- Done, accepted and live are three different things
- The system reads velocity; people find the cause
- Staff developmentMaster Black Belt Certification Process
- Trusting classes and certificates turns qualification into paper
- A company leader sponsors you; you cannot nominate yourself
- Events happen on site; the total and zero items are judged apart
- Submit only when signed; DBSL keeps the certificate
- Expiry at 18 months is unannounced; renewal needs two events
- The system tracks scores and expiry; people observe on site
- Lean workplace (Gemba).MBS Andon Triggers and Three-Level Mistake-Proofing
- Press by feel, and nobody presses when it matters
- Press when a number is crossed: in the window, in one batch
- 10% slower triggers; 10% faster does not
- Two buttons, two responses
- Without a response agreement, the light is only a light
- The light goes off on root cause; records follow in parallel
- Error-prone stations need at least level-2 proofing
- A safety accident is a veto that high scores cannot offset
- Actions become records so they can be handed over
- Triggers are in the rule pack; people press the button
- Management systemCase Transfer Review
- Copying another plant’s gains yields only an assumption
- Transfer the mechanism; classify evidence first
- Connect orders, trips and receiving batches
- Draw the local trial boundary
- Bound a small trial and its exit
- Trace the shift; record actual states
- Let local evidence shape the next step
- The system checks submission; people judge fit
- Lean workplace (Gemba).MBS Energy Five-Step Method and Three-State Five-Question Analysis (3456)
- Totals alone leave idle-time consumption unquestioned
- Draw the improvement boundary
- The meter keeps running after production
- Trace where the energy goes
- Investigate five questions around the asset
- Let five questions change the design
- Carry evidence through DREAM
- A smaller bill: is performance better?
- Hand records to the next owner
- Five questions give the list; action and verification stay with people
- Lean workplace (Gemba).MBS Energy Measurement and Savings Verification
- Without one boundary and baseline, a savings figure cannot be trusted
- Align the meter boundary
- Account for the whole day
- Compare at the same output
- Keep unresolved records visible
- Energy variance is not annual savings
- Hand over rebound and missing data
- Forms keep the trail; people judge fit and confirm cost
- Management systemBusiness Event Reconciliation and Metric Definitions
- Skip event reconciliation and the metric goes wrong
- Messages do not multiply physical goods
- Keep the ledger; compute valid quantity
- Two times answer different questions
- Replay eight business events
- Hand off exceptions with evidence
- Stabilize definitions before publishing
- Forms keep the record; people make the call
- Management systemMBS 5-Why Pitfall Checklist and Reverse Verification
- Blame a person and prevention has nowhere to land
- Where you find it is not where it happens
- A difference gives direction, not proof
- Ask down to the burr to cut the water path
- Bad answers send the action astray
- Reverse the chain; verify each link
- “Too much torque” is habit; split it in two
- Drying the floor is not prevention
- Grow the tree with the inquiry, not to five
- What you hand over is a process others can verify
- The system hints; judgment and countermeasures stay with people