Skip to content

If You Can’t Describe the Process, You Can’t Improve It

By Tomasz Lewandowski · 24 Jun 2026 · 5 min read

Ask a business owner how customer orders are handled, and the answer often sounds straightforward. “A customer gets in touch, we prepare a quote, they accept it, we do the work and send an invoice.” Simple enough.

Now ask five different employees to write down every step involved in that process. You may receive five different answers. One person checks stock before sending the quote. Another does it afterwards. Someone always telephones the customer for confirmation. Someone else relies entirely on email. Finance has its own procedure for invoicing. Operations keeps a separate spreadsheet. Customer service maintains another list altogether.

Suddenly, the process that seemed obvious is anything but.

And that is precisely why documenting your processes is one of the most valuable things you can do before investing in new technology.

We Often Work From Habit, Not Design

Most business processes evolve gradually. A new customer requirement appears. An extra approval is introduced. Someone creates a spreadsheet “just for now”. Another team develops its own workaround. Years later, nobody remembers why half the steps exist, but everyone continues following them because changing them feels risky.

The result is complexity that nobody intended.

If It Lives Only in People’s Heads, It Is Not a Process

Many organisations depend on experienced employees who instinctively know what to do. That experience is valuable, but it should not be the only place where operational knowledge exists.

A process should be understandable without relying on memory. It should be possible for a new employee to follow documented guidance and produce a consistent outcome.

If success depends entirely on “knowing how things are done around here”, your business is carrying unnecessary risk.

Draw It Before You Digitise It

One of the simplest exercises costs nothing. Take a sheet of paper or open a whiteboard application and map a common business activity from beginning to end.

For example:

  • Customer enquiry
  • Quotation
  • Approval
  • Order confirmation
  • Delivery
  • Invoice
  • Payment
  • Follow-up

Then identify every decision, every handover and every place where information is entered into a system. The visual representation is often revealing. Many companies discover they are collecting the same information multiple times or waiting days for approvals that add little value.

Every Decision Point Deserves a Question

As you review a process, ask:

  • Why does this step exist?
  • Who benefits from it?
  • Could it be simplified?
  • Could it happen automatically?
  • Does it still reflect how the business operates today?

You may find that procedures introduced years ago no longer serve any useful purpose. Removing them can improve efficiency immediately without purchasing any software.

Standardisation Creates Freedom

Some business owners worry that documenting processes makes work rigid. In practice, standardisation often has the opposite effect. When routine tasks are consistent, employees spend less time deciding how to perform them and more time solving genuinely interesting problems. It also becomes much easier to train new colleagues, delegate responsibilities and maintain quality during periods of growth.

Consistency reduces friction.

Practical Steps You Can Take This Month

  • Pick one important process. Do not attempt to document everything at once. Choose something that affects customers or consumes significant staff time.
  • Involve the people who actually perform the work. Managers see processes differently from frontline employees. Include both perspectives.
  • Write down every step. Avoid assumptions. Even actions that seem obvious should be recorded.
  • Identify repeated data entry. Every time information is copied manually, mark it for review.
  • Record exceptions. Businesses often focus on the standard workflow but overlook special cases that create most of the complexity.
  • Name the owner of each step. A process without clear ownership creates delays. Each step should have someone responsible for completing it or deciding what happens next.
  • Use simple symbols. You do not need specialist notation. Boxes for actions, diamonds for decisions and arrows for movement are enough to reveal most issues.
  • Review the process annually. Your organisation changes over time. Your documentation should change with it.

Good Processes Make Good Technology Possible

Businesses sometimes blame software when projects disappoint. In reality, the technology is often reflecting the underlying process it was asked to support. If approvals are unclear, the software will expose that confusion. If responsibilities overlap, digital systems will not magically separate them. If information is inconsistent, reports will remain inconsistent.

Technology performs best when the underlying workflow is already logical.

Clarity Is a Competitive Advantage

The companies that scale successfully are rarely those with the most complicated procedures. They are the ones where everyone understands what happens next. Employees know their responsibilities. Customers receive consistent service. Managers can identify bottlenecks quickly. Automation becomes straightforward because the rules are already clear.

Before You Buy Software, Reach for a Pen

There is something wonderfully simple about improving a business with nothing more than a blank sheet of paper. Map a process. Challenge every step. Remove what no longer adds value. Only then should you ask how technology might help.

Because if you cannot clearly explain how your business works today, no software package, AI assistant or digital platform will be able to improve it for you tomorrow.

The first step in digital transformation is not installing new technology. It is understanding your own business well enough to describe it.

How to map and document a business process before digitising it

  1. Pick one important process. Do not attempt to document everything at once. Choose something that affects customers or consumes significant staff time, such as how customer orders are handled.
  2. Involve the people who do the work. Managers see processes differently from frontline employees, so include both perspectives to capture how the work actually happens rather than how it is assumed to happen.
  3. Write down every step. Map the activity from beginning to end and avoid assumptions. Even actions that seem obvious should be recorded, along with every decision and every handover.
  4. Identify repeated data entry. Every time information is copied manually, mark it for review. Many companies discover they are collecting the same information multiple times.
  5. Record exceptions. Businesses often focus on the standard workflow but overlook the special cases that create most of the complexity, so capture these too.
  6. Name the owner of each step. A process without clear ownership creates delays. Each step should have someone responsible for completing it or deciding what happens next.
  7. Use simple symbols. You do not need specialist notation. Boxes for actions, diamonds for decisions, arrows for movement and initials for owners are enough; a free whiteboard tool such as diagrams.net works well.
  8. Review the process annually. Your organisation changes over time, so revisit and update your documentation each year to keep it reflecting how the business actually operates.

Frequently asked questions

Should I map my business processes before buying software?

Yes. Documenting your processes is one of the most valuable things you can do before investing in new technology. Technology performs best when the underlying workflow is already logical, and if you cannot clearly explain how your business works today, no software package, AI assistant or digital platform will be able to improve it. Reach for a pen before you buy software.

Why do different employees describe the same process differently?

Most business processes evolve gradually rather than by design, so people develop their own habits and workarounds. One person checks stock before sending a quote and another does it afterwards; finance has its own invoicing procedure while operations and customer service keep separate spreadsheets. Years later nobody remembers why half the steps exist, but everyone keeps following them because changing feels risky.

Won't documenting processes make my business rigid and bureaucratic?

In practice standardisation often has the opposite effect. When routine tasks are consistent, employees spend less time deciding how to perform them and more time solving genuinely interesting problems. It also becomes much easier to train new colleagues, delegate responsibilities and maintain quality during growth, because consistency reduces friction.

How do I actually start mapping a process?

Take a sheet of paper or open a whiteboard application and map one common activity from beginning to end, for example from customer enquiry through quotation, approval, delivery, invoice, payment and follow-up. Then identify every decision, every handover and every place where information is entered into a system. You do not need specialist notation: boxes for actions, diamonds for decisions and arrows for movement are enough to reveal most issues.

How can I improve a process without spending money on software?

Review each step and ask why it exists, who benefits, whether it could be simplified, whether it could happen automatically, and whether it still reflects how the business operates today. You may find procedures introduced years ago no longer serve any purpose, and removing them can improve efficiency immediately without purchasing any software.

Why do software projects often disappoint?

Businesses sometimes blame the software, but the technology is usually just reflecting the underlying process it was asked to support. If approvals are unclear the software will expose that confusion, if responsibilities overlap digital systems will not magically separate them, and if information is inconsistent reports will remain inconsistent. Good processes are what make good technology possible.

Share Follow
Mapping the Journey — Traceability as a Process
The Warehouse Blueprint

Mapping the Journey — Traceability as a Process

Traceability starts with a map, not a menu option. Follow one item dock-to-door, find the black holes, then let software record it.

6 Jul 2026 · 5 min read
Before You Hire Another Employee, Fix the Process
Digitalising Your Business

Before You Hire Another Employee, Fix the Process

Before hiring another employee, ask whether your processes are the real bottleneck. Adding headcount to a broken workflow costs money without fixing the underlying problem.

1 Jul 2026 · 5 min read
Don’t Wait for the Perfect System
Digitalising Your Business

Don’t Wait for the Perfect System

Waiting for the perfect system before you start is the single biggest reason digital projects stall. Learn why starting small and iterating delivers more value than planning indefinitely.

26 Jun 2026 · 4 min read