Project planning lessons from a Wyndham City Council engineer
Updated: Nov 12
When a council project goes well, you don't see the planning behind it.
That's one of the things Liam Collins said when I sat down with him for the first episode of my Lessons Learnt series. Liam is a senior project engineer at Wyndham City Council, which takes in Werribee, Point Cook and a big part of Melbourne's west. Over about 10 years he's gone from water into transport, through design, into project management and now strategic planning. So he's worked the project life cycle from the end back to the start.
Here's what stuck with me, and what we do with it at CBD.

1. Planning pays, but you never see it
"Putting in a lot of effort in the planning phases of a project, I think, always pays dividends."
Liam's point is that when a job runs smoothly, the planning is invisible. You only notice it when things go wrong.

I've seen the same on jobs since 2010. The hours spent upfront are the cheapest hours on the whole project. Skip them and you pay later in variations, delays and a crew waiting on an answer. That's money that buys the community nothing.
2. Build slack into the program
Liam called it optimism bias.
"You put in really tight time frames with no slack... no factors for anyone getting sick or wet weather or anything like that, and thinking that you can achieve it day on day, week on week, and it just doesn't happen."

Liam's fix for optimism bias
Plan from what you've actually achieved before.
Tell your stakeholders early.
Hold the line when the pressure comes.
Track the job closely enough that you see it slipping early, and do something about it.
On a tender the pressure is to sharpen everything, including the program. But a program with no slack just pushes the problem down the track, and it usually comes back as a variation. The contractor, that's us, pays, and the council and us wear it with the community. No one wins.
3. Handovers have to outlast the people
Some of Liam's projects run 5, 7, 9 years.
"People do come and go, so making sure that there's a sort of smooth transition between roles and phases is critical."
He sets up the governance from the start. Clear roles and responsibilities, a simple org structure, so everyone knows their place. And he puts experienced people in early to plan out each stage. It doesn't have to be in great detail.

That's why we put together the two templates below after our chat.
4. Lean on experience, and don't forget the soft skills
His advice to a young engineer: find the guru in the office and lean on them. Even when you think you know the answer, getting it checked gives you confidence.
And on young engineers with a good solution: "They might have a good solution, but they just can't sell it." If you can't bring the stakeholders with you, you'll fail. "Doesn't matter how good the idea is."

What we do with it in civil design and construction

On a bridge job in Queensland, for example, the bearings came from specialist overseas suppliers. We checked them at the supplier before they shipped and again once they landed at specialist testing facilities in Sydney. Two checks, so a problem shows up in a test lab and not on site.

Because design and construction sit in one team, the plan, the build and the handover stay connected. What the project learns doesn't fall through the gap between contracts.
The planning and the risk workshop is the cheapest and therefore the highest ROI work on the project.
Free project handover templates

Project Handover Page
One page that travels with the project, so what the project knows stays with it when people move on.
Asset Handover Form
Moves a finished project into the asset register with the full picture, including cost by component for capitalisation.
Watch the full conversation
The full interview with Liam is on my LinkedIn.
Thanks again Liam for being so open.
If you deliver council projects, how do you hand a project over when the lead moves on?


Comments