The Continuous Improvement Fallacy: why you need to Standardise (SDCA) before you Optimise (PDCA)

October 14, 2026 by
The Continuous Improvement Fallacy: why you need to Standardise (SDCA) before you Optimise (PDCA)
Sergio Solares Fernández

In the blind race to scale a company, there is an almost irresistible temptation for any management team: trying to solve operational problems by buying software or demanding "more productivity" from staff.

When invoices contain errors, orders are delayed in the warehouse or the customer complains, the usual reaction is to apply emergency patches or launch "Continuous Improvement" programmes. However, the golden rule of process engineering is non-negotiable: automating or optimising chaos only creates faster chaos. Before digitalising or improving, you must standardise.

1. The Variability Virus and Operational Debt

As a business grows, it accumulates what our firm calls Operational Debt: informal routines, improvised patches and hidden bad habits that made sense when the company was small and run by shouting from one desk to another, but that become a heavy anchor when the structure scales.

The most destructive methodological error in mid-sized companies is trying to apply Continuous Improvement through the classic Deming or PDCA Cycle (Plan, Do, Check, Act) on a system that hasn't been standardised.

📌 The Law of Operational Variability

  • Non-standardised process: each employee does the task their own way. Variations in delivery time and result quality are due to chaotic design, not worker performance. Trying to "improve" (PDCA) an unstable process is statistically useless.
  • Standardised process: a mathematical baseline is set. The process produces exactly the same result regardless of who carries it out. Arbitrariness is eliminated and predictability achieved.

2. The SDCA vs. PDCA Cycle: the Wedge of Corporate Growth

To build solid foundations, Business Architecture requires temporarily postponing the PDCA cycle and first securing operational stability through the SDCA Cycle (Standardise, Do, Check, Act).

The goal of SDCA is not speed but absolute predictability. Visually, the standard acts as a chock: if you try to push the Continuous Improvement (PDCA) ball uphill without placing the Standard (SDCA) chock underneath, the gravity of operational bad habits and day-to-day inertia will roll the organisation back down.

🔄 The 4 Non-Negotiable Steps of the SDCA Cycle

  1. Standardise: set the baseline. Scientifically document the inputs, tasks, tools and outputs needed for the process to be repeatable.
  2. Do: train staff in the strict discipline of the standard, eliminating unauthorised "individual creativity" that causes errors.
  3. Check: measure variance and process capability indicators to certify that the standard is being met.
  4. Act: consolidate the standard. If the process deviates, apply root-cause corrective measures to bring it back into balance.

Only when the process is stable, repeatable and predictable (SDCA) does Senior Management earn the right to start the PDCA cycle to plan an improvement, increase speed or widen a bottleneck.

3. The Theory of Constraints (TOC) and the 7 Hidden Wastes

Once the system is stabilised through the SDCA cycle, the next step in process engineering is to identify where cash is being burned. To do so, we apply Eliyahu Goldratt's Theory of Constraints (TOC) and identify the 7 Hidden Wastes (Muda) of the Lean Management philosophy.

The Theory of Constraints is relentless: your company's maximum capacity is exactly equal to the capacity of your slowest process (your bottleneck). Adding more workload or hiring more salespeople without first widening the bottleneck only collapses operations and sends costs soaring.

⚠️ The 7 Operational Wastes that Devour Margin (Muda)

  1. Overproduction: making or processing more than the customer or the next department needs.
  2. Waiting: idle time of employees or machines waiting for approvals, signatures or materials.
  3. Unnecessary transport: pointless movement of documents, data or materials from one place to another.
  4. Overprocessing: doing more work or adding more complexity than the customer really values.
  5. Excess inventory: cash frozen in the form of stock or half-finished projects.
  6. Unnecessary motion: needless physical or digital movement by staff to carry out a task.
  7. Rework and defects: errors in invoices, incorrectly taken orders or defective services that require the work to be redone.

4. From Inefficiency to Solid Institution

Mapping inefficiency and standardising under the SDCA cycle is a demanding exercise because it brings the organisation's hidden bad habits to light. However, it is the only legitimate way to build auditable foundations, protect operating margin and prepare the company for truly scalable growth.

At Pausa Fiscal we design the group's corporate architecture, tax planning and asset protection. However, experience shows us that a perfect tax or corporate chassis collapses if daily operations are dominated by improvisation and staff's hidden bad habits. 

For a tax or corporate shield to be sustainable over time, the operational trenches must be stable, predictable and efficient. That is why we integrate into our methodology the engineering of CōAb Soluciones Empresariales, our firm specialised in Process Orchestration and Hyperautomation, to get down to the factory floor, eliminate Operational Debt, design SDCA standards and remove the waste that devours margin.