Architect or Project Manager: Who Does What?

By Liat Pilo, Project Manager and Site Supervisor, Pilo-Management

Ask ten homeowners what the difference is between their architect and their project manager, and most will give you a vague answer about one drawing and the other building. It is close enough to sound right, and wrong enough to cause real damage. The two roles are different in kind, not in seniority, and understanding the difference is one of the first things that separates a calm project from an expensive one.

After years on construction sites, I have come to describe it like a family. The client and the architect are, in a sense, the couple. Together they imagine something that does not yet exist, and the architect gives that shared idea a form: plans, proportions, light. The project that follows is, in every real sense, their child. And like any birth, bringing it into the world is rarely as smooth as the people who planned it expected.

The architect owns the vision

The architect designs the home. They establish what the site permits, prepare the drawings, and decide how the space should look and feel. Their loyalty is to the design, and it should be. A home built without a strong idea behind it is just a structure with good plumbing.

The project manager owns the execution

My job begins where the drawing meets reality. I run the site, coordinate the trades, hold the budget and the schedule, and resolve the hundreds of small problems that live in the gap between an elegant detail and a wall that has to actually carry it. My loyalty is to the build: that it is done correctly, on time, within budget, and without quietly betraying the design along the way.

Why it occasionally looks like a fight

On most projects there is a moment, usually several, when the architect and the project manager appear to want opposite things. The architect is defending the vision. I am hunting for the way to deliver it well, on time, and without spending money that does not need to be spent. From the outside it can look like a conflict of interest.

It almost never is. When both sides are doing their job properly, the friction is theatre, not war. In practice we are solving the same problem from two directions: I bring the architect buildable alternatives, the architect picks the one that protects the design, and between us we find the solution that serves the client rather than anyone's ego. The projects that go wrong are rarely the ones with creative tension. They are the ones where nobody was willing to have the argument at all.

What actually decides whether a project succeeds

If there is one thing I am certain of, it is this: the outcome of a project is determined less by the talent on site than by the quality of the conversation between the people running it.

When the client, the architect and the project manager talk to each other honestly, and put the project ahead of their own pride, the result is usually good. When they do not, even a gifted team produces a mediocre home and a trail of disputes. A surprising amount of my work has nothing to do with concrete. It is keeping that conversation open, and occasionally protecting people from their own worst instincts.

What this means for you

You are not choosing between an architect and a project manager. You need both, and more than that, you need them to function together.

What you should look for in a project manager is someone who treats the architect's vision as something to protect rather than something to survive, who speaks the language of design and the language of the site with equal fluency, and who can tell you the uncomfortable thing before it becomes the expensive thing.

A home begins as an idea shared between a client and an architect. Carrying it into the world intact, on budget and on time, is the entire job. Not choosing between the vision and the realities of the site, but refusing to sacrifice either one.