From ideas to impact: Why teams struggle with automation, and how to fix it

Many automation programs fail quietly. Not because tools don’t work, but because adoption never becomes daily behaviour.

Many organisations are discovering this gap. Their people are willing, curious and often excited about automation. Yet progress feels slower than expected. Tools are considered, pilots are launched, and announcements are made, yet day-to-day work looks largely unchanged.

The issue is rarely the technology itself. More often, it’s the absence of a clear system for identifying the right problems to solve, making tools easy to find, and driving adoption.

Why automation ideas don’t surface naturally

Teams doing the work are usually closest to inefficiencies, but furthest from the mechanism to do something about it. They know where time is lost, where manual work creeps in, and where errors are most likely to occur. But that doesn’t mean those insights naturally turn into automation ideas.

Day to day delivery pressure plays a big role. When teams are focused on getting work out the door, inefficiencies are often tolerated because there’s little space to stop and rethink them. Familiar workarounds persist because “that’s how it’s always been done.” Over time, friction becomes normalised, and problems stop feeling fixable and start feeling like part of the job.

There’s also a perception gap. Many people assume that automation ideas need to arrive fully formed, complete with a solution and business case. Without a clear place to put early‑stage ideas, or even simple problem statements, most never get raised at all.

The result is an organisation that appears resistant to change, when in reality it’s simply missing a way to capture and shape ideas.

Teams as partners in improvement

A well‑performing automation strategy treats teams not just as users of tools, but as key contributors to how work can be improved.

This distinction matters. When teams are expected only to use what’s been rolled out, improvement becomes top‑down and sporadic. When teams are encouraged to surface friction points, automation becomes continuous.

An effective automation strategy doesn’t start with software. It starts with a repeatable way for teams to say:

• This task is painful
• This step feels unnecessary
• This is easy to get wrong

Crucially, those observations don’t need to include a solution. Capturing the problem is enough to start.

Building an ideas bank that actually works

Many organisations attempt to create an ideas list but find it quickly goes stale. The difference between a static list and a useful ideas bank is design.

Successful ideas banks tend to share a few characteristics:

• Low friction: Submitting an idea should take minutes, not hours. No business case required.
• Problem‑first: Ideas are framed around pain points, not “build a bot that…”
• Visibility: Teams can see what’s been raised, reducing duplication and building momentum.
• Timely acknowledgement: Letting people know their ideas have been seen matters more than immediate approval.

The simple act of capturing ideas sends a powerful message: improving how work gets done is part of the job, not a side project.

Why good tools fail to deliver

Even when automation tools exist, they may often go unused. Not because they don’t work, but because people can’t find them when it matters.

Under pressure, teams revert to familiar habits. If the right tool isn’t easy to locate, manual work quickly resurfaces.

 This is often treated as an IT problem, when it’s really a behavioural one. Tools need a clear “front door,” organised around tasks rather than technology, so teams instinctively know where to look.

Strong discoverability changes this dynamic. It ensures teams can answer a simple question in the moment they need it: “Is there already something that helps with this?”

We saw this in our own engagement letter workflow automation. While the tool removed much of the manual effort, rollout showed how sensitive adoption is to confidence. Even a small number of exceptions affected trust, and without full assurance teams naturally defaulted back to familiar manual approaches.

Why enablement beats features

Automation initiatives often focus on what a tool can do. However, adoption depends far more on how comfortable and confident people feel using it.

Short guides, quick training videos and accessible support dramatically reduce the barrier to first use. They remove the fear of getting it wrong and build trust in the solution.

This doesn’t require extensive documentation. In fact, lighter is usually better. A two‑minute walkthrough can be more effective than a detailed manual that no one opens.

Enablement removes the barriers that stop automation becoming part of everyday work.

Breaking old habits without breaking people

Old habits exist for a reason. They once worked. When new approaches feel unfamiliar and unsupported, people fall back on what they know.

Mandating change rarely fixes this. Sustainable behavioural change happens when the new way is easier, feels natural, and is well supported.

That means:
•    Clear expectations
•    Practical guidance
•    Time to adjust
•    And the right support when things don’t go perfectly

Automation succeeds when it respects human behaviour, not when it tries to override it.

Change fatigue is real

Teams are busy. Many are already managing heavy workloads and competing priorities. Adding automation on top, without coordination, can quickly turn enthusiasm into fatigue.
Change fatigue doesn’t show up as open resistance. It shows up as disengagement. Tools are acknowledged, then quietly ignored.

Leaders who recognise this focus deliberately on pacing. Fewer initiatives, better supported, deliver more than constant innovation noise. Automation needs prioritisation and clear ownership, not a steady stream of announcements.

A sustainable automation loop

Organisations seeing real returns from automation tend to follow a simple, repeatable rhythm:

1. Teams call out friction in their day-to-day work
2. Ideas are captured and visible
3. Existing tools are easy to find when they’re needed
4. Clear guidance lowers the barrier to first use
5. Ongoing support builds confidence
6. New habits take hold

The loop reinforces itself. As confidence grows, better ideas emerge. As adoption improves, trust increases.

Questions for leaders

As automation and AI continue to accelerate, a few questions are worth asking:

• Do our teams have a place to put improvement ideas? 
• Are we listening to insight from those closest to delivery?
• Can people easily find the tools we’ve already invested in?
• How are we measuring usage and time saved?
• Are we enabling adoption, or just announcing change?

Technology is no longer the limiting factor. The organisations that succeed will be those that design automation around people, working with teams to embed continuous improvement into everyday work.