Skip to content

The Nicest Email I Received This Week

Nobody remembers the database. Nobody remembers the reports. Nobody remembers the integrations. What people remember is what those things allowed them to achieve.

I was reminded of that this week when I received an email that wasn’t a support request, wasn’t a bug report and wasn’t asking for a new feature. Instead, it was a thank you from someone whose service is now coming to an end.

Many years ago, we helped implement an outcomes automation system for their organisation. At the time, the conversations were the sort you’d expect on any software project: reducing administration, improving consistency, capturing information more effectively and helping staff work more efficiently. The success of the project was measured in processes, time savings and operational improvements.

Over time the technology faded into the background. People didn’t think about the database behind it. They didn’t think about the automation workflows, the reports or the technical decisions that made it all work. They simply got on with delivering their service. The software became part of the everyday routine, quietly removing manual tasks and giving staff more time to focus on the people they were there to support.

That’s often the best outcome for any business system. Not that people notice it, but that they stop noticing it altogether.

Working in software, it’s easy to become absorbed by the technical side of what we do. We discuss platforms, performance, integrations, cloud services, upgrades and features. We focus on what the system can do. Yet the older I get, the more I think the real measure of success is what people can do because the system exists.

Can they spend less time on administration?

Can they respond more quickly?

Can they deliver a better service?

Can they focus their expertise where it matters most?

Technology is rarely the end goal. It’s simply the means to achieve something more important.

What made the email so meaningful wasn’t that someone remembered the software. It was that they remembered the difference it had made. Years after the project was delivered, they took the time to reflect on the impact it had had on their team and the people they supported.

When the system was first introduced, success was measured in efficiencies, processes and time savings.

Years later, the measure of success was much simpler.

Someone took the time to write a thank you.

For me, that’s probably the most meaningful project review you’ll ever receive.