Does your Project Manager really need to be in the office?
- 3 days ago
- 9 min read
The question isn't where your Project Manager sits. It's whether the project gets the leadership, coordination and oversight it needs.
IN THIS INSIGHT…
For many organisations, the idea of a Project Manager still comes with an image of someone sitting in the same office as the team they are managing. But does physical presence actually determine whether a project is well managed?
In this Insight, you'll discover:
Why physical presence and effective project management aren't the same thing
When being in the office can genuinely add value
What a Project Manager actually needs to be effective
Why the right working model depends on the project, not the job title
How remote, hybrid, fractional and external support can fit different organisational needs
DOES A PROJECT MANAGER NEED TO BE IN THE OFFICE?
It's an understandable question.
If you're paying someone to manage an important project, you might reasonably expect them to be visible, available and closely connected to the people delivering it.
For some projects, that may genuinely mean being in the office. But for others, it may not.
The important distinction is between physical presence and effective project leadership.
A Project Manager's role is to provide structure, coordination and accountability. They need to:
understand the objectives
know what's happening
identify risks
keep people aligned
communicate with stakeholders
challenge delays and unresolved decisions
keep the project moving towards its intended outcome
None of those responsibilities automatically require them to be sitting in the same building as the people involved.
The technology available to organisations today makes it possible to collaborate, communicate, review documents, manage plans, monitor progress and hold meaningful meetings without everyone being physically together.
That doesn't mean the office is irrelevant. It means the office is one possible way of supporting project delivery, rather than a requirement that should automatically be applied to every project.
PRESENCE ISN'T THE SAME AS PROGRESS
One of the easiest assumptions to make is that if a Project Manager is physically present, they must have better visibility of the project. Sometimes they will. But being in the office doesn't automatically create good communication, clear priorities or effective decision-making.
A Project Manager can spend every day surrounded by the project team and still struggle to get timely decisions from leadership.
They can attend every meeting and still lack clarity about changing organisational priorities. They can be physically close to colleagues while important risks remain hidden.
Equally, a Project Manager working remotely can maintain excellent visibility if the project has clear governance, reliable communication and the right information available at the right time.
This is particularly important for organisations where project teams are already distributed across locations.
If staff, partners, suppliers, trustees, funders or other stakeholders aren't all based in one place, insisting that the Project Manager is office-based doesn't necessarily solve the underlying coordination challenge.
The question becomes less about where the Project Manager works and more about how the project is managed.
REFLECTION:
If your Project Manager is physically present every day, what specific project outcome does that presence improve?
And if they weren't in the office, which part of their role would genuinely become harder?
WHEN DOES BEING IN THE OFFICE ADD REAL VALUE?
There are certainly projects where physical presence matters.
A Project Manager overseeing a significant operational change may need to spend time with frontline teams.
A project involving a physical site, new facilities or equipment may require regular visits.
A service transformation may benefit from the Project Manager observing how work actually happens rather than relying entirely on reports and meetings.
There can also be value in face-to-face interaction during particularly sensitive or complex periods. Difficult conversations can sometimes be easier in person.
Teams that have never worked together may benefit from spending time together at the beginning of a project.
A major project launch, workshop or planning session may be considerably more effective when everyone is physically present.
These are legitimate reasons to value office or site presence. But notice what they have in common. The requirement comes from the needs of the project. It isn't simply because "Project Managers should be in the office". That distinction matters.
A project may need a Project Manager to be physically present two days a week.
Another may benefit from monthly face-to-face sessions.
Another may genuinely require someone on site most of the time.
And another may be perfectly suited to remote management.
There isn't a universal answer because there isn't a universal project.
WHAT DOES A PROJECT MANAGER ACTUALLY NEED?
If physical location isn't the defining factor, what is?
At its simplest, an effective Project Manager needs the ability to do the things that keep delivery moving. That includes:
Access to the right information
Clear authority and accountability
Regular communication with the people involved
Access to decision-makers when decisions are needed
Reliable ways of tracking progress, risks, actions and dependencies
A clear understanding of organisational priorities
The confidence to raise concerns when something isn't going to plan
Enough time and capacity to actually manage the project
These requirements can exist in an office. They can exist in a hybrid environment. They can exist remotely. The working location is secondary to whether the underlying conditions for effective project management are present.
This is one reason why a project can struggle even when everyone involved is working from the same office.
As explored in our Insight "Why projects drift off course (even with good Project Managers)", projects can be affected by changing priorities, stretched resources, delayed decisions and limited organisational visibility.
Moving the Project Manager into the office doesn't automatically resolve any of those issues. Better project management does.
REFLECTION:
If you are considering making a Project Manager office-based, are you solving a genuine project delivery requirement — or trying to solve a communication or management problem through physical presence?
THE RIGHT MODEL DEPENDS ON THE PROJECT
Once organisations separate the role from the location, a wider range of options becomes possible.
A Project Manager could be:
Permanent and office-based
Permanent and hybrid
Permanent and remote
Part-time
Fractional
Contract
External
Brought in for a defined period of delivery
None of these models is inherently better. The right choice depends on what the organisation actually needs.
Consider a charity launching a new service. It may need experienced project leadership for nine months, but have no long-term requirement for a Project Manager once implementation is complete. A permanent appointment might still be appropriate. But it might also be worth considering whether a fixed-term, contract or external Project Manager provides a more proportionate way of accessing the capability required for that period.
Another organisation may have a permanent internal Project Manager but need additional capacity during a major programme of change. In that situation, external or fractional support could complement the existing team rather than replace it.
A smaller organisation may have strong operational leadership but lack dedicated project management expertise altogether. It may need experienced support to establish structure, manage delivery and build internal capability.
The important point is that the organisational requirement should come first. The employment model and working location should follow.
THE RISK OF STARTING WITH THE JOB DESCRIPTION
Sometimes the decision is made in the opposite order.
An organisation decides it needs a Project Manager.
It writes a job description.
The job description says the person must be full-time.
They must work from the office.
They must be available five days a week.
They must live within a particular geographical area.
Then the organisation begins recruiting.
At that point, the discussion has already moved away from the project itself. The organisation is recruiting for a particular employment and working model rather than first asking what capability the project requires.
That can unnecessarily narrow the field. It may exclude experienced people who could deliver the work effectively on a different basis. It may also create a longer-term commitment than the project actually requires.
This doesn't mean organisations should remove office requirements or avoid permanent recruitment. If there is a genuine reason for either, they should absolutely remain part of the decision.
The point is simply to understand why they are there. Is the Project Manager required to be physically present because the project genuinely benefits from it?
Or because that's how the role has traditionally been designed?
Those are very different questions.
PHYSICAL PRESENCE CAN BE A CAPABILITY, NOT A REQUIREMENT
There is another useful way to think about this.
Rather than asking: "Does our Project Manager need to be in the office?"
Ask: "What does the project need its Project Manager to be able to do?"
The answer might include:
Build relationships with frontline teams
Coordinate multiple stakeholders
Facilitate difficult discussions
Manage a complex programme of change
Work closely with senior leadership
Visit operational sites
Provide independent challenge
Coordinate a distributed project team
Provide additional delivery capacity
Bring a project back on track
Once those requirements are clear, the working model becomes much easier to determine.
Perhaps the answer is office-based.
Perhaps it is hybrid.
Perhaps it is predominantly remote with planned face-to-face sessions.
Perhaps the organisation needs someone for three days a week rather than five.
Perhaps it needs specialist expertise for a defined period rather than a permanent appointment.
The important thing is that the decision is being made because of the project, rather than because of assumptions about what a Project Manager is supposed to look like.
REFLECTION:
If you removed the words "office-based" and "full-time" from your current Project Manager role, what capability would you actually need to replace them with?
REMOTE DOESN'T MEAN DISCONNECTED
It's also important not to swing too far in the other direction. Remote working isn't automatically better.
A Project Manager working remotely still needs to build trust, understand the organisation and maintain strong relationships.
Poorly managed remote projects can suffer from communication gaps, delayed decisions and weaker relationships just as office-based projects can.
Some teams also benefit from regular face-to-face contact.
That is why a blanket "remote is better" approach isn't particularly helpful. The objective should be to create the right working environment for the project.
For some organisations, that might mean a Project Manager spending most of their time with the team. For others, it might mean a hybrid arrangement with deliberate face-to-face time at important points. For others, remote working may be entirely appropriate.
Good project management adapts to those circumstances.
THE VALUE OF FLEXIBILITY
For organisations delivering change, flexibility can be particularly valuable. Projects don't always need the same level of support throughout their lifecycle.
A project might need significant leadership during design and mobilisation, less support during a stable delivery period and additional input again as implementation approaches.
Organisations themselves also change.
Funding may become available for a defined programme.
A new strategic priority may emerge.
An existing project may suddenly become more complex.
A delivery team may lose key capacity.
A project that appeared manageable six months ago may begin to drift.
In those circumstances, being able to access experienced project management support without automatically creating a permanent structure can be useful.
That might mean a contractor.
It might mean fractional support.
It might mean an external Project Manager.
It might mean bringing in additional expertise alongside an existing team.
It could also mean using external support temporarily to help get a project back on track before handing responsibility back to the organisation.
The value isn't that one model is cheaper or better. The value is having enough flexibility to choose the model that is proportionate to the need.
REFLECTION:
Does your organisation have the flexibility to increase or reduce project management capacity when your delivery requirements change?
Or does your current structure make every change in capacity a major recruitment decision?
START WITH THE PROJECT, NOT THE LOCATION
The question of where a Project Manager works is worth asking. But it probably shouldn't be the first question.
Start with the project.
What are you trying to achieve?
How complex is the work?
Who needs to be involved?
Where are the stakeholders?
How much coordination is required?
What risks need active management?
How much leadership capacity is available internally?
How long will the project need dedicated project management?
What level of experience and specialist capability is required?
And where would physical presence genuinely make a difference?
Once those questions have been answered, the right model becomes much clearer.
Sometimes the answer will be a permanent, office-based Project Manager.
Sometimes it will be a hybrid employee.
Sometimes it will be a part-time or fractional role.
Sometimes a contract or external Project Manager will make more sense.
And sometimes the organisation may discover that what it actually needs isn't another permanent Project Manager at all, but additional oversight, coordination or PMO capability across several projects.
The important thing is that the organisation is choosing deliberately.
THE BEST LOCATION IS THE ONE THAT SUPPORTS DELIVERY
There is no prize for having a Project Manager in the office five days a week. There is also no prize for making a project remote simply because remote working is possible.
The measure of success is whether the project has the leadership, coordination, visibility and accountability it needs to achieve its intended outcome.
Physical presence can be valuable.
So can flexibility.
So can independence.
So can specialist experience.
The strongest organisations recognise that these are different considerations rather than competing ideologies.
They don't ask whether remote working is good or bad.
They ask what the project needs.
They don't assume every Project Manager should be permanent.
They ask how much capability is required and for how long.
And they don't build organisational structures simply because that's how project management has traditionally been provided.
They start with the outcome they need to achieve and work backwards.
CONCLUSION
The question isn't whether your Project Manager should be in the office. It's whether you're providing the right project management capability, in the right way, for the project you actually need to deliver.
Every organisation delivers projects differently. Whether you need a dedicated Project Manager, additional delivery capacity, specialist expertise or support to get an important project back on track, the right approach depends on your organisation, your project and your current capacity.
At RootRise, we provide practical Project Management support that can be shaped around the needs of the organisation — whether that means working alongside an internal team, providing additional capacity or supporting a defined project or period of change.
If you'd like to explore what level and type of project management support would be right for your organisation, we'd be pleased to have an initial conversation.
There's no obligation — just an opportunity to understand what you're trying to deliver and whether the way you're currently providing project management capability is helping you get there.
