Digitalisation does not begin with buying software. It begins by understanding what actually happens between a request and a result.
Many projects fail because a company digitises the visible form while keeping the same confusion underneath. A paper request becomes an online form, but employees still chase approvals in messages, retype information and ask which status is correct.
Use the following seven-step method to improve the process before automating it.
1. Choose one painful process
Do not start with “digitise the whole company.” Choose a process that is frequent, measurable and painful: quotations, maintenance requests, purchase approvals, attendance corrections or customer onboarding.
2. Observe the real process
Talk to the people doing the work. Record the trigger, information received, decisions, hand-offs, exceptions and final result. The official procedure may differ from reality; design for the real work while correcting unsafe shortcuts.
3. Remove steps before automating them
Ask of every step:
- Does it create value or control a real risk?
- Is the same information already available?
- Can two approvals become one?
- Is an exception being treated as the normal path?
Automating waste only makes waste move faster.
4. Define one source of truth
Decide where the authoritative record lives. Messages may notify people, but they should not be the only location of an approval or customer status.
5. Define statuses and ownership
Use a small set of clear states such as New, Under Review, Waiting for Customer, Approved and Closed. For every state, define who owns the next action and how long it should reasonably take.
6. Automate carefully
Start with predictable tasks: validation, routing, reminders, document generation and status updates. Keep a human decision for unusual pricing, sensitive customer communication, payments or high-impact actions.
7. Pilot and measure
Test with one team or branch. Compare before and after:
- Completion time
- Number of hand-offs
- Corrections and missing information
- Overdue requests
- Employee and customer effort
Example: a maintenance request
Before: a customer sends a voice note; an employee forwards it; someone writes it in Excel; a technician asks for the address; the manager later asks whether the job was completed.
After: a short form captures contact details, location, problem and photos. The system creates a job number, assigns a technician, records status changes and sends a completion message after review.
The improvement is not the form. It is the shared status, ownership and traceable history.
Keep the first version small
Build the core path and the most common exception. Do not attempt to encode every rare scenario on day one. A focused workflow that people use is more valuable than a comprehensive platform they avoid.