Every business reaches a point where informal coordination is no longer enough. When a company is small, people can make decisions quickly, everybody tends to know what everybody else is doing and, when something new needs to happen, someone usually takes responsibility and gets it done. There may be no formal project structure around the work, but with a small enough team and strong enough individuals, the business can still execute successfully.
The difficulty comes as the business grows and the work becomes more complex. There are more people involved, more dependencies between departments, more decisions that need approval and more demands competing for the same resources. What could once be resolved in a quick conversation now has to move through several people, and unless there is clear ownership and coordination, it becomes increasingly easy for work to stall, be duplicated or simply get lost.
They still associate it with a particular kind of work, perhaps a construction project, a major IT implementation or a large transformation programme, when the reality is that businesses are initiating change all the time. They launch products, enter markets, open branches, implement systems, recruit people, restructure departments and change processes. Whether the organisation chooses to call those activities projects or not, they all require people, resources, decisions, timelines and some understanding of the risks involved.
The difference is predictability
One of the biggest differences I see between organisations with strong project disciplines and those without them is predictability.
A business with the right structure around its projects has a much clearer view of what it is trying to achieve, what it is likely to cost, where the risks are and what needs to happen for the work to succeed. That does not mean there will never be problems or delays, but there is a framework for dealing with them and a clear understanding of who is responsible for making the necessary decisions.
If one person can execute successfully because they happen to be highly organised, while another struggles with exactly the same type of work because there is no structure to guide them, the business has built its delivery capability around people rather than around a repeatable process.
Problems usually start with ownership
When projects begin to struggle, I often see ownership becoming unclear before anything else. People do not know who has the authority to make a decision, priorities begin to shift, decisions are passed between people and accountability becomes blurred. Once that happens, time and effort are wasted because work gets duplicated, the wrong people may be pulled into the project and decisions that should be relatively simple take much longer than they need to.
This is particularly challenging in operational businesses because they can assume that project disciplines do not apply to them. If the organisation is not building a bridge, developing software or running something it formally recognises as a project, it may simply treat change as another part of normal operations.
But changing a business is not the same as running it. A significant system implementation, product launch or process change introduces risks, milestones and dependencies that do not exist in normal day-to-day activity. If that change is simply pushed into the normal flow of work, employees are expected to manage it alongside their existing responsibilities without the structure needed to coordinate it properly.
Growth eventually demands more structure
A small organisation can operate without a formal project manager because communication is easier and people tend to carry several responsibilities at once. Informal coordination can work very well in that environment, particularly when there are strong people leading the work.
As the business grows, the number of people, processes, products and reporting lines grows with it, and coordination has to become more explicit. People need to understand how work is initiated, who approves it, who makes decisions, how resources are allocated and where responsibility sits when something goes wrong.
That does not mean every growing business needs to build a large PMO. In some cases, an external project manager may make perfect sense for a once-off initiative, while an organisation that is continuously developing products or managing significant change may need that capability internally.
Without structure, the business forgets
There is also a longer-term cost that is easy to miss. When projects are not properly initiated, managed and closed, the business loses its institutional memory. There may be no useful record of which risks emerged, why certain decisions were taken, what worked well or what the team learned during delivery.
The next team can then walk straight into the same problems. Lessons learned are sometimes treated as an administrative exercise at the end of a project, but they matter because they allow the business to improve the next time it undertakes similar work. When that knowledge is captured properly, each project contributes something to the organisation beyond its immediate outcome. Without it, teams keep relearning lessons the business has already paid to learn.
Lack of structure is expensive
A lack of structure has a cost. It appears in missed deadlines, rework, duplicated effort, wasted time, poor allocation of resources and people becoming overwhelmed because they are constantly trying to compensate for unclear processes and decisions. Over time, it can also affect the credibility of the business if it repeatedly fails to deliver what it has promised.
Sometimes an initiative fails because the idea was wrong or the market did not want it, but sometimes the idea was perfectly good and the execution failed around it.
Project management cannot make a weak idea successful, but it can give a good idea a fair opportunity to succeed by bringing clarity to how the work will be executed, who is accountable and how the business will respond when things do not go according to plan.
