SEF Reference Guide G17 | Manufacturing OpEx Maturity Assessment
How to use this guide. This is SEF's standard method and the numbers we start from. Every operation is different, so treat the targets, timings, weightings, and templates here as a starting point and adjust them to your products, customers, and risk. Write your version down before you measure against it. Do not apply a tool just to apply a tool. Every method here carries a cost in time, attention, and discipline, and the benefit has to justify that cost in your operation. If it does not, leave it out and say why. A lower score on a criterion you have deliberately chosen not to pursue is an honest score, not a failure. One thing should not change: the maturity level definitions, because they are the scoring basis for the assessment.
What it is
This guide covers two habits that decide whether improvement spreads or stalls. The first is asking people for ideas, acting on the good ones fast, and recognizing the people who deliver results. The second is copying what already works, from the next line, the next site, or another industry, and sending your own wins back out.
Both have long histories. Toyota started its Creative Idea Suggestion System in May 1951, modeled on Ford’s suggestion system after Toyota executives trained at Ford’s River Rouge plant. It drew 789 ideas in its first year, and by 1973 Toyota expected more than 250,000 suggestions from about 43,000 employees. Formal benchmarking started at Xerox around 1979 and 1980, when the company compared its costs and methods with Japanese competitors and with non-competitors such as L.L. Bean’s warehouse operation. Robert Camp, who led that work, wrote the standard text on it in 1989.
Recognition tells people improvement is part of the job. Transfer makes sure a good idea is used everywhere it fits.
Why it matters
- Cost: Most savings in a mature plant come from many small ideas, not a few big projects. A working suggestion system collects them.
- Speed: Copying a proven practice is faster and cheaper than inventing one. The problem has often been solved already, somewhere nearby.
- Quality and safety: Operators see defects and hazards first. A system that asks them, and acts, finds problems before customers or injuries do.
- People: Being asked, heard, and credited is one of the strongest drivers of engagement. Ignored ideas teach people to stop offering them.
Key terms
| Term | Meaning |
|---|---|
| Suggestion system | A structured way for employees to submit improvement ideas, with fast response, implementation of good ideas, and recognition. |
| Idea board | A visual board in the work area where ideas are posted, tracked through stages (new, evaluating, doing, done), and closed. |
| Recognition | Public acknowledgment of a person or team for an improvement. Can be informal (thanks at the daily meeting) or formal (periodic awards). |
| Best practice | A proven method that produces better results than the alternatives and can be documented and transferred to other areas. |
| Benchmarking | Comparing your processes and results against other organizations, inside or outside your industry, to find better practices to adopt. |
| Internal benchmarking | Comparing areas, lines, or sites within the same company. |
| Competitive benchmarking | Comparing with direct competitors, usually on results rather than methods. |
| Functional or generic benchmarking | Comparing a process (such as warehousing or changeover) with a leader in any industry. |
| Yokoten | A Toyota term for sideways sharing: spreading a proven countermeasure to every place it applies. |
| Benchmarking code of conduct | Ground rules for ethical benchmarking, such as the APQC code: stay legal, only ask for what you would share, protect confidential data, and prepare before contacting a partner. |
How to do it
Part A: Suggestions and recognition (PE-4)
- Make it easy to submit. A card, a board, or a simple form. One question: “What is the problem and what would you try?” Small ideas are welcome.
- Respond fast. Set a response rule, for example every idea gets an answer within one week. Speed matters more than the size of any reward.
- Let the team decide small ideas. The supervisor and team approve ideas within their area and budget. Only larger ideas go up for approval.
- Help people do their own ideas. The best systems have the person who raised the idea implement it, with support.
- Turn big ideas into projects. When an idea needs a team or capital, open a structured problem solving project (A3 or equivalent) with an owner and date.
- Recognize in public. Thank people at the daily meeting. Hold a periodic award (monthly or quarterly) for the best completed projects, based on results, not just ideas.
- Build it into careers. At the top level, a record of successful improvement is a stated requirement for promotion to team lead, supervisor, and above.
- Measure. Ideas per person per year, percent implemented, average days to response, and participation rate (share of people who submitted at least one idea).
Research by Alan Robinson and Dean Schroeder found that the strongest idea systems rely on many small ideas, quick response, and recognition, rather than large cash payouts tied to calculated savings. Big payouts tend to slow evaluation and cause arguments over credit.
Part B: Best practice transfer (PE-5)
- Share locally first. When an area solves a problem, write a one-page summary (problem, what changed, result, contact). Present it at the next area meeting.
- Keep a practice library. Store summaries in one searchable place, tagged by process and problem type.
- Ask “where else does this apply?” Make it a closing step on every A3. List the other lines or areas and assign someone to check each one.
- Bring in practices from sister sites. Set up site-to-site visits, shared metrics, and a regular call between functional leaders (maintenance, quality, planning).
- Look outside. Join an industry group, visit non-competing plants, attend site tours, and use public benchmarking data. Follow a benchmarking code of conduct.
- Adapt, then adopt. Understand why the practice works before copying it. Run a small trial, measure, then standardize.
- Send your own wins out. Offer tours, present at company or industry events, and host visitors. Teaching others also forces you to document your own method.
- Measure. Practices imported and adopted per year, practices exported, and the results achieved at the receiving site.
What each maturity level looks like
PE-4 Recognition of Improvement
| Level | Assessment wording | What it looks like on the floor | How to move up |
|---|---|---|---|
| 1 | Improvement is not recognized. | Ideas go to a box nobody empties, or nowhere. People who improve things get no credit. | Start asking. Add an idea board to one area and answer every idea within a week. |
| 2 | People are asked for their improvement suggestions. | Ideas are collected, but many sit without a decision. Feedback is slow. | Set a response time, let supervisors approve small ideas, and turn good ones into owned projects. |
| 3 | As Level 2, plus good suggestions become improvement projects. | Ideas are tracked through stages. Good ones have an owner, a plan, and a date. | Add public recognition: thanks at the daily meeting and a periodic award for results. |
| 4 | As Level 3, plus successful improvement projects are recognized with periodic public awards. | A monthly or quarterly award is held on schedule. Winners are posted on the board. People can name recent winners. | Write improvement results into promotion criteria for leads and supervisors. |
| 5 | As Level 4, plus improvement project success is a requirement for promotion. | Promotion files show improvement results. Leaders are known for developing ideas in others. | Keep criteria current and audit that promotions actually follow them. |
PE-5 Best Practice Transfer
| Level | Assessment wording | What it looks like on the floor | How to move up |
|---|---|---|---|
| 1 | No evidence of best practice transfer. | Each area solves its own problems. The same fix is invented twice. | Start a one-page practice summary and share it at area meetings. |
| 2 | Best practices are shared locally between work areas. | Areas copy each other’s boards, fixtures, and methods. Shared practices show up in SOPs. | Set up regular exchange with sister sites or business units. |
| 3 | As Level 2, plus best practices are brought in from other sites or business units within the company. | Visits and calls with other sites happen on a schedule. Imported practices can be traced to their source. | Join an industry group or peer network and plan outside visits. |
| 4 | As Level 3, plus best practices are brought in from outside the company (benchmarking, peers, industry groups). | A benchmarking plan exists. At least one outside practice has been trialed and adopted this year. | Package your own strongest practices and offer them to other sites. |
| 5 | As Level 4, plus the operation’s own best practices are transferred out to other sites or organizations. | Other sites visit to learn. The operation presents at company or industry events. Exported practices are tracked. | Measure results at receiving sites and keep the library current. |
Evidence to look for
Document
- Idea log or tracker with dates submitted, decided, and closed.
- Award records: dates, winners, and the results that earned the award.
- Promotion criteria or job descriptions that name improvement results.
- Best practice library entries with source and receiving areas.
- Benchmarking visit reports and action lists.
Observation
- Idea boards in work areas with recent entries and closed items.
- Recognition displays with current winners.
- Practices visibly copied between areas or sites (same board layout, fixtures, or standards).
Statement
(questions to ask, and who to ask)
- Operator: “When did you last give an idea? What happened to it?”
- Supervisor: “How long does it take to answer an idea? Who can approve it?”
- HR: “What does a supervisor need to show to be promoted?”
- Plant manager: “Name a practice you took from another site or company this year, and one you gave away.”
Management report
- Ideas per person, percent implemented, days to response, participation rate.
- Number of awards given and results delivered by winning projects.
- Practices imported and exported, with measured results.
Common pitfalls
- The black hole. Ideas go in and nothing comes out. This is worse than having no system, because it teaches people not to bother.
- Paying for savings. Large cash rewards based on calculated savings create delays, disputes, and a focus on big ideas only.
- Awards on a whim. Recognition that happens when leadership remembers is not a system. Put it on the calendar.
- Copy without understanding. A practice lifted without knowing why it works often fails at the new site.
- Tourism. Benchmarking visits that produce photos but no actions. Every visit should end with a list of things to try, with owners.
- Hoarding. Sites that treat their methods as competitive advantage against sister sites. Make transfer part of how leaders are judged.
Template
Idea card / tracker fields
| Field | Entry |
|---|---|
| Idea number | |
| Date submitted | |
| Submitted by (person or team) | |
| Area | |
| Problem seen | |
| Idea to try | |
| Decision (yes / no / needs project) and date | |
| Reason if no | |
| Owner and target date | |
| Result (cost, quality, safety, delivery, time) | |
| Date closed | |
| Recognized (how and when) | |
| Where else could this apply? |
Best practice one-page summary
| Section | Content |
|---|---|
| Title | |
| Source area or site, contact person | |
| Problem it solves | |
| What was changed (with photo reference or sketch) | |
| Result, before and after | |
| Conditions needed for it to work | |
| Standards or documents updated | |
| Areas or sites it has been transferred to |
First 30 days
- Week 1: Put an idea board in one area. Agree the response rule (one week) and who can approve small ideas. Pull any old, unanswered ideas and answer them.
- Week 2: Review ideas in the daily meeting. Start the first small ideas. Write two one-page practice summaries from recent wins.
- Week 3: Set the award cadence and criteria. Book a call or visit with a sister site to trade one practice each way.
- Week 4: Hold the first recognition. Report ideas, implemented percentage, and response time. Plan one outside benchmarking contact for the next quarter.
Further reading
- Robert C. Camp, Benchmarking: The Search for Industry Best Practices That Lead to Superior Performance (ASQC Quality Press, 1989).
- Alan G. Robinson and Dean M. Schroeder, Ideas Are Free (Berrett-Koehler, 2004), and The Idea-Driven Organization (Berrett-Koehler, 2014).
- Yuzo Yasuda, 40 Years, 20 Million Ideas: The Toyota Suggestion System (Productivity Press, 1991).
- Carla O’Dell and C. Jackson Grayson, If Only We Knew What We Know: The Transfer of Internal Knowledge and Best Practice (Free Press, 1998).
- APQC, Benchmarking Code of Conduct: https://www.apqc.org/resource-library/resource-listing/benchmarking-code-conduct-0
- Toyota, history of the employee suggestion program: https://global.toyota/en/detail/7756353
Want this for your business?
This is a live example of what Systems Equal Freedom builds for owner-run businesses: operations that are documented, visible, and able to run without the owner in every loop.
