Development

Can your business keep working when a key colleague is away?

“Only she knows that.” An experienced colleague can help resolve a difficult question. But if nobody can even check an order's status without her, work can stop and business calls can follow her on holiday.

Author
CreateIT
Published
Reading time
8 min

Listen to the articlesynthesised voice, 11:32

Start reading
Image 1Illustrative workflow. Keep the order details, responsible person and next step in a shared system.

Experienced employees are valuable. They spot exceptions, know your customers and can make decisions when there is no ready-made answer. It is also worth checking how often colleagues need their judgement and how often they simply need to know where a file is, who approved an order or what happens next.

Understanding that distinction makes it easier to decide where to start with digitalisation. Begin by tracing one customer request from the moment it arrives to the completion of the work.

When you need advice and when you need information

Talking to an experienced colleague is valuable when a difficult customer issue needs resolving. If everyone has to ask whether an invoice has been sent for every order, however, they lack access to information about work already done.

The same applies to re-entering data. An employee may know their work extremely well but spend much of their time copying information from emails and Excel spreadsheets into warehouse and accounting software. That arrangement may have made sense when the business was starting out. As the workload grows, it is worth examining which data the systems could pass to one another automatically.

Start the review with someone who understands the process. They can usually show you the steps that never made it into the instructions. These may involve special terms promised to a customer, a correction before an invoice goes out or a check that nobody else knows about. That knowledge is essential to building a solution the team can trust.

One order, several versions of the information

A hypothetical example, not a CreateIT client case. A customer orders goods by email. A salesperson enters the order in a spreadsheet and forwards the email to the warehouse. A colleague prepares the information for accounting. Later, the customer calls to change the delivery address.

The new address reaches the spreadsheet, but the warehouse still has the original email. Before dispatch, someone notices the discrepancy and calls the person who spoke to the customer. The order is clarified, but only because that person is available and remembers the conversation.

First, establish where the current delivery address is held and who is allowed to change it. Work out which systems need the updated address and how warehouse staff will know that the change has been approved. Answer these questions before deciding whether to connect existing software, build a new system or introduce an artificial intelligence (AI) agent.

Five questions to check your process

Choose one recently completed order or customer request. With the people involved, map its journey on one page. At each step, note the software used, the responsible person and the next action.

  1. Which record is current? If customer details differ between an email, the customer relationship management system (CRM) and the invoice, how does the team identify the right version? Name the authoritative source for each important type of data.
  2. Where is information entered again? Mark each instance of copying, retyping and forwarding files. Establish whether the next system needs all the information or only part of it.
  3. Where does work stop, and who notices? Is responsibility clear, along with the next action? Establish whether a necessary approval is pending or the work is delayed because someone has not received the information.
  4. What happens when there is an exception? Choose one example, such as a changed address, missing data or a failed transfer to the warehouse system. Who finds out, and how is eventual completion checked?
  5. Can a colleague take over using their own user account? Check that they can see the necessary information and activity history. Taking over should not require another person's password or a search through their personal inbox.

Record the problems in a short list. Perhaps an address is retyped in three places, responsibility for an order is unclear or a failed data transfer is noticed only when the customer calls. These observations can become specific development tasks with agreed ways to check the result.

Start with an improvement you can verify

Choose a recurring process with a clear beginning and end. It might be sending an approved order to the warehouse. Describe the intended result. The warehouse must receive the required data, the team must be able to see whether it arrived and the responsible person must be informed if something fails.

Before making changes, examine several real examples. Count how often data is entered again and how often it needs clarification. Record why work is delayed. Once the changes are in place, you will be able to compare what has improved. Assess the unnecessary work created by the current process rather than comparing employees' speed.

Agree the circumstances in which the system must stop carrying out a task automatically. A missing address or contradictory order details may require a human decision. Route the task to the responsible person with the information they need to make that decision.

Where integrations, business systems and AI can help

When data repeatedly needs to move between programs, those programs can be connected so the information passes automatically from one to the other. That connection is called an integration. First, establish which data exchange options your existing tools support. Define the source of the data, the exchange rules and what should happen if something goes wrong.

If the team lacks a consistent way of organising work, it needs a system that shows tasks, progress, responsible people and required approvals. Sometimes this can be built into a tool already in use. In other cases, a custom business system or a separate module is needed. Software that already does its job well can remain in place.

For free-form emails and documents, AI can help find the required information, group requests by topic or prepare a draft reply. An AI agent can use company tools and carry out several tasks in sequence. Design the solution so that important decisions require human approval. Calculations and actions that must strictly follow company rules should use clearly programmed logic.

Define access permissions and keep an activity history

Connecting systems also requires a review of access permissions. Decide who may view customer data, change an order or approve an action. This applies to employees, integrations and AI agents alike.

A tool that sorts incoming requests, for example, does not automatically need permission to delete customer records. The more serious the potential consequences of an error, the more carefully you need to define the permitted actions and the points at which further checks are required.

An activity history helps establish who changed a record, when it happened, whether the change was approved and whether the next system received it. This supports both troubleshooting and security reviews. The team also needs to know how to stop the automation and continue working while a problem is being resolved.

How to write the first brief

At the end of the review, use one page to describe the process's beginning and end, the systems involved, the key data, the responsible person and the desired result. Add a typical example and a few exceptions that can be used to test the solution.

The brief might require an approved order to reach the warehouse without data being entered again. Required fields must be checked before transfer, and the responsible person must be informed if the transfer fails. The order status and activity history must also be retained. This description makes it possible to estimate the work and agree how completion will be verified.

After implementation, check the process from start to finish again. Test an exception and whether another colleague can take over. If that colleague can see the work already done through their own account, knows when approval is needed and can continue fulfilling the order, the improvement can be assessed in everyday work too.

Start where work gets stuck

CreateIT works with your team to understand how you handle requests, where data is entered repeatedly and why work is delayed. We then plan the first improvement. We connect existing tools, develop the missing parts of your systems and add AI where it helps process information. Our work continues after implementation.

Choose one process that currently creates the most unnecessary work for your team. For the first conversation, a description of its steps and a list of the software used will help. Do not send customers' personal data or access passwords with your initial enquiry.

Arrange a consultation

Read more about our work in business digitalisation and system integration, business systems development and AI agents.

Share

LinkedIn Facebook Email

Newsletter

New articles in your inbox

Sign up to the CreateIT newsletter for practical articles on development, AI, marketing and cybersecurity.

We plan to send the newsletter no more than once a month.