Most process analyses in small and mid-sized companies don't fail because of the method. They fail because of three thinking errors: treating the symptom instead of the cause - the slow quoting process gets new software, when in fact every quote is simply waiting for an approval. Measuring metrics that explain nothing - number of cases processed instead of idle time per case. And declaring the account of the most experienced employee the official truth, even though it only shows one slice of the picture. The result: a clean flowchart, a list of action items - and three months later, everyone is back to doing exactly what they did before.
This guide shows how to do it better: what process analysis actually is, which methods are worth it for companies with 10 to 500 employees, how to proceed in five steps - and which mistakes you can skip because others have already made them.
What process analysis is - and what it isn't
Process analysis means systematically examining an existing workflow to find weaknesses, risks, and improvement potential. Where does it take too long? Where is work done twice? Where does everything depend on one person? Where does information get lost?
The distinction from process mapping matters. Mapping delivers the raw material: who does what, in what order, with which tools. Analysis delivers the insight: which of it is a problem, and why.
How to capture the as-is state cleanly and without sugarcoating is a topic of its own - our guide Mapping as-is processes covers it in detail. For the analysis, what matters most is the order: map first, evaluate second. Mixing the two spoils your material.
And one more distinction: process analysis is not process optimization. The analysis tells you where things get stuck and why. What you do with that - change the workflow, introduce software, reassign responsibility - is the step that comes after.
Process analysis methods at a glance
There are dozens of methods, from Six Sigma to business process reengineering. For small and mid-sized companies, four are enough in practice - and none of them requires a certification course.
Weak-point analysis
What it's for: The classic. You walk through a process step by step and ask at each one: where does it snag? What takes too long, what goes wrong, what annoys the people involved? A good starting point when you don't yet know where the problem is.
Effort: Low to medium. One to two days per process if the mapping is already done. The skill is in the questions: "What do you do when the customer doesn't return the order confirmation?" yields more than "Is the process working well?"
Typical outcome: A prioritized list of weak points with root causes. Example from a metal fabrication shop: quotes take two weeks - not because the costing is complex, but because every quote waits for sign-off from the owner, who spends three days a week on job sites.
Value stream analysis light
What it's for: From the lean world, here in the stripped-down variant without symbol catalogs and takt-time calculations. You follow one concrete case - an order, a complaint, a purchase - from start to finish and record two times: how long is it actually being worked on, and how long does it just sit around?
Effort: Medium. You need real cases to trace, ideally five to ten, to spot outliers. Plan for two to three days per process.
Typical outcome: The ratio of processing time to idle time - and it is almost always sobering. An order that spends 14 days in-house is often actively worked on for only a few hours. The rest is waiting: for approvals, for clarifications, for the colleague who's back from vacation. The idle times are your leverage points.
Handoff analysis
What it's for: Most problems don't arise within a department but at the handoffs. Sales to production planning, production to shipping, service to accounting. Handoff analysis puts exactly these transfer points under the microscope: what is handed over, in what form, with what information - and what is regularly missing?
Effort: Medium. You have to interview both sides of every handoff, and separately. Because this is exactly where perceptions diverge: sales is certain the order folder is complete. Production planning still calls back on every other order because the delivery dates are missing.
Typical outcome: A handoff matrix: which interface, which information, where it snags. Most common finding: both sides have different ideas of what "done" means.
Media-break analysis
What it's for: A media break is any point where information changes systems and gets transferred by hand. The service technician fills out the timesheet on paper, accounting types it into the billing system. The order comes in by email, someone keys it into the ERP. Every one of these breaks costs time and produces errors.
Effort: Low. Media breaks are easy to find once you ask for them directly: "Where do you retype something that already exists digitally somewhere?" Half a day per process is often enough.
Typical outcome: A list of all system switches with their frequency. That's the best foundation for digitalization decisions - because a media break that occurs five times a day justifies automation; one that occurs once a quarter does not.
Process analysis: a 5-step approach
Step 1: Select and scope the process
Don't analyze the whole company. One process, clearly bounded: "order processing from order intake to invoice" - not "our sales department." Pick the process that grinds most often or ties up the most money.
Step 2: Map the as-is state
Talk to the people who execute the process every day - not the ones who defined it years ago. Ask about the concrete last case, not the typical case: "Take the last order. What exactly did you do?" The typical case is a construction; the last case is the truth.
Step 3: Apply the method
Choose the right one of the four methods - or combine them: weak-point analysis as the base, media-break analysis as a targeted second look. Important: every insight needs evidence. "The handoff to manufacturing is a problem" is a claim. "In 4 of 6 orders we examined, manufacturing had to ask for missing measurements, causing an average delay of 2 days" is a finding.
Step 4: Resolve contradictions
If three people describe the same process differently, that's not a measurement error - that's a result. Maybe three variants of the process really do exist. Maybe one person knows something the others don't. Put the contradictions openly on the table and resolve them with the people involved, not over their heads.
Step 5: Prioritize findings and derive actions
Not everything you find is equally important. Prioritize by frequency and damage: an error that occurs daily and affects customers beats a blemish that stays internal. And for each finding, one action with an owner and a deadline - otherwise the analysis ends up in the binder next to all the other analyses.
Common mistakes in process analysis
Mistake 1: Analyzing the to-be instead of the as-is
The most common mistake. What gets analyzed is the procedure from the QM manual - but that describes how the process was intended, not how it runs. In reality, the workflow changed long ago: the colleague who did the intermediate step is gone; the new system made two steps obsolete and three new ones necessary. Analyzing the to-be means optimizing a phantom.
Mistake 2: Only asking management
The department head knows the process - from a bird's-eye view. What he doesn't know are the tricks, workarounds, and shortcuts: that the clerk maintains her own side spreadsheet because the ERP can't handle tiered pricing. That the warehouse worker doesn't book goods receipts until the afternoon because the trucks arrive in the morning. Exactly these details are where the insights live. Ask only at the top and you get the org chart confirmed and learn nothing.
Mistake 3: Taking one person's account as the truth
The most experienced employee describes the process - and his version becomes the official version. But even the most experienced person sees only his slice. And sometimes he describes how he thinks it should be done, not how everyone actually does it. Interview several people along the process and compare their accounts. Contradictions are not an annoyance to be smoothed over - they are often the most valuable find of the entire analysis.
Mistake 4: Analyzing without consequences
An analysis that leads to nothing is more expensive than no analysis - because it consumed your employees' time and raised the expectation that something would change. If nothing then happens, the next round of interviews will be noticeably more tight-lipped. Plan the implementation from the start, even if it's just two small actions.
How wissa automates process analysis
The most laborious part of the analysis isn't the thinking - it's the collecting and cross-checking: conducting many interviews, comparing accounts, finding contradictions, backing up findings. That's exactly the part wissa.ai takes over.
An AI interviews your employees via chat or voice, 15 to 20 minutes per person, no workshop scheduling. Following the snowball principle, it works its way from knowledge holder to knowledge holder: if someone mentions "that gets sorted out by our colleague in purchasing," that colleague is interviewed next.
The conversations produce insights with evidence - automatically:
- Media breaks: Where information is transferred between systems by hand, including the statement it was derived from.
- Duplicate work: When two people independently describe maintaining the same data.
- Knowledge risks: Process steps that only a single person has mastered - the bus factor, with its source.
- Contradictions: When two employees describe the same workflow differently, it gets flagged and both statements are placed side by side - instead of silently declaring one version the truth.
Every statement is traceable, every finding has a source. The documentation is alive: it updates itself after every interview, with a diff against the previous version. GDPR-compliant, EU hosting, works-council-friendly. In the early beta for €149 per month with 12 interview credits - interviewees free of charge. Join the beta waitlist now.
FAQ
What is the difference between process mapping and process analysis?
Process mapping documents how a workflow actually runs - who does what, in what order, with which tools. Process analysis evaluates that material: it identifies weaknesses, risks, and improvement potential. Without clean mapping, there is no reliable analysis.
Which process analysis method is the right one to start with?
For most companies, weak-point analysis, complemented by media-break analysis. Both can be applied without prior training and quickly produce concrete findings. Value stream and handoff analysis are worthwhile as a second step, when you want to understand idle times or handoff problems in more detail.
How long does a process analysis take?
For a clearly scoped process with five to eight people involved: the mapping takes about one to two weeks (spread out, not in one block), the analysis itself two to three days. With AI-driven interviews, it's mainly the mapping that shrinks significantly, because conversations happen in parallel and without scheduling.
Who should I interview for the process analysis?
Above all, the people who execute the process every day - and several of them along the entire workflow, not just one person per department. Management provides the frame, but the decisive details live in the operational work.
What do I do when employees' accounts contradict each other?
Don't smooth anything over. Contradictions are a result: either several process variants exist side by side, or a shared agreement is missing. Put the contradictory accounts next to each other and resolve them together with the people involved - that's often where the most effective improvements come from.