In many Italian companies people work hard, they work well, and yet margins keep getting thinner. The background figure is well known: between 1995 and 2024, labor productivity in Italy grew by an average of 0.3% a year, against 1.5% for the EU-27 average and 1.2% for Germany [4][6]. The productivity gap between micro-enterprises and large companies, meanwhile, remains wide in most countries, particularly in manufacturing [8].
Operational efficiency — the ratio between useful output and resources consumed — is the most immediate lever for recovering margin without asking people to work more. The classification proposed by Taiichi Ohno distinguishes seven recurring categories of waste [2], to which later literature added an eighth: failing to use people's talent [3].
This article defines operational efficiency for managers, professionals and business owners, distinguishes it from related terms (effectiveness, productivity, optimization, continuous improvement), describes the 7+1 muda adapted to everyday business settings, proposes diagnostic methods for spotting waste in your own processes, and points to tools for measuring and reducing it and for involving people.
Since this is a practical guide, it is accessible to anyone running a professional practice, a small company or a mid-sized business: the examples cover all three profiles.
Recognizing operational efficiency in a company
Before tackling waste, it is worth pinning down exactly what the term means. Operational efficiency, effectiveness, productivity and optimization are often used as synonyms in everyday conversation, but they refer to different things. A shared definition keeps you from working on the wrong problems or applying unsuitable tools. This section offers a working definition and distinguishes the concept from its neighboring terms.
How many "optimization" meetings actually end up discussing effectiveness, without anyone making the distinction explicit? Confusing the two levels leads to cosmetic interventions: you change a process that was already efficient, while the one that really needs redesigning stays untouched.
Operational efficiency is the ratio between useful output produced and resources consumed: time, money, people, space. Womack and Jones [1] define it as the ability to create value for the customer by removing everything that does not contribute to that value. The ISTAT figure on labor productivity growth in Italy between 1995 and 2024 — 0.3% a year against 1.5% for the EU-27 average [4][6] — makes sense in this context: a significant share of that accumulated gap does not come from insufficient capability or effort, but from resources burned on activities that create no value.
Efficiency vs effectiveness. Effectiveness is about reaching the goal: a company is effective if it delivers the expected output (the customer receives what they bought, on the agreed schedule). Efficiency is about how it gets there: with how many resources, how many steps, how much waste. A company can be effective but inefficient (it delivers on time but wastes resources doing so); it can hardly be efficient but ineffective (no waste, but the wrong output).
Operational efficiency vs productivity. Productivity is the broader concept: output per unit of input (labor, capital, time). Operational efficiency is a specific component of it: it concerns reducing process waste, not increasing overall production capacity.
Operational efficiency vs process optimization. Optimization is an intervention on a single process to improve its parameters (reducing lead time, lowering the error rate). Operational efficiency is the systemic reading of the company: the sum of all its processes, with their waste and their improvement levers.
Operational efficiency vs continuous improvement. Continuous improvement (kaizen) is a recursive approach over time: you work to improve every day. Operational efficiency is a snapshot of the current state and the clean-up that follows. They are complementary but differ in time: snapshot vs continuous flow. The link with the recursive philosophy is developed in the cluster on continuous improvement in the company.
Using the 7+1 Lean muda to read waste in a business
The classification of the seven wastes was born at Toyota in the 1950s, from direct observation of production lines [2]. Over time, Western literature added an eighth muda — failing to use people's talent — which is particularly relevant in smaller companies, where knowledge is often concentrated in a few key people [3]. This section presents the 7+1 muda with specific examples for services, craft manufacturing, professional practices and retail: the settings in which most businesses operate.
Among overproduction, waiting, transportation, unnecessary processing, inventory, motion, defects and unused talent, which waste weighs most in your company? The most common answer — "inventory" — is often wrong: the 8th muda can cost more, but it is the least visible.
Muda 1 — Overproduction. Producing more than the customer asked for, or before they ask for it.
- Independent professional: preparing a detailed proposal for a client who is still exploring, before the request is confirmed.
- Small company: producing extra components "just in case" beyond the order, which then sit in the warehouse.
- Mid-sized company: generating weekly reports nobody reads, out of organizational habit.
Muda 2 — Waiting. Time when the flow stops because it is waiting for something: an approval, a file, an answer.
- Independent professional: waiting for client feedback before moving on to the next phase, without having agreed on a deadline.
- Small company: production stalled while waiting for the supplier to confirm material availability.
- Mid-sized company: an approval email bouncing between three managers for two days before an order is released.
Muda 3 — Transportation. Movement of materials or information that adds no value.
- Independent professional: documents bouncing between email, Drive and WhatsApp before reaching the right destination.
- Small company: paper passed between the sales office and production, when a shared system would eliminate the physical transfer.
- Mid-sized company: handoffs between departments with no tracking system, leading to lost or duplicated information.
Muda 4 — Unnecessary processing (over-processing). Doing more than the customer perceives as added value.
- Independent professional: polishing a document to graphic perfection when the client only needs the content.
- Small company: applying multiple quality checks to a product at overlapping stages.
- Mid-sized company: routing every document through three approvals when one would be enough for standard cases.
Muda 5 — Excess inventory. Materials, products or information waiting to be used.
- Independent professional: unprocessed emails piling up in the inbox as "pending to-dos."
- Small company: materials in the warehouse that tie up cash and physical space.
- Mid-sized company: projects in progress that advance slowly because too many initiatives are open at the same time.
Muda 6 — Unnecessary motion. Physical movements of people that add no value to the process.
- Independent professional: traveling in person to sign a document that could be signed digitally.
- Small company: whoever runs the warehouse walks more distance than necessary every day because the layout does not follow the logic of the flow.
- Mid-sized company: in-person meetings called for problems that a written note could solve.
Muda 7 — Defects and rework. Output that does not meet requirements and has to be corrected or scrapped.
- Independent professional: a proposal sent with incorrect data that requires a second version and an apology email.
- Small company: products that come back from quality control and need manual intervention.
- Mid-sized company: orders shipped with configuration errors that come back, with logistics and reputational costs.
Muda 8 — Unused talent. Failing to use people's skills, ideas and problem-solving ability [3].
- Independent professional: delegating valuable tasks to others while personally handling administrative work that could be managed differently.
- Small company: a skilled team member who is only given execution tasks and never involved in solving operational problems.
- Mid-sized company: team members' operational knowledge that stays implicit and is never turned into documented process improvements.
Recognizing hidden waste in business processes
The most expensive waste is the kind that has become invisible, because it is built into processes that "have worked this way for years." Recognizing it takes a method, not intuition. This section proposes a diagnostic procedure in sequential steps — mapping the flow, counting active and passive time, identifying the activities the customer would not be willing to pay for — that applies to both service and production settings.
Out of 100 minutes of an order's throughput time, how many are actually spent on work that adds value? In many smaller companies, the share of "active" time is a small fraction of the total — the rest is waiting, re-checking, double controls.
The Bank of Italy documents that adopting structured management practices — systematically collecting and using information to monitor and improve the production process, setting goals, incentives — is positively associated with the productivity of Italian companies, a link the authors describe as descriptive rather than causal [5]. The point is not a judgment of ability but a structural fact: unmapped processes tend to multiply waste over time.
The reference operational framework is simplified value stream mapping, described by Womack and Jones [1] as a tool for visualizing the value stream from the beginning to the end of a process. In a version adapted for smaller companies, it is applied in 5 steps:
Step 1 — Choose the process to analyze. Start from a critical, high-frequency process: the customer order (from quote to invoice), the delivery of your core service, complaint handling. Process mapping provides the complete method for building the map.
Step 2 — Follow the flow physically. Walk through (physically or virtually) every step of the process, noting who does what, how long it takes and where the flow stops. Don't trust descriptions: observe the process as it actually happens.
Step 3 — Separate active time from passive time. For each phase of the process, distinguish the time when value-adding work happens (something useful for the customer is produced) from the time when the flow is stopped (waiting, queuing, transfer). In many small-business processes, waiting time exceeds 70-80% of the total throughput time.
Step 4 — Identify the activities the customer would not pay for. The operational question: "If the customer knew this activity costs X and they get nothing direct in return, would they be willing to pay for it?" Activities that pass this test add value; the others are waste, candidates for removal or reduction.
Step 5 — List waste by muda category. Assign each waste you identify to the corresponding category (waiting, transportation, defects, etc.). This step lets you choose the most appropriate reduction tool for each type.
Measuring and reducing waste with a few operational indicators
Measure before you reduce is the basic operating rule: without a starting indicator, interventions turn into impressions. This section presents a small set of indicators — throughput time, rework rate, labor hours per output, average inventory level — and describes two reduction tools (5S and standard work) calibrated for organizations with fewer than 100 employees. The logic is "few indicators, measured well, periodically": you don't need an industrial dashboard.
What is the most reliable operational efficiency indicator for a company that doesn't yet have control systems? Often it isn't a financial figure: it's a time figure. Measuring it takes a few minutes a day and changes decisions sharply.
The model for integrating lean management and Industry 4.0 proposed by Sony (2018) puts measurement at the center: decentralized control of process data is what makes waste visible and ties its reduction to productivity and flexibility goals [7]. It is a conceptual work — a literature review and research propositions still to be tested — not a data-based survey; the original context is manufacturing and industrial, and the measurement-reduction mechanism carries over to service settings with the necessary adaptations.
Indicators to measure:
- Lead time of the core process: average time from the start to the close of the process (customer order, job, service delivery). Measured in days or hours, as a weekly or monthly average.
- Rework / non-conformity rate: percentage of output that needs correction before delivery. Measured by counting the cases in the period.
- Simplified OEE (Overall Equipment Effectiveness, in a small-business version): percentage of time in which key resources (critical staff, essential equipment) are actively productive compared with the time available. It doesn't require complex systems: a sheet with actual working hours vs available hours is enough.
- Inventory turnover (for those with a warehouse): ratio between the value of goods issued from the warehouse and the average value of the warehouse over a period. It shows how many times the warehouse "turns over" — a low value signals excess inventory.
For a broader treatment of performance indicators, the reference is the cluster on business KPIs.
Reduction tools:
- 5S (Sort, Set in order, Shine, Standardize, Sustain): a Lean methodology for organizing workspaces by removing what isn't needed and bringing order to what remains. Applicable to offices, warehouses and digital workstations. In a small company, a 5S intervention on a single area takes one day and produces immediate benefits in time spent searching, errors caused by confusion and stress caused by clutter.
- Standard work: documentation of the best currently known way to carry out a process, with defined sequence, times and quality requirements. It is the baseline on which later improvements are built. In a small company, standard work translates into simple SOPs (1-2 pages per process), updated every time a better way is found.
The process for involving people in identifying waste
The people who work in the process know its waste better than many outside observers. Often, though, they lack the context to recognize it or the room to speak up about it. This section describes a process in simple steps for activating team members' contribution: from "process walk" meetings to suggestion boards, all the way to a lightweight PDCA cycle for testing improvements. This is where the 8th muda — unused talent — becomes a concrete resource.
Why do team members often fail to report the waste they see every day? It isn't lack of interest: in most cases, the reporting mechanisms simply don't exist.
Liker documents how the contribution of frontline people is one of the 14 fundamental principles of the Toyota Production System [3]: it isn't just the manager who "goes and sees" (gemba walk); the people who work in the process become the active agents in identifying waste. Applied to smaller organizations, this principle becomes a structured 4-step process:
Step 1 — Participatory observation (a small-business gemba walk). Once a month, the process manager or the business owner walks the operational flow physically (or virtually, for remote processes) together with the people who carry it out. Not to check up on them, but to observe with fresh eyes and ask open questions: "What slows you down the most?", "Is there a step that seems pointless to you?", "What would you change if you could?"
Step 2 — Structured collection of suggestions. Observing isn't enough: you need channels to collect reports systematically. The minimum is a physical or digital board (even a simple shared folder) where team members can post reports of waste or improvement suggestions. The minimum format: what I observed, the process involved, a practical proposal.
Step 3 — Micro-test the improvement. Before implementing a change at scale, test it on a small sample. The lightweight PDCA (Plan-Do-Check-Act) cycle: define the change → apply it for 2 weeks to a subset of the process → measure the effect → decide whether to adopt or discard it.
Step 4 — Standardization and documentation. If the test is positive, the improvement becomes the new standard: it is written into the process SOP and communicated to everyone who performs it. Whoever proposed the improvement sees it adopted and credited as their contribution: this closes the loop and encourages new reports.
For managing team member involvement, the reference is the cluster on effective delegation to the team; for the operational meetings where contributions are collected systematically, the cluster on effective business meetings.
Common mistakes in operational efficiency projects
Knowing the most frequent mistakes lets you avoid at least some of them. This section gathers the recurring traps: confusing efficiency with cuts, starting with too many indicators, copying tools designed for large industry, excluding the people who work in the process, and dropping monitoring after the first results. For each mistake, it gives the warning sign and the practical countermove.
What is the most common way to turn an operational efficiency project into a failure? Starting with cost cutting instead of mapping value: reversing the priorities makes internal resistance inevitable.
Mistake 1 — Confusing efficiency with cost cutting. Warning sign: the project is presented internally as "we need to reduce costs" or "let's cut the inefficiencies." Team members perceive it as a threat to their roles. Countermove: position the project as "we want to eliminate what makes work harder and less satisfying." Cost reduction is a consequence, not the stated goal.
Mistake 2 — Starting with too many indicators. Warning sign: in the first week, you decide to measure ten different parameters, none of which is then monitored consistently. Countermove: start with a single indicator — the lead time of the core process — and add one at a time, only when the previous one is stable and interpretable.
Mistake 3 — Copying tools designed for large industry. Warning sign: you introduce a complex visual management system, multiple control boards, detailed daily reports — structures suited to a factory with 500 people, not to a company with 20. Countermove: adapt every tool to your actual scale. The Lean principle is transferable; the specific form has to be calibrated to the reality of the business.
Mistake 4 — Excluding the people who work in the process. Warning sign: the project is designed from the top (business owner and consultant/manager) and communicated to team members as a change to be implemented. Resistance is immediate. Countermove: involve the people who carry out the process in the diagnostic phase, even before designing solutions. Those who work in the process know where the waste is better than those observing it from outside. For handling resistance to change, the reference is the cluster on organizational change management.
Mistake 5 — Dropping monitoring after the first results. Warning sign: after three months of visible improvements, measurement stops. Within six to twelve months, waste returns to previous levels without anyone noticing. Countermove: build the review of efficiency indicators into the monthly operating routine. Improvements don't stick without continuous monitoring. Liker describes this as the principle of "continuous responsibility": improvement is not a project, it is a practice [3].
For the overall organizational system that operational efficiency fits into, the reference is the pillar on business systemization.
Limits and conditions of applicability
- Lean sources [1][2][3]: Womack-Jones, Ohno and Liker are robust conceptual references, but the original context is manufacturing (the Toyota Production System). Adapting them to services and to smaller companies requires calibration: the principles transfer, the metrics need to be adapted.
- [7] Sony 2018: this is a conceptual work — a literature review and research propositions — not a study with data collected in the field. The context is manufacturing with an Industry 4.0 orientation: it supports the measurement-reduction mechanism as a reasoned hypothesis, not as a measured result.
- [4][6][8] productivity data: ISTAT, Eurostat and the OECD provide the macro frame of Italy's productivity gap. That gap cannot be attributed directly to hidden process waste: the correlation is plausible and documented in the literature, but it is not direct causation.
- [5] Bank of Italy, QEF no. 678/2022: the survey is based on the 2019 wave of the Invind survey, which covers Italian manufacturing and service companies with at least twenty employees. Micro-enterprises are excluded by design, and the authors state that the analysis is purely descriptive: the association between structured management practices and productivity is not a causal link.
- Very small businesses (1-5 people): value stream mapping and a structured PDCA cycle may be oversized. In these settings, it is better to start from direct observation of the core process and a single time indicator.
FAQ
Where should an operational efficiency project start? With the process that has the highest frequency and the highest cost of error — usually the company's core process (delivery of the main service, order management, production). A simple map of the flow and a lead time measurement are the starting point.
Do the 7+1 muda also apply to services? Yes, with adaptations. Waiting, rework, transportation (of information), unnecessary processing and unused talent apply directly. In services, overproduction takes the form of outputs produced before the customer asks for them (proposals, reports, documents). Inventory translates into files in progress, unprocessed emails, pending tasks.
How long does an operational efficiency project take? A first cycle of diagnosis and intervention on a single process takes 4-8 weeks. Measurable benefits appear within 2-3 months. Consolidating the improvements requires an ongoing commitment to monitoring.
How do you involve team members without creating resistance? By positioning the project as an improvement in working conditions, not as an audit or a check. Whoever reports a waste must see their report taken into account: this turns resistance into contribution.
Operational summary
Operational efficiency comes from systematically removing the hidden waste in processes — the 7+1 muda identified by the Lean tradition. The improvement process unfolds in three phases: diagnosis (mapping the flow, separating active and passive time, identifying waste by category), measurement (lead time, rework rate, simplified OEE, inventory turnover), reduction (5S, standard work, structured involvement of people). The most frequent mistakes — confusing efficiency with cost cutting, starting with too many indicators, excluding the people who work in the process — are predictable and can be corrected before the project starts.
Conclusion
Operational efficiency, understood as the systematic clean-up of hidden waste, is the most underrated growth lever for managers and business owners. It doesn't ask you to work more or to cut resources: it asks you to look at your processes with fresh eyes, to measure the little that really matters, and to involve the people who work inside the flow every day. The 7+1 muda provide a robust map — developed over more than seventy years of industrial practice and adaptable to a business of any size.
Operational efficiency is the snapshot of the problem. The flow that sustains it over time is continuous improvement, which turns waste clean-up from a project into an organizational habit. To see how this logic fits into the broader picture of management, it may also help to read the guide to business management. For the next practical step — understanding where waste really hides — the reference is process mapping.
A company that systematically recognizes and reduces its hidden waste doesn't just become more productive: it becomes more manageable. Deadlines are met with fewer emergencies, team members propose solutions instead of putting up with problems, and margins become easier to read. If Italian companies recovered even part of the productivity growth gap they have accumulated against the EU-27 average since 1995 [4][6], the aggregate gain for the country would be significant: productivity is not just a company metric, it is the condition that allows incomes to grow.
Sources and references
[1] Womack, J. P., Jones, D. T., "Lean Thinking: Banish Waste and Create Wealth in Your Corporation", revised edition, Free Press / Simon & Schuster, 2003.
[2] Ohno, T., "Toyota Production System: Beyond Large-Scale Production", Productivity Press, 1988.
[3] Liker, J. K., "The Toyota Way: 14 Management Principles from the World's Greatest Manufacturer", McGraw-Hill, 2004.
[4] ISTAT, "Misure di produttività — Anni 1995-2024", Statistiche report, December 12, 2025. Available at: https://www.istat.it/wp-content/uploads/2025/12/REPORT_PRODUTTIVITA_2024.pdf
[5] Baltrunaite, A., Formai, S., Linarello, A., Mocetti, S., "Ownership, governance, management and firm performance: evidence from Italian firms", Banca d'Italia, Questioni di Economia e Finanza no. 678, March 2022. Available at: https://www.bancaditalia.it/pubblicazioni/qef/2022-0678/QEF_678_22.pdf
[6] Eurostat, "Labour productivity and unit labour costs", Eurostat database, indicator [nama_10_lp_ulc], 2024 — https://ec.europa.eu/eurostat/databrowser/view/nama_10_lp_ulc/default/table
[7] Sony, M., "Industry 4.0 and lean management: a proposed integration model and research propositions", Production & Manufacturing Research, vol. 6, no. 1, pp. 416-432, 2018. Available at: https://doi.org/10.1080/21693277.2018.1540949
[8] OECD, "SME and Entrepreneurship Outlook 2023", OECD Publishing, Paris, 2023. Available at: https://www.oecd.org/content/dam/oecd/en/publications/reports/2023/06/oecd-sme-and-entrepreneurship-outlook-2023_c5ac21d0/342b8564-en.pdf