Process Mapping Before Digitisation: A Practical Guide

Process Mapping Before Digitisation: A Practical Guide for Syrian Companies and Organisations

Mapping a process means writing down what actually happens from the moment a request arrives until it is completed: who does what, with which document, and where work gets delayed. This simple step reveals problems nobody sees from inside the daily routine, and it needs nothing more than paper, pens and time with the team.

Strategy and roadmap 5 min read

By Nour Aldein Tleti. Updated 7 October 2026.

What is process mapping, and why does it come before digitisation?

Process mapping is documenting the steps of work as they actually happen, with the people, documents and decisions at each step. It comes before digitisation because it reveals duplication, bottlenecks and unnecessary steps, so you can fix them before moving them into a system. Without it, you may pay for software that repeats the same chaos, only faster.

What to document in each process

The start and end points: Such as “from the moment a customer’s order arrives” to “collecting the invoice amount”.
The steps in order: Every action that happens, even small steps like calling the warehouse to check availability.
People and roles: Who carries out each step, who approves and who must be informed.
Documents and tools: The ledger, Excel file, WhatsApp message or paper invoice used at each step.
Decision and waiting points: Where work stops while waiting for an approval or a piece of information, and roughly how long that takes.

What to look for after mapping

Duplicate entry: The same information written in more than one place, a major source of errors and conflicting figures.
Bottlenecks: A step that depends on one person, so everything stops when they are absent or busy.
Unnecessary approvals: Signatures requested out of habit that add no real control.
Lost information: WhatsApp orders or phone agreements that aren’t recorded anywhere you can refer back to.

Mapping tips for Syrian workplaces

Map reality, not the ideal: Ask employees what they actually do, not what the old instructions say.
Document what happens during outages: Write down the procedure followed when the electricity or internet goes down, because it is a real part of the process.
Record the currency points: Identify where the price is set or currency is converted, and who decides which exchange rate is used.
Don’t forget informal channels: Much of the work flows through WhatsApp groups and personal calls, so map them as they are, because they are part of the process.

Mapping one process step by step

01
Choose the process and set its boundaries
One process with a clear start and end, not a whole department.
02
Sit with the people who do it
Ask staff to explain what they do step by step, ideally while they are actually working.
03
Draw it on paper or a whiteboard
Use boxes for steps, arrows for the sequence and a different shape for decisions; no special software is needed.
04
Review the map with the team
Make sure the map reflects reality, and correct anything missed or described as it should be rather than as it is.
05
Draw the improved version
Remove duplication and assign an owner to each step, then make this version the basis for choosing and setting up the system.

Before and after mapping: an example goods order process

Step	Current situation	After improvement
Receiving the order	A WhatsApp message on the sales rep’s phone	The order is logged immediately in a shared record
Checking availability	A call to the storekeeper	Stock visible to the rep before confirming
Approving credit	Waiting hours for the manager	A clear credit limit for each customer
Issuing the invoice	Handwritten, then copied into Excel	One invoice issued from the same record

Read also

Strategy and roadmap

Frequently asked questions

Do we need specialist software for process mapping?

No. Paper, a whiteboard and coloured pens are enough at the start, and the map can be moved into a digital tool later for saving and sharing.

How long does it take to map a process?

It depends on its complexity, but a well-defined process can be mapped in a few sessions with the people involved.

Who should attend the mapping session?

Those who carry out the process daily, those who receive its output, and a manager with the authority to change the procedure.

What do we do with the map after choosing the system?

Use it to set up the system and train staff, and update it whenever the procedure changes.

Does mapping reveal problems unrelated to technology?

Often, yes, such as unclear permissions or conflicting instructions from different managers. Fixing these alone can improve the work before any system arrives.