Process analysis for SMEs: how to do it

Process analysis in an SME: what it is for

Process analysis means recording and measuring a recurring workflow so you can see where time, errors and waiting time appear.

In an SME, one workflow, one week and one table are enough. No BPM suite, no modelling programme. You already picked the candidate if you worked through which process to automate first with the four questions. Analysis shows where the workflow loses time and where the rule-based part starts. After that come documentation and a decision. In this cluster the order is: choose, analyse, document, Process Check.

Photo: 2H Media on Unsplash.

This article is for leadership, office and finance leads in Swiss SMEs where the same manual job hurts every week. It does not repeat the difference between digitalisation, automation and AI or what an AI agent is. It shows how to measure the workflow you picked before you spend on tools or delivery.

Five steps through one workflow

The five steps fit on one sheet. You need the person who does the job today and someone who asks follow-up questions.

1. Draw the boundary

   Trigger and outcome in one sentence each. «Email with PDF arrives» until «amount is in the accounting system» is a workflow. «Somehow pull numbers for the board» is not.

2. Capture as-is

   Watch one real run at the screen or record it briefly. Last week’s version, not the ideal from memory.

3. Measure

   For one week: how often it happens, minutes per run, errors or queries, waiting on someone else or on a system.

4. Mark media breaks

   Email, spreadsheet, PDF, portal, accounting: where someone copies, prints or waits. Double entry sits next to the step where it happens.

5. Decide

   Split rule-based work (same fields, same order) from judgement (exception, approval, conversation). Only the rule-based part is a automation candidate.

Photo: Zulfugar Karimov on Unsplash.

If you are unsure the workflow is a candidate at all, go back to the four questions in the pillar article. Process analysis assumes frequency, pain, a clear end and existing data already scored «yes».

Log the same four columns on every run as in the example table below: step, minutes, media break, rule-based yes or no. That keeps the week comparable when someone else reads it. On Friday add the minutes and count errors. That is enough for a decision without a project charter.

Example: receipts and a monthly report

A fictional 18-person office, no company name. The office lead does two recurring jobs: supplier invoices from the inbox and a monthly report for leadership.

Receipts: About 40 invoices per month arrive by email with a PDF. For each one she types amount, supplier and cost centre into accounting, often four minutes. Twice a month a field is missing, then email to the buyer and one to two days of waiting.

Monthly report: Every first Monday she exports five lists from CRM, accounting and two spreadsheets, copies rows into a master Excel file, checks totals and sends the file to leadership. The block takes 75 to 90 minutes.

Two things become visible. Receipts are mostly rule-based work with a clear judgement slice when data is missing. The report is rule-based with high minutes and many media breaks. Which workflow you tackle first depends on what hurts most at your place, not on the method.

Process analysis methods: what an SME actually needs

Searches for process analysis methods often mean large programmes. An SME needs fewer tools than jargon.

You do not have to «implement» a method. Use SIPOC on one page if boundaries are missing. Otherwise start at step 2: one walk-through, one tick sheet, mark media breaks.

Where analysis fails in the office

Four patterns show up before anyone measures.

Too many workflows at once. Three tabs for three processes, and after a week nothing moves. One workflow, one week, one table.

Interviews only. The person who does the job skips steps that feel obvious. A screen walk-through shows clicks that never appear in conversation.

Exceptions waved away. «It is always different» often hides five recurring exceptions with their own rules. Write them down. They tell you whether automation should stop or ask.

Tool first. A demo is not a measurement. If minutes and media breaks are unclear, you buy software on fog.

If error rates are high because Excel column names change every week, that is not a failed analysis. It is the finding: fix the source and columns, then measure.

From results to a decision

After one week you want on the table: minutes per month (frequency times run time), a rough error or query rate, and the share of steps that follow the same rule.

A rule of thumb without a promise: if the same workflow binds more than an hour every week and at least two media breaks are pure copy-paste, automation is worth a look. If it happens twice a quarter and every round differs, wait.

The measurement does not replace a management decision. It gives numbers and rules so nobody confuses felt load with a tool. Serious process automation in an SME starts with a table like this, not with a licence.

The next cluster step is writing the workflow on one page. For the decision, analysis plus one appointment is often enough.

Look at this workflow with us

Bring the workflow you analysed. In the Process Check we review it for 60 minutes on Teams. Afterwards you know what can be automated and what it costs. CHF 99.

What happens in the hour and what lands on paper afterwards is in what the Process Check is.

Frequently asked questions