From Proposal Systems to a Culture of Improvement — Building a Comprehensive Continuous Improvement System

Continuous improvement (Kaizen) is one of the core principles of quality management. However, many companies face a common dilemma: training has been conducted, systems are in place, and rewards have been distributed, yet employees' enthusiasm for improvement remains unsustainable. What is the issue?

The answer often lies not in the tools themselves but in whether the company has truly established a system that fosters a "culture of improvement." This article will systematically outline the complete path from proposal systems to a culture of improvement, helping companies transform "improvement for me" into "improvement by me."

1. Three Levels of Improvement Culture

To understand how to build an improvement culture, it is essential to recognize its three levels:

Level 1 — Reactive Response: Improvement activities are initiated only when major quality incidents or customer complaints occur. Improvement is seen as the work of a "fire brigade," disconnected from daily operations.

Level 2 — System-Driven: Proposal systems, QC teams, improvement weeks, and other mechanisms are established, with employee participation driven by system evaluations and rewards. Improvement activities are often separate from daily work and can become formalistic.

Level 3 — Culture of Awareness: Improvement is integrated into everyone's daily work, forming a routine cycle of "identifying issues → analyzing root causes → implementing solutions → standardization." Employees proactively identify and solve problems, making improvement an organizational instinct.

Most companies are in the transition phase from Level 1 to Level 2. The goal is to advance to Level 3.

2. Proposal Systems — The First Cornerstone of Improvement Culture

2.1 Common Pitfalls of Proposal Systems

Many companies' proposal systems have critical flaws:

• Overemphasis on Economic Benefits — Only proposals that "save money" are recognized, overlooking small improvements in quality and safety.
• Lengthy Approval Processes — A proposal from submission to implementation may require three levels of approval, taking several months, which can dampen employee enthusiasm.
• Delayed Incentive Cycles — Annual evaluations and year-end rewards mean employees do not see results for six months after submitting a proposal, breaking the positive feedback loop.
• Quantity Over Quality — Departments may submit proposals to meet KPIs, leading to a decline in proposal quality and a loss of management confidence.

2.2 Key Elements of an Effective Proposal System

Immediate Feedback Principle: Proposals must receive a response (acceptance, modification suggestions, or postponement) within 48 hours of submission, regardless of their size. This "48-hour window" is crucial for maintaining employee engagement.

Tiered Handling Mechanism:

• Class A (Minor Improvements): Can be approved and implemented at the team level, with rewards settled weekly.
• Class B (Cross-Departmental Improvements): Approved at the department level, with monthly reviews and rewards.
• Class C (Major Improvements): Approved at the company level, managed as projects, with quarterly rewards.

Agile Implementation: 80% of proposals are Class A (minor improvements) and should be "implemented immediately, followed by formal procedures." A hallmark of an excellent proposal system is that employees' improvement suggestions begin to be implemented on-site within 72 hours of submission.

Primarily Spiritual Incentives: Display the names of proposers on improvement achievement boards, establish "Improvement Stars" honors, and share best practices at morning meetings—these spiritual incentives have a more lasting effect than one-time bonuses.

Case Study: After implementing a "48-hour response + 72-hour pilot" mechanism, a certain electronics manufacturing company increased its average monthly proposals from 37 to 286, and the implementation rate rose from 23% to 81%. The key was not the amount of rewards but the fact that employees saw their suggestions being adopted and implemented.

3. From Proposals to an Improvement System — Building a Closed Loop

Systems alone do not create culture; culture grows naturally when systems form a closed loop and operate continuously.

3.1 Four Phases of the Improvement Loop

① Identification and Reporting: Use standardized forms (one-page A3 reports, problem-solving templates) to lower the reporting threshold, allowing frontline employees to complete reports within 5 minutes.

② Review and Classification: Establish a rapid review team (daily/weekly rotation) to handle classification. The focus should be on "whether it is worth trying" rather than "whether it is good." Tolerate failures appropriately—exploratory improvements, even if they do not meet expectations, are valuable organizational learning.

③ Implementation and Tracking: Minor improvements are implemented by teams autonomously, while major improvements are tracked through project management. The key is process visualization—display the progress of each improvement in real-time on improvement boards or digital platforms. Transparency itself is a driving force.

④ Standardization and Institutionalization: Improvement outcomes must be converted into new standard operating procedures (SOS) or control plans to truly solidify as organizational capabilities. Improvements without standardization are like "fixing a roof that leaks again."

3.2 Linking Policy Deployment and Daily Management

Improvement activities should not operate independently of the company's management system but should be linked to policy deployment (Hoshin Kanri) and daily management:

• Policy Deployment (Upward): The company's annual strategic goals (e.g., "reduce customer complaint rate by 30%") are broken down into departmental/team improvement topics.
• Daily Management (Horizontal): Abnormalities in daily operations (nonconforming products, equipment downtime, delivery delays) trigger temporary improvement activities.
• Proposal Systems (Downward): Employee-initiated improvement suggestions are aggregated upwards, and valuable ones are incorporated into departmental improvement plans.

These three directions of improvement activities are cross-verified at "improvement review meetings": Are performance indicators trending positively? Are the improvement topics covering key issues? Are employees' proposals being effectively utilized?

4. Measuring Improvement Culture — Quantifying the Intangible

While "culture" seems intangible, the health of an improvement culture can be measured from the following dimensions:

The monthly trends of these indicators are more meaningful than their absolute values—upward trends indicate that the culture is growing.

5. Common Obstacles and Breakthrough Strategies

Obstacle One: "Too Busy to Improve"

This is the most common and dangerous excuse. Solution: Institutionalize improvement time—adopt the Toyota concept of "improvement days," with 2 hours of company-wide participation in improvement activities each week (not counted in performance evaluation time). Time is squeezed out, but it is also reserved by the system.

Obstacle Two: "No One Cares About My Suggestions"

The root cause is the lack of a feedback mechanism. Solution: Implement the 48-hour response system and establish a "proposal tracking board" (physical or digital), making the status of every proposal visible to all employees. Rejected proposals should also be given reasons—respectful responses to suggestions build more trust than rewards for accepted suggestions.

Obstacle Three: "Improvements Revert to the Old Ways"

This is a typical symptom of a missing standardization phase. Solution: When each improvement is completed, update the corresponding documents (work instructions/control plans) and include them in the scope of the next internal audit. Standardized improvements are "locked-in improvements."

6. Gradual Implementation Roadmap

Not all companies can leap directly to Level 3. It is recommended to proceed in the following stages:

Stage One (Months 1-3): Establish the simplest proposal system—a one-page form + a suggestion box + a weekly review meeting + immediate small rewards. The goal is to let employees know that "someone will listen to their suggestions."

Stage Two (Months 4-6): Introduce the one-page A3 improvement method and integrate the proposal system with QC team activities. Establish monthly improvement release meetings to recognize outstanding improvement cases.

Stage Three (Months 7-12): Link improvement activities with policy deployment and daily management systems to build a complete improvement loop. Establish a dashboard for measuring improvement culture.

Stage Four (Months 12-24): Digitize the system—implement a continuous improvement management system (CMS) to achieve digitalization of the entire proposal reporting, review, tracking, and standardization process. Transition the improvement culture from "system-driven" to "culture of awareness."

Knowledge Number: 5.1.2

Version: v20260602

Author: Quality Excellence Think Tank