If you have worked in project delivery across both the public and private sectors in New Zealand, you will know the difference is significant. It is not a matter of one being harder or more important than the other. They are genuinely different contexts, operating under different pressures, with different definitions of success and very different accountability structures. The mistake some make is treating them as interchangeable, or assuming that a delivery approach that works brilliantly in a commercial context will translate without adjustment to a Crown entity or a government agency.

At IQANZ, we have worked across both sectors for years. Our observations on what makes public sector delivery distinctive go beyond the familiar complaints about bureaucracy and process. There are structural realities that explain, without excusing, why government projects behave the way they do. Understanding those realities is the starting point for doing anything useful about them.

The Financial Year Problem, Revisited

Government agencies in New Zealand are funded and held accountable within a twelve-month financial year, governed through the Public Finance Act and managed through Vote appropriations. The problem is that most meaningful transformation programmes do not fit neatly into twelve months. They run for three, five, or more years. The Inland Revenue Business Transformation, one of the largest programmes the New Zealand public sector has undertaken in recent years, took the better part of a decade.

The misalignment between annual appropriations and multi-year projects creates persistent structural pressure. Teams feel compelled to compress activity into the current year to avoid losing budget at year end. Milestones get set to satisfy annual reporting cycles rather than to reflect the project’s genuine progress. Activity that should sit in year two gets pulled forward, creating congestion and confusion in year one. And the prospect of having to go through the budget reallocation process to move money into the next financial year creates an anxiety that distorts decision-making in ways that have nothing to do with what the project actually needs.

The Treasury’s Better Business Cases methodology exists precisely to address this by building robust investment logic, including multi-year costs and benefits, before funding decisions are committed. It is a well-designed framework. Its effectiveness depends entirely on the willingness of decision-makers to follow where the analysis leads, rather than using it to justify a conclusion they have already reached on other grounds.

The Three-Year Election Cycle and What It Actually Means for Projects

New Zealand has a three-year parliamentary term, which is among the shortest of any comparable democracy. Every three years, an election determines whether an outgoing government’s priorities continue under a new administration or are replaced by different ones. For policy wonks and political commentators, this is a feature of the constitutional landscape. For project teams in the public sector, it’s an operational constraint that has to be actively managed.

The maths of this is worth doing carefully, because the effective project window is considerably shorter than the nominal three years. By the time a government changes, there’s typically four or five months before the new administration has organised itself, settled its priorities, and is ready to progress substantive work. Account for the hundred-day planning process, ministerial briefings, agency briefings, the Christmas and New Year period, and the practical reality that major new initiatives just don’t get signed off in the first few months. You’re already looking at two and a half years instead of three.

Then take off the other end. In the final months before an election, politicians are focused on campaigning. Agencies become cautious about visibly progressing work that might become a political issue during the campaign period. Decision-makers are less accessible. So take off another three or four months there, and the effective delivery window compresses to something closer to two years, perhaps just over.

For a large transformation programme that needs three to five years to complete, this is a genuinely serious problem. The IR transformation ran to something like seven years. That’s almost three parliamentary terms. Managing continuity of intent, of funding, and of executive sponsorship across that kind of timeframe requires a level of institutional resilience that’s genuinely difficult to sustain.

Political risk in the risk register

Political risk, while it is almost always discussed in the room when major public sector programmes are being planned, is rarely captured formally in a risk register. It tends to live in corridor conversations rather than formal documentation. But the possibility that an incoming minister will want to change direction, that a change of government will pause or cancel a programme, or that a project will become politically inconvenient and find itself quietly deprioritised: these are real risks, and they deserve honest treatment in project planning documentation.

The practical response is not to pretend the risk does not exist but to design the programme with it in mind. That means building strong benefits narratives that are genuinely compelling to any political flavour of government. It means creating clear evidence of progress and value at regular intervals. And it means structuring the programme so that it can demonstrate meaningful outcomes before any potential change of administration, rather than requiring a full term to show results.

The Difference Between Public and Private Sector Pressure

We draw a clear distinction between the way financial pressure operates in the public and private sectors. In the private sector, financial constraint is a driver of innovation. Organisations that can’t afford to keep doing things the expensive way have no choice but to find a better way. Scarcity forces creative thinking. In our experience, the greatest motivation for innovation is a lack of money.

In a public sector environment, where the option to go back and ask for more money is often genuinely available, that pressure does not operate in the same way. This isn’t a criticism of the public sector. But it does help explain why the innovation and efficiency gains that private sector organisations achieve through financial pressure are harder to generate in government settings, and why the disciplines of cost management and scarcity-driven problem-solving need to be more deliberately cultivated.

The Difficulty of Saying No

There‘s a specific challenge in the public sector that we see constantly, and it’s one that is rarely discussed openly: the difficulty of saying no to people who have authority over you.
In a governance group, the question “can we do it faster?” is a completely legitimate thing to ask. In a project context, it deserves a careful, evidence-based answer. The problem is that in a public sector environment, when that question comes from a minister, a chief executive, or a powerful steering group member, the social and organisational dynamics make an honest answer very hard to give. We have seen this play out repeatedly: the project team does the work, proves the timeline is what it is, and is still met with pressure to go faster.

This is where project leadership earns its keep. Pushing back in the right way does not mean simply saying no. It means being prepared with data and options. It means being able to say: here’s what going faster would require, here are the risks if we do it, here’s what might fall over, and here are the implications of that. Then the decision sits with the person who asked the question, as it should. That conversation requires preparation, confidence, and a planning function robust enough to support it.

There’s an important corollary to this. If your plan isn’t robust enough to answer that question with data, then that’s its own red flag. A well-founded project schedule, built from proper bottom-up planning, should make it relatively straightforward to show what happens if you compress a milestone. If you can’t answer the question with evidence, the planning work may not have been done properly in the first place.

Optimism Bias and the Right Answer in the Room

Optimism bias is one of the most consistent patterns we observe in project delivery, and it’s particularly prevalent when people are asked direct questions in pressured environments without the context and data that would make a careful answer possible.

The natural response when someone senior asks “can we do it faster?” in a room full of people is to say yes. The instinct to be positive, to not disappoint, to not be the person who says something is not possible: these are powerful social forces. They are also consistently expensive. The professional alternative is not to say no on the spot. It’s to say: that deserves a considered answer, and I will come back to you with options and their implications. That response requires a culture in which it‘s acceptable to do that, and building that culture is a leadership responsibility.

Where it doesn’t exist, project managers are routinely put in positions where their only choices are to be honest and face the consequences or to be optimistic and delay them until the only option left negatively impacts project delivery.

Risk Aversion and the Tactical Fix

Beyond the challenge of managing upward, there’s a deeper tendency in the public sector toward safe, incremental action rather than radical change. The fear of a poor outcome becoming public, the accountability pressures that come with public money, and the natural conservatism of large institutions all push in the same direction.

If a genuine fix is considered too risky because it might attract public criticism, the default is to fix a symptom instead. The result is a tactical project that delivers something visible, something defensible, but not the underlying change the organisation actually needed. The Office of the Auditor-General has noted similar themes in its reviews of major public sector programmes, pointing to the tendency for systemic recommendations to be accepted and then incompletely implemented.

Tactical projects have their place. Fixing a symptom while building the capability to address the underlying cause is sometimes the right sequencing. The problem arises when a pattern of tactical interventions replaces the structural change an organisation actually needs, and when the risk aversion that drives this becomes so embedded that meaningful transformation stops being an available option. Over time, this is a very expensive way of staying in the same place.

What Strong Public Sector Project Leadership Looks Like

Given all of this, what does effective project and programme leadership actually look like in a New Zealand public sector context? Our answer comes down to a few consistent themes.

It means understanding the structural constraints and working with them rather than against them: building benefits cases that speak to any political configuration, managing the annual funding cycle while keeping sight of the multi-year programme, and being realistic about the delivery window each political term genuinely offers. It means having the courage to give honest assessments to governance groups rather than optimistic ones, backed by data and accompanied by options. It means protecting the continuity of good people through the inevitable turbulence of a long programme.

And it means recognising that the public sector’s constraints aren’t obstacles. They represent legitimate accountability to the people who fund public projects. The balance between proper planning, genuine pace, and public accountability is genuinely difficult to hit, and hitting it consistently is what distinguishes the programmes that succeed from the ones that become case studies in what not to do.