In a large organisation, an automation idea often starts with a very practical frustration: copy-and-paste work, manual follow-ups, or information that does not move smoothly between tools.
The first reaction can be to conclude that nothing is possible. Access is restricted, some applications cannot be connected freely, and approvals take time.
Those constraints exist for good reasons. They do not necessarily mean there is nothing to improve. The aim is not to work around the rules or add new software at any cost. It is to make better use of what is already approved, then identify the improvement that will be most useful to the people doing the work.
A constraint is not always a dead end
IT, security and tool-governance teams are not there to stop business teams from moving forward. They protect data, keep services reliable and prevent every department from creating its own isolated way of working.
That is why a broad request is hard to assess. Saying “we want to automate everything” does not identify the task that causes the problem, the checks that must remain, or the people involved.
A specific request makes the conversation clearer:
- which task currently takes too much time;
- which information does not move well;
- which tools are already available;
- what still needs a person’s review or approval;
- what could improve without changing the whole environment.
Automation then becomes a shared design question, not an opposition between a business team and the people responsible for its tools.
Start by making better use of what you have
In many organisations, deployed tools have underused capabilities. Some connections between them are already available. Forms, notifications, shared spaces and exports can sometimes remove part of the manual work.
So the first question should not be, “Which new tool should we buy?”
It should be: what are we still doing manually even though our existing tools could coordinate it better?
The answer may be a better configuration, a built-in connection between two tools, or a small, controlled automation. It may also be the decision not to automate a step while the process remains unclear or human control is essential.
That is part of good advice: do not automate for the sake of it. Choose the improvement that fits the situation.
Our article on underused business tools explores the same idea: handoffs between tools often reveal tasks that have gradually come to feel unavoidable.
Connect the business need to the existing environment
Before suggesting a solution, it helps to understand how the work actually happens. Where does the task begin? Who is involved? What data is handled? Which approvals must remain?
This makes it possible to separate what should remain human from what can be prepared, passed on or organised differently. The goal is not to rebuild the organisation’s systems. It is to reduce an identifiable friction without making the organisation more fragile.
In some cases, automation is the right answer. In others, using existing tools more effectively already saves time. Both approaches have a place.
One visible gain can make a wider need easier to see
When one department improves a specific task and the benefit is visible, other teams may recognise a similar friction in their own work.
They will not necessarily need the same solution. But the improvement becomes easier to explain: it is grounded in a concrete use case, known limits and an observed need, rather than an abstract request for another tool.
The need can then become an organisational conversation. Several teams may have a related problem, the expected benefits are clearer, and the people responsible for the tools have more information to assess it.
This does not guarantee that a broader solution will be approved. A useful first improvement can, however, create the conditions for a more factual and constructive conversation.
Keep the checks that matter
Time saved is not the only measure of good automation. A solution should also respect responsibilities, important checks and the realities of the work.
A step can be prepared automatically and then checked by the right person. Information can be brought together without delegating the decision. A team can receive an earlier alert while keeping control of what happens next.
The best solution is not always the most spectacular one. It is often the one that fits the team’s work, stays understandable and delivers a verifiable improvement.
Start with one specific task
You do not need a large transformation programme to make progress. A first step can be a repetitive, frequent and sufficiently clear task: re-entering data, following up, preparing a case file, or passing information from one tool to another.
You can then look at the existing tools, available access and required approvals. This approach helps identify a realistic improvement before considering a broader solution.
Have you identified a task that keeps coming back, but work in a constrained environment? Let’s discuss what can be improved using the tools you already have.