Project coordination in SMEs: the 5 mistakes that sink your projects (diagnosis + solutions)
Project management in SMEs
17.04.26
•
10 min
Projects in small and medium-sized businesses rarely fail because of a lack of skills. They go off track because information circulates poorly, nobody knows exactly who is doing what, and decisions made on Tuesday are forgotten by Thursday. It's a coordination problem, not a talent problem. According to PMI (Pulse of the Profession 2025, 2,841 professionals surveyed), only 50% of projects are considered successful, and poor communication is cited as a failure factor in one out of three projects. In small and medium-sized businesses, the problem takes a particular form. No PMO, no dedicated project manager, teams of 5 to 30 people where everyone wears several hats. Coordination relies on goodwill and human memory. It works as long as the company stays small and projects are short. As soon as projects get longer or the team grows, the cracks appear. This article identifies the five most destructive coordination mistakes in SMEs, the warning signs that help spot them before it's too late, and practical levers to fix them. If you've ever felt that your teams are working hard without moving forward together, the rest will speak to you.
Why coordination is the Achilles' heel of SMEs
In a large organization, coordination is a role. There is a PMO, certified project managers, documented processes, imposed tools. In an SME, coordination is an expected reflex from everyone, without anyone explicitly being responsible for it.
The result is predictable. According to Asana (Anatomy of Work Index 2024, more than 10,000 respondents), 58% of knowledge workers' time is spent on "work about work": coordination, information retrieval, sync meetings, follow-up emails. Only 26% of the time goes to the skilled work these people were hired to do.
In France, the situation is worsened by the meeting culture. An Asana study (2024) ranks France first in the world for time lost in unproductive meetings: 9.1 hours per week on average, compared with 5.2 hours in the United States and 4.1 hours in the United Kingdom. For an SME of 10 people, the annual cost of inefficient meetings approaches 58,700 euros (ADP/RhInfo estimate, 2024). This is not a case of meetingitis. It is the symptom of a coordination system that is not working. When information does not circulate between meetings, more meetings are needed to coordinate.
This vicious circle has a name in large organizations: the meetingitis. In SMEs, it has no name. It is simply experienced as normal.
The 5 coordination mistakes that sink projects
Error 1: no one knows who is responsible for what
This is the foundational mistake. In an SME of 20 people, everyone thinks they know who does what. But when you ask the question precisely, "who approves the deliverable before it is sent to the client?", you get three different answers.
According to Atlassian (2024, survey of 5,000 workers), 54% of participants leave a meeting without clearly knowing what to do or who is responsible. In SMEs, this vagueness is amplified by the versatility of roles. The same employee handles sales, project follow-up and sometimes production. Responsibilities overlap, and in the overlap zones, nobody acts.
The warning sign: duplicate tasks, or tasks that nobody did because each person thought it was the other's role.
Error 2: decisions are made orally and are never documented
The leader runs into a project manager in the hallway, approves a scope change, and goes on with the day. Two weeks later, the rest of the team discovers the change when delivering the wrong version to the client.
In SMEs, spoken communication is the rule. Decisions are made over the phone, over coffee, or in a WhatsApp exchange that will be buried under fifty messages. There is no usable record. According to Grammarly and Harris Poll (2024), the cost of ineffective communication reaches $12,506 per employee per year. For an SME of 15 people, that's the equivalent of nearly $190,000 lost to poor coordination and lost information.
The solution starts with a simple reflex: any decision made outside a formal meeting must be recorded somewhere. Meeting minutes solve part of the problem, but they do not cover informal decisions, which often represent the majority.
Error 3: information is scattered across five tools that nobody masters
Tasks are in an Excel spreadsheet. Emails contain client approvals. Files are on an internal server. Meeting notes are in OneNote or a paper notebook. Urgent messages go through Teams or WhatsApp.
According to IDC, knowledge workers spend an average of 2.5 hours a day looking for information (that is, 30% of their day). In SMEs, where there is no IT administrator to structure the tools, fragmentation is the norm. Everyone uses the channel that suits them, and information becomes fragmented.
The concrete result: a project manager who spends 15 minutes finding the latest version of a deliverable because there are three versions in three different places. Multiplied by five projects and twenty employees, the cost is massive but invisible. The issue of project information centralization is directly linked to this problem.
Error 4: the leader is the bottleneck for every decision
In SMEs, the leader or main manager is often the only one with the big picture. All decisions go back up to them. Teams wait for their approval before moving forward. When they are in a client meeting or traveling, the project stops.
This pattern is structural, not accidental. The Wellingtone report (State of Project Management 2025) shows that only 23% of organizations use project management software, and that 21% still manage their projects with spreadsheets. Without a tool that gives the whole team visibility, the leader remains the only point of reference.
The warning sign: emails that start with "I'm waiting for approval on..." or "did you have time to look at..." If these messages make up a significant share of your inbox, you are the bottleneck.
Error 5: no continuity between meetings and actions
The meeting ends. Ten action items were listed. Three days later, no one knows where the others stand. The next meeting starts with "okay, where were we?", and we spend twenty minutes reconstructing what was said the time before.
According to Fellow.ai, 44% of the action items decided in meetings are never carried out. It's not a motivation problem. It's a follow-up problem. The action leaves the meeting room and dies in an email or a sticky note. To understand how to structure project follow-up when you don't have a PMO, you first have to recognize that the break happens between the meeting and execution.
How to spot a coordination problem before it blows up
Coordination errors do not show up as a single incident. They build up silently over weeks, then explode when a client follows up, a deadline slips, or a collaborator leaves. The table below lists the early warning signs to watch for.
Warning sign | What it reveals | Associated error |
|---|---|---|
Tasks done twice or forgotten | Unclear responsibilities | Error 1 |
The client knows things the team doesn't | Undocumented decisions | Error 2 |
More than 15 minutes to find a document | Scattered information | Error 3 |
A flood of emails saying "I'm waiting for your approval" | Bottleneck leader | Error 4 |
Meetings that start with "where were we?" | Meeting-to-action disconnect | Error 5 |
New employee lost for weeks | Lack of project memory | All of them |
The same debates that keep coming back every month | Untracked decisions | Errors 2 + 5 |
One of these signals alone is not serious. Three or more at the same time indicate a systemic coordination problem, not just an isolated hiccup.
What changes when coordination works
Coordination is not a theoretical topic. Its effects are measurable. PMI (2025) shows that organizations with mature project management practices lose 28 times less budget than those that do not. The Standish Group (CHAOS Report) observes that small, well-scoped projects achieve a 90% success rate, compared with less than 10% for large, poorly coordinated projects.
At the scale of an SME of 20 people, correcting the five errors described above means recovering between 5 and 10 hours per week per employee. It also drastically reduces the risk of information loss during a project handoff, a moment when coordination failures become starkly visible.
The levers are not complex. They come down to four principles: clarify who does what (a simple RACI chart is enough), document decisions systematically (not just in meetings), centralize information in one place, and create an explicit link between what is decided and what is executed. Tools like 5Days make it possible to automate this link by connecting a project's meeting notes, tasks, and documents in a single searchable space.
FAQ: Project Coordination in SMEs
Quelle est la différence entre coordination et gestion de projet ?
Faut-il un chef de projet dédié pour bien coordonner ?
Quels sont les outils de coordination adaptés aux PME ?
Combien coute un problème de coordination dans une PME ?
Comment savoir si mon problème est la coordination ou la stratégie ?
La coordination se dégrade-t-elle avec la croissance de l'entreprise ?
Quel est le premier geste pour améliorer la coordination dans une PME ?
Comment coordonner un projet avec des prestataires externes ?
Coordination is not a consultant's concern. It is the invisible thread that links decisions to actions, and people to one another. In SMEs, there is no one to take formal responsibility for it, and that is precisely why the problem is so widespread. The first step is not a tool. It is recognizing that coordination doesn't happen by itself, even in a small team. The second step is to put in place a project tracking suited to your size, without importing the processes of large organizations.
