In my experience, the success of a project without a formal PM depends on the maturity of the team and the complexity of the work. I’ve seen highly skilled and self-organizing teams deliver results efficiently, especially in Agile environments. However, in projects with multiple stakeholders, dependencies, and risks, the absence of a dedicated project manager often leads to misalignment and delays. A good PM doesn’t just track tasks they provide clarity, remove roadblocks, and ensure accountability. Have you worked on a project without a PM? What challenges did you face?
Good PMs are costly and hard to find. Most companies don't have the financial resources or time to get all the PMs they should have so the choices are either to overload the existing PMs with more projects than they can handle, cut back on the number of concurrent projects or have non-PMs manage the projects.
Like everything else in our profession, this is a risk-based decision. Lower complexity projects might be a good fit for folks who are not experienced in leading projects, but all project leads should get a minimal level of PM training before taking on any type of project.
Kiron
Absolutely, Kiron. It’s all about balancing cost, risk, and capability. Even basic PM training can make a big difference for non-PM leads.
Totally agree with this. I’ve been on Agile projects where a solid, self-organizing team handled things just fine without a formal PM. That said, someone usually stepped up to lead certain tasks and keep things on track.
But once you introduce multiple stakeholders, tight deadlines, or cross-team dependencies, things can get messy fast.
Without a PM, I’ve seen issues like unclear ownership, delayed decisions, and miscommunication come up often. Having someone dedicated to removing roadblocks, aligning the team, and keeping momentum makes a huge difference. Even in Agile, that kind of support is super valuable.
That said, I’ve also noticed that some organizations purposely avoid assigning a dedicated PM to small projects to keep costs down which can work if the team is experienced and the scope is limited. But it’s a gamble when complexity starts to creep in.
To Kiron’s point, this is really a risk-based decision for the organization - balancing cost savings against the potential impact of misalignment or delays.
Curious to hear what others have experienced - has anyone successfully run a complex project without a PM?
Totally with you—small teams may manage, but as complexity grows, dedicated PM support becomes crucial to avoid chaos and delays.
I wouldn't throw someone without any project management experience at an SAP implementation project, but when you consider the number of people that got their start by growing into the role and were doing the work before they were given the title, many projects can succeed, and have succeeded, without a formal project manager. To the point others have made, the more complex the project, the more experience you want the person running the project to have dealing with complex projects. I've worked at organizations where managers ran projects within their organization and project managers ran cross-functional projects. I no longer hold the formal title of project manager, but I still manage projects (on top of everything else).
Looking at your question from a different perspective, can a project succeed without someone filling the role of a project manager? As a project manager, I feel the role is required for project success. As someone with a different functional title, I feel the skills are more important than the title. Having a formal role/title can be helpful in an organization where role/title delineation is important, and the bigger the organization the more likely it is a titled project manager will be needed. But, like so many other things in project management, it depends.
Really appreciate your balanced view—it’s true, skills often matter more than titles. But as complexity grows, clear PM ownership becomes vital.
A manager is like a captain steering a ship through a storm: sets the course, cuts through hesitation, and makes it happen.
Three pillars sustain this strength: - Clear responsibility — Someone takes the helm and is accountable for the outcome. - Agile decision-making — No detours, the north is set, and the course is followed. - Focus on execution — Less planning, more action.
And what about committees? They are like a team of architects designing a bridge: they take time but build something solid.
They shine when: - The problem is a knot — More heads untangle it better. - Consensus is essential — Without unity, nothing moves forward. - Legitimacy matters — The “how” is just as important as the “what.” - Diversity adds up — Different angles spark brilliant solutions.
In short, if you want to decide and act, appoint a manager. If you want to analyze, engage, and build legitimacy, appoint a committee. If you want both, intentionally combine them
I love the analogy! Clear leadership drives action, but committees bring depth. Combining both can truly drive solid, well-rounded success.
Community Champion
