Studying a master's in New Zealand: what I tell my students

Why I wrote this

I teach master's students in New Zealand: information systems strategy, database management, IT project management and business analytics in a Master of Business Informatics programme, with classes in Christchurch and Auckland. I'm also a researcher at HIT Lab NZ at the University of Canterbury, where I did my PhD after coming here from Sri Lanka.

So I've seen postgraduate study in New Zealand from both sides of the desk. Every intake, students ask me the same questions in the first few weeks, and most of them are things nobody told them before they enrolled. This guide is my answer, written once, for anyone thinking about a master's degree in New Zealand, whatever the subject and wherever you study.

Taught or research master's?

New Zealand master's degrees sit at Level 9 of the New Zealand Qualifications Framework, and they come in two broad kinds. Knowing which one you're looking at changes almost everything about the experience.

• Taught (coursework) master's. You take a set of courses, each with its own assessments, often ending in a capstone or applied project. This is what I teach. It suits people who want to change careers, move into a technical or management role, or build a portfolio of real work.
• Research master's. Most of the degree is a thesis, supervised by one or two academics. It suits people heading towards a PhD or a research career. The relationship with your supervisor matters more than any course list, so talk to potential supervisors before you apply.

Many programmes mix the two: coursework first, then a research project or dissertation. Read the structure carefully and count how much of your time will be in classes and how much will be on your own.

What a week really looks like

The biggest surprise for new students is how little of the degree happens in the classroom. In New Zealand, one credit is designed around ten hours of learning. A 15-credit course therefore expects about 150 hours from you across the term, and class time is only a fraction of that.

The rest is yours to organise: reading, practising, working on assessments, meeting your group. Nobody checks that you did the reading, but everybody can tell in the next class when you didn't.

In my database course, for example, the students who do well are the ones who write SQL between classes, even ten minutes a day. The ones who wait for the next lecture to practise fall behind by week three, because each week builds on the last: tables, then queries, then joins, then design. A master's rewards steady weekly effort far more than a heroic week before a deadline.

A realistic plan for a full-time student: treat it like a full-time job. Block the hours in your calendar, including the independent ones, and protect them.

Assessment: projects, not exams

Many students arrive expecting big final exams, because that's how they were assessed before. In a lot of New Zealand master's programmes, and certainly in mine, most of the marks come from work you produce during the term:

• In information systems strategy, students write a strategic plan for a real organisation, working from case data.
• In database management, they design and build a working database, from the ER diagram to the SQL.
• In project management, they run a simulated project from start to finish: sprints, a risk register, stakeholder updates and a final report, with structured peer review along the way.

This changes how you should study. Memorising definitions won't carry you. What gets marks is applying ideas to a specific situation, justifying your choices, and showing your reasoning. When I mark a Scrum assignment, "Scrum has three accountabilities" is worth very little; explaining why the Product Owner, not the manager, should decide the order of the backlog in this case is where the marks are.

Read the marking rubric before you start, not after. It tells you exactly what the marker is looking for, and students who plan against it consistently do better than equally able students who don't.

The classroom culture shift

If you've studied somewhere with a more formal classroom, New Zealand can feel very relaxed at first. Most lecturers go by their first name. Classes are discussions as much as lectures. You're expected to ask questions, disagree politely, and bring your own experience into the conversation.

This isn't informality for its own sake. It's how you'll be assessed. Critical thinking, in practice, means comparing ideas, questioning assumptions (including the lecturer's), and reaching your own supported conclusion. Students who stay silent in class often write the same way: accurate summaries with no argument of their own.

My advice to anyone who finds this hard, and I did when I arrived: speak once in every class, even to ask a small question. It gets easier within a few weeks, and your lecturers will know who you are when you need help.

Academic writing and APA 7

Referencing is where capable students lose easy marks. Most New Zealand programmes in business, IT and the social sciences use APA 7th edition, and markers notice missing citations, inconsistent formats and reference lists that don't match the text.

The common mistakes I see every term:

• Paraphrasing a source closely without citing it, which counts as plagiarism even if you didn't mean it to.
• Citing a website's home page instead of the specific page or report.
• A reference list that includes sources never cited in the text, or misses ones that are.
• Leaning on one or two sources when the assignment asks you to compare several.

I built a free APA 7 crash course with a practice quiz for exactly this. Do it before your first assignment, not the night it's due.

Academic integrity and AI tools

Every institution takes academic integrity seriously, and generative AI has made the rules matter more, not less. Policies differ between institutions, and often between courses, so the only safe approach is to read the assessment instructions each time and ask your lecturer when anything is unclear.

In my own courses I use AI deliberately. In the strategy course, for instance, students work with a guided AI tool that walks them through strategic planning step by step, and they're asked to show how they used it and where they disagreed with it. What I'm assessing is their judgement, not the tool's output.

Three rules that will keep you safe almost anywhere: never submit AI-written text as your own words; declare how you used AI when the course allows it; and make sure you can explain every line of what you hand in, because in many courses you'll be asked to.

Group work in an international class

Master's classes in New Zealand are often very international. Across the cohorts I've taught, students have come from more than twenty countries, with different working styles, different expectations of the lecturer, and different ideas about who should speak first in a meeting.

That mix is one of the best things about studying here, and it's also where most group-work trouble starts. What works, from watching many groups over the years:

• Agree roles, deadlines and a meeting rhythm in the first week, in writing.
• Use a shared board or tracker, so progress is visible and nobody has to chase anyone.
• Raise problems early and with the group, not the day before submission.
• Assume good intent. Silence in a meeting often means someone is being polite, not that they have nothing to say. Ask them directly.

Employers here value exactly this: people who can deliver with a team from different backgrounds. The group project is practice for the job, so treat it that way.

Habits of students who do well

After many intakes, the pattern is clear. The students who finish strongly are rarely the ones who arrived with the best grades. They're the ones who build these habits early:

1. They turn up. In my experience, attendance and results go together more reliably than anything else.
2. They start assessments in week one, even if only to read the brief and the rubric.
3. They practise between classes: a query, a diagram, a paragraph, a little every day.
4. They ask for feedback on drafts while there's still time to use it.
5. They use office hours. Most students never do, which means the ones who do get real attention.
6. They reference as they write, not at the end.
7. They look after themselves. Sleep, food, friends and a bit of the outdoors do more for your grades than one more late night.
8. They build something to show. A working database, a project plan, a portfolio piece: evidence you can talk about in a job interview.

Choosing a programme: questions worth asking

Rankings and brochures tell you little about what the teaching is actually like. Before you commit to a master's anywhere in New Zealand, try to find out:

• How is each course assessed? Projects, exams, or a mix?
• Who teaches it? Are the lecturers active in industry or research in the field?
• Can you see real course material, such as a lesson, a reading list or a past assignment brief?
• How big are the classes, and how much contact will you have with lecturers?
• Is there a capstone, industry project or research component, and how is it supervised?
• What support is there for academic writing, and for students new to studying in English?

Good programmes are happy to answer these questions. If nobody can tell you how a course is assessed, that tells you something too.

Funding runs on its own clock. Several scholarships for study starting in 2027 close in October and November 2026, and almost all of them need an offer of place first. I've put every current deadline in one place: New Zealand scholarships 2027: deadlines Sri Lankans can't miss.

Try the lessons before you apply

The best way to know whether a subject suits you is to try it. The interactive lessons I use in class are free and open, with no login:

• Systems thinking and strategic planning: run a sales loop for twelve months and watch the obvious fix backfire.
• Introduction to databases and SQL programming: from your first table to your first query.
• The Scrum studio: watch a team build a parcel drone over three Sprints, in 3D.
• Predicting with data: three machine-learning models, explained without the maths.

There are 40 in total on the lessons page. If you enjoy two or three of them, you'll probably enjoy the degree.

Questions students ask me