Das Bild zeigt einen weitläufigen Industriekomplex aus der Vogelperspektive, der moderne Infrastruktur und Produktionsanlagen zeigt.

BLOG

Workflow Automation in Manufacturing SMEs

Workflow Automation: Which Processes Are Best Suited?

ERP, ticketing systems, various tools—and yet key processes at the interfaces are still handled manually. Approvals via email, master data maintained in multiple places, issues reported verbally. It’s understandable that the desire for workflow automation is growing. The real challenge begins before implementation: Which processes should come first? Many initiatives fail because processes that are too complex or organizationally immature are chosen. After all, digitizing unstable processes accelerates one thing above all else: existing inefficiencies.

In this article, we present a two-step framework that manufacturing companies can use to systematically prioritize suitable processes, and we highlight four clear “winners” for improving efficiency in medium-sized industrial companies.

Successful workflow automation rarely fails because of the technology. It fails because companies tackle the wrong processes first.

Dominik Fackler, Manager

Why Choosing the Right Process Is Key to ROI

Workflow automation is not an end in itself. In an operational setting, it must accomplish three things: reduce effort, shorten turnaround times, and increase process reliability. For this to succeed, a thorough pre-selection process is needed—one that pays off in multiple ways:

  • Faster Results: Processes with a high degree of repetition and clear rules deliver visible benefits early on.
  • Lower risk: Complex automation projects for special cases with little leverage can be specifically avoided.
  • Clearer implementation logic: It becomes apparent early on whether a process is suitable for full automation, assisted automation, or—initially—only for standardization.

This is especially crucial for small and medium-sized businesses. Resources in IT and line organizations are limited; therefore, it shouldn’t be the loudest process that wins, but the one with the best balance of feasibility and impact.

The first automation initiative rarely determines the ROI of a single process, but it almost always determines whether the initiative gains momentum within the company or fizzles out.

Niklas Blöcker, Consultant

Step 1: Quick preselection using a 2×2 matrix

The first stage serves as a preliminary filter. Each process is classified along two dimensions:

  • Frequency: How often does the process occur?
  • Process Complexity: How many exceptions, decisions, and variations does the process involve?

This leads to four possible areas and recommendations for action:

The figure shows how the processes are categorized along two dimensions.
Figure 1: Classification of processes along two dimensions
  1. High Frequency, Low Complexity: Full Automation
    This is where the classic candidates for automation are found. The process occurs frequently, follows consistent rules, and has few exceptions—an ideal combination for direct automation. Typical examples include workflows in which data is fully available, approval rules are clearly defined, and no in-depth case-by-case evaluation is necessary.
  2. High Frequency, High Complexity: Assisted Automation
    These processes occur frequently but cannot be fully captured in rules. The system can collect data, assign tasks, monitor deadlines, and make suggestions; however, the final decision remains with the human user. The goal is not fully automated “black-box” processing, but rather to provide a noticeable reduction in the workload for the business units.
  3. Low Frequency, Low Complexity: Quick Wins
    Not every simple process needs to be automated. If a process occurs infrequently, clear standardization is often sufficient: templates, forms, checklists, or clearly defined responsibilities. The benefit here lies more in consistency than in the depth of automation.
  4. Low frequency, high complexity: Decomposition. Taken as a whole, these processes are usually poor candidates for automation. The better approach: break the workflow down into subprocesses and specifically automate the rule-based steps. The insights gained from this approach are often more valuable than direct implementation, because while not every process is immediately suitable for automation, almost every process contains subcomponents that can be automated.

The detailed evaluation based on six criteria

Processes that appear promising in Stage 1 are evaluated in greater detail in Stage 2. To do this, each process is rated on a scale of 1 to 10 across six dimensions; the scores are then weighted individually and aggregated into a total score. The higher the score, the better suited the process is for workflow automation.

The image shows the detailed evaluation based on six criteria.
Figure 2: Detailed evaluation based on six criteria

An overview of the six dimensions:

  1. Frequency
    How often does the process run in daily, weekly, or monthly operations? The higher the frequency, the greater the impact of automation.
  2. Rule Definition
    How clearly can the process be described? Are there clear “if-then” logic patterns, or do exceptions and informal decision-making processes dominate?
  3. Technical Feasibility
    Is the relevant data available in digital form? Can the systems involved be integrated? Where are the data discontinuities?
  4. Process Stability
    Is the process well-established, or is it currently undergoing a restructuring? Automating unstable processes ties up resources without delivering reliable results.
  5. Organizational Maturity Level
    Are roles, responsibilities, and handoffs clearly defined? If it’s already unclear in the current state who makes which decisions, even a workflow won’t solve the problem.
  6. Business Impact
    What specific benefits does automation offer? For example, in the form of time savings, error prevention, shorter turnaround times, or avoided downtime.

Sample weighting as a starting point:

Dimension

Frequency
Policy Definition
Technical Feasibility
Process Stability
Organizational Maturity
Business Impact

Weighting

0.15
0.20
0.10
0.15
0.20
0.20

These weightings are intentionally not a rigid model. A company facing a severe shortage of skilled workers may place greater weight on business impact, while one with a heterogeneous IT landscape may place greater weight on technical feasibility. What matters most is that the weighting is determined deliberately and discussed as a team.

The detailed evaluation does not provide a truth accurate to two decimal places, but it does force us to have the right discussion.

Dr. Clemens Wolf, Head of Digital Operations

Four Strong Case Studies for Small and Medium-Sized Manufacturing Companies

To make the framework more tangible, we’ll classify four typical processes that are common in manufacturing SMEs and that perform particularly well in terms of quality.

Processing of Incoming Invoices, Including the Approval Workflow, in Financial Accounting

In medium-sized industrial companies, incoming invoices are still frequently processed manually: Invoices arrive by mail or email, are printed out, manually posted to accounts, forwarded via internal mail, and eventually entered into the ERP system. This process, which involves a change in media, ties up resources in the accounting department and is prone to errors; at the same time, it is highly amenable to standardization.

What makes him so strong?

  • High volumes and regularity: Incoming invoices arrive continuously, often numbering in the hundreds or thousands per month. Even small efficiency gains per invoice add up to a noticeable reduction in workload.
  • Clear, verifiable rules: Verification steps such as “Is the supplier known?” and “Is the invoice amount within the budget limit?” can usually be clearly defined as rules. Value thresholds, cost centers, supplier status, or deviation tolerances (e.g., ±5%) are ideal criteria for automated decisions.
  • Direct Impact on Transparency and Liquidity: An automated workflow reduces processing times, prevents lost invoices, and improves visibility into outstanding liabilities. Discount periods can be taken advantage of more consistently, and late fees can be avoided.
  • Strong technical foundation: Many data points are already available: supplier master data, purchase orders, goods receipts, cost center structures, and authorization schemes are all stored in the ERP system. Modern OCR and capture solutions can extract invoice data in a structured format from PDFs and scans and transfer it to the workflow.

Depending on the complexity of the supplier base and the exception logic, the spectrum ranges from largely fully automated (“no-touch invoice”) to highly assisted automation, in which the system automatically processes standard cases while the accounting department focuses on exceptions. In both scenarios, the potential for boosting productivity and process reliability is particularly high for medium-sized industrial companies.

Handling Complaints and Nonconformities in Quality Management

Complaints and quality deviations typically follow a formalized process: recording, evaluation, assignment, tracking of corrective actions, feedback, and documentation. While the technical root cause analysis remains the responsibility of the relevant department, everything else involved is a classic workflow use case.

What makes him so strong?

  • Robust workflow logic: Many companies already use defined quality processes (8D, CAPA, etc.) in this area.
  • Clear deadlines and the need for escalation: That’s exactly what a workflow is designed for.
  • High level of transparency: Status, responsible parties, and pending tasks are visible at a glance.
  • Tangible benefits: Response times are reduced, tracking becomes more reliable, and compliance improves.

Since not every technical evaluation can be automated, this process is particularly well-suited for assisted automation. The system controls the workflow, and a human makes the substantive decision.

Creating and Modifying Material Master Data

Material master data is an often-underestimated bottleneck in everyday industrial operations. New materials or changes must pass through design, purchasing, work planning, scheduling, and controlling. However, without a well-defined workflow, this leads to follow-up questions, data gaps, and delays that directly impact planning, procurement, and production.

What makes him so strong?

  • Clearly defined handoffs: The steps follow a logical sequence with clearly defined responsibilities.
  • Significant organizational impact: The workflow fosters accountability across departmental boundaries.
  • Significant Business Impact: Incorrect or incomplete master data has a direct impact on downstream processes.
  • Good process stability: Especially in the master data environment, well-defined standards retain their value particularly well.

This process isn’t a spectacular digital topic, but it’s extremely effective from an operational standpoint. That’s exactly what makes it so attractive to small and medium-sized businesses.

Inaccurate master data not only causes systems to crash, but also disrupts actual processes in planning and production. That is precisely why a well-organized workflow is especially important here.

Dominik Fackler, Manager

Reporting and Assignment of Machine Malfunctions

When a machine is down, every minute counts. Yet in many plants, reporting, prioritization, and assignment still rely on verbal calls, phone calls, or personal habits. In fact, the process from the initial fault report to the assignment of the right maintenance technician could be automated exceptionally well.

What makes him so strong?

  • Significant Business Impact: Unplanned downtime costs real money; every minute saved counts.
  • Clear routing logic: Assignments can often be clearly mapped based on line, machine, warehouse area, priority, or shift model.
  • High Frequency: Malfunctions and maintenance alerts are part of day-to-day operations.
  • Good scalability: Escalations, notifications, and status updates can be added incrementally.

Of course, the actual repair is still the responsibility of the maintenance technician. But logging, assignment, and escalation are prime candidates for full automation.

How to Create Your Own Automation Roadmap

A simple but effective approach can be derived from the framework:

Identify potential processes
. Ask specific questions in Purchasing, Quality, Work Planning, Maintenance, and Supply Chain about processes that involve a high degree of manual work, frequent follow-up inquiries, or long lead times.

Categorize Processes at a High Level
Use the frequency-complexity matrix to identify initial candidates and weed out obviously unsuitable processes early on.

Evaluate Processes in Detail
Evaluate your shortlist across the six dimensions and define your weightings deliberately, not haphazardly.

Starting with a clear winner
Don’t choose the most prestigious process, choose the most sensible one. Early successes build trust and facilitate further scaling.

Summary

Workflow automation delivers its greatest value not where the technology is most advanced, but where processes are clear, frequent, and effective. That is precisely why choosing the right starting point is so important. A robust prioritization model helps keep discussions objective and ensures resources are allocated strategically, so you can tackle the right process first. For manufacturing SMEs, this means less knee-jerk action and more effectiveness.

Please contact us!

Would you like to find out which processes in your company offer the greatest potential for workflow automation? We’re here to help!

    Das Bild zeigt Niklas Blöcker, Berater im Bereich Digital Operations.

    Niklas Blöcker

    Consultant, Hamburg

    Niklas Blöcker ist studierter Wirtschaftsinformatiker und Berater im Hamburger Rothbaum Office. Seine fachlichen Schwerpunkte liegen unter anderem in der Entwicklung digitaler Prozesse, Datenmigration und Sales Planning.

    Portrait of Dominik Fackler, Senior Consultant at Rothbaum

    Dominik Fackler

    Manager, Munich

    Dominik Fackler is a manager at Rothbaum Consulting Engineers in Munich and is responsible for transformation projects in the areas of business and system transformation. His focus is on the end-to-end optimization of business processes, as well as the selection and implementation of appropriate IT solutions.

    You might also be interested in

    Feature image for the Autostore automated storage system. The picture shows an Autostore warehouse.
    22. Jul 2025 | Automated storage systems, Logistics
    Automated storage systems: AutoStore

    AutoStore is one of the leading automated storage systems. Find out how the system increases…

    Learn more

    The picture shows an automatic pallet warehouse in Rothbaum style placed in the center.
    23. Jan 2026 | Automated storage systems, Logistics
    Automated storage systems: Automated pallet warehouse

    Automated pallet warehouses offer efficient, safe and space-saving solutions for modern logistics requirements. Find out…

    Learn more

    Frau schaut sich Daten auf einem Tablet an.
    7. Feb 2020 | Logistics, Production, Supply Chain
    Process indicators: When data becomes meaningful

    You don't know how good or bad you are in a particular area of the…

    Learn more

    Talk to us!

    Do you have a specific project inquiry or questions about our services or Rothbaum? Then send us a message and we will get back to you as soon as possible. We look forward to the exchange.