Skip to main content

Wiseside

A professional analyses and reorganises a business workflow, using diagrams and charts to assess how to digitise a business process.

Digitizing a process means rethinking it from scratch?

Digitizing a process means making its activities, rules, responsibilities, data, and decisions explicit. And that’s exactly how it becomes clear what’s worth keeping, what needs to be simplified, and what needs to be reimagined.

During a project, one of our clients made a very clear request.

Before digitizing the designated processes, they wanted to analyze the very way in which they were managed, with a specific goal: to understand whether it was possible to work more efficiently.

This request led us to a question that applies to many business process digitization projects: if we digitize a process, do we also need to rethink it?

It depends.

A process can be digitized while retaining much of its existing structure, especially when tasks, responsibilities, and rules are already functioning well.

But the moment a process must be translated into data, tasks, rules, roles, and decisions offers something that is often missing in day-to-day operations: the opportunity to examine it closely enough to ask whether we could design it better today.

Digitizing a process means organizing tasks, information, and rules into a workflow that can be tracked and managed using digital tools.

Process review isn’t limited to large-scale digital transformation programs. According to Istat, during the 2022–2024 period, 57.6% of Italian industrial and service companies with at least 10 employees introduced process innovations, compared to 53% in the previous three-year period.

The most common initiatives involved work organization and human resources management, information systems, and production processes and methods. Process digitization therefore simultaneously involves technology, organization, and day-to-day work.

A company may have a well-established process with clear steps, defined responsibilities, and operational procedures that work. In this case, digitization can focus on making it easier to execute, monitor, and document.

Consider, for example, the handling of an internal request.

Today, this might start with an email, continue with the manual entry of some data into a file, require approval, and conclude with an update to the management system. Digitizing this action could mean creating a workflow in which the request is entered automatically just once, routed to the correct manager, accompanied by the necessary information, and tracked through to completion with its status always visible.

The logic of the process can remain essentially the same, while the way information flows, visibility into the status of activities, and coordination among those involved change.

The issue becomes more interesting when, as we try to map out the process, questions begin to emerge.

  • Why are multiple approvals needed?
  • Why is this information first entered into a file and then into the management system?
  • Why, when an exception occurs, do we have to ask a specific person how to proceed?
  • Why does the procedure include a step that is almost always skipped in practice?

At this point, digitization is bringing to light rules, steps, and exceptions that routine had gradually rendered invisible.

Many business processes operate through a combination of formal procedures and workarounds developed over time. Individually, each solution may have a specific rationale. Over time, however, these workarounds can accumulate, and part of the process’s operation ends up depending on the experience of those who have learned to manage them.

When the process is digitized, these implicit rules must become explicit.

  • The system must know who performs a given task.
  • It must be clear what information is needed to initiate it.
  • It must be established what happens when a condition is met and when it is not.
  • It is necessary to define when a task can be considered complete, who can approve it, and how to handle any exceptions.

Process mapping therefore creates an opportunity to bring to light questions that day-to-day operations tend to bury.

One option is to copy and paste the current process into the software: this can be the right choice, but it must be made with full awareness.

In 2024, a study published in Data & Knowledge Engineering analyzed 40 cases in which digital technologies were used to redesign business processes. The authors observed that simply replacing one technology with a newer one offered limited value compared to using digital capabilities to rethink how processes operate.

This does not mean we must turn every digitization project into a major reengineering program. It does, however, mean considering possibilities that the previous process may not have offered, for example:

  • More tasks could proceed in parallel.
  • A condition could trigger an action without waiting for manual input.
  • A person could receive only the exceptions that truly require their judgment.
  • Data collected during one activity could be used directly by the next one.

Transferring the process to the new environment without evaluating these possibilities may mean leaving part of the value of digitization untapped.

An interesting example comes from a big Fashion Group: in analyzing its Order-to-Cash processes, the company used process mining tools to identify which repetitive parts of the workflow were best suited for automation and to simulate the effects of the changes before implementing them.

In one of the processes analyzed, the simulated changes showed a potential reduction of up to 90% in customer service resolution times and a 46% reduction in the average cost per resolution.

The methodological approach is particularly interesting: automation was evaluated after observing the process, pinpointing bottlenecks, and identifying where intervention could generate the most value.

To decide what to keep and what to change, you first need a shared representation of the process.

Modeling tools using BPMN (Business Process Model and Notation) can be useful for precisely this purpose. BPMN is a language that allows you to graphically represent a process by describing activities, sequences, decisions, events, and the actors involved.

It’s an approach we also use in Wiseside projects: BPMN logic helps us model processes and clarify steps, responsibilities, decisions, and exceptions before translating them into digital workflows.

The value of a shared representation lies in the ability to bring together those who execute the process, those who govern it, and those who will digitize it, all viewing the same workflow.

It is often at this stage that the most useful questions arise:

  • Is this step still necessary?
  • Is this information already available?
  • What happens when the process deviates from the expected path?
  • Who should intervene?

The diagram alone does not improve the process. However, it can highlight steps, dependencies, responsibilities, and exceptions, and provide a common ground on which to analyze them before translating them into a digital workflow.

A project can proceed gradually.

You can start with a limited process. Keep activities and systems that already work well. Digitize only certain steps. Focus first on the areas that cause the most delays, duplication, errors, or manual work.

To determine the extent of the changes, three scenarios can be distinguished.

  • If activities, responsibilities, and controls are clear and adequate, you can maintain the logic of the process and focus on improving the flow of information.
  • If duplications or approvals without a clear purpose emerge, you can correct those steps while verifying which controls need to remain.
  • If frequent exceptions require bypassing the procedure, the workflow needs to be reviewed with those who execute it and those responsible for it.

The goal should not be to change as many things as possible. It should be to understand which elements of the process create value and which create friction.

For this reason, before transforming a procedure into a digital workflow, it can be helpful to ask a very simple question: if we were to design this process today, would we still build it the same way?

Sometimes the answer will be yes. And that’s important information.

Other times, a step will emerge that can be eliminated, information that can be conveyed differently, a responsibility that needs to be clarified, or a decision that can be handled more effectively.

In that case, the digital project will have already produced its first result: it will have made the way the organization works more transparent.


Sources

  • Fredrik Milani, Kateryna Kubrak, Juuli Nava, “Strategic Redesign of Business Processes in the Digital Age: A Framework,” Data & Knowledge Engineering, vol. 154, 2024, 102367.
  • IBM, How to Improve Order-to-Cash Through Process Mining.
  • Istat, Innovation in Businesses – Years 2022–2024, published on September 24, 2026.

Condividi: