Slow & Steady

Three months after implementing those first digital improvements, something interesting usually happens. The initial enthusiasm settles into routine, people have adapted to the new ways of working, and inevitably, someone suggests the next thing that could be improved.

This is actually a fantastic sign. It means your team has moved from seeing digital change as something that happens to them, to seeing it as something they can actively participate in. But it’s also a crucial moment that determines whether your digital transformation continues to build momentum or stalls completely.

The temptation at this stage is to capitalise on the enthusiasm by introducing multiple improvements at once. After all, people are feeling positive, they’ve seen that changes can actually make their work better, and there’s probably a long list of potential improvements you’ve been documenting.

This is precisely when you need to slow down.

Improving existing ideas

We’ve seen organisations get so excited by early wins that they overwhelm their teams with too many changes too quickly. The result is usually a return to the cautious wariness we talked about last time, except now it’s accompanied by a sense that digital transformation is just an endless series of adjustments to learn.

How do you maintain momentum without creating change fatigue? The key is shifting focus from implementing new solutions to optimising existing ones. Instead of asking "What should we improve next?", ask "How can we get even more value from what we’ve already implemented?"

This might involve advanced training on features that weren’t covered in initial rollouts, or exploring integrations between systems that are already working well independently. Sometimes it means having honest conversations about aspects that aren’t working as well as expected and making adjustments.

Recently, when working with the team at Resolve Poverty, we’ve created a tool that helps people in the Greater Manchester area find advice and be referred to money services in their area based on their needs. Historically this was done on paper, but our new tool gave a much wider audience access to the advice, as well as gave Resolve Poverty an unprecedented amount of data on needs in the region.

You can probably begin to imagine the day long workshops that took place to outline and design the dashboard and the impressive reports that the tool would generate can’t you? How did we present it, a humble excel file. We wanted to get the tool in the hands of real people quickly, and test our assumptions.

Once the tool had been used for a few months, and the team at the charity had time to understand if the data we were collecting would benefit their research, we were able to make the decision to make improvements to the data export that would help the team.

Evolution

Another approach is to let improvements emerge organically from your team’s experience rather than planning them in advance. Keep a running list of suggestions and frustrations, but resist acting on them immediately. Often, what seems like an urgent problem in week one turns out to be a minor irritation that people adapt to naturally.

However, some suggestions will keep coming up or gain support from multiple team members. These are worth investigating, but even then, the implementation approach matters. Instead of announcing the next improvement, frame it as responding to feedback: "Several people have mentioned [specific issue], so we’re going to test a solution."

The most sustainable digital transformations feel less like transformation and more like evolution. Changes happen regularly enough that the organisation continues to improve, but gradually enough that each change can be properly absorbed before the next one begins.

The key insight is that momentum doesn’t require constant motion. Sometimes the most productive thing you can do is pause, consolidate, and let people fully absorb the changes you’ve already made. This creates a much stronger foundation for future improvements than constantly adding new complexity.

When you get this balance right, your team develops genuine digital confidence. They become partners in identifying opportunities rather than recipients of imposed solutions. They start to see digital tools as flexible resources they can adapt and optimise rather than fixed systems they must learn to use correctly.

In our final part of this series, we'll explore how to recognise when your digital foundation is solid enough to support more ambitious improvements, and how to identify opportunities that could genuinely transform your impact rather than just improving your efficiency.

Maintaining momentum without overwhelming anyone