What actually makes a project successful

Back to the blog

Ask what a successful project looks like and most people say on time and on budget. Those are the two things that get measured, and they are both worth having.

They are also, on their own, a poor definition. A project can hit both and still be a failure, and it happens more often than you would expect.

The triangle, and why it is a trade-off

Cost, time and quality are linked. Push one and at least one other moves. Compress the schedule and you pay overtime or accept rougher work. Cut the budget and you get cheaper materials or fewer hours. Insist on the highest quality and it takes longer and costs more.

This is not a reason for pessimism. It is a reason to decide in advance which of the three you are least willing to compromise, because under pressure you will trade one whether you meant to or not.

A better definition

A project succeeded if, a year later, you would make the same decision again.

That covers things the usual measures miss. Does it solve the problem you had? Does it hold up? Was the process bearable? Would you use the same contractor?

By that definition, a job that ran two weeks late and slightly over budget but produced exactly what you needed is a success. A job delivered on the promised date with a finish you notice every day is not.

What successful projects have in common

The scope was written down before pricing

Every successful project had a moment where someone described the work specifically enough that it could be priced and built. Where that is missing, the project runs on assumptions, and assumptions differ.

Surprises were handled as decisions

Something unexpected happens on nearly every project involving an existing building. The difference between a good and bad outcome is not whether it happened, but whether it was raised immediately with options and a price, or absorbed quietly and revealed at the end.

Communication was frequent and boring

Projects that go well tend to have unremarkable communication. A short update, a question answered the same day, a heads-up about a delivery. Projects that go badly often have long silences punctuated by difficult conversations.

Payment tracked progress

When money moves ahead of work, incentives drift. When it follows completed milestones, both sides stay pointed at the same thing.

Someone owned it

On every good project, one person is holding the whole thing in their head. On a large job that is a project manager. On a home job it is usually the contractor, and sometimes it has to be you. What does not work is nobody.

The most common cause of failure

Not incompetence, and not dishonesty. It is a gap between what the homeowner pictured and what the contractor understood, which nobody discovered until the work made it visible.

Both parties were reasonable. Both were describing something real. They were describing different things, in language vague enough that the difference did not surface until the tile was up.

That is why the unglamorous parts matter so much: the written scope, the exclusions, the photographs, the change orders in writing. They exist to make the gap visible early, while it is still cheap.