The Moment It Usually Goes Wrong
Most SME project teams do not fail because the people in them are incapable. They fail because of a conversation that never happened — usually at the very beginning, before anyone had written a plan or booked a single meeting. Someone senior decided a project was happening, named a few people, and assumed the rest would sort itself out. It rarely does.
What gets skipped is the explicit agreement about how the team will actually function: who makes which decisions, how much time people are genuinely committing, what happens when operational work and project work collide, and who carries the accountability if things drift. These are not process questions. They are the difference between a group of people working on the same project and a team delivering one.
Getting project team structure right in an SME is less about frameworks and more about having the conversations most organisations avoid. This article sets out what those conversations need to cover — and what a functional SME project team actually looks like in practice.
Separate the Team from the Stakeholders
One of the most common structural mistakes in SME projects is conflating the project team with the broader stakeholder group. The MD wants to be kept informed, so they end up in the team meeting. The finance lead has opinions about the budget, so they become a standing attendee. The operations manager raises concerns at every update, so they get added to the distribution list for everything. Before long, a working team of four has become a consultation group of twelve, and nothing moves quickly enough because consensus is being sought from people who were never actually accountable for delivery.
The project team is the group responsible for delivering the work. Stakeholders are the people with an interest in the outcome. These are different things and they need different structures. The team meets frequently, works through detail, and makes decisions at pace. Stakeholders receive clear, concise updates at appropriate intervals and are consulted on specific questions rather than invited into the day-to-day. Drawing this boundary early — and holding it — is one of the highest-leverage structural decisions you will make.
For every person you are considering adding to the project team, ask: will they be doing work, or reviewing work? If the honest answer is reviewing, they are a stakeholder. Keep the team for doers only and manage reviewers through structured updates instead.
Title Inflation Is Your Enemy
SMEs tend to give project roles generous titles without attaching genuine authority to them. The Project Sponsor who has no power to unblock resource. The Steering Committee that meets quarterly and cannot make a decision between meetings. The Workstream Lead who is accountable for outputs but has no say over the people producing them. These titles create the appearance of structure while leaving the actual delivery team without the support they need.
The antidote is to define roles by what the person will actually do, not by what sounds appropriately senior. The sponsor's role is to make the decisions the delivery team cannot — and to make them within 48 hours of being asked. If the person you have in mind cannot commit to that, they are a stakeholder, not a sponsor. The steering committee's role is to provide direction when direction is genuinely needed, not to receive a formatted slide deck once a month. If you cannot articulate what decisions would come to them that could not be made elsewhere, the committee does not need to exist.
This is uncomfortable in organisations where seniority and inclusion are closely linked, but it is the conversation that determines whether the team structure will actually function.
The Core Team Should Be Small Enough to Fit in a Minibus
The optimal size for an SME project team is almost always smaller than the instinct suggests. The collaborative culture that makes many SMEs good places to work also creates pressure to include people — to ensure representation, to avoid anyone feeling left out, to benefit from diverse perspectives. All of these are legitimate values. They are just not well-served by making the delivery team larger.
Practically speaking, a core team of four to six people with clear individual accountability will outperform a team of ten to twelve where responsibility is shared and therefore, in practice, belongs to no one. Beyond a certain size, every additional member increases coordination cost faster than they add capacity. Meetings get longer. Decisions require more alignment. The people actually driving the work spend more time managing the people nominally supporting it.
Broad involvement and a small core team are not mutually exclusive. You can run a tight delivery team of five while consulting ten others at defined points in the process. The discipline is being explicit about the difference and resisting the gradual expansion of the core group that happens when stakeholders want to feel closer to the action.
The projects we see struggling most in SMEs are almost never under-resourced in terms of people. They are over-complicated in terms of who is involved and under-clear in terms of who is responsible.
Accountability Cannot Be Shared
Shared accountability is, in practice, no accountability. When two people are jointly responsible for a deliverable, each assumes the other is tracking it. When a team collectively owns a milestone, no one individual feels the weight of it slipping. The language of shared ownership feels collaborative and fair; the operational reality is that things fall through the gap between people.
Every deliverable, decision, and workstream in your project should have a single named owner — not a team, not a function, not a role. A person. That person can draw on others, delegate tasks, and collaborate extensively. But they are the one who answers the question: where are we with this? They are the one the delivery lead chases. They are the one who raises the flag when something is at risk.
This feels like more pressure than shared responsibility. It is — and that is precisely why it works. Clarity of accountability changes how people engage with their commitments. It is not about blame when things go wrong; it is about ensuring someone is always watching the thing that matters.
Build the Rhythm Before You Need It
Project teams in SMEs frequently operate without a defined communication rhythm, relying instead on ad hoc updates, informal check-ins, and the weekly all-hands that covers everything except the detail anyone actually needs. This works adequately when nothing is going wrong. When something starts to slip — and it always does at some point — the absence of a regular, structured touchpoint means problems surface later than they should.
A functioning SME project team typically needs three things: a brief weekly check-in of no more than thirty minutes focused on blockers and progress against the plan; a monthly review at which the delivery lead presents an honest assessment to the sponsor or steering group; and a clear escalation path that everyone on the team understands and trusts. The escalation path matters as much as the regular cadence — people will only raise problems early if they are confident that raising them will result in help rather than additional scrutiny.
Set the rhythm at the start of the project, protect it when operational pressure mounts, and treat cancellations as a signal worth paying attention to. When project meetings start getting pushed to accommodate BAU, it is usually a sign that the project is losing ground — not just in the diary, but in practice.
When the Gaps Become Too Big to Fill Internally
There is a point in many SME projects where an honest assessment reveals that the internal team, however committed, cannot provide what the project needs. Sometimes it is the delivery lead function — no one internally has the capacity or the structured PM experience to own it properly. Sometimes it is the governance layer — the sponsor is too stretched to engage meaningfully and the team is making decisions above its authority or deferring them indefinitely. Sometimes it is simply that the project has grown in complexity beyond what was anticipated when the team was assembled.
Recognising this early is far less costly than discovering it at the point of crisis. A Fractional PM embedded two or three days a week can provide the delivery lead function without displacing internal people — working alongside the team rather than above it. An Outsourced PMO can provide the governance and oversight infrastructure for organisations running multiple concurrent projects without the overhead of a permanent internal function. Both options are designed to flex around what an SME actually needs rather than imposing a structure built for a different kind of organisation.
If you are looking at your current project team and feeling uncertain about whether the structure is right, a conversation with us is a useful place to start.