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.

94 / 94 items

13. Staff developmentDBS Immersion Requirements

    1. Without an order, new hires find their own way in
    2. The role decides what comes first; month one is watching, not doing
    3. Settle who signs, on what basis and what overdue means; then HR files
    4. Executives are not ticked off by gate; site evidence and phase signoff carry them
    5. The system reminds on the gates; people judge completion
    ↗
14. Leadership TransformationDBS Overview (Global Lean Benchmark)

    1. Everyone reads their own colors, so a missed month goes unaddressed
    2. All three conditions or no diligence; keep watching ROIC after closing
    3. Pass five minimum requirements first: one set for cells, another for offices
    4. Judge eight metrics monthly, and act on a missed month
    5. Talent is not left to luck: two tracks, both with a mentor
    6. The overview teaches the view; judgment lives in each tool; decisions stay with people
    ↗
15. Staff developmentDBSL Continuing Education Workshop

    1. Retraining without checking role use ends in the same form-filling
    2. Before sending anyone to class, ask whether the role has narrowed
    3. Read the two outside clocks first, then pick a channel by rating
    4. A workshop’s output is not notes but a three-line list with owners
    5. Look only at events they led: do they still stand after three months
    6. Channels and clocks to the system; role use and trade-offs stay with people
    ↗
16. Staff developmentCreating Impactful Development Plans

    1. Writing only what to learn leaves him unable
    2. Talk about where he is going before what he lacks
    3. Trace the fact to its cause; name the behavior, person and date
    4. Four parties each own a part; his ownership makes it real
    5. Having acted is not success; feedback decides
    6. The system checks; people own and talk
    ↗
17. Management systemDaily Management

    1. A gap found at month end has already gone cold
    2. Foundation before boards — without hourly facts a board is decoration
    3. Is today normal? The board must answer in three seconds
    4. A signal needs a responder — recovery is not a fix
    5. Leaders go and see daily — an unrecorded exception is an accepted one
    6. Colouring and chasing go to the system; going to see and deciding stay with people
    ↗
18. Logistics pullDanaher Materials Process

    1. Push to plan: surplus never stops, shortage goes unseen
    2. Management shifts first; no cards before the prerequisites
    3. Fix usage and lead time, then choose stock or sequencing
    4. Card counts are calculated, and only round up
    5. Cards need owners: spikes stay temporary, changes mean recalculating
    6. Arithmetic goes to the system; discipline and fewer cards stay with people
    ↗
19. Variation ReductionTaguchi Methods & Design of Experiments (DOE)

    1. Without designed experiments, interactions stay hidden
    2. Only when simple tools fail and all four criteria hold
    3. One factor at a time misses the corner that matters
    4. An orthogonal array gives every factor pair equal counts
    5. Saved runs are bought with assumptions
    6. Higher resolution leaves fewer effects mixed together
    7. The S/N formula follows the response, or you pick backwards
    8. Stabilize first, then center on target
    9. Four combination means are enough for a transfer function
    10. A screening cutoff is not proof
    11. Hand over assumptions and confirmation together
    12. Whether to escalate goes to the system, runs and conclusions stay with people
    ↗
20. Variation ReductionDanaher Reliability System

    1. Reliability leaks at four stages; no single department can hold it
    2. Raise the beam first: count the cost, name who owns the result
    3. Find and fix what already fails: ask where, then why
    4. After the fix, the numbers still travel three stages: bank first, then read through
    5. Fixing is after the fact: build reliability into design, process and metrics
    6. Banding and read-through go to the system; ownership and priorities stay with people
    ↗
21. Logistics pullE-Kanban

    1. The value is not “electronic”: it makes discipline system-enforced
    2. Prerequisites decide whether; missing processes decide the payoff
    3. Building a card: people supply data and an owner; the system sizes it
    4. One scan reaches the supplier; no blind spot before arrival
    5. Floor first, then the system: exceptions, lost cards, resizing
    6. Exceptions can be corrected; history cannot be rewritten
    7. Keep the first rollout small; close gaps one by one
    8. The system exposes; the floor and the fix stay with people
    ↗
22. Business processesFinancial Acumen

    1. Watching profit alone hides where cash is stuck
    2. A sale is not a cash receipt
    3. Three statements must tell one story
    4. How many units win back the fixed cost
    5. Why less inventory can look worse in profit
    6. Three clocks sit between cash out and cash back
    7. Profit must clear the cost of capital
    8. Did cash follow the reported profit?
    9. Normalize before explaining the margin
    10. Unchanged products, a different mix
    11. Three green cells hide rising costs
    12. Saved seconds count only with headcount and a P&L line
    13. Five questions before trusting a number
    14. Investing in growth thins this period’s profit first
    15. Low-share businesses earn below the capital-cost line
    16. Hand over a reviewable financial packet
    17. The system flags the reading; people own attribution
    ↗
23. Variation ReductionFailure Mode and Effects Analysis

    1. Rank by RPN alone and the fatal item goes last
    2. Problems outside the boundary go to whoever owns them
    3. Connect failure, cause and effect
    4. Severity looks only at the consequence, and takes the worse side
    5. Occurrence needs a real denominator
    6. Detection is where the defect gets stopped
    7. Low RPN does not mean low risk
    8. Prevent first; do not rely on end detection
    9. An action may change only the score it really changes
    10. Close rows without erasing old scores
    11. A lower total still needs cause-by-cause review
    12. When something changes, the living file returns to the workplace
    13. The system computes and checks; the team does the scoring
    ↗
24. Leadership TransformationFunctional Department Planning Template

    1. When every department reports its own way, strategy breaks in the middle
    2. Every department goal should trace back to the company mission
    3. Every piece of work needs an owner
    4. Prerequisite capability first, results after it
    5. A request moving up needs someone to catch it
    6. Days and people are two ledgers; never convert
    7. A gap is not just a number; attach its cause analysis
    8. Progress can be full while support goes unanswered
    9. Hand over only when all four parts are in; hand over again after any edit
    10. The template gives the format; content and judgment stay with people
    ↗