Skip to content
On this page
Our approachRemove what is unnecessary

Business process optimization: remove the unnecessary first

Process first → Technology second

Many companies repeat the same actions for years: entering the same information in several spreadsheets, passing routine requests through layers of approval, and preparing reports that no one uses. These steps may appear essential simply because the workflow evolved that way.

Core principle

Do not speed up every task. First remove the steps the process can safely do without.

Automating such tasks is technically possible. But if a step serves no business purpose, automation only makes unnecessary work happen faster while preserving its cost and complexity.

That is why BPFlow AI begins with a review of the entire process. We define the required outcome, identify unnecessary handoffs and repeated checks, and distinguish essential controls from historical habits. Only then do we decide which remaining steps are worth automating.

What we remove

Duplicated actions and data

The same customer or order information may be copied between CRM, Excel, and departmental spreadsheets. If a reliable source of truth is already available, repeating data entry and sending parallel copies adds no value. Before building integrations between duplicates, we ask whether those duplicates should exist at all.

Unnecessary approvals and handoffs

Requests often pass through employees who only forward them or repeat the same check. We distinguish genuine decision rights and risk controls from administrative routing, retain the controls that matter, and remove handoffs without independent purpose.

Intermediate steps with no useful output

An employee exports a file, another reformats it, and a third looks up the original source again. Where the next role can work directly with existing information without losing necessary control, the intermediate stage can be eliminated.

Operations without a customer or purpose

Reports, notifications, document copies, and checks should have a clear user or required purpose. If a report is unused, not mandatory, and disconnected from decisions, removing it may be more valuable than generating it automatically.

Simplify the workflow, keep the result

Select a scenario to see how individual steps are reviewed. The visualization marks redundant activities, preserves mandatory controls, removes unnecessary steps, and redraws the route with an updated step count.

A · Redundant approvals

A company purchases standard supplies within an approved budget. The same routine request passes several people even though some approvals add neither new authority nor a distinct control.

Before · 7

  1. Employee submits a request
  2. Re-enter details in another form
  3. Manager reviews the routine request
  4. Assistant forwards the request
  5. Coordinator repeats the approval
  6. Authorized person checks the budget
  7. Purchasing places the order

After review · 3

  1. Submit the request
  2. Check budget and authorization
  3. Place the purchase order

Budget and authorization checks stay. Requests beyond delegated limits and exceptional purchases still require approval.

Duplicate entry, two formal sign-offs, and the purely administrative handoff are removed in this policy setting. If a request exceeds delegated limits or is exceptional, the relevant approval stays in place.

B · Duplicate records

A customer request is entered in CRM and then copied into Excel, a departmental spreadsheet, and a separate email summary. Employees reconcile versions even though the main CRM record already exists.

Before · 6

  1. Receive a customer request
  2. Create or update the CRM record
  3. Enter the same details in Excel
  4. Copy into a departmental sheet
  5. Email a separate summary
  6. Process the request

After review · 3

  1. Receive a customer request
  2. Maintain one shared CRM record
  3. Process the request from the record

The shared CRM record and authorized access stay. Required archival copies are assessed separately.

The primary record remains available. Copies required by law, archival policy, or offline continuity are not removed without assessing their purpose.

C · An unused report

Every week an employee builds a status spreadsheet from ERP data. Managers already use live ERP information, and the emailed report is not used for any decision or mandatory obligation.

Before · 5

  1. Export ERP status information
  2. Copy the data to Excel
  3. Reformat the sheet
  4. Email the report
  5. Archive another report copy

After review · 0

0 unused reporting steps

This sub-process is discontinued. ERP data and required reporting stay.

Only the unused reporting sub-process is discontinued. ERP data, operational records and required reporting stay.

The review confirms that this report has no consumer or separate compliance purpose. The entire reporting sub-process is discontinued. Core ERP records and required reporting remain unchanged.

How we decide what can be removed

Process simplification is evidence-based rather than a matter of preference. Every proposed removal is checked against its purpose, required controls, and potential consequences.

Does the action create value?

Does it change the result for the customer or internal user?

Does the check add control?

Does it detect a distinct risk or merely repeat a previous check?

Is the step mandatory?

Legal, contractual, security, audit, or delegated-authority requirements.

Can we eliminate the handoff?

Can the next participant use existing authorized information?

Does the output have a user?

Who makes a decision using this document or report?

What changes if it disappears?

Effect on accuracy, lead time, risk, and traceability.

Candidates are tested through an approved small-scale pilot, with retained controls and a rollback option when needed.

Our process improvement method

  1. Define the required business outcome, quality level, recipient, and deadline.
  2. Map the as-is process: actions, roles, handoffs, data, waiting time, and exceptions.
  3. Classify every step as value-creating, mandatory control, duplicate, handoff, or unsupported activity.
  4. Check legal, contractual, security, authorization, and data-quality constraints.
  5. Design a simpler to-be process that preserves necessary decisions and records.
  6. Pilot the change, measure its effects, then consider automation only for steps that remain necessary.

Metrics and validation

MeasureApproachWhy it matters
Number of steps7 → 3 / 6 → 3 / 5 → 0Reductions in the three chosen workflows.
Cycle timeMeasured in the pilotIncludes both active work and waiting time.
Number of handoffsMeasured from the processTracks unnecessary transfers and delays.
Duplicate entryReviewed separatelyTracks repeated work and inconsistency risk.
Errors and exceptionsMust not deteriorateSimplification must not mask defects.
Required controlsAll applicable controls retainedRemoving steps is not permission to bypass mandatory requirements.

Time and cost are measured in the pilot using process frequency, work duration and waiting time.

What must stay

Simplification must not remove legitimate financial approvals, separation of duties, access controls, safety requirements, audit trails, or legally mandated actions. The outcome of a review is a redesigned workflow, documented reasons for removed steps, retained controls, and measurable success criteria.

Business outcome

The result is not merely a faster version of an inefficient procedure. It is a process designed around the required outcome: fewer redundant approvals, duplicate records, intermediate files, and reports without a purpose. Teams spend less time transferring information and more time doing work that affects the business.

A shorter process is easier to document, measure, control, and later automate. The company also avoids building integrations and software around activities it could eliminate altogether.

Fewer steps are not the goal in themselves. The goal is the same or better outcome at lower cost, while preserving necessary control.

Remove unnecessary steps → automate what remains → keep people where judgment and accountability matter.

Discuss process simplification

Show us one real workflow that feels slow, repetitive, or overly complicated. We will review its steps, identify unnecessary work, and determine what to remove before selecting technology.