top of page

Project Management for SMEs: Deliver Change Without the Chaos

Writer: Ian Wainwright
Ian Wainwright
Oct 13
4 min read

If you’re responsible for change in an SME, project management is relevant to you.

You can spend years managing change without calling it project management.

Introducing systems, moving premises, taking on contracts and changing how the business operates. These are things that need to get done, usually alongside keeping everything else running.


You will probably recognise the usual problems too: different expectations, not enough time, delayed decisions and work turning out to be more complicated than expected.

In an SME, these problems often land with the owner or a manager who already has a full workload. Customers still need looking after. Staff need support. The existing work still needs doing. The change has to fit somewhere.


There may be no dedicated project manager or spare team to take it on. The people delivering the change are also the people keeping the business running.

That is where practical project management can help.


Start with what you need to achieve

“Introduce a new system” tells us something about the work, but very little about the result the business needs.


Are we trying to reduce errors? Get invoices out sooner? Give staff access to reliable information? Stop entering the same details three times?

Those answers affect what we buy, how we introduce it and how we judge whether it has worked.


Without that agreement, people can put considerable effort into delivering different things. The supplier works towards its specification. A manager expects a particular improvement. Staff assume the new system will solve problems it was never designed to address.

For an SME with limited time and money, discovering those differences late can be costly. Finding them early gives you a chance to resolve them before committing further resources.


Look at the whole change

The supplier’s work is often the most visible part of a project. It has a price, a schedule and someone reporting progress.


The business’s own work can be much less clear.


For a new system, someone needs to prepare the information, agree how processes will work, make decisions about configuration and arrange time for testing and training. People also need to understand what will be expected of them when it goes live.

If that work is missing from the plan, the supplier can appear to be progressing well while the business falls behind.


I have worked on both sides of that relationship. A supplier can deliver its part and still leave the customer some way from being ready. Someone needs to coordinate the whole change and understand how the different pieces fit together.


Be realistic about people’s time

Giving a project to a capable manager can be a sensible decision. They know the business and understand what needs improving.


But assigning responsibility does not create capacity.

In a smaller business, the same person may be managing operations, dealing with customers and sorting out staffing issues. Their knowledge makes them valuable to the project, but it also means there are plenty of other demands on their time.

When will they do the project work? What can wait? Who else can contribute? Is some additional support needed?


Leaving those questions unanswered means the project competes with whatever is most urgent that day. Actions carry over. Meetings get postponed. Decisions wait.

A plan needs to reflect the time people can actually give. Otherwise, it is based on availability that does not exist.


Make sure decisions can be made

Projects bring questions that cannot always be answered through the usual day-to-day arrangements.


Different teams may want different things. A supplier may need an answer before it can continue. A proposed change may affect cost, timing or how the business operates.

People need to know who can decide and when that decision is needed.


If they do not, work can stop while everyone waits. Or someone makes an assumption to keep things moving, only to discover later that it was the wrong one.


An SME may be able to make decisions quickly because the owner is close to the work. But that only helps if the question reaches them and they have enough information to answer it.

A regular conversation with the right person may be enough. What matters is that decisions get made when they are needed.


Use progress reporting to prompt action

A report should help the business understand what is happening, why it matters and what needs doing.


“Configuration is 80% complete” tells you how the supplier’s work is progressing. But you also need to know if a decision about the invoicing process is overdue and testing will be delayed unless it is resolved this week.


That gives you something to act on: a decision to make, a reason it matters and a deadline.

For an SME, this might only need a brief update and a conversation. What matters is whether it helps the people responsible keep the change moving.


The No Fluff takeaway

You may have years of experience of delivering change. Project management gives you a way to organise that work more deliberately.


Be clear about the result. Plan the whole change, including the work your business needs to do. Agree responsibilities and make sure people have time. Get decisions made when they are needed, and use progress updates to identify what needs attention.


You don’t have to call yourself a project manager. But the change still needs managing.

Comments


bottom of page