Lessons from delivering spatial plans, strategies, policy and regulatory projects in New Zealand and Canada.
Planning professionals spend a lot of time thinking about plans and not enough time is spent thinking about how to deliver the projects that create those plans in the first place. After managing projects ranging from community spatial plans, business cases, to fast-track planning programmes, I've come to a simple conclusion: Most planning project failures are not planning failures. They are project management failures.
The technical planning is often sound. The evidence may be robust. The engagement can be extensive. Yet projects still stall, miss deadlines, blow budgets, lose stakeholder support, or produce plans that never get implemented. The difference between success and failure is often determined long before the plan itself is written.
Start with delivery, not documents
One of the biggest mistakes in planning projects is treating the document as the outcome. Planning projects succeed when they create better decisions, align investment, influence behaviour, and lead to real-world change. The most successful projects maintain a relentless focus on the value they are trying to create, rather than the document they are trying to produce or the processes they are working through. This principle sits at the heart of good planning project management. Projects exist to realise benefits, not generate deliverables.
Get the governance right early
Many planning projects run into trouble when governance is treated as administration rather than a core delivery activity. In practice, governance often sets the critical path.
Councils, committees, elected members, steering groups, iwi partners and executive sponsors all have decision-making roles. If their requirements are not built into the programme from the start, the project team can find itself scrambling to meet reporting deadlines it can no longer influence.
Good project managers work backwards from key decisions. This sounds obvious. Yet governance-related delays are a common causes of programme slippage in planning projects. Your programme can be flexible; committee reporting cycles usually are not.
Scope creep is planning's silent killer
Every planner has experienced it. Your plan attracts new scope like moths to a flame, becoming the panacea for everyone’s issues and opportunities. This can look like a new item raised in a workshop, a stakeholder requests additional analysis, a councillor asks for another option. Individually each request seems reasonable. Collectively they can derail a project. Change is inevitable in multi-stakeholder parties as these require compromise to succeed. The problem is unmanaged change.
One of the most valuable project management disciplines is maintaining a clear baseline scope and requiring conscious decisions whenever that baseline changes. The question should always be: what does this change mean for programme, budget, quality and resources? Effective project managers make scope visible, regularly revisit it, and create clear processes for evaluating change requests before they become additional work.
Stakeholders matter more than methodology
Planning is fundamentally a people business. It’s about relationships. I've seen beautifully designed project plans fail because influential stakeholders weren't brought along on the journey. I've also seen technically imperfect projects succeed because the right people understood the purpose, supported the outcome, and helped solve problems along the way.
Project success depends on how effectively you influence people to prioritise their time to work on your project, and to make informed decisions. The best project managers spend as much time thinking about stakeholders as they do schedules. They focus on converting influential stakeholders from passive observers into active champions.
Communication is not reporting
Many project teams equate communications with sending updates. Effective communication is much more deliberate, requiring careful thought about who needs what information, when it’s needed, how to share it, and what action is needed as a result.
Internal communication is particularly overlooked and the effort and time needed easily underestimated. In many planning projects, the ultimate success of a plan depends on transport teams, infrastructure specialists, economic development staff, asset managers, regulators and decision-makers applying it after project completion. If those people are not engaged throughout delivery, with early buy in, implementation becomes significantly harder.
The best planners spend time looking up
A challenge for many planners managing projects is balancing technical delivery with leadership responsibilities. When workload increases, project management is often the first thing sacrificed. Ironically, that usually creates more work.
One of the simplest but most effective habits is scheduling time to step back and review the overall project. Ask yourself: are we still solving the right problem? Are stakeholders aligned? Are risks increasing? Is the programme still realistic? What has changed since we started? Be proactive in making changes to fix what isn’t working.
Plans that sit on shelves are a project failure
This may be uncomfortable for planners to hear, as we have all been part of these projects. A technically excellent plan that is never implemented is not a successful project. It is an unfinished one. The highest-performing planning projects actively consider implementation from day zero. This means early thinking about funding pathways, infrastructure delivery, regulatory changes, organisational ownership, governance arrangements, monitoring and reporting.
Some of the strongest projects I've been involved in - including growth strategies and spatial planning programmes - spent as much time discussing implementation as vision and strategy. That's not accidental, delivery is where value is created.
Final thought: success is usually 100 small things
There is rarely one magic ingredient behind successful planning projects. Project management is often viewed as an administrative discipline when it is the leadership mechanism that turns strategy into action and ideas into outcomes. The best planning projects do not happen because the planning is good. They happen because the planning, governance, relationships, leadership, and project management all work together. And when that happens, plans stop sitting on shelves and start shaping places.
