Micro-credentials are easy to start. Hard to get right.

---

Micro-credentials, properly done

There’s a quiet surge happening across Aotearoa.

Micro-credentials are everywhere.

On paper, they promise agility. Fast response to industry need. Targeted capability. Flexible delivery.

In practice?

Most people underestimate what it actually takes to get one approved — and more importantly, to make one worth anything once it is.

This isn’t a criticism. It’s a pattern.

And it’s solvable.

---

The tension — what people think vs reality

From the outside, a micro-credential can look deceptively simple:

• Define a topic
• Write some learning outcomes
• Add an assessment
• Submit to NZQA

But under the surface, the real questions are sharper:

• Is there genuine evidence of need, or just a good idea?
• Does this duplicate something that already exists?
• Is it actually a micro-credential — or drifting into qualification territory?
• Can the capability be verified, not just described?
• Does it fit inside a provider’s QMS and delivery reality?

This is where most builds stall.

Or get declined.

Or worse — get approved but never used.

---

The shift — from idea to verification

The real shift is this:

A micro-credential is not a piece of content.

It is a verified capability claim.

That changes everything.

It means:

• Assessment matters more than content
• Evidence matters more than intention
• Design matters more than enthusiasm

And in an AI-saturated environment, this becomes even more important.

Because generating content is now trivial.

Verifying capability is not.

---

The pattern — what actually works

Across recent builds, a consistent pattern emerges:

1. Start with the capability, not the topic What should someone be able to do that they can’t do now?
2. Map the evidence of need early Who cares about this — and why does it matter now?
3. Design assessment as verification Not just submission, but demonstration + judgement
4. Align tightly with NZQA expectations Especially around duplication, scope, and level
5. Work within a provider structure The QMS is not an admin layer — it’s part of the design

When these align, things move quickly.

When they don’t, friction shows up everywhere.

---

Why this matters now

We’re moving into a period where:

• Capability needs are shifting faster than qualification cycles
• AI is compressing the value of generic knowledge
• Employers care less about completion, more about performance

Micro-credentials sit right in that gap.

But only if they are done well.

Otherwise they become noise.

---

What I’ve built

I’ve pulled together a simple microsite that makes the landscape clearer:

→ What a micro-credential actually is (in practice)

→ How the NZQA process works at a high level

→ Where things tend to go wrong

→ What’s involved in moving from idea → approved → usable

It won’t walk you through every step.

But it will show you enough to understand what you’re really dealing with.

👉🏻 https://thisisgraeme.me/nzqa-micro-credentials/

---

Invitation

If you’re working inside a PTE, ITO, or industry group and trying to make sense of micro-credentials right now, you’re not alone.

The system is still finding its shape.

But the signal is clear:

Done properly, micro-credentials are one of the most effective tools we have for building real capability, quickly.

Done poorly, they disappear.

---