How does a business process review work, step by step?

What does the four-step version include?

Lanrex describes a review in four parts, briefly paraphrased here:

• Record current processes, including roles, actions, handoffs and exceptions.
• Analyse them with participants and stakeholders, including customers where appropriate.
• Prepare a desired future state with realistic, measurable objectives.
• Determine how technology could support the plan.

This approach places the business need before tool selection. It includes future-state planning, not just drawing the present flow. It is a particular provider’s description, not the only standard for every business or a guarantee of successful implementation.

What does the ten-step version add?

ISM presents a more detailed sequence for reviewing and improving processes in a customer-strategy context:

• Meet participants to establish direction and a tentative schedule.
• Research relevant industry practices.
• Interview people who know the process about its current state.
• Document current flows and compare with suitable available benchmarks.
• Gather feedback on the description.
• Hold a workshop to clarify that feedback.
• Hold a workshop for improvement proposals.
• Prepare future flows at overview and detailed levels.
• Review and refine the proposed future flows.
• Give final approval, prioritise recommendations and prepare an action plan.

This divides discussion and checking into more activities. It does not establish that every small business needs the same number of meetings. A “best practice” comparison also requires suitable data and context; the label alone does not establish a sound benchmark.

Which version emphasises written instructions?

Visual South presents five parts in guidance linked to ERP use:

• An overview of flow between departments.
• Process detail within each department.
• A written procedure explaining actions and decisions.
• Work instructions for particular execution.
• A continuous-improvement plan.

The author emphasises instructions as protection against knowledge loss when people change. This is a useful emphasis, not evidence that a document replaces training or human judgement. Instructions need an owner, current examples and a change process to remain useful.

How does the Expert Review run?

The Expert Review has its own agreed scope. It usually examines three to six linked processes with read-only access. In the first week, processes, people and tools are defined and both sides sign the scope. The report timeframe is three to four weeks from the signed scope.

The second and third weeks cover mapping with those doing the work. Each finding links to a checkable row: process, step, hours a week and source. Under the described schedule, the fourth week delivers the map and report, discussed on a joint call.

This does not automatically include every activity in the three outside methods. Building, implementing a new process, detailed new work instructions and ongoing support are not promised by that list. A subsequent change is a separate decision; the report provides findings and possible actions within the agreed scope.

Questions

Sources

• Lanrex — a four-step approach.
• ISM — a ten-step process-review approach.
• Visual South — five parts of review and documentation.

Related reading

• What is value stream mapping?
• What is process mapping, and why does your business need it?
• When do you need a process consultant rather than your own map?