Smarter systems. Simpler processes. Ready for growth.

One of the things I'm best at is looking at something that isn't working particularly well, understanding why, and finding a practical way to make it better.

I've spent more than 20 years working across operations, professional services, start-ups, events, community organisations and businesses I've built myself. Those environments can look very different, but the problems often aren't. Information lives in too many places, people repeat work unnecessarily, processes have developed organically without anyone reviewing them, useful tools aren't being used properly, or something that worked perfectly well for three people becomes increasingly difficult when there are ten.

I enjoy untangling those problems.

My approach isn't about adding technology for the sake of it or producing an enormous process document nobody will use. I look at what people are actually trying to achieve, where time and effort are being lost, what needs to happen consistently, and whether existing tools can do more of the work.

The aim is simple: make things easier to manage today without creating problems when you grow tomorrow.

Finding the actual problem

The problem somebody initially identifies isn't always the problem that needs solving.

A team might think it needs another person when the real issue is that somebody is spending hours manually transferring information between systems. A communication problem might actually be unclear ownership. A complicated reporting process might exist because several old processes have gradually been layered on top of each other.

That's why I tend to ask a lot of questions.

What are you trying to achieve? Why does this step happen? Who needs this information? Where did it come from? Where does it go next? Does somebody really need to do this manually? What happens if the volume doubles?

Sometimes there is a good reason for every step.

Sometimes nobody can remember why half of them exist.

Finding that distinction is usually where the interesting work starts.

Using tools to give people time back

I love finding a tool that removes a repetitive task.

That might mean introducing a better system, connecting tools that already exist, creating templates, improving how information is captured, using automation appropriately or simply showing somebody a feature in software they already pay for that saves them hours every month.

Increasingly, that also includes understanding where AI can genuinely help.

I'm interested in practical applications rather than using technology because it is fashionable. If an automation takes longer to maintain than the task it replaced, it hasn't made anything more efficient. If a new platform creates three new processes around it, we probably haven't solved the original problem.

Technology should reduce unnecessary work and allow people to spend more time on the things that actually need people.

Building for the business you're becoming

Efficiency isn't only about saving time.

It's also about being ready for growth.

This is something I've learnt particularly strongly from building organisations myself. In the early stages, you can keep an extraordinary amount of information in your head. You know every customer, every relationship, every process and every workaround because you created most of them.

Then something grows.

More customers arrive. More people join. More projects happen simultaneously. Somebody else needs to do something that previously only you understood.

Suddenly all those informal systems become a risk.

I like helping organisations think about that point before they reach it.

You don't need heavyweight corporate infrastructure when you're a small organisation, but you do need processes that another person can understand, information that can be found, tools that can accommodate increased volume and enough structure that growth doesn't simply create more work.

The best systems should be able to grow with you.

People are part of every process

One of the reasons I enjoy this work is that efficiency isn't really about spreadsheets, software or workflows.

It's about people.

A technically perfect process that nobody understands or wants to use isn't a good process.

I've managed teams, worked within large organisations and built businesses with extremely limited resources. I've seen what happens when processes are designed around what management thinks people do rather than what actually happens day to day.

So I want to understand the reality.

Where are people frustrated? What are they duplicating? What information do they struggle to find? Which workarounds have they created because the official process doesn't work?

Very often, the people doing the work already know where the problems are.

They just haven't been given the time, permission or support to fix them.

Making limited resources go further

Some of my most useful experience has come from environments where there simply wasn't enough money, time or people to solve every problem by adding more resources.

When you're building a start-up, running a grassroots organisation or delivering something ambitious on a small budget, efficiency isn't a nice-to-have. It determines what is possible.

I've had to find ways of managing growing workloads, coordinating remote teams, delivering large numbers of events, organising complex projects and building businesses without the infrastructure a larger organisation might take for granted.

That has made me resourceful.

Before recommending that somebody buys something, hires somebody or builds something new, I'm usually interested in what they already have.

Can we simplify it?

Can we connect it?

Can we automate part of it?

Can we stop doing something that no longer serves a purpose?

Sometimes the most valuable efficiency improvement is deciding that something doesn't need to happen at all.

Where I can help

I can support organisations, teams, entrepreneurs and projects that know something could be working better but don't necessarily know what needs to change.

That might involve reviewing processes and workflows, identifying inefficiencies and duplicated work, improving operational structures, exploring appropriate tools and automation, preparing systems for growth, documenting processes so knowledge isn't held by one person, or helping make sense of a particularly complicated operational problem.

I'm particularly useful when things have grown organically. Perhaps the organisation is bigger than it used to be, the workload has increased, different systems have accumulated over time or the person who used to be able to keep everything in their head simply can't anymore.

You don't necessarily need to know what the solution is before we start.

Working out what the real problem is tends to be one of my favourite parts.