One of the easiest things to confuse in a growing business is activity with progress.

There can be meetings all day, messages coming in from every direction, people working late, projects moving between teams and a constant stream of things that need attention. From the outside, it can look like a very productive organisation. Everyone is busy, so it must be working.

I've worked in enough fast-moving businesses to know that those two things aren't necessarily connected.

A team can be incredibly busy while very little is actually moving forward. People can spend most of their time reacting to whatever appeared in their inbox that morning, jumping between priorities and waiting for decisions from someone else. They can finish a lot of tasks and still have the feeling that they're somehow falling further behind.

I've also seen the opposite. A team can look surprisingly calm while handling a considerable amount of work. There is still plenty happening, but people know what they're responsible for, decisions don't constantly get stuck, and everyone has enough visibility to understand what needs to happen next.

The difference usually isn't that one team works harder. It's that one has a better way of operating.

Busy businesses tend to create their own interruptions

When I'm looking at how a business operates, I pay attention to how often people have to stop what they're doing to find information, ask someone for a decision or work out what has changed since they last checked.

Those interruptions don't always look like operational problems. Someone sending a Slack message asking for an update seems harmless. A quick meeting to clarify something seems harmless. A manager answering a question from someone on the team seems harmless.

Multiply that across twenty people and an entire week starts looking very different.

The same thing happens with projects. If priorities change frequently but there isn't a clear way of communicating those changes, people can spend as much time figuring out what they should be working on as they do actually working.

This was particularly relevant at Melewi because we were managing digital projects with different clients, markets, teams and timelines. The work was often moving quickly, and there wasn't much value in pretending that a project plan created at the beginning would remain perfectly accurate several weeks later.

Our approach used timeboxed design sprints, shorter mini-sprints and frequent reviews. Design and development could also happen in parallel rather than waiting for one discipline to finish completely before the other started.

That structure wasn't there to make the work look organised. It gave the team a way to keep making decisions and moving forward while the details of a project inevitably changed.

A good process should make work easier, not give people more work

This is one of the things I think gets missed when companies start trying to "improve their processes."

The natural response to an operational problem is often to add something. Another meeting. Another tracker. Another approval step. Another spreadsheet. Another status update.

Sometimes those things are necessary. Often they are a symptom that the underlying problem hasn't been understood.

If a team keeps missing information, the answer might be better visibility rather than another meeting. If decisions keep being delayed, the issue might be unclear ownership rather than a lack of communication. If projects constantly need rescuing, perhaps the problem is how work is being scoped and prioritised rather than how hard the team is working.

I've always been more interested in what a process allows people to stop doing.

If a good system means a project manager doesn't have to chase five people for the same update, that's useful. If a support team can resolve a customer issue without escalating every unusual case, that's useful. If a founder doesn't need to answer the same operational question for the tenth time, that's useful.

The best processes tend to disappear into the work. People use them without spending their days thinking about the process itself.

Visibility changes behaviour

One of the biggest differences between a busy team and an effective one is often how much everyone can see.

When people don't have visibility, they create their own version of the truth. They ask for updates because they don't know what is happening. They duplicate work because they aren't sure whether someone else has already done it. They escalate because they can't see who owns the decision.

This is particularly difficult in distributed teams.

At Melewi, we worked across multiple countries and time zones, so relying on everyone simply knowing what everyone else was doing wasn't realistic. The way work was structured had to provide enough visibility for people to keep moving even when other team members weren't immediately available.

That doesn't mean every person needs access to every piece of information.

It means the information that people need to do their jobs shouldn't depend on finding the right person at the right moment.

That principle applies whether you're running a nine-person digital agency or a much larger organisation.

The goal isn't to eliminate chaos

I don't think good operations means a business becomes completely predictable.

Clients change their minds. Customers complain. Suppliers miss deadlines. A team member gets sick. Something breaks. A new opportunity appears that wasn't in the plan.

Those things are normal.

The difference is how much of the organisation's energy gets consumed by dealing with them.

A well-run operation still has problems. It just doesn't have to reinvent the response to every problem.

There are clear owners. There are known escalation paths. People have enough context to make decisions. The team can adjust without everything having to stop while someone works out what to do.

That was one of the reasons I liked the sprint approach at Melewi. We weren't trying to predict every detail of a project weeks in advance. We were creating enough structure around the work that we could respond when something changed without losing the entire direction of the project.

That distinction becomes increasingly important as a business grows.

Sometimes the busiest person is actually the warning sign

One of the things I look at when I join an operationally messy business is who seems to be doing everything.

There is usually someone who is constantly answering questions, fixing problems, chasing people, checking work and stepping into situations that don't seem to have a clear owner.

They are often also the person everyone considers indispensable.

Sometimes they are simply very good at their job.

But sometimes their workload is telling you something about the system around them.

If one person has become the human version of the company's search function, approval system, project tracker and escalation process, hiring another person to help them may not solve the underlying problem. You may just end up with two people doing the same thing.

The more useful question is why all of those decisions and pieces of information are reaching that person in the first place.

That is where operations becomes interesting to me. You're not just trying to make someone less busy. You're trying to understand why the work is accumulating there and whether the business can be designed differently.

Operating well should create capacity

Ultimately, I don't think the point of good operations is efficiency for its own sake.

The point is capacity.

Capacity for the team to handle more customers without everything becoming an emergency. Capacity for a project manager to think about the project rather than constantly chase it. Capacity for a founder to work on the direction of the business instead of answering questions that should have been resolved elsewhere.

When the systems around a business are working properly, growth doesn't necessarily feel easy. There will still be pressure, decisions and plenty of work.

But the organisation has somewhere for that pressure to go.

That's the difference I look for. Not whether everyone is busy, because they probably will be. Not whether there are lots of processes, because there probably should be some.

I want to know whether the way the business operates is creating more capacity as it grows, or whether every increase in customers, projects or revenue simply creates more work for the same people to absorb.

Because those are two very different kinds of growth.