Start with one recurring task
Choose a task that happens often: a customer inquiry, a purchase request or an order update. Write down where it starts, who handles it, which information is needed and what finishes the task. A clear picture of the current process is more useful than a long list of tools.
Look for repeated entry and unclear handoffs
Notice where the same information is copied between systems, where people wait for approvals and where ownership becomes unclear. These are useful candidates for integration or workflow improvements. Keep steps that need judgement visible instead of treating every decision as a task to automate.
Define a useful first improvement
Agree on a small outcome: one shared request record, a clear approval path or fewer fields to re-enter. Decide how your team will review the change. Start with a focused release and use what you learn to choose the next improvement.
Example: follow an inquiry all the way to a decision
Imagine a company receiving inquiries through its website and messaging accounts. One employee copies the request into a spreadsheet, another checks availability, and a manager approves the quotation. The issue may be unclear ownership rather than a missing application. This is an illustrative workflow, not a report of a client project.
Map the normal journey and an exception: a request with incomplete information. Give every transition an owner, an expected output and a visible status. Only then decide whether the improvement needs a form, an integration or a custom system.
Choose a baseline before automating
Record when a request arrives, when someone first handles it and when the customer receives an answer. Distinguish waiting time from active work. Compare similar request types rather than averaging unrelated tasks.
- Count repeated data entry and requests returned for missing information.
- Ask staff which exceptions require judgement.
- Choose a pilot owner and a review date.
- Keep a manual recovery path when a connected service is unavailable.
What the first deliverable should contain
A useful first deliverable is a process map, a responsibility list and a small agreed change with acceptance criteria. For example, a request can be received once, assigned to the correct person and found later by its reference.
During review, ask staff to locate an old request, handle an incomplete one and explain who takes over when the usual owner is away. If those tasks remain unclear, improve the process before adding more automation.
