01 / SERVICE

Where do operations get stuck?

The same data is entered in several places, reports need manual reconciliation and the effects of a change are hard to predict. I identify the causes and recommend where to make changes first.

Let's discuss your situation What will you receive?

01 / SITUATION AND SOLUTION

When daily work relies on workarounds.

Familiar workarounds can hide wasted time, sources of error or dependence on individual people.

Is the same data entered manually in several systems?I trace data through ERP, custom applications and spreadsheets. I identify where a data transfer or process step should change.

Does an important process depend on the knowledge of a few colleagues?With colleagues, I review responsibilities, manual steps and documentation gaps to identify dependence on individuals.

Is it difficult to decide which improvement would make a real difference?I prioritize interventions based on operational impact, system connections and technology constraints.

02 / WORKING TOGETHER

How the work proceeds

Two professionals examining connections on a system diagram.

Defining the task

I clarify the business question through structured interviews. Using SIPOC, I summarize the process inputs, outputs, participants and boundaries.

Understanding operations

I use BPMN process diagrams to make steps and responsibilities clear. A data flow diagram (DFD) shows where data comes from, where it changes and where it goes.

Evaluating risks

I use root cause analysis (RCA) to investigate recurring errors and bottlenecks. I validate the findings against concrete cases and available data.

Prioritizing changes

Dependency analysis reveals which systems or processes a change affects. I recommend priorities based on operational impact, risk and effort.

I tailor the methods and level of detail to the task. Colleagues who use and operate the processes contribute concrete examples, and I validate the resulting system view with them.

03 / DELIVERABLES

What do you receive, and how can you use it?

Executive summary: what causes the bottleneck and which intervention is justified.
System, process and data flow diagrams: making dependencies and participants visible.
Risks and documentation gaps: what still needs to be clarified before making changes.
Prioritized recommendations: a basis for defining the first development task.

You can continue with your own team or supplier using the deliverables. By separate agreement, I can also help with planning and technical decisions during implementation.

04 / GETTING STARTED

What is needed to get started?

A contact person who understands the business objective of the assessment
Participation of colleagues familiar with the processes and applications
Existing documentation and read-only access where needed
A few interviews and joint discussions arranged in advance

05 / FREQUENTLY ASKED QUESTIONS

Frequently asked questions

How long does an assessment take?

Typically 2–6 weeks. The exact duration depends on the systems being assessed.

Is access to the production system required?

That depends on the purpose of the assessment. Many questions can be answered through interviews and documents. If system access is needed, we agree the required permissions and duration in advance.

Can the assessment be done remotely?

Yes. Interviews and joint document reviews can take place online. I recommend an on-site assessment when understanding the process requires direct observation.

What happens after the assessment?

The assessment is a standalone engagement. You can continue with your own team or supplier using the deliverables. You decide which improvements to implement and who will deliver them. If needed, I can help with planning and subsequent technical decisions.

Where does work get stuck in your company?

Share a concrete example: a report reconciled manually, recurring data corrections or a process that is hard to change. We can use it to discuss what is worth investigating.

Let's talk