Every iwi development trust I've worked with has a shelf of consultant reports. Beautifully formatted. Thoroughly researched. Gathering dust. The consultants leave, the capability leaves with them, and the iwi is back where it started, only poorer.
What You Need to Know
- The consulting dependency cycle in iwi development is real and damaging. Iwi spend limited resources on external expertise that doesn't transfer capability.
- Data sovereignty isn't just a principle, it's a practical requirement. Iwi need systems that keep their data under their governance, not locked in a consultant's methodology or a vendor's platform.
- Technology that builds internal capability is worth ten times more than a report that recommends what to build.
- Emerging AI tools could accelerate this shift, but only if they're designed with iwi, not for them.
The Consultant Dependency Cycle
Here's how it works. An iwi secures funding for a development project. The funding body requires a strategic plan. The iwi doesn't have the internal resource to produce the plan in the format the funder wants, so they hire a consultant. The consultant interviews whānau, runs workshops, writes a report, and delivers it. The funder is satisfied. The consultant moves on.
Six months later, the iwi needs to implement the strategy. But the consultant built the framework in their own methodology. The data sits in the consultant's systems. The institutional knowledge walked out the door.
So the iwi hires another consultant.
$47M
spent annually on external consulting by Māori organisations
Source: Te Puni Kōkiri, Māori Economic Development Report, 2022
That's money leaving Māori communities. And much of it funds work that could be done internally if the right systems and capability existed.
What Iwi Actually Need
I saw this clearly at Te Hiku Iwi Development Trust. The most effective investments weren't in reports. They were in tools and people.
Data systems they own. Not a consultant's spreadsheet. Not a government portal they can't control. Systems where iwi data stays under iwi governance, accessible to the people who need it, structured in ways that make sense for their kaupapa.
Capability, not deliverables. Train the comms person. Upskill the data analyst. Build the internal team's ability to do the work themselves next time. A consultant who builds dependency has failed, even if the report is excellent.
Technology that fits their context. Most enterprise software assumes a certain organisational structure, language, and set of priorities. Iwi don't operate like corporates. The whakapapa of decision-making is different. The accountability structures run through whānau, hapū, and iwi, not through a board and CEO. Technology needs to reflect that.
Where AI Fits
There's a lot of hype about AI transforming every sector. For iwi development, the opportunity is real but specific.
AI tools that help iwi analyse their own data, generate their own reports, and build their own strategies could break the consultant dependency cycle. But only if those tools respect data sovereignty, work in te reo where needed, and are designed with iwi governance in mind.
18%
of Māori organisations report having adequate internal data capability
Source: Data ILG, Māori Data Sovereignty Report, 2023
The gap is obvious. And it won't be closed by more consultants telling iwi what they already know. It'll be closed by putting better tools in their hands and trusting them to use those tools well.
The tech sector has a role here. But it's a supporting role, not the lead. Iwi development is led by iwi. Technology should serve that kaupapa, not redirect it.