District Council Plan Change Simulation Use Case | MOI

CONSTRUCTED SCENARIO — LOCAL GOVERNMENT Simulating Stakeholder Complexity in Contentious Planning Choices This use case examines how the Ministry of Insights could help a local authority navigate intense public and commercial friction, mapping systemic risks prior to a formal statutory vote. Sector Local Government (NZ) Featured Lab Engage Lab Decision Under Test District Plan Change … Read more

Crown Entity Restructure: Verifying Operational Reality

Constructed Scenario Analysis Crown Entity Restructure: Testing Structural Variations Against Front-line Reality This use case examines how the Ministry of Insights could assist a governance board to stress-test a proposed national organizational reconfiguration, exposing operational dependencies before ministerial approval is sought. Week Identity Week 02: Governance Under Pressure[cite: 1] Featured Lab Insights Lab[cite: 1] Sector … Read more

AI in High Stake Environments

Decision Intelligence Architecture Why High-Stakes Decisions Require More Than a Good Prompt Relying on linguistic engineering to guide complex organisational investments introduces significant, unmeasured governance vulnerabilities. True assurance requires moving beyond simple productivity enhancements into robust system simulation. Topic AI-Assisted Decision Making MOI Lens Decision Assurance Lab Related Labs Insights Lab and Consult Lab Core … Read more

Change Lab Case Study

Change Lab Case Study

Testing whether change can survive the real operating environment.

This case study shows how Ministry of Insights can use Change Lab to test whether a proposed transformation is realistic before leaders commit people, time, reputation and delivery capacity.

Focus Adoption, readiness and implementation realism
Related Labs Insights Lab and Engage Lab
Best used when The decision only succeeds if people change behaviour
The situation

The plan looked sensible. The adoption conditions were uncertain.

An organisation was preparing to introduce a significant operational change. The intended future state was clear enough on paper, but leaders were not confident that the change could survive day-to-day reality.

The risk was not that the strategy lacked logic. The risk was that the implementation plan assumed too much: too much available capacity, too much staff confidence, too much behavioural change and too little friction between current work and future expectations.

Change Lab is designed for this exact point: before the implementation pathway is locked in, when there is still time to test whether the change can realistically land.

The current operating environment was already under pressure.
The proposed change depended on people adopting new routines, responsibilities and decision behaviours.
Leaders needed more than a communications plan. They needed a realistic view of adoption risk.
The organisation needed to understand what had to be true before the change could be safely committed.
The challenge

Most change risk was hiding in the space between approval and behaviour.

On paper, the change could be described as a logical improvement. In practice, it required people to understand the reason for change, trust the direction, absorb new work, shift established habits and continue delivering existing services at the same time.

That meant the real question was not simply whether the change was desirable. The question was whether the organisation had the readiness, capacity, leadership clarity and behavioural conditions needed for the change to hold.

The Change Lab approach

Change realism before implementation commitment.

The work used Change Lab as a structured decision environment, not a generic change management template. The focus was on testing the conditions that would make adoption possible or fragile.

Step 01
Clarify the change being proposed.

The first step was to define what was actually changing, including roles, routines, decisions, responsibilities, systems, reporting and expected behaviours.

Step 02
Test current-state reality.

Where needed, the work connected with Insights Lab thinking to understand operational pressure, workarounds, constraints and existing failure points.

Step 03
Map adoption risk.

The analysis identified where staff confidence, capability, incentives, time, decision rights or leadership alignment could affect adoption.

Step 04
Translate risk into decision conditions.

The findings were turned into practical conditions leaders could use before approving, sequencing or adjusting the change pathway.

What was tested

The Lab focused on the things that usually break change after approval.

Readiness Can the organisation absorb the change?

Leadership clarity, operating load, fatigue, competing priorities and capability were tested against the proposed pathway.

Behaviour What must people do differently?

The work separated general awareness from the specific behaviours, decisions and routines that had to change.

Friction Where will implementation struggle?

Likely points of confusion, resistance, delay, low ownership or rework were made visible before rollout.

The insight

The change was not only a delivery problem. It was a decision-quality problem.

The key finding was that implementation confidence could not be separated from decision confidence. Leaders needed to know whether the change pathway was realistic before treating the decision as ready for commitment.

This is where MOI’s wider AI Simulation Labs model becomes useful. The Lab does not replace leadership judgement. It improves the evidence available before that judgement is exercised.

The output

A practical adoption pathway, not a motivational change plan.

The final output helped leaders understand what had to be strengthened before the change moved forward. The goal was not to slow the decision down. The goal was to reduce the likelihood of preventable implementation failure.

A clearer view of the current operating pressure affecting adoption.
A practical map of behaviours, roles and routines that needed to change.
A ranked view of adoption risks and implementation friction.
Decision conditions showing what needed to be true before approval or rollout.
Recommended sequencing to reduce overload, confusion and avoidable resistance.
Why it matters

Change does not fail in the slide deck. It fails in the handover to real work.

Many organisations approve change because the strategic logic is sound. Change Lab helps leaders ask a different question before commitment: can the organisation realistically act on this decision?

When the answer is uncertain, the decision should not be treated as implementation-ready. It should be tested, adjusted and strengthened before people are expected to absorb the consequences.

Related decision support

Change Lab can work alone or as part of a wider assurance pathway.

Where the change depends on operational truth, stakeholder alignment, public confidence or high-stakes approval, Change Lab can connect with other MOI Labs.

Insights Lab Case Study

Insights Lab Case Study

Finding the operational reality beneath the process map.

This case study shows how Ministry of Insights can use Insights Lab to uncover the real operating conditions behind a decision, transformation or improvement programme before leaders commit to the wrong solution.

Focus Operational reality, evidence quality and workarounds
Best used when The documented process does not match real work
The situation

The organisation had process documentation, but not enough operational truth.

An organisation was preparing to improve a service, workflow or operating model. On the surface, the process appeared to be documented. There were reports, dashboards, policies, role descriptions and process maps that explained how the work was supposed to move.

But leaders were not confident that these artefacts reflected what was really happening. Delivery delays, workarounds, inconsistent data, informal handoffs and repeated friction suggested that the official version of the process was incomplete.

Insights Lab is designed for this point: when leaders need to understand the real operating environment before approving change, automation, reporting or transformation.

The documented process did not explain recurring delay or rework.
Staff relied on informal workarounds to keep the work moving.
Reports and stakeholder accounts told different stories about performance.
Leaders needed evidence before deciding what should change.
The challenge

The visible problem was not necessarily the real problem.

Many improvement programmes begin by solving the problem that appears in a report or complaint. But visible symptoms often sit downstream from deeper operating conditions: unclear ownership, weak data, duplicated checks, broken handoffs, decision bottlenecks or tools that no longer fit the way work actually happens.

The challenge was to separate process appearance from operational reality so leaders could avoid investing in a solution that only treated the surface issue.

The Insights Lab approach

Reality capture before recommendation.

The work used Insights Lab as a structured decision environment. The aim was not to produce another static process map. The aim was to create a reliable view of how work actually moved through people, systems, decisions and constraints.

Step 01
Capture the documented process.

The first step was to understand the official version of the workflow, including policy, process maps, roles, reports, systems and expected handoffs.

Step 02
Compare documentation with real work.

The Lab examined where frontline activity, informal workarounds, system behaviour and stakeholder accounts differed from the documented process.

Step 03
Map constraints and failure loops.

Recurring friction, bottlenecks, rework, data gaps, unclear ownership and decision delays were mapped as operating conditions, not isolated incidents.

Step 04
Translate findings into decision-ready insight.

The findings were turned into decision options, requirement logic, improvement priorities and evidence-based next steps.

What was tested

The Lab focused on the conditions that distort decisions when they are left hidden.

Reality How does the work actually happen?

The Lab compared documented workflows with real activity, informal routines and the decisions people made to keep work moving.

Evidence What can leaders trust?

Reports, stakeholder accounts, system data and process evidence were tested for consistency, gaps and decision usefulness.

Friction Where does the system repeatedly break?

Recurring delay, handoff failure, duplicated effort and rework were traced back to structural causes.

The insight

Operational truth is a decision asset.

The key finding was that the organisation did not need a better-looking process map. It needed a more accurate understanding of the work system before deciding what to change.

This is where the wider MOI AI Simulation Labs model becomes useful. Insights Lab improves the quality of the evidence before leaders move into change, assurance or implementation.

The output

A clearer evidence base for improvement decisions.

The final output helped leaders distinguish symptoms from structural causes. This gave the organisation a stronger basis for prioritising improvement, automation, reporting, system change or operating model work.

An operational reality map showing how the work actually moved.
A constraint and friction register identifying bottlenecks, gaps and recurring failure loops.
An evidence quality view showing what could be trusted, questioned or strengthened.
Decision options linked to real operating conditions rather than assumptions.
Practical recommendations for sequencing, governance and future-state design.
Why it matters

Improvement fails when leaders optimise the process they think they have.

Many organisations invest in tools, automation or restructure before they fully understand the operating reality. That creates a risk of automating broken work, measuring the wrong thing or solving a symptom while the structural cause remains intact.

Insights Lab helps leaders understand the real system first. Once that reality is visible, the organisation can make better decisions about what to fix, what to redesign and what not to automate.

Related decision support

Insights Lab often becomes the foundation for wider decision assurance.

Where the operational findings affect adoption, stakeholder confidence, public trust or high-stakes approval, Insights Lab can connect with other MOI Labs.

What Is AI Simulation and Why Should New Zealand Businesses Care?

AI Simulation Insight

What Is AI Simulation and Why Should New Zealand Businesses Care?

Every organisation makes decisions based on incomplete information. AI simulation does not fix that, but it lets you see how those decisions are likely to play out before you commit real money, real people and real reputation to finding out the hard way.

The decision gap

The gap is between deciding and knowing what happens next.

There is a gap in how most New Zealand businesses make decisions, and it is not where people think it is.

The gap is not in strategy. Most organisations have more strategy than they can execute. It is not in data either. There is plenty of it, even if it is messy. And it is not in leadership intent. Most leaders want to make good decisions.

The gap is between deciding and knowing what happens next.

AI simulation exists to test consequences before the organisation has to learn them through cost, resistance, rework or public backlash.

A council approves a rates increase. What happens to public trust? Which community groups mobilise? Does the backlash hit the mayor’s office or the front-desk staff first?
A business restructures its customer service team. Where do the bottlenecks appear? Which processes break? Does the workload redistribute evenly or crush the two people who already carry everything?
An organisation rolls out a new system. Who adopts it? Who works around it? Where does the training fail to translate into changed behaviour?
Plain language

AI simulation is structured exploration of consequences.

Strip away the jargon and AI simulation is a straightforward concept: you build a model of how your organisation, community or system actually works, then you run scenarios through it to see what is likely to happen.

It is not prediction. Nobody is claiming to tell the future. It is structured exploration of consequences, a way to ask “what if” questions against a realistic model of your environment rather than against assumptions in someone’s head.

Traditional planning does this informally. Leaders sit in a room, discuss options and mentally model the likely outcomes. The problem is that mental models are limited by individual experience, biased by optimism and invisible to everyone else in the room.

How it works

AI simulation makes assumptions explicit, visible and testable.

Two people can look at the same proposal and have completely different assumptions about how it will land, and neither knows the other’s assumptions exist.

AI simulation makes those assumptions explicit. It builds them into a model you can see, test, challenge and refine. Then it runs scenarios across that model, not once, but many times under different conditions, to show the range of likely outcomes rather than the single outcome you were hoping for.

The AI component accelerates what would otherwise take weeks of manual analysis. It synthesises messy inputs, including interview data, operational metrics, stakeholder feedback and financial constraints, into a coherent model faster than any team could do manually.

But the human stays in charge. AI does not make the decision. It shows you what your decisions are likely to produce, so you can adjust before committing.

See Decision Assurance Lab Explore the Lab system
Why this matters now

Three pressures are converging on New Zealand businesses and public organisations.

AI simulation is relevant now in a way it was not even two years ago because organisations are being asked to make bigger decisions with less margin for error.

The cost of getting decisions wrong is rising.

Cost Failed decisions are harder to absorb.

Margins are tighter. Budgets are constrained. Councils are under pressure from ratepayers. A botched restructure or system implementation can set an organisation back years.

Pace Change is stacking up.

AI adoption, digital transformation, service redesign and workforce restructuring are often happening simultaneously, without a clear view of how they interact.

Trust Public confidence is fragile.

Councils and public organisations need to understand not just operational impact but civic impact: how communities respond, where resistance forms and what narratives take hold.

AI simulation addresses all three by letting leaders test before they commit, grounded in actual data, actual constraints and the actual operating environment.

This is also why the work often connects with Civic Lab, Engage Lab, Change Lab and Decision Assurance Lab.

What it looks like in practice

AI simulation is an approach to decision-making, not a single tool.

This is not a single platform. It is a decision approach that uses AI-supported models to explore outcomes across several practical use cases.

Use 01
Organisational reality mapping.

Before you can simulate change, you need to know how things actually work today: where work gets stuck, where handoffs fail, where decisions stall and where informal workarounds keep things running.

Use 02
Change impact simulation.

Before a restructure, new system, automation programme or service shift goes live, you model it against the operational baseline to test workload, capacity, service levels and friction.

Use 03
Stakeholder and civic simulation.

For councils and public organisations, simulation can model how different community segments may respond, where trust is fragile and where engagement needs to build legitimacy.

Use 04
Decision stress-testing.

Before committing to a major investment, policy change or transformation programme, leaders can test operational constraints, funding scenarios, adoption dynamics and stakeholder behaviour over time.

Use 05
Scenario comparison.

AI simulation lets leadership teams model several scenarios side by side, with explicit assumptions and transparent reasoning, so options can be compared on evidence rather than instinct.

Implementation through Changeable Explore Insights Lab Explore Change Lab
What AI simulation is not

The boundaries matter.

The term “simulation” can carry expectations from other fields that do not apply here.

It is not engineering-grade modelling that predicts outcomes to three decimal places. The goal is decision-ready insight, not false precision.
It is not a platform clients buy and operate. In the MOI model, simulation is a consulting methodology supported by AI, not a software product.
It is not a replacement for human judgement. The simulation informs. Leaders decide.
It is not a crystal ball. It shows likely consequences based on the best available evidence and explicit assumptions.

When assumptions change, the model changes. That is a feature, not a flaw. It means the reasoning is traceable and challengeable.

The New Zealand opportunity

New Zealand has characteristics that make AI simulation particularly valuable.

New Zealand is small enough that decisions have outsized impact. A restructure in a 200-person council affects a meaningful part of the community it serves. A botched system implementation in a regional business can lose money and the institutional knowledge of the people who leave because of it.

We also have a concentrated stakeholder environment. In many New Zealand communities, the people affected by a decision and the people making it are separated by one or two degrees. This creates accountability, but it also creates pressure to get things right the first time.

Our public sector is being pushed to adopt AI while still figuring out how. The government’s own AI direction and responsible AI guidance are useful, but organisations still need practical ways to test where AI will genuinely remove work and where it may simply shift problems elsewhere.

NZ AI Strategy MBIE Responsible AI MOI Ethical AI Policy
Where to start

AI simulation does not have to start as a large enterprise exercise.

A focused simulation engagement can be scoped around a single decision, a single service area or a single change programme. It does not require perfect data. It works with what exists and fills gaps through targeted discovery.

The starting point is almost always understanding reality. What is actually happening in your organisation today? Where does work get stuck? Where are the constraints? What assumptions are being made about capacity, capability and readiness that may not be true?

Once that baseline exists, everything else becomes possible: change simulation, scenario comparison, stakeholder modelling and decision stress-testing. Every decision after that is made against evidence rather than optimism.

The takeaway

The organisations that navigate the next few years best will test strategy against reality before committing to it.

The organisations that will navigate the next few years most successfully will not simply be the ones with the best strategies. They will be the ones that tested those strategies against reality before committing to them.

Ministry of Insights uses AI-supported simulation to help councils, SMEs and complex organisations make better decisions with less regret.

Next step

Bring the decision before reality tests it for you.

If your organisation is considering a restructure, service redesign, system implementation, automation programme, AI adoption pathway or public-facing decision, the best time to test the consequences is before commitment hardens.

Talk to MOI Explore Decision Assurance Lab Explore the AI Simulation Labs
Related decision support

AI simulation sits behind the wider MOI Lab system.

The Lab system applies AI-supported simulation to different kinds of decision pressure, including operational reality, civic consequence, stakeholder alignment, adoption risk, independent challenge and full decision assurance.

MOI Lab system Civic Lab Insights Lab Change Lab

Consult Lab Case Study

Consult Lab Case Study

Challenging a recommendation before it becomes commitment.

This case study shows how Ministry of Insights can use Consult Lab to test the quality of a recommendation, business case or decision paper before leaders approve, fund, defend or implement it.

Focus Independent challenge, executive synthesis and decision quality
Best used when A recommendation needs sharper judgement before approval
The situation

The paper was polished, but the decision logic needed testing.

An organisation had a recommendation moving toward senior approval. The material looked professional. The structure was clear, the preferred option was stated and the case for action had been presented in a way that appeared ready for endorsement.

But there were still important questions beneath the surface. Was the evidence strong enough? Had the options been tested fairly? Were the risks clear? Did the recommendation follow from the analysis, or had the paper simply made one pathway look more certain than it was?

Consult Lab is designed for this point: when leaders need independent challenge before a recommendation becomes policy, investment, procurement, delivery work or public commitment.

The recommendation was nearing approval and needed sharper review.
The supporting material looked complete, but the strength of the evidence was uneven.
Some assumptions had been accepted without enough challenge.
Leaders needed a clearer view of what should be approved, revised, paused or escalated.
The challenge

Most executive review checks the paper. Consult Lab checks the decision.

Formal papers can meet formatting expectations while still carrying weak decision logic. They may present options without testing trade-offs properly, state risks without showing their implications, or rely on assumptions that would materially change the recommendation if challenged.

The challenge was to move beyond presentation quality and examine decision quality: the evidence, reasoning, assumptions, options, risks and conditions that leaders needed before committing.

The Consult Lab approach

Independent review, structured for senior judgement.

The work used Consult Lab as a focused decision challenge environment. The aim was not to rewrite the paper for style. The aim was to test whether the recommendation was sufficiently clear, evidenced and defensible.

Step 01
Review the decision material.

The first step was to examine the recommendation, problem framing, options, evidence base, assumptions, risks and proposed pathway.

Step 02
Test evidence and assumptions.

The Lab separated what was known from what was inferred, assumed, optimistic, missing or presented with more confidence than the evidence supported.

Step 03
Challenge the recommendation logic.

The work tested whether the preferred option followed from the evidence and whether alternative options, trade-offs and consequences had been considered fairly.

Step 04
Translate challenge into executive advice.

The findings were turned into decision conditions, clarifying questions, challenge points and practical advisory notes leaders could use before approval.

What was tested

The Lab focused on the areas where weak decisions often hide inside strong-looking papers.

Logic Does the recommendation follow from the evidence?

The Lab tested whether the problem, options, analysis, trade-offs and recommendation pathway were coherent.

Evidence What is proven, inferred or unsupported?

The work separated strong evidence from assertion, optimism, missing data and assumptions that required further testing.

Judgement What should leaders know before approval?

The output identified what should be clarified, revised, escalated or tested before the decision hardened.

The insight

A better paper is not the same as a better decision.

The key finding was that the organisation did not need more polish. It needed sharper judgement about the evidence, recommendation logic and conditions for approval.

This is where the wider MOI AI Simulation Labs model becomes useful. Consult Lab helps leaders test the quality of the decision before the organisation becomes committed to the consequences.

The output

Executive challenge points that improved the decision pathway.

The final output helped leaders understand where the recommendation was strong, where it needed revision and what should be clarified before approval. The goal was not to block the decision. The goal was to make the decision more defensible.

An independent review of the recommendation, options, evidence and decision logic.
A clear distinction between known facts, assumptions, gaps and unsupported confidence.
Challenge points showing where the recommendation needed stronger reasoning.
Decision conditions showing what should be clarified before approval.
Practical advisory notes supporting approval, revision, escalation, pause or further assurance.
Why it matters

Decision challenge should improve confidence, not slow momentum.

Leaders do not need every recommendation delayed by unnecessary review. But when a decision carries strategic, operational, financial, stakeholder or reputational consequence, weak reasoning can become expensive very quickly.

Consult Lab helps leaders see whether the recommendation is ready for judgement. It gives executives and boards a clearer basis for approval, revision, escalation or further testing.

Related decision support

Consult Lab can work alone or lead into deeper assurance.

Where the recommendation depends on operational reality, stakeholder confidence, adoption readiness or high-stakes commitment, Consult Lab can connect with other MOI Labs.