OPEXSTUDIO
OPEX learning notes / System chapters

Lean Leadership and Daily Management

Show how direction, local evidence, coaching and follow-through reinforce each other. The labelled map shows Shared direction, Catchball, Local target, Daily evidence, Leader response, Team experiment, Capability building, Review and adjust.
AI-generated system teaching illustration. Follow the steps below, then try the practice question. View full size ↗
← All lessons and training aids

Lean leadership connects direction with what happens in daily work. Use this chapter when targets, team routines and improvement efforts feel disconnected. Follow how leaders agree feasible commitments, respond to visible gaps and coach people to test and sustain better ways of working.

Fictional teaching examples and AI-generated illustrations. Proposed changes and goals are not achieved results. Use the written instructions and check local conditions before applying a method.

Published by OPEX Studio, a Prometheus Platforms product. Read the method sources and their scope.

On this lesson
Teaching view 1 of 3

Turn strategy into daily learning

Direction becomes useful through discussion of actual capability and resources. Catchball links organizational intent with local feasibility rather than cascading unsupported targets. A daily board then exposes the gap between the agreed plan and observed work. Leaders go to the work, ask what is understood and remove obstacles while developing the team’s problem-solving ability. A small experiment records its prediction and observed result. Job instruction supports the competence required to execute safely and consistently. Review checks evidence of effect, not merely completed actions or attendance, and carries learning back to both local targets and the wider plan.

Follow the method

  1. Shared direction: Customer purpose and meaningful challenge
  2. Catchball: Test feasibility, resources and ownership
  3. Local target: Describe the next observable condition
  4. Daily evidence: Plan versus actual and abnormality
  5. Leader response: Go see, ask and remove obstacles
  6. Team experiment: Prediction, small test and observation
  7. Capability building: Teach key points and reasons
  8. Review and adjust: Verify outcomes; adapt the plan

Read the example carefully

Daily management supports response and learning; a board alone is not the system.

Catchball includes feasibility and horizontal resource conflicts.

A completed action is not proof of an improved or sustained result.

Try it before revealing the answer

A board lists all actions complete, but no later condition check exists. What should the leader ask next?

Reveal the answer and reasoning

Ask what changed in the work, where it was observed and when it will be checked again. Keep effectiveness pending until evidence is available.

Teaching view 2 of 3

Align direction through catchball

Turn an organizational challenge into feasible contributions and two-way learning. The labelled map shows Purpose and challenge, Current condition, Proposed contribution, Catchball conversation, Horizontal alignment, Agreed experiment, Observed result, Adjust the plan.
AI-generated system teaching illustration. Follow the steps below, then try the practice question. View full size ↗

Catchball is a dialogue about purpose, contribution and feasibility. Begin with current evidence, then propose how a local team can contribute. Make resource needs and cross-team dependencies visible; the same specialist cannot be promised to incompatible work at the same time. Agree a bounded experiment or commitment with an owner, prediction and review point. Observe the result and its effect on workload and neighboring processes. Bring that learning back to both local plans and wider direction. The system depends on honest negotiation and learning; a cascade of targets without discussion does not provide the same mechanism.

Follow the method

  1. Purpose and challenge: Why this matters to customers
  2. Current condition: Evidence of capability and gaps
  3. Proposed contribution: Local result and supporting work
  4. Catchball conversation: Question assumptions and resources
  5. Horizontal alignment: Resolve shared capacity and dependencies
  6. Agreed experiment: Owner, prediction and review point
  7. Observed result: Outcome, workload and side effects
  8. Adjust the plan: Return learning to local and wider direction

Read the example carefully

Catchball is two-way discussion, including horizontal dependencies.

A proposed target is not an achieved outcome.

A shared resource needs an explicit feasible allocation.

Try it before revealing the answer

Two teams each promise daily support from the same specialist, whose capacity allows only one team per day. What should the catchball conversation produce?

Reveal the answer and reasoning

Expose the conflict and agree priorities, timing, scope or another feasible support arrangement. Record the resulting commitment and review evidence; do not approve both promises merely to preserve the target cascade.

Teaching view 3 of 3

Observe, coach and build capability

Connect direct observation, a learning conversation, deliberate practice and follow-through. The labelled map shows See the work, Ask the learner, Define next condition, Predict and test, Compare and reflect, Teach the job, Try and explain, Follow through.
AI-generated system teaching illustration. Follow the steps below, then try the practice question. View full size ↗

Observe what actually happens and separate facts from interpretations. Ask the learner how the work is understood and what obstructs the next condition. Where uncertainty calls for learning, use a small experiment with a prediction and compare the observation with that prediction. Where the need is competence in an established job, use job instruction: prepare, present the important steps with key points and reasons, let the learner try and explain, then follow up. These are related but distinct routes. Leader standard work creates time and responsibility for this support. Attendance, a coaching conversation or a completed demonstration alone does not establish sustained competence.

Follow the method

  1. See the work: Observe facts without assigning blame
  2. Ask the learner: Understand current reasoning and obstacles
  3. Define next condition: One observable step toward the challenge
  4. Predict and test: Small experiment with expected evidence
  5. Compare and reflect: What happened; what was learned?
  6. Teach the job: Important steps, key points and reasons
  7. Try and explain: Learner demonstrates understanding
  8. Follow through: Check competence and later condition

Read the example carefully

Gemba observation does not justify conclusions about unseen events.

Coaching an experiment differs from teaching an established job.

Follow-up should verify understanding and performance, not attendance alone.

Try it before revealing the answer

A learner repeats a step correctly once but cannot explain the identity check. Is the instruction complete?

Reveal the answer and reasoning

Not yet. Revisit the key point and reason, let the learner explain and demonstrate the full method, then follow up under appropriate supervision until competence is evidenced.

Build on reliable methods

Sources and further reading

  • LEI: Hoshin Kanri ↗

    Vertical/horizontal alignment, PDCA and capability development

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Daily Management and Hoshin Kanri ↗

    Daily standards/abnormalities and strategic feedback; do not copy source diagram

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Leader Standard Work ↗

    Gemba, reflection, andon response, accountability and mentoring

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Kata ↗

    Challenge, current condition, target condition, experiments and coaching

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Training Within Industry ↗

    Prepare, present, try out, follow up; steps/key points/reasons

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Standard Work for Lean Leaders ↗

    Leaders observe work and coach capability rather than blame or take over

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
Put this lesson to work

Start with the resource for this topic.

Read online without signing in, or take this lesson into your next team conversation.

Topic pack · 11 pages · Reviewed teaching edition.

Explore the full workbooks and facilitator collection
Free learning resources

Resources for a wider learning programme

Read the lessons online or use these PDFs to prepare, practise and review with your team. No sign-in needed.

Facilitators and team leads

Facilitator guide

Case objectives, demonstration plans, debriefs, common mistakes and application checks across all 81 workplace cases and method lessons.

Download Facilitator guide PDF · 166 pages · 65.1 MB
Learners and improvement teams

Learner workbook

Printable case worksheets, blank observation records and five calculation exercises; answers are separate.

Download Learner workbook PDF · 169 pages · 10.7 MB
Learners after practice and facilitators

Answer key and coaching notes

Reasoned sample responses, worked calculations and coaching guidance; fictional examples are clearly labelled.

Download Answer key and coaching notes PDF · 105 pages · 8.5 MB
Practitioners and facilitators seeking detailed worked methods

Method and application reference

The native method mechanisms and worked applications for all 68 detailed lessons, in a separate bookmarked portrait reference.

Download Method and application reference PDF · 141 pages · 10.2 MB
Self-study learners and workshop groups

Illustrated systems atlas

Five illustrated system chapters: 15 Flare concept maps and 26 original workplace teaching cards, with links to all 81 supporting cases and method lessons.

Download Illustrated systems atlas PDF · 69 pages · 55.8 MB
Connect the methods

Practise the methods in this system.

  • Show how direction, local evidence, coaching and follow-through reinforce each other.
  • Turn an organizational challenge into feasible contributions and two-way learning.
  • Connect direct observation, a learning conversation, deliberate practice and follow-through.
Explore 49 more connected methods
  • Hoshin: align strategy through catchball

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Improvement and coaching kata

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Job instruction: steps, key points and reasons

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Make tomorrow ready

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • TPS: people, quality and synchronized flow

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Muda, mura and muri reinforce each other

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Takt, cycle time and lead time are different

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Batch transfer versus one-piece flow

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Production and withdrawal kanban

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Office pull: capacity, blocked work and aging

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Heijunka mix and pitch release

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Connect processes: flow, bounded FIFO or supermarket

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Standardized work: sequence, takt and standard WIP

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Manual, walking and machine time

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Yamazumi: movable elements and constraints

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • SMED: externalize safely, verify first good output

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Replenishment stock: lead time and uncertainty

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • PFEP to point-of-use replenishment

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • TOC five focusing steps

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Find the constraint: evidence, not the biggest queue

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Drum-buffer-rope: schedule, protect, release

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Buffer management: priorities and recurring causes

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Throughput versus local utilization

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Critical chain: dependencies, resources and buffers

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Lean and TOC: complementary questions, distinct controls

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Shorten the handoffs

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Give the request a clear next step

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Keep the assembly line ready for the next frame

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • A clearer start for every cut order

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Make the welding bay ready to work

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • 5 Whys with evidence and alternative branches

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Choose a problem-solving approach

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • From broad complaint to a testable problem

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Conflict cloud: challenge assumptions

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Choose the quality tool for the question

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Record defects without changing the denominator

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Rank problems on one declared basis

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • See the distribution without losing the sequence

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Test a relationship without declaring a cause

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Unmix the data before blaming a shift

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Turn fishbone branches into testable hypotheses

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Close an NCR with verified action against recurrence

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Stop the recurring leak

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Make referrals ready

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Send the right shipment

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Make the morning easier

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Find it. Use it. Reset it.

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • A tool room ready for the next job

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Give the press area a clear reset

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

Explore all chapters and detailed lessons →

Apply the learning to your own work

Ask OPEX Guide how to apply this learning to your situation. Describe the expected condition, the gap and the evidence you have. Review its suggestions with the people doing the work before deciding on a change.

Explore your question with OPEX Guide →