IN THIS ARTICLE
Project tracking in small and medium-sized businesses without a PMO: a practical method to never lose track again (2026)
Project management in SMEs
17.04.26
•
10 min
Project tracking in SMEs is about making sure the decisions made in meetings turn into actions that get carried out, that deadlines are met, and that no one loses the thread after six months. The problem: in most SMEs with 10 to 200 employees, there is neither a PMO, nor a dedicated project manager, nor a formal process for this. Tracking relies on goodwill, individual memory, and Excel files that no one updates. The numbers are telling. According to the PMI (Pulse of the Profession, 2025), only 50% of projects achieve their objectives. The remaining 50% are struggling or fail. And the main cause of failure is not technical: it is the loss of visibility over what was decided, by whom, and where things stand. In France, a Capterra survey of 250 SMEs shows that 35% of them have no specialized tool at all and manage their projects in spreadsheets or on paper. This guide offers a realistic method for structuring project tracking in SMEs, without hiring a PMO, without deploying a heavy tool, and by starting where most project information is actually created: meetings.
Why project tracking goes off track in SMEs (and it’s not a tool issue)
Most articles on project tracking start by listing methods (Gantt, Kanban, Agile) and end by recommending software. They miss the point. In SMEs, tracking does not go off the rails because of a lack of method. It goes off the rails because decisions made in meetings are not turned into traceable actions.
The scenario is always the same. Monday morning, project meeting. Three decisions are made, five actions are handed out verbally. No one records them in a structured way, or else in a meeting summary that ends up in an email never reopened. Two weeks later, in the follow-up meeting, half of the actions have not moved forward. Not out of negligence. Out of plain forgetfulness.
According to Fellow.app, 44 % of actions decided in meetings are never completed. WE-DO estimates that 70 to 80 % of them are not even properly recorded. In France, the situation is worsened by a record volume of meetings: 9.1 hours per week deemed unproductive according to the Asana Work Innovation Report 2024, the highest level among the countries studied.
The real bottleneck in project tracking for SMEs, it's not the absence of Gantt charts. It's the break between what is said in meetings and what is done afterward.
What “tracking a project” actually means when you don’t have a PMO
A PMO (Project Management Office) is a function or team dedicated to cross-functional project oversight. In large organizations, it standardizes methods, allocates resources, and consolidates reporting. It's a luxury that SMEs don't have, and one they don't necessarily need.
What they do need is to be able to answer four questions at any point in the project: what has been decided? Who is doing what, by when? What's blocking things? And what's changed since the last time?
In a 30-person SME, these answers are often scattered between the manager's head, the project manager's emails, a shared spreadsheet updated only sporadically, and meeting minutes that no one ever rereads. Result: when the manager wants a progress update on all ongoing projects, they have to chase down each person in charge one by one. It's a problem that prospects in engineering firms and service companies regularly describe: getting a consolidated view of progress without spending half a day on it.
Tracking a project without a PMO therefore means putting in place a minimal but reliable system that captures decisions, assigns actions, and makes it possible to pick up the thread at any time. The rest (Gantt charts, advanced KPIs, formalized risk management) can come later. But without these foundations, no tool will save project tracking.
The 4-step method: from the meeting to project follow-up
This method starts from a simple observation: in SMEs, most project information is created in meetings. That's where decisions are made, trade-offs are decided, and priorities adjusted. If you capture what comes out of meetings in a structured way, you have 80% of your project tracking.
Step 1: capture decisions and actions in real time
Each project meeting should produce three things: a list of decisions, a list of actions (with owner and due date), and a list of outstanding points. This is the non-negotiable minimum. IFOP and Wisembly estimate that 3 out of 4 meetings result in no formalized decision-making. Formalizing does not mean making things heavier. It means that someone notes in real time, in a consistent format, what was decided.
In practice, the most effective approach is to use a structured meeting minutes template with fixed sections. Or better: a tool that automatically captures exchanges and extracts actions from them. According to Fellow.ai, teams that use structured templates see 73% higher task completion rates.
Step 2: centralize actions in a single repository
The actions decided in meetings must end up in a single place, visible to the entire project team. Not in three different emails, not in the body of meeting notes that no one will open. A simple Kanban board (to do, in progress, done) is enough for most SME projects.
The classic mistake: multiplying the places where tasks are referenced. A prospect from an engineering consultancy sums it up well: the information ends up split between the internal server and the tracking tool, no one knows where the current version is, and after a few weeks the system is abandoned. One repository, or nothing.
Step 3: link each action to its original context
This is the step no one does, and it changes everything. An isolated action ("Follow up with the supplier for the quote") loses its meaning after two weeks. Why this follow-up? What was the context? What compromise had been discussed? If the action is linked to the meeting where it was decided, with the associated minutes, anyone can find the context in 30 seconds.
This is what is called decision traceability. On a project lasting 9 to 18 months with multiple stakeholders, it's the difference between smooth tracking and chronic loss of context. Engineering companies that manage long projects know this: the ability to find out why a decision was made six months ago is just as important as the decision itself.
Step 4: capitalize for the next project
A project ends. Files are archived. The team moves on to the next one. And all the knowledge accumulated over months disappears. According to McKinsey, employees spend an average of 1.8 hours per day searching for information. A significant part of this time is spent finding answers to questions already handled in previous projects.
Capitalizing on it is not about writing a 20-page lessons learned report that no one will read. It's about making sure the meeting notes, decisions, and deliverables from a project remain accessible and searchable once the project is over. When a new similar project starts, being able to query the previous project's knowledge base saves days, not hours.
Project tracking in SMEs: Excel, a dedicated tool, or knowledge management?
The tool question always comes up. And the answer depends on the size of your organization, the number of simultaneous projects, and above all on your collective discipline.
Approach | Strengths | Limitations | For whom |
|---|---|---|---|
Excel / Google Sheets | Free, familiar, flexible | No notifications, no link to meetings, quickly outdated if not updated | Team of fewer than 5, single project |
Project management tool (Trello, Asana, Monday) | Kanban/Gantt view, notifications, collaboration | Does not capture the context of decisions, disconnected from meetings, requires disciplined use | SME of 10-50, multiple projects, identified project manager |
Project knowledge management (centralization of meetings + tasks + docs) | Direct link between meetings and actions, searchable history, automatic knowledge capture | Still an emerging category, fewer integrations | SMEs of 10-200, long projects (6-18 months), need for traceability |
The important point: 35 % of French SMEs still manage their projects without a specialized tool (Capterra, 2018 survey of 250 SMEs). And among those that adopted a tool, many abandon it after a few months. The reason is almost always the same: the tool requires manual entry that no one has time to do. Adoption fails not because the tool is bad, but because it adds work instead of removing it.
That is why solutions that start from what already exists (meetings, exchanges, documents) to automatically feed tracking have a structural advantage. Teams are not asked to change their habits. We leverage what they already produce.
The 4 warning signs of poor project tracking
All projects that go off track send the same signals before collapsing. Recognizing them early makes it possible to act before the delay becomes impossible to recover from.
Signal 1: the same topics keep coming up in meetings. If you are revisiting a point already settled three weeks ago, it means the decision was not recorded, or it cannot be found. This is the most common symptom of poor tracking. Every re-discussion costs time and energy for the whole team.
Signal 2: no one knows who does what. According to Atlassian, 54% of participants leave a meeting without clearly knowing what their responsibilities are. If this ambiguity persists between meetings, tasks slip through the cracks. This is the classic breeding ground for SME coordination errors.
Signal 3: the leader has no consolidated view. When getting a progress update on ongoing projects requires individually contacting each manager, it means the information is too fragmented. An SME leader should not need to chase down their teams to know where the projects stand.
Signal 4: a departure creates a loss of knowledge. An employee leaves the project or the company, and suddenly no one knows why a particular technical option was chosen or what agreement was reached with the client in March. This is the ultimate test of tracking: does the handover happen in a few hours or over several weeks of trial and error? According to PwC (2023), average staff turnover in companies is 13.7%. At this rate, every long project experiences at least one staff change.
How to move from reactive follow-up to structured follow-up
The transition does not happen in a day. Here is a gradual approach suited to SMEs starting from scratch or almost.
Week 1: standardize meeting minutes
Adopt a single meeting minutes template with three required sections: decisions, actions (owner + due date), open items. Apply it to every project meeting, without exception. This is the foundation. Without it, nothing that follows works.
Week 2: create a single source of truth for actions
Choose one place to list ongoing actions. A shared Kanban board, a column in a spreadsheet, a dedicated tool. It doesn't matter what it is, as long as it is unique and the whole team has access. Every action from a meeting minutes should land there within 24 hours.
Month 1: establish a weekly review ritual
Every week, review ongoing actions for 15 minutes. This is the moment of truth: what is not moving forward becomes visible. This simple ritual is more effective than any sophisticated dashboard. PMI estimates that organizations that invest in structured project management practices waste 28 times fewer resources than those that do not.
Month 3: connect meetings to tracking
This is the key milestone. Instead of treating meeting minutes and project tracking as two separate systems, link them. Each task must be traceable back to the meeting where it was created. Each decision must remain traceable over time. It is at this stage that project knowledge management really makes sense: not as an extra layer, but as the cement between your meetings and your actions.
Tools like 5Days are designed exactly for this stage: they start from the meeting (transcription, automatic minutes) and feed project tracking directly (task extraction, Kanban, searchable history), without double entry.
FAQ — Project Tracking in SMEs
Qu'est-ce qu'un PMO et est-ce indispensable en PME ?
Quel est le meilleur outil de suivi de projet pour une PME ?
Comment suivre un projet sans chef de projet dédié ?
Comment éviter que les décisions de réunion soient oubliées ?
À quelle fréquence faut-il faire un point de suivi ?
Que faire quand un collaborateur quitte un projet en cours ?
Quelle est la différence entre gestion de projet et suivi de projet ?
Comment convaincre sa direction d'investir dans le suivi de projet ?
Project tracking in SMEs does not need a PMO, software costing 1,500 euros per month, or a Prince2 certification. It needs a simple system that turns what is said in meetings into traceable actions, and that makes it possible to pick up the thread of a project at any time. That is exactly what project knowledge management makes possible, and it is the reason SMEs that structure the link between their meetings and their operational follow-up see the difference within a few weeks.
