Answer.

Business process analysis consists of several key stages, each serving its purpose and requiring different approaches and tools. The correct sequence helps to identify inefficiencies, determine growth points, and implement changes smoothly.

Identification and mapping of processes — the boundaries of the process are defined, the main steps, their interconnections, and participants are collected. This is done through interviews, workshops, or document analysis.
Process analysis — bottlenecks, duplicate actions, and losses of time and resources are identified. Modeling techniques (e.g., BPMN or SIPOC) are applied.
Redesign and optimization — recommendations for improvement are developed, and optimal versions of processes are formed taking into account existing constraints and business goals.
Implementation of changes — a pilot is launched, impact is assessed, adjustments are made, and then it is scaled across the company.

Key features:

Each stage requires a specific set of communications and documentation.
The analyst must be able to formalize processes and visualize them correctly.
It is important to combine a lean approach with a deep understanding of business logic.

Tricky Questions.

Which stage of business process analysis is considered the most difficult?

It is commonly mistakenly believed that process mapping is the hardest. In practice, the stage of implementing changes causes more difficulties because it requires taking into account employee resistance, unexpected technical issues, and the need for quick responses to feedback.

Is it possible to use one notation (e.g., BPMN) for all stages of business analysis?

It is incorrect to assume that BPMN covers all needs. For identification and information gathering at the start, simpler tools (e.g., flowcharts or SIPOC) are often used, and then it moves to BPMN for detailing.

Do changes to business processes need to be agreed upon with all process participants from the outset?

Not always. This is a common mistake. It is important to first ensure that changes are supported by key major stakeholders; the involvement of all employees is required at pilot stages and mass implementation, but not at the start.

Typical Mistakes and Anti-Patterns

Too detailed development at early stages instead of iterative refinement.
Ignoring the real opinions of process executors.
Insufficient involvement of management in agreeing on changes.

Real-life Example

Negative case: When designing the contract approval process at a factory without involving the executors, a complex automated route based on BPMN was launched.

Pros:

Fast implementation.
High formalization.

Cons:

Executors did not understand the nuances of the new process.
Workarounds appeared, the system encountered resistance, and tasks started to be delayed.

Positive case: The team of business analysts implemented the restructuring of the customer service process by conducting a series of interviews and workshops with direct participants, four iterations of improvements, and staged implementation.