Lean Leadership, Culture, Ethics and Governance

Introduction

Lean manufacturing is often introduced through tools such as 5S, value-stream mapping, standardized work, kanban, quick changeover, and mistake-proofing. Yet tools do not sustain improvement by themselves. They produce lasting results only when leaders create the conditions in which people can identify problems, test solutions, learn from failure, and protect process quality. Lean leadership is therefore not simply the supervision of production. It is a system of behaviors, routines, decision rights, measures, and ethical commitments that connects organizational purpose with daily work.

This chapter examines the human and governance foundations of lean manufacturing. It focuses on daily management, leader standard work, coaching, team problem solving, and change management. It also addresses difficult questions that arise when lean methods are implemented: How should workers participate? How can productivity improvement be separated from unsafe work intensification? What responsibilities do managers have when technology displaces jobs? When do performance dashboards become surveillance systems? How can organizations prevent KPI manipulation and govern improvement fairly?

The central argument is that lean performance and ethical performance are interdependent. A factory that improves output by concealing defects, discouraging reporting, or exhausting employees is not lean in the strategic sense. It is transferring cost and risk to workers, customers, suppliers, or society. Sustainable lean systems improve flow and capability while preserving safety, dignity, voice, accountability, and long-term learning.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain the purpose and elements of lean leadership and daily management.
2. Design basic leader standard work and distinguish it from employee surveillance.
3. Apply coaching and structured team problem-solving methods.
4. Analyze the cultural conditions required for continuous improvement.
5. Evaluate change-management strategies in a manufacturing setting.
6. Discuss worker participation, safety, dignity, job displacement, and data ethics.
7. Identify KPI manipulation and propose balanced governance controls.
8. Develop an improvement-governance framework that combines performance, ethics, and accountability.

1. Lean Leadership as a Socio-Technical System

A manufacturing system is socio-technical: it combines physical assets, information, methods, organizational roles, and human judgment. Lean leadership must therefore manage both technical variation and social conditions. A technically excellent process may fail if operators are afraid to stop production, if maintenance technicians are excluded from improvement decisions, or if supervisors are rewarded only for short-term output.

Lean leadership has four complementary responsibilities:

• Set direction: Translate customer, safety, quality, and strategic requirements into understandable priorities.
• Stabilize the system: Ensure that standards, resources, staffing, equipment, and escalation routes support reliable work.
• Develop people: Teach problem solving rather than merely issuing instructions.
• Improve the system: Remove causes of waste and variation while learning from evidence.

These responsibilities reflect two dimensions of lean management. The first is process management, which concerns flow, quality, equipment, materials, and information. The second is people development, which concerns capability, participation, motivation, and judgment. Treating only the first dimension produces tool-driven lean; treating both produces a learning organization.

A useful distinction is between authority over people and responsibility for the system. A supervisor may have authority to assign work, but leadership requires responsibility for making good work possible. If an operator repeatedly bypasses a safety device, the first question should not be “Why is the operator noncompliant?” It should also be “What design, production pressure, training gap, or conflicting target makes the unsafe behavior appear necessary?” Accountability remains important, but it should be informed by system analysis.

2. Daily Management

Daily management is the set of routines through which a team observes current conditions, compares them with expected conditions, responds to abnormalities, and learns. It is not a daily meeting alone. It is a management control system operating at the workplace or gemba, where value is created.

A practical daily-management cycle contains five elements:

1. Make standards visible. Display the expected production sequence, quality criteria, safety controls, staffing plan, and escalation contacts.
2. Check actual conditions. Review a small number of current indicators and observe the process directly.
3. Identify abnormalities. Distinguish normal variation from conditions requiring immediate attention.
4. Respond and escalate. Correct what can be corrected locally and escalate issues beyond the team’s authority.
5. Reflect and learn. Record causes, countermeasures, unresolved risks, and follow-up responsibilities.

Daily management should answer four questions:

• What should be happening now?
• What is actually happening?
• What is preventing the expected condition?
• Who will take what action, by when, and with what evidence of completion?

Measures for daily management

A strong board or digital dashboard usually combines leading and lagging indicators. Lagging indicators describe outcomes, such as defects or delivery misses. Leading indicators describe conditions that influence future outcomes, such as completion of preventive maintenance, training qualification, safety observations, or closure of root-cause actions.

Measures should be limited to those that support decisions. A useful classification is:

Measures become dangerous when a single target dominates all decisions. For example, a production target that excludes safety and quality may encourage over-speeding, inspection avoidance, or under-reporting. Balanced measures do not mean that every indicator receives equal numerical weight; they mean that unacceptable harm cannot be traded away for output.

Escalation and abnormality management

Daily management requires a clear escalation path. An operator should know when to stop, whom to call, what information to record, and how the issue will be reviewed. Escalation must not be interpreted as personal failure. If every abnormality is hidden to protect a performance score, the organization loses the information needed for improvement.

A useful escalation record includes:

• time and location;
• observed condition and expected condition;
• immediate containment;
• safety or customer risk;
• person responsible for investigation;
• due date and verification method.

The distinction between containment and corrective action is essential. Containment protects the next process or customer immediately; corrective action removes or controls the cause. Reworking defective parts may be necessary containment, but it is not proof that the process has improved.

3. Leader Standard Work

Standardized work is commonly associated with operators, but leaders also need standard work. Leader standard work defines recurring leadership activities that maintain system health and develop people. Examples include workplace observation, review of abnormality records, safety verification, coaching conversations, layered process audits, and follow-up on improvement actions.

Leader standard work differs from a checklist of managerial tasks in three ways:

1. It is connected to a purpose, such as detecting process drift or developing problem-solving capability.
2. It specifies a frequency and a method, not merely an intention.
3. It requires reflection and adaptation when the routine does not reveal or solve important problems.

A basic leader-standard-work schedule might include:

Leader standard work is not a justification for intrusive surveillance. The purpose is to improve conditions and capability, not to collect excessive personal data or rank employees by isolated observations. A leader should observe the process, ask respectful questions, and remove barriers. Data collection should be necessary, proportionate, transparent, access-controlled, and retained only as long as justified by policy or law.

4. Coaching and Developing Problem Solvers

Lean leaders coach people to understand situations and test causes rather than immediately supplying answers. Effective coaching combines inquiry, observation, and challenge. Typical questions include:

• What is the actual condition?
• What was expected?
• What evidence supports that conclusion?
• Which causes have been tested rather than assumed?
• What is the smallest safe experiment that can be run?
• How will we know whether the countermeasure worked?

The coach should not turn inquiry into interrogation. Psychological safety matters: people must be able to report a mistake or uncertainty without humiliation or retaliation. Psychological safety does not mean the absence of standards. It means that standards and accountability can be discussed honestly.

A practical coaching sequence is:

1. Ask the learner to state the problem in observable terms.
2. Visit the work location and examine facts.
3. Ask the learner to propose a cause and a test.
4. Agree on a small experiment with a defined safety boundary.
5. Review evidence and revise the explanation.
6. Standardize the learning if the countermeasure is effective.

This method develops capability because it teaches a repeatable way of thinking. It also prevents a common failure mode in which managers solve every problem personally and unintentionally create dependence.

5. Team Problem Solving

Lean problem solving should be rigorous without becoming bureaucratic. A team needs a common language for defining problems, analyzing causes, selecting countermeasures, and verifying results. The Plan–Do–Check–Act cycle is a useful general framework:

• Plan: Clarify the gap, establish facts, analyze causes, and predict a countermeasure.
• Do: Test the countermeasure on a controlled scale.
• Check: Compare results with the expected condition and examine unintended effects.
• Act: Adopt, revise, or reject the countermeasure; update standards and share learning.

A problem statement should avoid vague language such as “operators are careless.” A stronger statement identifies what, where, when, and the size of the gap: “During the second shift, torque failures increased from the normal level in Station 4 after tool changeover.”

Root-cause tools include the five-whys method, cause-and-effect diagrams, process observation, stratification, and basic data analysis. These tools are aids to reasoning, not substitutes for evidence. The five-whys method is especially vulnerable to oversimplification when a team stops at a person’s action instead of examining design, training, workload, materials, equipment, and management controls.

Worked application: validating an improvement

Suppose a team reports that defects fell from 40 to 20 per 1,000 units after a fixture redesign. The apparent reduction is 20 defects per 1,000 units, or 50%. The calculation is:

Here, the numerator and denominator are both defects per 1,000 units, so the ratio is dimensionless. This calculation describes an observed change; it does not by itself prove that the redesign caused the improvement. The team should check production mix, inspection method, sample size, shift effects, and whether the result persists over time. It should also verify that the redesign did not increase cycle time, ergonomic risk, material waste, or defects in another characteristic.

A credible improvement claim therefore includes both the primary result and possible trade-offs. Lean governance requires evidence of net improvement, not merely a favorable number on one dashboard.

6. Culture and Change Management

Organizational culture is expressed through repeated behavior and the consequences attached to it. Posters and slogans have little effect if managers punish bad news, ignore worker ideas, or reward output regardless of quality. A continuous-improvement culture has several observable characteristics:

• problems are made visible rather than concealed;
• standards are treated as current hypotheses that can be improved;
• workers have meaningful influence over work design;
• leaders spend time at the workplace and listen;
• experiments are controlled and reviewed;
• learning is shared across teams;
• safety and dignity are non-negotiable conditions.

Change management is needed because lean implementation changes routines, authority, measures, and sometimes employment structures. A technically sound change can fail when affected people do not understand its purpose, lack the capability to use it, or believe that participation will harm them.

A practical change process includes:

1. Establish the operational and human case for change.
2. Identify affected groups, interests, risks, and sources of expertise.
3. Involve workers before the design is fixed.
4. Pilot the change under safe and measurable conditions.
5. Provide training, time, equipment, and support.
6. Review results, including unintended consequences.
7. Revise standards and governance rules.
8. Scale only when the process is stable and accepted.

Resistance should not automatically be treated as irrational. It may reveal legitimate concerns about workload, fairness, job security, or a poorly designed process. Listening to resistance is a form of risk analysis.

7. Worker Participation, Safety and Dignity

Worker participation is both an ethical requirement and a source of operational knowledge. Operators often understand variation, awkward motions, material behavior, and informal workarounds that are invisible to engineers or managers. Participation can take the form of suggestion systems, improvement teams, safety committees, design reviews, stop-work authority, skills development, and representation in governance forums.

Participation is meaningful only when several conditions exist:

• people have access to relevant information;
• their input can influence decisions;
• they are given time and resources to participate;
• credit and recognition are fairly assigned;
• retaliation is prohibited;
• decisions and reasons are communicated.

Safety must be integrated into lean decision making. Removing waiting time or motion is not an improvement if it creates excessive fatigue, unsafe reach, inadequate recovery time, or pressure to bypass controls. Ergonomic evaluation, hazard assessment, incident learning, and legal compliance should occur before and after process changes.

Dignity includes respectful treatment, privacy, fair scheduling, freedom from harassment, and recognition that employees are not merely units of labor. A lean system may use performance data, but the data should describe process conditions and support development rather than reduce a person to a score.

8. Surveillance, Data Ethics and Artificial Intelligence

Digital manufacturing technologies can record cycle times, location, machine interactions, quality events, and operator identifiers. These data can support traceability and process improvement, but they can also create continuous surveillance. The ethical question is not whether data are technically collectible; it is whether collection and use are justified.

A responsible data-governance policy should specify:

• the legitimate purpose of collection;
• the minimum data needed;
• who can access the data;
• how accuracy is checked;
• how long data are retained;
• whether data may be used for discipline or evaluation;
• how workers can challenge errors;
• how privacy and security are protected.

Artificial intelligence can identify patterns in downtime, predict equipment failure, or support scheduling. However, algorithmic recommendations may reproduce historical bias, confuse correlation with cause, or penalize workers for conditions outside their control. Human review, explainability appropriate to the decision, audit trails, and appeal mechanisms are necessary when AI affects safety, discipline, scheduling, or employment.

Technology should augment human judgment, not eliminate the obligation to investigate context. A model that flags a slow cycle may be detecting a damaged tool, a training need, an accessibility requirement, or a deliberate safety action. Treating the signal as proof of poor performance is analytically and ethically unsound.

9. Job Displacement and a Just Transition

Lean improvement can reduce labor requirements through automation, process redesign, or elimination of rework. Increased productivity can benefit an organization, but job displacement creates responsibilities beyond the narrow project business case. Ethical governance asks who receives the benefits, who bears the costs, and what transition support is available.

Responsible responses may include retraining, redeployment, phased implementation, reduced involuntary displacement, transparent consultation, severance consistent with law and policy, and partnerships with educational institutions. Workers should be informed early enough to influence alternatives, not merely notified after decisions are irreversible.

This issue also affects improvement participation. If every suggestion is perceived as a threat to employment, employees may rationally withhold ideas. A credible commitment to fair treatment encourages participation and increases the quality of improvement information.

10. KPI Manipulation and Balanced Accountability

A KPI becomes vulnerable to manipulation when it is strongly rewarded, poorly defined, difficult to audit, or disconnected from the system’s broader purpose. Common examples include delaying defect recording until the next reporting period, producing inventory ahead of demand, reclassifying downtime, avoiding difficult orders, or pressuring inspectors to accept marginal products.

KPI manipulation can be addressed through:

• clearly defined operational terms;
• independent data validation;
• balanced measures;
• trend and exception analysis;
• separation of reporting and reward decisions where appropriate;
• review of unintended consequences;
• protection for good-faith reporting;
• consequences for deliberate falsification.

Accountability should distinguish error, negligence, systemic constraint, and intentional deception. A person who reports a defect should not receive the same treatment as someone who knowingly falsifies records. At the same time, systemic pressure does not excuse fraud; it signals that governance and incentives require correction.

A useful principle is no target without a countermeasure for gaming. When a measure is introduced, leaders should ask how it could be achieved in a way that harms quality, safety, workers, customers, or the environment. This question should be revisited as conditions change.

11. Improvement Governance

Improvement governance defines who may propose, approve, implement, audit, and reverse changes. Without governance, local optimization can damage the wider value stream. For example, one department may reduce its queue by sending incomplete work to the next department, or a maintenance shortcut may improve uptime while increasing future failures.

An improvement-governance system should include:

1. Decision rights: Clarify which changes teams can make independently and which require engineering, safety, quality, labor, or regulatory review.
2. Risk classification: Classify changes according to potential effects on people, product, process, data, environment, and compliance.
3. Evidence requirements: Define what baseline, pilot, validation, and follow-up evidence are required.
4. Worker consultation: Require participation from people who perform or are affected by the work.
5. Change control: Update standard work, training, maintenance information, and documentation.
6. Post-implementation review: Check whether the intended benefit occurred and whether harm or new waste appeared.
7. Reversibility: Where feasible, pilot changes so that they can be safely withdrawn.
8. Audit and learning: Review not only compliance but also whether governance improves decision quality.

A simple governance matrix can distinguish low-, medium-, and high-risk changes. A low-risk change to visual labeling may be approved by the team after a local check. A change to a machine guard, product specification, chemical process, or worker-monitoring system requires formal technical, safety, legal, and employee review.

Governance should not become an excuse for paralysis. The goal is proportionate control: fast learning for low-risk experiments and strong review for changes with irreversible or high-consequence effects.

12. Illustrative Case: The Orion Pump Assembly Line

Background

Orion Pumps, a fictional industrial-equipment manufacturer, introduced lean methods on a pump assembly line. Management installed a digital dashboard showing hourly output, cycle-time adherence, defects, and individual workstation performance. The initial objective was to reduce delivery delays.

Problem

After three months, reported output increased by 9%, but customer returns rose. Operators also reported that they were discouraged from stopping the line because a stop reduced the hourly score. Maintenance staff found that minor equipment abnormalities were being recorded as operator delays. Several employees stopped submitting improvement suggestions because previous ideas had reduced rework but had also eliminated overtime opportunities.

Analysis

A cross-functional team examined production records, interviewed operators, observed the line, and compared internal defect data with customer returns. It found four interacting causes:

• the dashboard emphasized output more strongly than quality or safety;
• individual rankings encouraged workarounds and competition;
• stop-work authority existed in policy but not in practice;
• improvement governance did not require worker or maintenance approval.

The team also discovered that one workstation’s cycle-time target was below the time required for a safe ergonomic motion sequence. Employees were compensating by rushing or skipping a pause.

Approach and solution

The company made several changes. It replaced individual rankings with team-level indicators and added first-pass yield, verified safety-control completion, and unresolved-abnormality age. A stop-work signal was treated as a positive control action when used appropriately. Leaders received coaching on asking for facts rather than assigning blame.

The line introduced a weekly worker–engineer improvement review. Changes affecting ergonomics, guarding, quality characteristics, or data collection required documented review. The digital system was revised so that operator identity was not displayed on the main performance board; access to individual records was limited and governed by a written purpose.

Management also created a transition policy for productivity improvements. When a change reduced labor demand, affected employees would first be considered for training and redeployment. This policy increased willingness to propose ideas.

Outcome

After six months, delivery adherence improved, customer returns declined, and improvement suggestions increased. Output was lower than the misleading short-term peak but more stable. The company concluded that the original output increase had partly represented hidden quality and human costs. The revised system produced slower but more reliable improvement.

Learning points

1. A KPI can improve while the system worsens.
2. Stop-work authority must be reinforced by actual managerial behavior.
3. Worker participation improves both ethical legitimacy and technical diagnosis.
4. Digital measurement requires purpose limitation and access controls.
5. Productivity gains need a fair transition policy.
6. Improvement governance should evaluate trade-offs, not only headline results.

13. Challenges and Limitations

Lean leadership is not a universal recipe. Several limitations require critical judgment.

First, standardization can become rigid bureaucracy if leaders treat every deviation as misconduct rather than as information. Standards should define safe and effective current practice while allowing controlled improvement.

Second, visual management can become visual pressure. Boards that display individual rankings or public failure counts may encourage concealment and humiliation. Visibility should support problem solving, not punishment.

Third, participation can become tokenism. Asking workers for suggestions without providing decision power, time, or feedback damages trust.

Fourth, lean methods may be applied in environments with unstable demand, unsafe employment conditions, or inadequate labor protections. In such settings, management should not use lean language to disguise work intensification or transfer risk to vulnerable workers.

Finally, no governance system eliminates judgment. Rules may conflict, data may be incomplete, and improvement effects may take time to appear. Ethical leadership requires openness about uncertainty and willingness to revise decisions.

14. Best-Practice Principles

The following principles summarize robust practice:

• Begin with purpose, customer value, safety, and dignity rather than tools.
• Make expected conditions and abnormalities visible.
• Use leader standard work to develop people and stabilize processes.
• Treat bad news as valuable information.
• Separate containment from verified corrective action.
• Use balanced measures and anticipate gaming.
• Involve workers before decisions are fixed.
• Apply proportional data governance to digital and AI systems.
• Review productivity changes for employment and distributional effects.
• Require evidence, consultation, and follow-up for significant changes.
• Reward learning and reliable improvement, not merely favorable reports.
• Hold individuals accountable fairly while examining system causes.

Chapter Summary

Lean leadership is the disciplined practice of aligning purpose, process, people, and improvement. Daily management makes expected conditions visible, detects abnormalities, assigns action, and creates a learning rhythm. Leader standard work gives managers repeatable routines for observation, coaching, escalation, and follow-up; it should develop capability rather than create intrusive surveillance.

Coaching and team problem solving rely on facts, respectful inquiry, controlled experiments, and verification. A continuous-improvement culture depends on psychological safety, meaningful worker participation, and leaders who respond constructively to problems. Change management must address capability, workload, job security, and trust as well as technical design.

Ethical lean leadership protects safety, dignity, privacy, and fair treatment. Digital dashboards and AI require purpose limitation, transparency, access controls, human review, and appeal mechanisms. Productivity improvement may create job displacement, so responsible organizations plan retraining, redeployment, and fair transition. KPI governance must prevent manipulation and distinguish honest error from deliberate falsification. Improvement governance establishes decision rights, risk review, worker consultation, evidence requirements, change control, and post-implementation learning.

The strategic lesson is that lean performance cannot be separated from ethical governance. An organization that conceals defects, intensifies unsafe work, or silences workers may produce favorable short-term metrics but has not built a capable or sustainable lean system.

Key Terms

Daily management: Routine control and learning activities used to compare actual conditions with expected conditions.

Gemba: The actual place where work and value creation occur.

Leader standard work: Defined recurring leadership activities that stabilize processes and develop people.

Abnormality: A condition that differs from the expected standard or creates unacceptable risk.

Escalation: Transfer of an issue to a person or level with the authority or capability to respond.

Containment: Immediate action that protects the next process, worker, or customer from a problem.

Corrective action: Action intended to remove or control the cause of a problem.

Coaching: Guided questioning and support used to develop another person’s problem-solving capability.

Psychological safety: A shared belief that people can raise concerns, questions, or mistakes without humiliation or retaliation.

Standardized work: The documented current best-known method for performing work safely and effectively.

Worker participation: Meaningful involvement of employees in decisions affecting work, safety, improvement, or employment.

KPI manipulation: Deliberate alteration or gaming of behavior or data to improve a measure without improving the underlying system.

Balanced measures: A set of indicators covering multiple dimensions such as safety, quality, delivery, cost, people, and environment.

Improvement governance: Rules and decision processes governing the proposal, approval, implementation, validation, and review of changes.

Purpose limitation: Restricting data collection and use to a specified legitimate purpose.

Stop-work authority: The right and responsibility to pause work when a serious safety or quality risk exists.

Just transition: Fair support for people and communities affected by technological or organizational change.

Layered process audit: Repeated process checks performed at different organizational levels to verify critical conditions.

Review Questions

Short Answer Questions

1. What are the five basic elements of daily management?
2. How does leader standard work differ from a simple managerial checklist?
3. Why should containment be distinguished from corrective action?
4. Name four conditions required for meaningful worker participation.
5. What is purpose limitation in manufacturing data governance?

Long Answer Questions

1. Explain how lean leadership combines process management with people development.
2. Discuss how psychological safety and accountability can coexist in a lean organization.
3. Describe the risks of using individual productivity rankings on a digital manufacturing dashboard.
4. Explain how an organization should govern a change that affects safety, product quality, and employment.
5. Evaluate the ethical responsibilities of a manufacturer introducing automation that displaces workers.

Analytical / Application Questions

1. A plant’s output KPI improves by 8%, but customer complaints, overtime, and near-miss reports also increase. Analyze possible causes and propose a balanced daily-management response.
2. Design a leader-standard-work schedule for a production-cell supervisor. Include activities, frequency, purpose, and evidence of completion.
3. A worker-monitoring system flags one operator as consistently slow. Develop an investigation and governance process that considers equipment condition, ergonomics, training, privacy, and fairness before any employment decision is made.

Multiple Choice Questions with Answers

Question 1

What is the primary purpose of daily management in a lean system?

A. To rank employees publicly by individual output

B. To compare actual conditions with expected conditions and respond to abnormalities

C. To eliminate the need for standardized work

D. To replace all long-term planning with daily meetings

Correct Answer: B. To compare actual conditions with expected conditions and respond to abnormalities

Question 2

Which activity is an example of leader standard work?

A. Changing targets whenever results are unfavorable

B. Ignoring abnormalities that do not affect the current shift

C. Regularly observing work against a standard and coaching the team

D. Collecting personal data without a stated purpose

Correct Answer: C. Regularly observing work against a standard and coaching the team

Question 3

Why is containment different from corrective action?

A. Containment protects against immediate effects, whereas corrective action addresses causes

B. Containment is always permanent, whereas corrective action is temporary

C. Containment applies only to safety, whereas corrective action applies only to quality

D. Containment requires no decision, whereas corrective action requires no evidence

Correct Answer: A. Containment protects against immediate effects, whereas corrective action addresses causes

Question 4

Which condition best represents meaningful worker participation?

A. Workers submit ideas but never receive feedback

B. Workers are consulted only after a change is finalized

C. Workers influence decisions and receive time and resources to participate

D. Workers are responsible for improvements but cannot access relevant information

Correct Answer: C. Workers influence decisions and receive time and resources to participate

Question 5

A defect rate falls from 40 to 20 defects per 1,000 units. What is the observed percentage reduction?

A. 20%

B. 40%

C. 50%

D. 80%

Correct Answer: C. 50%

Question 6

Which practice most directly reduces KPI manipulation?

A. Using one output target for all decisions

B. Combining balanced measures with data validation and review of unintended consequences

C. Concealing unfavorable results until trends improve

D. Rewarding departments solely for meeting numerical targets

Correct Answer: B. Combining balanced measures with data validation and review of unintended consequences

Question 7

What is the most appropriate response when an AI system flags an operator as slow?

A. Automatically discipline the operator

B. Delete the data because algorithms are never useful

C. Investigate context, data accuracy, equipment, ergonomics, and fairness before deciding

D. Publish the operator’s score to motivate the entire team

Correct Answer: C. Investigate context, data accuracy, equipment, ergonomics, and fairness before deciding

Question 8

Which statement best describes psychological safety?

A. All performance standards are removed

B. People can raise concerns and mistakes without humiliation or retaliation

C. Managers accept every explanation without verification

D. Employees are protected from all forms of accountability

Correct Answer: B. People can raise concerns and mistakes without humiliation or retaliation

Question 9

What is a key responsibility when automation displaces jobs?

A. Avoid informing affected workers until implementation is complete

B. Provide fair transition measures such as retraining and redeployment where feasible

C. Transfer all costs to workers who lose employment

D. Stop measuring productivity improvements

Correct Answer: B. Provide fair transition measures such as retraining and redeployment where feasible

Question 10

Why is proportionate improvement governance important?

A. It ensures every minor change requires the same lengthy approval process

B. It prevents all experimentation in production

C. It matches review and control requirements to the potential risk of the change

D. It allows high-risk changes to bypass worker consultation

Correct Answer: C. It matches review and control requirements to the potential risk of the change