From Proposal System to Improvement Culture — 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. Where does the problem lie?

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

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 only initiated when major quality incidents or customer complaints occur. Improvement is the work of a "fire brigade" and is disconnected from daily operations.

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

Level 3 — Culture-Aware: Improvement is integrated into everyone's daily work, forming a routine cycle of "identifying problems → 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 System — The First Cornerstone of Improvement Culture

2.1 Common Pitfalls in Proposal Systems

Many companies' proposal systems have fatal flaws:

• Overemphasis on Economic Benefits: Only proposals that "save money" are recognized, neglecting small improvements in quality and safety.
• Lengthy Approval Process: A proposal from submission to implementation requires three levels of approval, with a cycle lasting several months, which drains employee enthusiasm.
• Delayed Incentive Cycle: Annual evaluations and year-end rewards mean employees see results only six months after submitting a proposal, breaking the positive feedback loop.
• Quantity Over Quality: Departments submit proposals to meet KPIs, leading to a decline in proposal quality and a loss of management confidence.

2.2 Key Points for Effective Proposal System Design

Immediate Feedback Principle: Proposals must be responded to within 48 hours (accepted, modification suggestions, or deferred), regardless of their size. This "48-hour window" is crucial for maintaining employee participation.

Tiered Handling Mechanism:

• Class A (Small Improvements): 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 fall into Class A (small improvements) and should be "implemented immediately, followed by procedural formalities." A hallmark of an excellent proposal system is that employees' improvement suggestions are implemented on-site within 72 hours of submission.

Primarily Spiritual Incentives: Display the proposer's name on the improvement results board, establish an "Improvement Star" honor, and share excellent cases in 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 reward amount but the fact that employees saw their suggestions being adopted and implemented.

3. From Proposal to Improvement System — Building a Closed Loop

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

3.1 Four Links in the Improvement Loop

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

② Review and Classification: Establish a rapid review team (daily/weekly rotation) to achieve tiered handling. The focus of reviews should not be on "whether it is good" but on "whether it is worth trying." Tolerate appropriate failures—exploratory improvements, even if they do not meet expectations, are valuable organizational learning.

③ Implementation and Tracking: Small improvements are implemented autonomously by teams, 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 Solidification: Improvement results must be converted into new standard operating procedures (SOPs) or control plans to truly become organizational capabilities. Improvements that are not standardized are like "a fixed roof that leaks again."

3.2 Linking Policy Management and Daily Management

Improvement activities should not operate independently of the company's management system but must be linked to policy management (Hoshin Kanri / Policy Deployment) and daily management (Daily Management):

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

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

4. Measuring Improvement Culture — Quantifying the Invisible

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 a growing culture.

5. Common Barriers and Breakthrough Strategies

Barrier One: "Too busy to make improvements"

This is the most common and dangerous excuse. Solution: Institutionalize improvement time—adopt the Toyota concept of "improvement days," dedicating 2 hours per week for all employees to participate in improvements (not counted in performance evaluation time). Time is squeezed out, but it is also reserved by the system.

Barrier Two: "Proposals are useless anyway, no one looks at them"

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" are more effective in building trust than "approved rewards."

Barrier Three: "Improvements revert to the old ways"

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

6. Gradual Advancement Roadmap

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

First Stage (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 address their suggestions."

Second Stage (Months 4-6): Introduce the one-page A3 improvement method and combine the proposal system with QC team activities. Establish a monthly improvement release meeting to recognize excellent improvement cases.

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

Fourth Stage (Months 12-24): Digital upgrade—implement an improvement management system (CMS) to achieve digitalization of the entire process from proposal submission, review, tracking, to standardization. Transition the improvement culture from "system-driven" to "culture-aware."

Knowledge code: 5.1.2

Version: v20260602

Author: Quality Think Tank