What Government and Iwi Can Teach Tech About Collaboration

The tech sector uses the word "partnership" a lot. Strategic partnerships. Technology partners. Community partnerships. In most cases, what they mean is "we'd like to sell you something and call it a collaboration."

Real partnership, the kind that produces lasting outcomes, requires three things that technology companies are structurally bad at.

Patience. Government-iwi relationships operate on generational timelines. The Treaty settlement process, for example, spans decades. Iwi organisations think in terms of their mokopuna, not their quarterly results. When a tech company shows up proposing a "partnership" with a 12-month engagement and a renewal clause, the mismatch is immediate.

Shared power. In genuine government-iwi collaboration, both parties have authority. Treaty principles require partnership, and that means decision-making is shared. Tech companies are used to being the expert in the room. In cross-sector collaboration, expertise is distributed, and the community's expertise about its own needs always outranks technical knowledge.

Accountability that outlasts the project. When a government agency and an iwi agree on a set of outcomes, both parties remain accountable indefinitely. There's no sunset clause on Treaty obligations. Tech companies typically structure accountability around contract terms. When the contract ends, so does the relationship. That's not partnership. That's a service engagement.

Having worked in both government and iwi organisations, I've seen collaboration done well and done badly. The model that works has consistent features, regardless of the specific kaupapa.

The difference between governance and advisory input is decision-making authority. Advisory boards recommend. Governance bodies decide. Every successful government-iwi collaboration I've been part of had shared governance, a structure where both parties had genuine authority over direction, resource allocation, and outcomes.

In the iwi development space, this looks like co-governance of trusts, joint working groups with delegated authority, and shared ownership of data and intellectual property. It's messy. Decisions take longer. But the outcomes have legitimacy that no amount of unilateral decision-making can achieve.

Tech companies typically offer "advisory boards" or "community panels." These serve a purpose, but they're not governance. If the community can recommend but not decide, it's consultation, not collaboration.

In government-iwi work, the people matter as much as the process. Relationships are built between individuals, and those relationships carry institutional memory, trust, and accountability that can't be transferred to a replacement.

I've seen projects stall for months because a key relationship holder left and their replacement had to start the trust-building process from scratch. That's frustrating. It's also honest about how collaboration actually works. Trust is personal. You can't inherit it through a handover document.

The tech sector rotates people through projects routinely. A project manager leads the engagement for six months, then moves to the next client. For a standard technology implementation, this is fine. For cross-sector collaboration that depends on trust, it's destructive.

Government agencies operate within political, fiscal, and regulatory constraints that aren't always visible to external partners. Iwi organisations operate within cultural, governance, and capacity constraints that aren't always visible to government partners. The collaborations that work are the ones where both parties are transparent about their constraints.

AI is rapidly becoming a cross-sector issue. Government is developing AI policy. Iwi are asserting data sovereignty over AI training data. Communities are being affected by AI-driven decisions in health, education, housing, and justice.

The collaboration framework for AI governance already exists. It's the same framework government and iwi have been developing for decades: shared governance, genuine power-sharing, community authority over decisions that affect them, and accountability that extends beyond the project timeline.

That number should concern anyone who thinks we've learned from the past. If AI governance decisions are being made without the communities most affected by those decisions at the table, we're repeating the same mistakes with a more powerful technology.

If you're a technology company working in Aotearoa, or working with government and community organisations anywhere, here's what government-iwi collaboration teaches you.

Slow down. The urgent desire to ship doesn't override the need to build relationships. If your timeline doesn't allow for genuine engagement, your timeline is wrong.

Share power genuinely. Give community partners decision-making authority, not just input opportunities. If you can't do that, be honest about the nature of the engagement instead of calling it partnership.

Invest in relationship continuity. Assign people to community relationships for the long term. Don't rotate them out when the project plan says delivery is complete.

Be accountable after deployment. The technology doesn't stop affecting communities when the project closes. Stay engaged. Respond to feedback. Fix what isn't working. The relationship doesn't end when the invoice is paid.

Learn from existing models. Government-iwi collaboration in Aotearoa isn't perfect. But it represents decades of practice in how organisations with different values, priorities, and power levels can work together toward shared outcomes. That practice is directly applicable to how the tech sector should engage with the communities it serves.

Cross-sector collaboration is hard. It's supposed to be hard. Easy collaboration usually means one party isn't being heard. The difficulty is the signal that you're doing it right.