Does a Project Manager Need Subject Matter Expertise?

A good project manager can lead a project without knowing how to do every specialist’s job.

I’ve managed projects across industries and technologies where I couldn’t personally perform half the tasks on the schedule. I needed people who could, and I needed to understand how their work connected.

That doesn’t give a PM permission to sit in meetings collecting updates they don’t understand. Leading unfamiliar work takes curiosity, preparation and the confidence to ask questions.

Understanding the work takes effort

There’s a difference between being able to configure a system and understanding what its configuration means for delivery.

A PM might not know how to build an integration. They still need to establish what it depends on, who owns it, how it will be tested and what happens if it arrives late.

“Development is nearly finished” needs more investigation.

Does finished include testing?

Has the receiving team agreed the interface?

Are the environments available?

Who accepts the result?

Those questions help turn specialist activity into a delivery plan people can rely on.

Technical knowledge can help

Relevant experience can shorten the learning curve. Familiarity with an industry can help a PM recognise constraints, understand terminology and spot an optimistic estimate.

Some roles also explicitly combine project management with technical leadership. In those cases, the person needs the qualifications and experience required for both responsibilities.

But technical expertise alone won’t tell you whether someone can lead a project. They also need to handle conflicting priorities, establish accountability, make consequences clear and get decisions in front of the right people.

Expertise becomes a problem when it blurs ownership

A technically experienced PM can be tempted to solve the problem themselves.

They start prescribing the solution, revising estimates without the delivery team or becoming the person everyone waits for before proceeding. Meanwhile, the wider project receives less attention.

The same can happen in reverse. A PM with limited subject knowledge can defer so completely to specialists that they stop challenging anything.

Both situations need clearer boundaries. Specialists should own their professional recommendations. The PM should make sure those recommendations are understood, connected to the wider plan and brought to the appropriate decision-maker.

You need access to people who know

A PM entering an unfamiliar field needs credible specialists, time to learn and a clear route for technical assurance.

They should be able to say, “I don’t understand that yet. Explain what it means for the project.”

They also need to recognise when a question exceeds their competence and requires qualified advice. Confidence isn’t a substitute for technical assurance.

If an organisation expects one person to manage delivery and provide specialist judgement across several disciplines, it needs to resource that expectation properly.

Ask a better hiring question

Alongside asking whether a PM has worked in your industry, ask how they approach unfamiliar work.

How do they test an estimate?

How do they establish whether progress is real?

When do they seek specialist review?

How do they resolve conflicting advice?

Subject matter knowledge can strengthen a PM. The ability to lead delivery determines how effectively they use it.

About the author

Gill Townsend is the founder of Cherry PI and a project delivery leader specialising in project governance, delivery leadership and PMO improvement. She writes about the realities of managing projects, challenging common assumptions and making project delivery more effective.